RE: nRF52832 PCA10040 armgcc application .ld RAM/FLASH

John — Wed, 01 Aug 2018 19:38:13 GMT

Thank you. I decided to take the ses option. It worked and the ble_app_blinky works with some log output I added and changed the button and led, so the problem is not with my changes but with the armgcc configuration. I installed the correct version of the gcc compiler (GCC ARM Embedded 6.3 2017-q2-update) but that didn't correct the problem. I will try some other examples to see if I can get the gcc version to work. I will use the ses IDE for now since I plan to stick with the nRF52 devices. My understanding is I can develop a commercial product with the nRF52 with the free version of ses.

RE: nRF52832 PCA10040 armgcc application .ld RAM/FLASH

bjorn-spockeli — Wed, 01 Aug 2018 11:33:13 GMT

Hi John

SDK v15.0.0 uses GCC ARM Embedded 6.3 2017-q2-update, see the nRF5 SDK v15.0.0 Release Notes, so I would recommend updating your GCC toolchain.

All the SDK examples should compile and work "out-of-the-box" with our development kits, so you should not have to modify the linker settings to get an unaltered example to run. I fyou have modified the example in such a way that the SoftDevice require more RAM, then the SoftDevice will return the new application ram start address the first time it calls sd_ble_enable(), this new start address is printed as log output. It is also possible to examine the returned value in a debug session.

Have you tried debugging the application using GDB or Segger Ozone and verified that the application is not asserting before the log output is printed? Alternatively, you could use Segger Embedded Studio (both IDE and debugger) instead of GCC as you get a free perpetual license when developing with nRF5x devices.

Best regards

Bjørn