RE: arm-none-eabi-objcopy generates different hex files

Sigurd — Mon, 20 Jan 2025 14:23:48 GMT

Hi!
Try

--change-start or

--change-addresses

RE: arm-none-eabi-objcopy generates different hex files

Constantin — Wed, 15 Jan 2025 20:41:22 GMT

Okay I see. How do I tell objcpy about the offset?

RE: arm-none-eabi-objcopy generates different hex files

Jørgen Holmefjord — Mon, 06 Jan 2025 16:42:17 GMT

Hi,

Can you elaborate on which parts of the hex-files are different between the commands? .bin files does not contain any information about memory offsets, in comparison to ihex format. If your application is based on nRF5 SDK examples and using a softdevice, the application is typically offset to make room for the softdevice in start of flash. If you don't tell objcopy about the offset, it will likely just place code at the start of the bin file, and then the placement information is lost when converting from bin to ihex.

I tested your commands on my end, and the only difference I can see is that the first line (offset) is removed, and the checksums are different.

Best regards,
Jørgen