Issue programming example on S132 SDK12/13 with PCA10040

[Dajgoro Labinac]

When I try to program an example with nRF go Studio from the new SDK12 or SDK13(fresh download) I get the following error:

It does not show up if I don't program the softdevice first, but then ble doesen't works. I also get an error in keil where it just says "Error: Flash Download failed - "Cortex-M4" ". I did not have such issues with the old SDK11.

Edit: Yes, I do erase all before writing.

[AmbystomaLabs]

You need to set the starting memory address IROM1 START in options for target. Most versions of the SoftDevice have different memory requirements. Your application needs to start after the SD. Review the release notes for your SD for the correct memory settings.

[Dajgoro Labinac]

Does that mean that I can't load the precompiled example on its own?

[AmbystomaLabs]

You can load the precompiled examples with the version of the SD that they were intended for.

However, most examples have precompiled hex images that include the SD already. You can tell which ones do since they include the SD type in the file name (eg, ble_app_beacon_s132_pca10040.hex). Also the files are rather big.

Since these already include the SD you just do an erase all and then load them as "application" in nRFgo Studio.

[AmbystomaLabs]

And, after looking at the file name in your error msg above, yes your hex image already includes the SD. Just erase all and load image as application. The segger will give you a virtual uart (com port). You will see it show up in your OS. I think you can configure the port number from nRFgo if you wish. Then you can use any terminal application or something else to move data to the connected blue tooth device. The mating smartphone app for the uart example, I think just gives you a terminal interface.

[Dajgoro Labinac]

Yes, I actually already did a custom pcb and firmware for it but using SDK11, and now I'm migrating it to the new SDK, but a lot things don't match with the new SDK and I keep running into things to patch.

[AmbystomaLabs]

Ok, make sure to review the API changes for your current sdk and softdevice. Also, some of the library files will change. Occasionally you can just modify your existing library files to move to a new SD. You really have to just read through the release notes to figure out what to change when moving through code versions. I have never found an easier way to do it. Even Android just gives me a bunch of compiler errors and deprecated notices when they update Android Studio. So Android OS isn't easier. Same too for iOS.