RE: BootLoader

Simon — Fri, 11 Dec 2020 14:25:22 GMT

If you want to use the immutable bootloader, the simplest (and intended) approach is to simply set CONFIG_SECURE_BOOT=y in the prj.conf of your sample, e.g. zephyr/samples/hello_world/prj.conf. Then the generated build output for the bootloader should get placed into hello_world/<build folder>/bootloder/ (I think) and the file hello_world/<build folder>/zephyr/merged.hex contains both the application and the bootloader image. If you build it this way, all the partitions/memory placement and signing will get handled automatically and you don't have to do anything regarding this.

Try this and see if you're able to make it work. Check if you get the following log from the hello_world sample:

Attempting to boot from address 0x8000.

Verifying signature against key 0.

Signature verified.

Booting (0x8000).

If you for some reason want to build the immutable bootlader separately, please tell me and I can look into the issues you described in your initial post.

By the way, if you want to have the possibility to update your main application, you should use MCUBoot in addition, which can be done by setting CONFIG_BOOTLOADER_MCUBOOT=y in the prj.conf

Best regards,

Simon

RE: BootLoader

Flying Spaghetti Monsterism — Thu, 10 Dec 2020 12:32:48 GMT

By the way, I used NRF5340PDK PCA10095, version 0.8.0

Although I don't think it has anything to do with hardware