Cannot program WT51822-S4AT

[zolotiyeruki]

I'm trying use an nRF51 PDK to upload firmware (or, rather, just confirm that I can upload firmware) to one of these modules: www.wireless-tag.com/.../WT51822-S4AT.html

The target is externally powered, so I've connected it like so: Target Vcc -> P20 Pin 3 (VTG) Target SWDIO -> P20 Pin 4 (SWDIO) Target SWCLK -> P20 Pin 5 (SWCLK) Target GND -> P20 Pin 8 (Gnd Detect)

However, when I try to connect to the target using jlink.exe, I get a timeout error.

I hooked up an oscilloscope to the SWDIO and SWCLK lines (connected to the wires between the nRF51 PDK and the target module), and I see the signals changing, so it appears that at least the SEGGER bit is trying to connect.

I've seen a couple other users work with these modules, but I can't seem to have any success. Does anyone have any insights they could lend?

[endnode]

Is the module pre-programmed? Isn't it also lcoked from read-back which also should affect SWD interface? Why not use nrfjprog or nRFgo Studio instead of generix SEGGER J-Link SW?

[zolotiyeruki]

Yes, the module is pre-programmed, so read-back is probably locked. How would I go about doing a full erase? When I use nRFgo Studio and attempt to recover, it fails. Are there other pins which need to be connected in order to do a Recovery?

[endnode]

Not really, you just need to have SEGGER J-Link SWD PINs on flashing board (Dev Kit) correctly connected to detect the target. The best is to search the forum (there are several good Q&S on this topic) and try to target nRF5x chip on another Nordic Dev Kit or similar HW where you know this chip is OK (because you can flash/erase it by other means). The usual problem is with grounding both boards properly and connecting VTG and GND detect PINs on flashing board's P19 or P20 connector because otherwise SEGGER OB firmware will fail to notice that you want to flash external target.

Then simply look to nRF Tools guides on Nordic Infocenter.

[zolotiyeruki]

When I attempt to do a recover like so:

nrfjprog -f NRF51 --recover --log

I get the following:

Recovering device. This operation might take 30s.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

LED5 flashes rapidly for a while, then goes solid again. I also heard the "usb device unplugged" sound when LED5 goes solid again.

[zolotiyeruki]

Here's the log that comes out: log.log