How to erase a nrf51422 using JLink after flashing a softdevice

RE: How to erase a nrf51422 using JLink after flashing a softdevice

RK — Tue, 07 Oct 2014 07:12:10 GMT

Hmm - JLink works through the debug interface, it can basically read and write anything it wants to read and write. It is true that most of the scripts I've seen, and written, do erase the whole flash first because you may as well at that point.

I never by the way use that fully-qualified name on the device, just --device nrf51822, not that I remember now where on earth I got that from and Segger's list of devices has all the variants and not just the base 'nrf51822'

Certainly using what you have works so you may as well use what you have with the erase of the UICR. It's not like you have to change the softdevice very often anyway.

RE: How to erase a nrf51422 using JLink after flashing a softdevice

Torsten Robitzki — Tue, 07 Oct 2014 06:56:39 GMT

Hi RK, yes I was setting the device type. Programming a softdevice worked exactly once. After that, the UICR was set to read protect the lower flash and this causes the errors, because JLinkExe can not verify that the bin file content was correctly written.

RE: How to erase a nrf51422 using JLink after flashing a softdevice

RK — Tue, 07 Oct 2014 00:42:43 GMT

How are you calling JLinkExe? If you don't specify

--device nrf51822

on the JLinkExe command line, then you get errors much like that one.

RE: How to erase a nrf51422 using JLink after flashing a softdevice

Torsten Robitzki — Mon, 06 Oct 2014 09:47:50 GMT

I've came up with the followin solution:

halt
exec device = nRF51422_xxAA
w4 4001E504, 2
w4 4001e50C, 1
Sleep 100
r
q

Does this looks resonable?

Edit: Sorry, I've forgot to mention, that the sequence above erases the entire flash.