RE: dfu from sd132v2.0.1 to s132v3.0.0 got NO bootup

Hung Bui — Mon, 28 Nov 2016 09:05:41 GMT

@Enfl: Please open a new case and describe what you observed.

RE: dfu from sd132v2.0.1 to s132v3.0.0 got NO bootup

Enfl_JWT — Fri, 25 Nov 2016 22:40:28 GMT

I am still unable to update even after this patch devzone.nordicsemi.com/.../

RE: dfu from sd132v2.0.1 to s132v3.0.0 got NO bootup

jasonbu — Tue, 16 Aug 2016 14:07:40 GMT

It worked tks~!

RE: dfu from sd132v2.0.1 to s132v3.0.0 got NO bootup

Hung Bui — Tue, 16 Aug 2016 12:58:58 GMT

Hi Jasonbu,

We have been aware of this issue.

It was due to a bug with the bootloader that the blocksize was not adapted to meet with the new block size on the nRF52 (4KB instead of 1 KB). This caused about 2KB of code erased inside the softdevice when swapping softdevice as you noticed.

I attached here the bug fix, you would need to use this fix for both the bootloader for S132v2.0 and the to-be-updated bootloader for S132v3.0.

If you already have your devices deployed and can't flash the new bootloader for S132v2.0 you would need to do a DFU first to update this bootloader before you update the new softdevice+bootloader+application.

I also noticed that the HRM example you sent was not updated to work on S132v3.0 the RAM and ROM setting was not updated. Maybe it was it's not saved after your modification.

dfu_dual_bank_with_fix.c