How to update softdevice via SPI in nRF52832

RE: How to update softdevice via SPI in nRF52832

Vidar Berg — Fri, 29 Apr 2022 10:45:51 GMT

Hi,

OK, the entry point after reset is always at address 0x0 so an update of the bootloader will have a critical window where a reset will brick device.

Have you checked that flash protection is not enabled for the bootloader (BPROT — Block protection) and that interrupts are not forwarded via the bootloader but directly to APP1/APP2 by using the VTOR register?

RE: How to update softdevice via SPI in nRF52832

ChenC Tai — Fri, 29 Apr 2022 10:07:36 GMT

Hi,

Our bootloader is put at 0x00000000, and occupy 2 pages (8KB), it will help to jump to APP1 / APP2.

But we found we cannot update bootloader by APP1 / APP2,

When APP1/ APP2 try to erase 0x00000000, the NRF52832 crashed.

RE: How to update softdevice via SPI in nRF52832

Vidar Berg — Thu, 28 Apr 2022 09:09:47 GMT

Hi,

What does your memory layout look like now? Is it the bootloader that starts at address 0x0?

RE: How to update softdevice via SPI in nRF52832

ChenC Tai — Thu, 28 Apr 2022 03:57:13 GMT

Hi,

Thanks. In our test, if we tried to erase memory address 0x00 and start write MBR data, but happened hard fault. Do you have any suggestion for this issue?

Thanks,

ChenC

RE: How to update softdevice via SPI in nRF52832

Vidar Berg — Wed, 27 Apr 2022 09:21:02 GMT

Hi,

I think you should be able to update the Softdevice along with the application over SPI provided your existing SPI bootloader doesn't overlap with the Softdevice in flash.The Softdevice+MBR is not relocatable and must therefore always start at address 0x0.

Memory layout used with the nRF5 SDK bootloader for comparison:

Best regards,

Vidar