We couldn't flashing the hex file on a board.

[Jaehong Park]

We are under development on our custom board. then we suddenly were able to flashing the firmware, hex files onto our target board. SES showed the popup message such as " couldn't find JLINK ARM DLL.....". message. so we tried to flash the same firmware to another board and it succeed to flash on it. Here, we tried to flash the hex file on the problem-like board again using CLI command such as "nrfjprog --program ble_APMATE.hex --chiperase --log" so we got the log.log file with problem of flashing, attached below. please let us know the problem.

We were attaching the log.log file with some log.

log.log

 

2019-Apr-22 14:42:02  . . . . nRFXX_power_debug_and_system_regions:	JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.

2019-Apr-22 14:42:02  . . nRFXX_read_access_port_register_robust
2019-Apr-22 14:42:02  . . . nRFXX_read_access_port_register
2019-Apr-22 14:42:02  . . . . nRFXX_power_debug_and_system_regions
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register:	JLink:	JLINK_CORESIGHT_WriteAPDPReg(DP reg 0x02, 0x00000000)
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register:	JLink:	 >0x0D TIF>
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register:	JLink:	  returns -1
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register:	JLink:	 (0005ms, 2678ms total)  
2019-Apr-22 14:42:02  . . . . . nRFXX_write_debug_port_register:	JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.

[Håkon Alseth]

Hi,

 

Which programmer are you using? Have you tried to recover the board using "nrfjprog --recover -f nrf52"?

If you are using a nRF5x DK as an external programmer, it is important that your external board has the same voltage as the DK (3.3V). This also applies to debuggers such as the JLink Lite Cortex M, which only operates at a set voltage.

 

Kind regards,

Håkon

[Jaehong Park]

I used SES as a programmer. SES showd the popup message like below capture screen on SES. and it's useless even if I tried to recover the board using "nrfjprog --recover -f nrf52".

[Håkon Alseth]

Hi,

 

Your logs and the screenshot indicate that the debugger is not able to get any communication with the nRF. This might be due to many reasons, such as bad connection / cable, low VDD voltage, etc.

What programmer are you using? Are you programming a nRF-DK or a custom board?

 

Kind regards,

Håkon

[Jaehong Park]

We have used our custom board and I tired to test another board with the same schematic and it's good to flash images. In fact, the problematic board was suddenly the trouble after we used to flash images or binary to the problematic board for a while. I didn't know what I did it on the problematic board. suddenly, the problem occurred to the board. In short, it's good to flash hex to another board with same schematic.

The problem is why this board only have a trouble.

[Håkon Alseth]

If it is used for development purposes, it might be that you are in an assert loop. The default behavior for assertions is to reset, so if the assert occurs early in the program, your board is in a reset-loop. This can be difficult to recover from. If you want to investigate further, you can try this batch file posted here:

https://devzone.nordicsemi.com/f/nordic-q-a/45078/nrf52832-not-connected-anymore-after-first-trying-to-debug-keil/177579#177579

Run this while power-cycling the nRF, and see if it recovers successfully after a while.

 

Kind regards,

Håkon