MCUXpresso 11.0.1 - J-Link support unavailable

wolfgangschmidt · ‎09-06-2019

Today i tried 11.0.1 together with a J-Link Plus debugger.

The result was when pressing the blue Debug button in Quickstart Panel a message occurs :

J-Link support unavailable!
Click on 'Yes' to set the path to J-Link server or 'No' to disable J-Link for future debug connections.

On pressing yes i canselect JLinkGDBServerCL.exe but nothing changes.

A bit later the following message appears:

Error in final launch sequence:
Failed to execute MI command:
-target-select remote localhost:2331
Error message from debugger back end:
localhost:2331: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
Failed to execute MI command:
-target-select remote localhost:2331

We used 11.0.0 before and I imported all settings to 11.0.1.

I tried to compare J-Link settings

In 11.0.1 the difference seems to be:

C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe

and 11.0.0 shows as executable:

C:\Program Files (x86)\SEGGER\JLink_V644i\JLinkGDBServerCL.exe

Even if i set the 11.01 to the 644 directory same message keeps reapearing.

I also tried to uninstall MCUXpresso 11.0.1 and reinstall , a few restarts of the system, but everything keeps the same.

OS is Win 10 / 1903.

11.0.0 still works. Also manually start of the Segger GDB Server and then using it from 11.0.1 works, but is giving the same error message first.

BlackNight · ‎09-06-2019

It is not the normal way to do this, but maybe it is releated to some Windows permission issues? Maybe it can work if you launch the IDE in administrator mode?

mike_katz · ‎09-06-2019

I even tried upgrading to the latest jlink 6.50b

BlackNight · ‎09-06-2019

could you post here your console log similar to the one I did?

BlackNight · ‎09-06-2019

I have imported 11.0.0 projects into 11.0.1 too, but I had not seen something like this. could you post your Console output (I have pasted mine below as a reference).

I do have the J-Link V6.46k, and this are my settings:

And just as a wild guess: will it help if you delete the j-link launch file in your project, so it has to re-create the configuration?

About the message

localhost:2331: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
Failed to execute MI command:
-target-select remote localhost:2331

I get something like this if a) the J-Link server is not responding at all or if it cannot find the binary/executable for it.

I hope this helps,

Erich

[06-9-2019 03:37:40] Executing Server: "C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe" -nosilent -swoport 2332 -select USB=621000000  -telnetport 2333 -singlerun -endian little -noir -speed auto   -port 2331    -vd -device MK22FN512xxx12 -if SWD -halt -reportuseraction
SEGGER J-Link GDB Server V6.46k Command Line Version

JLinkARM.dll V6.46k (DLL compiled Jul 22 2019 10:49:32)

Command line: -nosilent -swoport 2332 -select USB=621000000 -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MK22FN512xxx12 -if SWD -halt -reportuseraction
-----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:                 MK22FN512xxx12
Target interface:              SWD
Target interface speed:        auto
Target endian:                 little

Connecting to J-Link...
$$UserActionStart$$: Terms of use
$$UserActionEnd$$: Terms of use
J-Link is connected.
Device "MK22FN512XXX12" selected.
Firmware: J-Link OpenSDA 2 compiled Nov 16 2017 12:37:19
Hardware: V1.00
S/N: 621000000
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...InitTarget()
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x001C0000)
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
InitTarget()
Found SW-DP with ID 0x2BA01477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
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
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00003C96 (Data = 0xAF00B084)
Read 2 bytes @ address 0x00003C96 (Data = 0xB084)
Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00003C96 (Data = 0xAF00B084)
Read 2 bytes @ address 0x00003C96 (Data = 0xB084)
Received monitor command: reset
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
AfterResetTarget()
Resetting target
Downloading 9644 bytes @ address 0x00000000 - Verified OK
Downloading 4 bytes @ address 0x000025AC - Verified OK
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (10240 bytes)
J-Link: Flash download: Total time needed: 0.267s (Prepare: 0.057s, Compare: 0.004s, Erase: 0.032s, Program: 0.165s, Verify: 0.000s, Restore: 0.006s)
Writing register (PC = 0x     190)
Reading all registers
Read 4 bytes @ address 0x00000190 (Data = 0xB672B510)
Reading 64 bytes @ address 0x00000440
Read 2 bytes @ address 0x00000440 (Data = 0xF001)
Received monitor command: semihosting enable
Semi-hosting enabled (Handle on BKPT)
Received monitor command: exec SetRestartOnClose=1
Executed SetRestartOnClose=1
Received monitor command: reset
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
AfterResetTarget()
Resetting target
Setting breakpoint @ address 0x00000440, Size = 2, BPHandle = 0x0001
Starting target CPU...
...Breakpoint reached @ address 0x00000440
Reading all registers
Removing breakpoint @ address 0x00000440, Size = 2
Read 4 bytes @ address 0x00000440 (Data = 0xFD5BF001)
Starting target CPU...
Debugger requested to halt target...
...Target halted (PC = 0x00000426)
Reading all registers
Read 4 bytes @ address 0x00000426 (Data = 0xDCF82B00)
Read 4 bytes @ address 0x0000045E (Data = 0x48032104)
Reading 64 bytes @ address 0x2000FFC0
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

giusloq · ‎09-06-2019

Same situation here.