Dear Nordic Team,
I am working on a custom board and I am currently implementing the firmware-over-the-air library via https.
For this I need to use the MCUBootloader. Unfortunately I ran into some troubles implementing the bootloader.
I am using Visual Studio in combination with the "nRF Connect for Desktop" and the SDK version 2.0.0.
To configure the bootloader I created a child_image folder in my project and in the folder I created a mcuboot.conf file like suggested in many of the Nordic devzone forum entries.
The changes in the mcuboot.conf are quite simple I changed the BOOT_SIGNATURE_TYPE to RSA and included a path for my key. Since I am working with a out-of-tree build I had to use a absolute file path for the key since otherwise the autogenerate file of the mcubootloader could not find the key file.
Furthermore I activated the bootbanner and told the bootloader to use RTT for the logging interface.
This seems to work fine when building the project and here is the bootloader logging information which I get:
But after that the nrf9160 does nothing and also does not start my application.
At the end I added the mcuboot.conf and the prj.conf files
I have searched through the forum and found some entries regarding the bootloader unfortunately none of the offered answeres helped in my case.
I have also tried to to a simple small sample to make sure my custom board is not the problem and used the tfm_hello_world sample and added
"CONFIG_BOOTLOADER_MCUBOOT=y" to the sample prj.conf. This seems to work fine so I am very sure the problem somehow originates either in my bootloader configuration or in my application itself.
I hope someone can help me with my problem.
Best regards,
Andreas
mcuboot.conf:
proj.conf: