I did this with 11.5 and have the same symptom: it fails
Uninstalled 11.4, and installed 11.5.0_7232
To be sure, I created a fresh Workspace and imported the led_blinky example.
Active configuration: Debug
Built project,
Plugged the LPCXpresso55S69 into the PC and it enumerates:
Then ran debug, selected the probe, and continued
The first error message:
Unable to open probe index 1.
Error: Probe not open
Unable to open probe index 1.
Error: Probe not open
Error: Probe not open
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.checkServerReply(RedlinkServerClient.java:224)
at com.nxp.mcuxpresso.core.debug.support.linkserver.redlink.client.RedlinkServerClient.openByIndex(RedlinkServerClient.java:777)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.ideConnect(AbstractJtagDiscovery.java:205)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.connect(AbstractJtagDiscovery.java:187)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.jtag.AbstractJtagDiscovery.discover(AbstractJtagDiscovery.java:146)
at com.nxp.mcuxpresso.core.debug.support.linkserver.emulators.TargetDiscovery.jtagDiscovery(TargetDiscovery.java:445)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.getEmulatorInfo(LaunchScriptUtils.java:248)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.init(LaunchScriptUtils.java:488)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:156)
at com.nxp.mcuxpresso.core.debug.support.linkserver.launch.LaunchScriptUtils.<init>(LaunchScriptUtils.java:143)
at com.nxp.mcuxpresso.core.debug.support.linkserver.services.TargetDiscoveryService.getTargetDiscovery(TargetDiscoveryService.java:138)
at com.nxp.mcuxpresso.core.debug.support.linkserver.override.LSFinalLaunchSequence$TargetDiscoveryJob.run(LSFinalLaunchSequence.java:124)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
2nd pupup:
02: Failed on connect
02: Failed on connect
Could not connect to core.
31: No connection to chip's debug port
Debugging context: lpcxpresso55s69_led_blinky LinkServer Debug
3rd error popup:
Error in final launch sequence:
Failed to execute MI command:
-target-select extended-remote localhost:10989
Error message from debugger back end:
Remote communication error. Target disconnected.: (undocumented errno 10061).
Failed to execute MI command:
-target-select extended-remote localhost:10989
Error message from debugger back end:
Remote communication error. Target disconnected.: (undocumented errno 10061).
Console output:
MCUXpresso IDE RedlinkMulti Driver v11.5 (Dec 16 2021 12:38:31 - crt_emu_cm_redlink build 2)
Found chip XML file in C:/Users/jancu/Documents/MCUXpressoIDE_11.5.0_7232/lpcxpresso55s69_led_blinky/Debug\LPC55S69.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Connecting to probe 1 core 0 (using server started externally) reports:
'Ee(42). Could not connect to core.'
Retrying...
Reconnected to existing LinkServer process.
Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.
Failed on connect: Ee(42). Could not connect to core.
No connection to chip's debug port
Additional info: when using the manual boot option (the red boot at the top of the screen),
I can list the probe but it gives the same error when trying to list the cores:
I retested on my Windows 10 PC, same physical device, and the debugger starts there.
I tried both:
"Clean Up Debug" :
this did not solve. Same error: Error: Probe not open
Update debugger firmware:
this did not solve. Same error: Error: Probe not open
I used the LPC-Link2 Debug Probe Firmware Programming instructions
Installed LCPScrypt v2.1.2, and replaced the Segger firmware with the latest [2021-08-23] as described on that page (this requires renaming the two BIN files.
Executed the upgrade.
C:\nxp\LPCScrypt_2.1.2_57\scripts>program_JLINK
...
LPCXpresso V2/V3 programmed successfully:
- To use: remove DFU link and reboot.
Removed the DFU jumper, restarted board. MCUXpresso reports the firmware version you advised: 5.361
Confirmed: Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.361
It does not change the behaviour - the errors are the same as initially posted.
No connection to chip's debug port
Hi,
Can you go please to Window->Preferences->MCUXpresso IDE->DebugOptions->LinkServer Options->Miscellaneous and:
1. On extended debug trace use: 0xFFFFFFFF
2. check "Stream all stub messages to Console"
Apply and Close, Debug
Can you then:
a) attach the log shown on " ... Debug message" console
b) attach the log shown on "RedlinkServer" console
c) Send the next commands in the RedlinkServer console and send us the results:
probelist
probeopenbyindex 1
wireswdconnect 1
it should look like:
Regards,
MCUXpresso IDE Support
Hi,
We couldn't reproduce the issue so no obvious solution for it, but what you can try:
1. check the device status in Device Manager (Details/Events)
2. re-install the driver and/or use other USB port (if it is available):
Regards,
MCUXpresso IDE Support
