How to troubleshoot and diagnose J-Link connection and USB DK board power-on errors.

hi all,

Hello, my board(nrf5340 dk,pca10095,0.11.0,2020.45 and  nrf52840 dk ,pca10056,1.0.0) often encounters the issue of "J-Link not found" (no LED(LED3)/USB not mounted).

Alternatively, it initially works 

correctly for debugging and programming, but after some time(random), it disconnects((To restore the connection, try unplugging and plugging the USB cable repeatedly.), and the LED either does not light up or flashes slowly. Additionally, when programming sample code that requires higher current or  the LED to light up, there is a slight Electric current sound coming from the USB or power source.

jlink error:

error message:

Flashing build to 960172161
C:\Windows\system32\cmd.exe /d /s /c "west flash -d c:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build --skip-rebuild --dev-id 960172161"

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build\zephyr\merged_domains.hex
-- runners.nrfjprog: c:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: c:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and c:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ ###### ] 0.000s | Erase file - Check image [ ##### ] 0.000s | Check image validity - Initialize device info [ ########## ] 0.000s | Check image validity - Check region 0 settings [ ############### ] 0.000s | Check image validity - block 1 of 2 [ #################### ] 0.175s | Check image validity - Finished [ ############# ] 0.000s | Erase file - Erasing [ ########## ] 0.000s | Erasing non-volatile memory - block 1 of 1 [ #################### ] 0.000s | Erasing non-volatile memory - Erase successful [ #################### ] 12.375s | Erase file - Done erasing
[ ###### ] 0.000s | Program file - Checking image [ ##### ] 0.000s | Check image validity - Initialize device info [ ########## ] 0.000s | Check image validity - Check region 0 settings [ ############### ] 4.221s | Check image validity - block 1 of 2 [ #################### ] 0.048s | Check image validity - Finished [ ############# ] 0.000s | Program file - Programming [ ########## ] 0.000s | Programming image - block 1 of 1 [ #################### ] 0.000s | Programming image - Write successful [ #################### ] 1.312s | Program file - Done programming
[ ###### ] 0.000s | Verify file - Check image [ ##### ] 0.000s | Check image validity - Initialize device info [ ########## ] 0.000s | Check image validity - Check region 0 settings [ ############### ] 4.712s | Check image validity - block 1 of 2 [ #################### ] 0.047s | Check image validity - Finished [ ############# ] 0.000s | Verify file - Verifying [ ########## ] 0.000s | Verifying image - block 1 of 1 [error] [ Client] - Encountered error -105: Command verify_file executed for 155 milliseconds with result -105
[error] [ JLink] - Communication timed out: Requested 8196 bytes, received 0 bytes !
[error] [ nRF53] - Failed while performing 'Verify' operation on target address 0x01000000.
-105: An unknown error.
[error] [ nRF53] - Failed while verifying device. -105: An unknown error.
[error] [ Worker] - 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:\Users\steve\nordic\bt-fund-1\lesson3\blefund_less3_exer2\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex' --sectorerase --verify -f NRF53 --coprocessor CP_NETWORK --snr 960172161

* The terminal process terminated with exit code: 35.
* Terminal will be reused by tasks, press any key to close it.

Parents
  • Hello,

    This doesn't sounds good at all, the DK should be drawing in the tens of mA, this should not cause any USB power issues.

    Do you have a second DK for comparison, have you measured the current drawn, I recommend to order yourself a new DK.

    Edit: I can see you are using a preview kit (v0.11.0), please get a new one.

    Kenneth

  • HI nordic,

    Thanks for your response.
    In addition, I have another version of nrf52840 pca10056,1.1.0 dk which also has problems.
    The following is the comparison (TP, test pin,A is normal; B is  abnormal)

    A                                               ----------------      B
    ------------------------------------------------------------------------------------------------------
    3.0v                                            TP29             2.8v

    ------------------------------------------------------------------------------------------------------


    3.0/4.6v                                     TP30/TP32    0.5/4.9v

    ------------------------------------------------------------------------------------------------------

    4.9v                                           TP36               4.9v

    ------------------------------------------------------------------------------------------------------

    2.8v                                           TP35              0.0v

    ------------------------------------------------------------------------------------------------------

    1.4v                                           TP34              0.4v

  • We are not aware of any issues, but recommend to take some ESD precautions when handling the kits. There should be a date code printed on the label also, I believe the v1.1.0 kit must be from 2019 or older? There will be some wear and tear when used for development for many years.

    Kenneth

Reply Children
No Data
Related