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

MQTT_Simple zephyr.hex not offset correctly starts at 0x00000000 instead of 0x00040000

Hello,

I have cloned the latest master repos and I am using the command line to build, compile, and flash. I have successfully built and compiled the new MQTT_simple example. However, when I try to flash it I noticed that it overwrites secure_boot.  When I pull the MQTT_simple zephyr.hex file into the nRF_Connect programming utility together with the secure_boot zephyr.hex I noticed that the images overlap! 

I have included a snippet of the zephyr.lst for the mqtt_simple example.  As you can see, the text region starts at 0!  I have verified that the compiled dts file indicates it should go to x40000.

Please advise.

zephyr.lst:

Section Headers:
[Nr] Name Type Addr Off Size ES Flg Lk Inf Al
[ 0] NULL 00000000 000000 000000 00 0 0 0
[ 1] text PROGBITS 00000000 0000b4 000144 00 WAX 0 0 4
[ 2] _TEXT_SECTION_NAM PROGBITS 00000144 0001f8 0112b4 00 AX 0 0 4

nrf9160_pca10090ns.dts_compiled

chosen {
zephyr,console = "/soc/peripheral@40000000/uart@8000";
zephyr,shell-uart = "/soc/peripheral@40000000/uart@8000";
zephyr,flash = "/soc/peripheral@40000000/flash-controller@39000/flash@0";
zephyr,sram = "/memory@20020000";
zephyr,code-partition = "/soc/peripheral@40000000/flash-controller@39000/flash@0/partitions/partition@40000";
};

Overlapping images from nRF_Connect Programmer tool.

Parents Reply Children
No Data
Related