Possibly, incorrect start address in HEX files in SDK for Mesh

RE: Possibly, incorrect start address in HEX files in SDK for Mesh

Vidar Berg — Wed, 04 Sep 2019 05:42:49 GMT

Thanks for the update. Hope the question gets answered on Launchpad.

RE: Possibly, incorrect start address in HEX files in SDK for Mesh

Geom — Tue, 03 Sep 2019 18:19:52 GMT

Thanks for your answer
It explained me many

I added a question in Launchpad GNU Arm Embedded Toolchain forum

RE: Possibly, incorrect start address in HEX files in SDK for Mesh

Vidar Berg — Tue, 03 Sep 2019 13:34:06 GMT

Hi,

The type 03 "Start Segment Address" record seems to be pointing to the reset vector (@0x26000 + 0x4) which holds the address of your reset handler plus the thumb bit, and the thumb bit explains why it's not word-aligned. But I'm not sure why objcpy is producing the "strange" byte order for this particular record type. It's probably correct but I couldn't find any specification to confirm it. Are you using any tools that use reads this record type, or are you just trying to understand the format? Either way, it will not affect program execution as the entry point is fixed on the ARM architecture.