JLink communication time out

[AndrewCichy]

I have been using an nRF52840 dev board and a nRF5340 dev board to program Bluetooth demos. Just today my nRF52840 board became very difficult to flash I get the error, 

-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: c:\nordic\myApps\central_fragmenter\build_nRF52840\zephyr\zephyr.hex
[ #################### ] 6.508s | Erase file - Done erasing
[error] [ JLink] - Communication timed out: Requested 4 bytes, received 0 bytes !
[error] [ Client] - Encountered error -105: Command program_file executed for 5984 milliseconds with result -105
[error] [ nRF52] - Failed while performing 'Write' operation on target address 0x00000000.
-105: Failed to read access port 1 register 3.
This indicates that the debug port is available, but the access port is not.
An unknown error.
[error] [ nRF52] - Failed while reading device information.
[error] [ Worker] - Failed to read access port 1 register 3.
This indicates that the debug port is available, but the access port is not.
An unknown error.
ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 35: nrfjprog --program 'c:\nordic\myApps\central_fragmenter\build_nRF52840\zephyr\zephyr.hex' --sectoranduicrerase --verify -f NRF52 --snr 1050237320

I get this error roughly 90% of the time when attempting to flash an application to the board. There does not seem to be any rhyme or reason as to why the board fails to flash the application. I have tried to use the nrfjprog --recover command and this does not seem to improve the rate of failure. I reran the command with the --log option aswell and have attached the log. Additionally I have attached the log from running nrfjprog -f NRF52 -r --log.

The nRF5340 does not experience this issue. 

For reference, my toolchain is v2.7.0, and my SDK is v2.6.1

program log output:
program.log

nrfjprog -f NRF52 -r --log output:

nrf52.log

[Jared]

Hi,

Thank you for the clear description of your problem. 

• Have you checked that the USB port hasn't been physically damaged and that the USB header is still firmly connected to the solder pads? It hasn't been loosened, has it? Sometimes this can happen if the USB cable is bent while it's inserted into the DK?
• Can you go through the steps here and see if any of them fixed your issue?
• What voltage do you measure on RESET, GND, and VDD?
• Can you share a picture of your board that shows the sticker with version number?

regards
Jared 

[AndrewCichy]

The USB port does not seem damaged. I used a new cable, I don't have a different computer to try flashing with. I don't have a volt meter to measure the voltage currently but I can get one next week. The board was working better for a couple days when I used an additional USB connected to power, but now the board will no longer flash an application. I have replaced the coin cell battery and that did not improve things.