nRF52832 SDK 15.3 Secure UART Bootloader: errors when modifying original project

RE: nRF52832 SDK 15.3 Secure UART Bootloader: errors when modifying original project

Pierre B. — Tue, 26 Mar 2019 13:00:19 GMT

Thank you for your answers, adjusting IROM start address and size indeed made things better.

RE: nRF52832 SDK 15.3 Secure UART Bootloader: errors when modifying original project

Sigurd — Mon, 25 Mar 2019 17:03:04 GMT

Hi,

[quote user=""]- Where do those errors come from, why are they returned for such little modifications of the project, and how do I get rid of them ?[/quote]

Because the size of the bootloader code has increased with your changes, you need to adjust IROM settings for the project. If you need more space for the bootloader you can allocate more by reducing the start address (IROM start, and increase the size setting with the same amount). You can see an example on how this is done in the debug variant of the bootloader project.

[quote user=""]- In order to then flash the bootloader: I saw that the bootloader is now trying to write its start address into MBR, thus in SoftDevice memory region. Is the solution exposed in this thread (devzone.nordicsemi.com/.../177444) in order to correctly flash SoftDevice than bootloader still the best one ?[/quote]

Yes. See also this post.

[quote user=""]- In the serial secure UART bootloader example, is it possible to use UARTE instead of UART ?[/quote]

It's actually using UARTE by default. (NRF_DRV_UART_USE_UARTE -> true)

RE: nRF52832 SDK 15.3 Secure UART Bootloader: errors when modifying original project

Pierre B. — Thu, 21 Mar 2019 10:05:56 GMT

I am sorry, links seems to not be working. I will just quote here the part that interests me in particular :

"nrfjprog will have trouble writing to the MBR/Softdevice area. And if you use --sectorerase with nrjfprog it will erase the MBR make the chip firmware stops working. The workaround is to do an erase all, write the MBR/Softdevice and then flash the bootloader without sector erase."