JLinkGDBServer log errors JLINK_HasError()

[billyhw]

I have a custom board with NRF52833 that I'm unable to flash or communicate with using JLinkGDBServer. I was hoping for some help understanding the errors seen in this log as clues to why the device will no longer respond.

The first error appears after a "JLINK_GetHWStatus(...)" returns 0. Which is confusing because I'm used to return 0 being ok...

Anyhow I'm able to flash another identical board, so I believe there could be some damage to the one that is not responding but I'm just trying to get more clues as to what is wrong. Any help appreciated.  Thanks!

SEGGER J-Link GDB Server V7.60a LogFile
Logging started @ 2022-01-19 23:23
03-00000000-00-00000000-001F: SEGGER J-Link GDB Server V7.60a
03-00000000-00-00000000-000E:  GUI Version


03-00000000-00-00000000-0039: JLinkARM.dll V7.60a (DLL compiled Dec 16 2021 10:39:12)


03-00000000-00-00000000-01AC: -----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      yes
Generate logfile:              on
Verify download:               off
Init regs on start:            off
Silent mode:                   off
Single run mode:               off
Target connection timeout:     5000 ms

03-00000000-00-00000000-0150: ------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 nRF52833_xxAA
Target interface:              SWD
Target interface speed:        1000kHz
Target endian:                 little

03-00000000-00-00000000-0001: 

03-00000000-00-00000001-0018: Connecting to J-Link...

02-00000000-00-00000008-005C: T2BC8 000:008.903   Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Dec  3 2021 15:41:28
02-00000000-00-00000009-005C: T2BC8 000:009.624   Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Dec  3 2021 15:41:28
02-00000000-00-00000013-0023: T2BC8 000:013.467   Hardware: V1.00
02-00000000-00-00000013-0022: T2BC8 000:013.513   S/N: 685297863
02-00000000-00-00000013-001F: T2BC8 000:013.525   OEM: SEGGER
02-00000000-00-00000013-0042: T2BC8 000:013.536   Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
02-00000000-00-00000016-003F: T2BC8 000:016.203   TELNET listener socket opened on port 19021
02-00000000-00-00000017-0046: T2BC8 000:016.745   WEBSRV WEBSRV_Init(): Starting webserver thread(s)
02-00000000-00-00000017-0040: T2BC8 000:017.066   WEBSRV Webserver running on local port 19080
02-00000000-00-00000045-002B: T2BC8 000:045.389 - 44.314ms returns "O.K."
03-00000000-00-00000045-0015: J-Link is connected.

02-00000000-00-00000045-0044: T2BC8 000:045.633 JLINK_ExecCommand("device = nRF52833_xxAA", ...). 
02-00000000-00-00000058-0055: T2BC8 000:057.645   XML file found at: C:\Program Files\SEGGER\JLink\JLinkDevices.xml
02-00000000-00-00000058-005A: T2BC8 000:058.246   C:\Program Files\SEGGER\JLink\JLinkDevices.xml evaluated successfully.
02-00000000-00-00000088-0034: T2BC8 000:088.294   Device "NRF52833_XXAA" selected.
02-00000000-00-00000089-0029: T2BC8 000:089.186 - 43.532ms returns 0x00
02-00000000-00-00000089-002E: T2BC8 000:089.223 JLINK_GetFirmwareString(...)
02-00000000-00-00000089-001B: T2BC8 000:089.232 - 0.010ms
03-00000000-00-00000089-0049: Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Dec  3 2021 15:41:28

02-00000000-00-00000089-002C: T2BC8 000:089.287 JLINK_GetHardwareVersion()
02-00000000-00-00000089-0029: T2BC8 000:089.299 - 0.012ms returns 10000
03-00000000-00-00000089-0010: Hardware: V1.00

02-00000000-00-00000089-001F: T2BC8 000:089.328 JLINK_GetSN()
02-00000000-00-00000089-002D: T2BC8 000:089.341 - 0.012ms returns 685297863
02-00000000-00-00000089-0029: T2BC8 000:089.353 JLINK_GetOEMString(...)
03-00000000-00-00000089-000F: S/N: 685297863

03-00000000-00-00000090-002F: Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB

02-00000000-00-00000090-0028: T2BC8 000:089.821 JLINK_GetHWStatus(...)
02-00000000-00-00000090-0025: T2BC8 000:090.343 - 0.524ms returns 0
02-00000000-00-00000090-0029: T2BC8 000:090.371 JLINK_EnableSoftBPs(ON)
02-00000000-00-00000090-001B: T2BC8 000:090.383 - 0.012ms
03-00000000-00-00000090-001B: Checking target voltage...

03-00000000-00-00000090-0017: Target voltage: 3.30 V

