nrfjprog failed to erase nRF52832 device

[snowuyl]

I would like to use nrfjprog to erase nRF52832 device. But it failed with "An unknown error". The nRF52832 device connect to laptop through J-Link USB interface.

D:\Nordic>nrfjprog --log --family nRF52 --eraseall
[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

[error]: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

[Amanda Hsieh]

Hi, 

I think you use a  j-link debugger to connect the custom board. If so, What j-link debugger are you using? 

-Amanda

[snowuyl]

Yes, I am using  j-link debugger to connect the custom board. After I change j-link debugger whose chip made by SEGGER, nrfjprog command works.

nrfjprog --family nRF52 --eraseall
Erasing user available code and UICR flash areas.
Applying system reset.

[Amanda Hsieh]

How do you get the RTT log in your other case?

-Amanda

[snowuyl]

RTT can connect to nRF52832 device after running application code but can't connect to nRF52832 device when running bootloader code.

[Amanda Hsieh]

In that case, you said

"I can see RTT log messages if I use nRF5_SDK_16.0.0\examples\dfu\secure_bootloader\pca10040_s132_ble_debug."

What did you change this time? 

-Amanda

[snowuyl]

I didn't chnage any thing. I just change using pca10040_s132_ble_debug instead pca10040_s132_ble. RTT can't connect to nRF52832 device occur when nRF52832 device is running bootloader code. But RTT can connect to nRF52832 device occur when nRF52832 device is running application code.

[Amanda Hsieh]

Hi,

snowuyl said:

I didn't chnage any thing. I just change using pca10040_s132_ble_debug instead pca10040_s132_ble. RTT can't connect to nRF52832 device occur when nRF52832 device is running bootloader code.

You would not get the RTT log if loading pca10040_s132_ble. Please make sure you are using pca10040_s132_ble_debug.

What image is running on the board?  Only the SD and pca10040_s132_ble_debug? Or SD+BL+APP?

-Amanda

[snowuyl]

SD+BL+APP

[Amanda Hsieh]

Hi, 

Have a look at the following posts:

 How to see LOG in Bootloader if app moves into bootloader ? 

 Easy way to merge bootloader and application RTT output  

 RE: Logs in Bootloader and Main Application 

Regards,
Amanda

[snowuyl]

Thanks for your reply!