DFU from SD130 v1.0.0 to SD130 v2.0.3 on nRF51822 with CLENR0 set

RE: DFU from SD130 v1.0.0 to SD130 v2.0.3 on nRF51822 with CLENR0 set

Hung Bui — Tue, 26 Jun 2018 15:53:21 GMT

Hi Will,

Thanks for sharing the solution. I was thinking the size of the S130 v2 should be bigger than S130 v1.x. But it's the opposite. Your solution looks good.

RE: DFU from SD130 v1.0.0 to SD130 v2.0.3 on nRF51822 with CLENR0 set

Hung Bui — Tue, 26 Jun 2018 15:45:24 GMT

Hi Will,

Using the softdevice with the CLENR0 pointing to the middle of the softdevice is not recommended. If you have read back protection of the code region 0, code in code region 1 won't be able to read the code in region 0.

But if you don't have read back protection, I think it should still work. S130 and the bootloader in SDK v12 doesn't use CLENR0 to jump to the bootloader.

What you would need to test is to test the application first, just test it the new softdevice and the chip with wrong CLENR0 , no bootloader, to see if it can operate.

Then you can try to test with the bootloader. If you still have the issue, you would need to check what doesn't work. If it stuck at the bootloader, or it crash when in the application, or if it's the softdevice doesn't function properly.

You can also test to update a very simple application, just blinking an LED, to make sure the bootloader can receive the image and switch to the application.

RE: DFU from SD130 v1.0.0 to SD130 v2.0.3 on nRF51822 with CLENR0 set

Will Dimmit — Tue, 26 Jun 2018 15:45:05 GMT

To anyone else who runs across this; it can be done, but it requires:

Relocating the application to 0x1c000 from the default 0x1b000
Redefining MAIN_APPLICATION_START_ADDR to 0x1c000
Redefining CODE_REGION_1_START to 0x1c000

With these changes, DFU works normally - you just lose those pages of flash between 0x1b000 and 0x1c000.

Cheers,

Will

RE: DFU from SD130 v1.0.0 to SD130 v2.0.3 on nRF51822 with CLENR0 set

Will Dimmit — Mon, 25 Jun 2018 17:38:07 GMT

*Should be SD130 v2.0.1 in the above description