Hello,
This morning my J-Link Plus suddenly was not able to connect to my target MCU. Seems like the error is related to the inability of opening the listener port. I tried to debug my application in both Atollic and Eclipse(GNU MCU).
Display All
However, if I were to connect to using the application "J-Flash vx.xxx", the J-Link was able to established a connection:
Display All
Tried resetting my PC multiple times but to no avail. Any idea what is going on and how I can go about fixing it? It was working perfectly fine until now.
Thanks
This morning my J-Link Plus suddenly was not able to connect to my target MCU. Seems like the error is related to the inability of opening the listener port. I tried to debug my application in both Atollic and Eclipse(GNU MCU).
Source Code
- SEGGER J-Link GDB Server V6.42b Command Line Version
- JLinkARM.dll V6.42b (DLL compiled Feb 5 2019 17:31:40)
- Command line: -port 2331 -s -CPU Cortex-M -device STM32L496VG -endian little -speed 4000 -vd
- -----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: localhost only
- Generate logfile: off
- Verify download: on
- Init regs on start: off
- Silent mode: off
- Single run mode: on
- Target connection timeout: 0 ms
- ------J-Link related settings------
- J-Link Host interface: USB
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: STM32L496VG
- Target interface: JTAG
- Target interface speed: 4000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link V10 compiled Jul 23 2019 13:46:10
- Hardware: V10.10
- S/N: 600106282
- Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
- Checking target voltage...
- Target voltage: 3.33 V
- ERROR: Failed to listen at socket (Err = -1)
- ERROR: Failed to open listener port 2331
- Restoring target state and closing J-Link connection...
- Shutting down...
- Failed to open listener port 2331
However, if I were to connect to using the application "J-Flash vx.xxx", the J-Link was able to established a connection:
Source Code
- Application log started
- - J-Flash V6.42b (J-Flash compiled Feb 5 2019 17:32:19)
- - JLinkARM.dll V6.42b (DLL compiled Feb 5 2019 17:31:40)
- Opening project file [D:\JFlash Project Files\STM32L496VE.jflash] ...
- - Project opened successfully
- Failed to open data file [C:\Users\whuang\Downloads\Firmware-20190628.246\RoamBase-1.1.5.246\RoamBase_1.1.5.246_Bank0.hex]...
- Connecting ...
- - Connecting via USB to J-Link device 0
- - J-Link firmware: J-Link V10 compiled Jul 23 2019 13:46:10
- - Device "STM32L496VE" selected.
- - Target interface speed: 4000 kHz (Fixed)
- - VTarget = 3.328V
- - TotalIRLen = 9, IRPrint = 0x0011
- - JTAG chain detection found 2 devices:
- - #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
- - #1 Id: 0x06461041, IRLen: 05, Unknown device
- - STM32 (Protection Detection): Unexpected IDCODE DEV_ID 0x 461 found. Only checking the 1st flash bank for write protection.
- - TotalIRLen = 9, IRPrint = 0x0011
- - JTAG chain detection found 2 devices:
- - #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
- - #1 Id: 0x06461041, IRLen: 05, Unknown device
- - Scanning AP map to find all available APs
- - AP[1]: Stopped AP scan as end of AP map has been reached
- - AP[0]: AHB-AP (IDR: 0x24770011)
- - Iterating through AP map to find AHB-AP to use
- - AP[0]: Core found
- - AP[0]: AHB-AP ROM base: 0xE00FF000
- - CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
- - Found Cortex-M4 r0p1, Little endian.
- - FPUnit: 6 code (BP) slots and 2 literal slots
- - CoreSight components:
- - ROMTbl[0] @ E00FF000
- - ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
- - ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
- - ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
- - ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
- - ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
- - ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
- - Executing init sequence ...
- - Initialized successfully
- - Target interface speed: 4000 kHz (Fixed)
- - J-Link found 2 JTAG devices. Core ID: 0x4BA00477 (None)
- - Connected successfully
Thanks