dfu\secure_bootloader

[xixili]

nRF5_SDK_17.0.2_d674dde\examples\dfu\secure_bootloader\pca10056_ble\arm5_no_packs

Why the compiled hex file is different from before, and the code is not modified

[Einar Thorsrud]

Hi,

If you compile the bootloader example with the exact same code (no changes in any SDK files that are used) and with the exact same toolchain version you will get the same hex file. You can verify this by for instance comparing the md5 sum of the two files. If there are any changes what so ever, for instance differences in toolchain version, the files will be different. Also if you have added things like a build time string to the bootloader, that would cause a different hex even if the code and toolchain remain the same.

[xixili]

I think it’s a toolchain version issue. Which version are you testing?

[Einar Thorsrud]

I tested with keil uVision 5.26.2.0. I would expect that this would be the same regardless of which version you use though, as long as you use the same when building both the old and new hex.