This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

IoT SDK VS nRF51 SDK

I am trying to get this working with GCC, and I use github.com/.../nrf51-pure-gcc-setup as a base.

I am not too sure how all this works together but:

  1. Can these SDKs be merged into one directory? They seem to share a lot of the same code.
  2. Does the IoT SDK support things like SPI, analog reading, or do I have to merge the SDKs?
  3. Does the IoT SDK support over the air firmware updates, or do I have to merge the SDKs?

Thanks!

Update: I am using the IoT SDK alone for now, but I came across issues with pure-gcc setup:

It compiles all files which makes it impossible to link ble_6lowpan which is necessary. Also I get "region RAM overflowed with stack".

Which LD file do I use? gcc_nrf51_s1xx_iot_xxaa, gcc_nrf51_s1xx_iot_xxab or gcc_nrf51_s1xx_iot_xxac? I have the NRF51-DK.

Parents
  • The github example you refer to was written when the SDK did not contain any or had poor gcc support and makefiles, and is no longer maintained. The recent SDK versions, including the IoT SDK, all have gcc support and makefiles in each of the examples. I think you are better of using these files as a base.

    Which LD file to use depends on the SD version you use and the chip revision. If you have the newest nRF51-DK you have the nRF51422_qfac chip, and together with the IoT SD you should then choose gcc_nrf51_s1xx_iot_xxac.ld

  • Thanks!!! I have already moved to the makefiles in the SDK.

    One more small question. I am trying to incorporate math in the linking process for main.c but it seems difficult the way they are made. -lm after $(CC) doesn't seem to have any effect, neither does it work in $(LDFLAGS)

Reply Children
No Data
Related