[nRF52832]Was it broken?

[Daisuke____]

I use rRF52832.
After doing "Flash Tab -> Erase" of Keil's development environment, it became impossible to connect at all.
I tried using nRF 5x Command Line Tools (nrfjprog.exe), but the following log will appear and an error will result.
Was it broken?
Please help me!

--------------------------------------------------------------------------------
nrfjprog.exe --eraseall --jdll JLinkARM.dll --log
nrfjprog verion 9.7.2
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.
--------------------------------------------------------------------------------
nrfjprog.exe --recover --jdll JLinkARM.dll --log
nrfjprog verion 9.7.2
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.

[Vidar Berg]

Hi,

The erase all function in Keil should not cause this. Does the device show up as a mass storage device named "JLINK" after you plug-in the USB cable, or does it show up as something else? Reason I ask is that it is possible to erase the JLINK fw on the on-board programmer, and then it wouldn't show up as a jlink device.  

 

[Daisuke____]

thank you for your answer

When you insert the debugger into the USB, it will be displayed as a JLINK device.
The debugger is the same, and it connects to another nRF 52832 and it works normally.

Is there anything you need about pin processing of nRF 52832?

[Vidar Berg]

Just to make sure I understand this correctly (please correct me if I'm wrong), you are able to program external boards with the on-board programmer, but not the 52832 on the 52 DK? Maybe you can take a picture of your setup? 

[Daisuke____]

I am using BTS - 04 made by SMK using nRF 52832.
SLWSTK 6101 A made by SILICON LABS is used as the debugger.

A picture of the peripheral circuit of the BLE module is attached.

[Vidar Berg]

Ok, I assumed you were using the nRF52DK, which as an on-board J-link programmer (can also be used to program external board with nordic ICs). I tried googling SLWSTK 6101, but couldn't find it. Note that nrfjprog only works with j-link programmers. 

[Daisuke____]

Information on SLWSTK 6101 A is available at the following site

https://www.silabs.com/documents/login/user-guides/ug122-brd4300a-user-guide.pdf

It operates as JLINK and can write to another board.

[Vidar Berg]

Please make sure that you have common ground between the programmer and the 52 module. Also, have you connected VTARGET to the module? The programmer uses VTARGET to determine the voltage on the target.