CMSIS DAP Problem in Windows 10

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CMSIS DAP Problem in Windows 10

1,597 Views
denizcan
Contributor II

In MacOS on MacBook and in Ubuntu 18.04 on PC LpcLink with CMSIS-DAP works OK. However, on the same machine in Windows 10, I get the following console output:

MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:33:57 - crt_emu_cm_redlink build 748)
Found part description in XML file nxp_lpc17xx.xme
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
Connecting to probe 1 core 0 (using server started externally) gave 'Ee(42). Could not connect to core.'
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

In the RedlinkServer console, I got the following:

probelist
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC11U3x CMSIS-DAP v1.0.7
Serial Number = 0B023028
VID:PID = 1FC9:0132
Path = \\?\hid#vid_1fc9&pid_0132&mi_00#9&236ef90&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

probestatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC11U3x CMSIS-DAP v1.0.7
Serial Number = 0B023028
VID:PID = 1FC9:0132
Path = \\?\hid#vid_1fc9&pid_0132&mi_00#9&236ef90&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 64
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0

probeopenbyindex 1
Probe not open

On the same PC, the probe works in virtual machine as well..

What shall I do?

1 Reply

1,341 Views
denizcan
Contributor II

Reinstalling Windows solved the problem..