- 21 Mar, 2017 1 commit
-
-
Alexander Alashkin authored
PUBLISHED_FROM=2babde0d0c6add14aa500f4bf1c833715d979c6c
-
- 08 Feb, 2017 1 commit
-
-
Dmitry Frank authored
And also fix `flash` target for nrf51 PUBLISHED_FROM=decc6242380eb7070bfbcb26c57780e756588cc3
-
- 06 Feb, 2017 1 commit
-
-
Alexander Alashkin authored
This reverts commit 1a17e17c462bdd4e1d26d8742f8b7087273e04c2. PUBLISHED_FROM=80028de308c9a021955d1425d2bfee8feb85f193
-
- 03 Feb, 2017 1 commit
-
-
Alexander Alashkin authored
-
- 23 Nov, 2016 1 commit
-
-
Marko Mikulicic authored
PUBLISHED_FROM=ea64670e42ae58bbe26abee5d928f2afcd83bd46
-
- 04 Nov, 2016 3 commits
-
-
Dmitry Frank authored
Now all warnings are disabled on SDK files, and enabled on our application's files. Fixed a couple of things in nRF52 which were unnoticed because all warnings were disabled there from the beginning. PUBLISHED_FROM=a33ab22d0ce85efea364b80478986b88f4b0a3a2
-
Dmitry Frank authored
PUBLISHED_FROM=f8b4e8650d72c2ec5525e0510fbc8a80f8645a14
-
Dmitry Frank authored
Unfortunately it turns out Nordic's examples were able to build with GCC just because they suppressed all warnings; I had to do the same here because there are some macro redefinitions of arm-none-eabi-gcc and lwip. TODO: resolve that and do not suppress warnings. PUBLISHED_FROM=e65c7b0f2451f85765d958d7f67eb9262f7bc929
-
- 03 Nov, 2016 1 commit
-
-
Dmitry Frank authored
Now it works in hardware. PUBLISHED_FROM=f223bde2d2bebe97513ce073eb887552bc3d93af
-
- 28 Oct, 2016 1 commit
-
-
Dmitry Frank authored
PUBLISHED_FROM=6af3ed56802d2619f673c36059370440a0c06397
-