DFU on nRF51422 rev.2

[PW]

I try to make bootloader via USART for my application. I'm using: nRF51422rev.2, SDK6.1.0, S210 ver3.0.0. KEIL5.11. I did everything like describes in post here: devzone.nordicsemi.com/.../

I uploaded SD via nRFgo Studio and my bootloader via ULINK and KEIL. While programming, KEIL return: "No Algorithm found for: 10001014H - 10001017H". So, if this register is not available on nRF51422rev.2, is it possible to make bootloader for chip rev.2 using examples from SDK7.0.1 or higher?

PW

[Hung Bui]

Hi PW,

You have that issue because in DFU bootloader we don't use KEIL programmer to program, but we use nrfjprog.exe to program the chip. The default KEIL programmer doesn't program UICR.

You can have a look at the stock DFU bootloader example , Project Option -> Utilities -> Use External Tool for Flash Programming.

You can also have a look at this case.

[PW]

What about UICR.BOOTLOADERADDR. According to nRF51_Series_RM_ver.2.1 there is no such of register. So I wonder, will examples I mentioned above work with chip rev.2?

[Hung Bui]

@PW: Yes it should work. The register is just what we defined and used for the MBR and the bootloader. It's not really defined in the hardware itself.

[PW]

I changed in your example: #define BOOTLOADER_REGION_START 0x0003B800 and it "almost" works. When I call ble_stack_init(bool init_softdevice), it return: NRF_ERROR_SVC_HANDLER_MISSING after err_code = sd_mbr_command(&com); How does it work exactly? When button is high level hen chip is starting, shouldn't jump to my app?

PW

[Hung Bui]

@PW: I assume that you have updated the IROM1 start address of the bootloader project to 0x3B800 as well. The reason you received NRF_ERROR_SVC_HANDLER_MISSING was because there was no MBR on the S210 v3.0.0. So there is no sd_mbr_command() in the Softdevice. It is implemented from S210 v4.0.0 (see the release note).

So you have 2 options:

• Update API header to S210 v4.0.0
• Use the bootloader from SDK v6.0 (application update only )