RedlinkAPI: Probe not open

lpcware · ‎06-15-2016

Content originally posted in LPCWare by StampVoet on Thu Jul 03 06:57:11 MST 2014
Hello,

I am new to programming LPC devices and am experiencing problems with debugging in the LPCXpresso IDE.
After buying the LPCWare motor control devkit + LPC1549 Xpresso V2 and building the example code (successfully) I'm now experiencing this problem.

This is what Redlink tells me:

[Started server]
[Connected on port 3025]
redlink>

Probelist
Index = 1
Manufacturer = Keil Software
Description = LPC-Link-II CMSIS-DAP
VID = C251, PID=F001
Path = \\?\hid#vid_c251&pid_f001#7&6aabb73&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

probestatus
Index = 1
Manufacturer = Keil Software
Description = LPC-Link-II CMSIS-DAP
VID = C251, PID=F001
Path = \\?\hid#vid_c251&pid_f001#7&6aabb73&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = FALSE
HasSWD = TRUE
Probe Type = CMSISDAP

probeisopen 1
FALSE

probeopenbyindex 1
RedlinkAPI: Probe not open

I am using:
windows 7 x64
LPCXpresso v7.2.0 [Build 153] [2014-05-19]
I've tried multiple USB ports/hubs

On a collegues PC it does debug/program without problems.

Thanks in advance and best regards,

Gijs de Graaf

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 04 02:23:11 MST 2014
Sorry, but I do not know how to help you any further - it is seems to be a problem unique to your machine. The only things I can suggest (most of which you say you have done):
- make sure you are using the latest version of LPCXpresso (v7.2.0 is the currently shipping version)
- try connecting to different USB ports
- try uninstall the drivers for LPC-Link2 and/or CMSIS-DAP via Device Manager (making sure you select the option to remove the drivers software too).

We do, very rarely, encounter problems on customer computers where the Windows Driver Database becomes corrupt, and the only reliable fix for this has been a re-installation of Windows.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by StampVoet on Fri Jul 04 01:41:40 MST 2014
I've tried debugging with JP3 inserted, it now registers as an "LPCLINK2 Redlink" but I'm still not able to debug on my PC.
Like I said in my first post I am able to debug on a colleagues PC (windows

without any problems.
Maybe it's a problem with my redlink install? I did try reinstalling the ide and allowing redlink to my firewalls in and outbound rules, still no success.

[Started server]
[Connected on port 3025]
redlink>
probelist
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#8&4d934e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

probestatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#8&4d934e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 64
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK

probeisopen 1
FALSE


probeopenbyindex 1
RedlinkAPI: Probe not open

I keep getting the "Probe not open" error.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Thu Jul 03 07:30:35 MST 2014
Sorry, getting confused between a standalone LPC-Link2 and the one built into and LPC1549 LPCXpresso board.

On the LPC1549 LPCXpresso board, you should ensure that JP3 is inserted.

http://www.lpcware.com/LPCXpressoV2Boards

lpcware · ‎06-15-2016

Content originally posted in LPCWare by StampVoet on Thu Jul 03 07:14:09 MST 2014
Thanks for your quick reply.
JP1 was already removed.
There is only one jumper connected and that one is connected to JP2 pin 1 and 2

Best regards

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Thu Jul 03 07:10:54 MST 2014
To fix this issue:

Unplug LPC-Link2 from your computer,
remove JP1 from your LPC-Link2,
reconnect to your computer and try debugging again.

Note that you will need to "search for any enabled emulator" the first time after starting your debug session.