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

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

Håkon Alseth — Thu, 25 Apr 2019 13:06:25 GMT

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

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

Jaehong Park — Thu, 25 Apr 2019 08:18:39 GMT

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.

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

Håkon Alseth — Thu, 25 Apr 2019 08:03:28 GMT

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

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

Jaehong Park — Thu, 25 Apr 2019 05:21:27 GMT

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".

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

Håkon Alseth — Tue, 23 Apr 2019 08:09:12 GMT

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