mqtt_simple programmed to wrong address range 00008000 -- 00020abb

RE: mqtt_simple programmed to wrong address range 00008000 -- 00020abb

GJSea — Sun, 19 May 2019 06:46:57 GMT

Hi Martin Lesund thanks this worked for me too.

What is the proper procedure for debugging in this current state of SES/NCS disparity?After I do the Download File step per above the, I initiate Debug..Go then SES proceeds to flash the firmware again (in the wrong location 0x00008000) but somehow debugging magically works. Can I assume the Debug..Go flash isn't affecting the location of the first flash and attaching the debug session in the correct location?

Thx!

RE: mqtt_simple programmed to wrong address range 00008000 -- 00020abb

Martin Lesund — Wed, 08 May 2019 11:03:41 GMT

The same would apply for the mqtt_simple sample or any other samples/applications in NCS for that matter.

Just change the folder paths and samples to what suits your use case.

RE: mqtt_simple programmed to wrong address range 00008000 -- 00020abb

JNair — Wed, 08 May 2019 09:44:49 GMT

Hi Martin,

Thanks for the answer. I just had a query that should i need to follow these steps only while building programs in applications folder like asset tracker or also for projects in samples folder like mqtt_simple also?

RE: mqtt_simple programmed to wrong address range 00008000 -- 00020abb

Martin Lesund — Wed, 08 May 2019 08:20:28 GMT

Hello JNair,

The current version of SES (v4.16) does not take into account an updated feature which has been introduced in NCS.

Basically when building the application it will also build the "Secure Partition Manager" (spm) [earlier known as "Secure_boot"] and then merging those two together for your convenience.

So you need to manually select this "merged.hex" file when you want to flash the application to the nRF91.

Here is a quick guide on how this is done:

Build solution as normal

See that the output shows it has made a “merged.hex” file (which will consist of your application and the “spm”)

Then make sure your nRF91DK is powered ON and then “connect J-Link”:

And then manually choose the correct “merged.hex” file to be flashed to the kit:

It is located in the applications build folder under zephyr:

Then it will be flashed to your kit and you should see “Download Successful” in the Output:

Best Regards,
Martin L.