03-00000000-00-00000091-001E: Listening on TCP/IP port 2331

03-00000000-00-00000091-0018: Connecting to target...

02-00000000-00-00000091-0022: T2BC8 000:090.650 JLINK_ClrError()
02-00000000-00-00000091-001B: T2BC8 000:090.667 - 0.018ms
02-00000000-00-00000091-0028: T2BC8 000:090.680 JLINK_GetHWStatus(...)
02-00000000-00-00000091-0025: T2BC8 000:091.095 - 0.419ms returns 0
02-00000000-00-00000091-0022: T2BC8 000:091.136 JLINK_HasError()
02-00000000-00-00000091-0034: T2BC8 000:091.158 JLINK_TIF_Select(JLINKARM_TIF_SWD)
02-00000000-00-00000093-0028: T2BC8 000:093.184 - 2.033ms returns 0x00
02-00000000-00-00000093-0026: T2BC8 000:093.244 JLINK_SetSpeed(1000)
02-00000000-00-00000094-001B: T2BC8 000:093.551 - 0.310ms
02-00000000-00-00000094-0022: T2BC8 000:093.590 JLINK_GetSpeed()
02-00000000-00-00000094-0028: T2BC8 000:093.608 - 0.018ms returns 1000
02-00000000-00-00000094-0040: T2BC8 000:093.627 JLINK_SetResetType(JLINKARM_RESET_TYPE_NORMAL)
02-00000000-00-00000094-003E: T2BC8 000:093.645 - 0.018ms returns JLINKARM_RESET_TYPE_NORMAL
02-00000000-00-00000094-0028: T2BC8 000:093.663 JLINK_SetResetDelay(0)
02-00000000-00-00000094-001B: T2BC8 000:093.680 - 0.017ms
02-00000000-00-00000094-0034: T2BC8 000:093.698 JLINK_SetEndian(ARM_ENDIAN_LITTLE)
02-00000000-00-00000094-0025: T2BC8 000:093.715 - 0.017ms returns 0
02-00000000-00-00000094-0022: T2BC8 000:093.733 JLINK_HasError()
02-00000000-00-00000094-0021: T2BC8 000:093.752 JLINK_Connect()
02-00000000-00-00000094-0026: T2BC8 000:094.249   InitTarget() start
02-00000000-00-00000094-003F: T2BC8 000:094.283    J-Link Script File: Executing InitTarget()
02-00000000-00-00000206-0024: T2BC8 000:205.915   InitTarget() end
02-00000000-00-00000377-0026: T2BC8 000:377.076   InitTarget() start
02-00000000-00-00000377-003F: T2BC8 000:377.144    J-Link Script File: Executing InitTarget()
02-00000000-00-00000489-0024: T2BC8 000:488.788   InitTarget() end
02-00000000-00-00000597-0030: T2BC8 000:597.309 - 503.574ms returns 0xFFFFFFFF
02-00000000-00-00000597-0022: T2BC8 000:597.422 JLINK_HasError()
03-00000000-00-00000597-0024: ERROR: Could not connect to target.

03-00000000-00-00000597-0035: Target connection failed. GDBServer will be closed...
02-00000000-00-00002207-0028: T5098 002:206.782 JLINK_GetHWStatus(...)
02-00000000-00-00002207-0025: T5098 002:207.385 - 0.610ms returns 0
03-00000000-00-00002609-0038: Restoring target state and closing J-Link connection...

02-00000000-00-00002609-0020: T2BC8 002:608.989 JLINK_IsOpen()
02-00000000-00-00002609-0028: T2BC8 002:609.005 - 0.016ms returns 0x01
02-00000000-00-00002617-001F: T2BC8 002:617.391 JLINK_Close()
03-00000000-00-00002628-0011: Shutting down...

[JONATHAN LL]

Hi,

Can you test with nrfjprog, use it to see if everything is operational. From what you provide seems to be a HW issue but i am not sure, and i am not familiar with JLinkGDBServer so to see if it is HW issue test with nrfjprog. 

nRF Command Line Tools - nordicsemi.com

https://infocenter.nordicsemi.com/topic/ug_nrf_cltools/UG/cltools/nrf_nrfjprogexe_reference.html?cp=10_1_3_0 

Use the newest version. 

Regards,
Jonathan

[billyhw]

Hi

Thanks for your help! I was able to compare the working and not working boards using the following

C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>nrfjprog.exe --deviceversion --log

On a good board  I get 'NRF52833_xxAA_REV1' and on the bad one I see errors. Then I did a test with external power removed (MCU powered by debugger only) and found the bad board is able to respond in this state. I will proceed to verify the firmware image and then debug my hardware to see what is locking up the MCU.