LPC-Link USB problems. Again.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Mon Apr 23 02:05:28 MST 2012
Hello,
I am experiencing LPC-Link problems, when trying to debug the target.
The debugger: LPCXpresso board debug part, powered from USB.
The target: my own board, LPC1227, powered from my own power supply. The debugger and target are connected using SWD/SWCLK.

When I try to debug, about 8 times out of 10, I get stuck on 57% of progress and it says: Launching: JTAG Discovery.
If I get this problem, then there's no other solution to make it working, but restart the PC. Sometimes it works fine for 1-2 iterations of debug, but sometimes it doesn't work at all - gets stuck in the same place.

I've read the forum and bought a proper, USB2 certified cable. It's short - 0.5m, thick, properly shielded and has [U]two[/U] USB connectors on the PC side (yep, that's for current). With this cable, the debug doesn't work at all. Never. I'm using 1m long, simple USB cable used for mobile phones data connection. This allows to run debug once/twice.

Lets go deeper. I've not enabled HID option, since the debug doesn't work at all then. Also gets stuck on the same progress place. So the configuration here is default. I've enabled debug log:

cscript //E:vbscript //NoLogo "C:\nxp\LPCXpresso_4.2.2_275\lpcxpresso\configuration\org.eclipse.osgi\bundles\5\1\.cp\Data\dfu.vbs"
VID_0471&PID_DF55Done
cscript //E:vbscript //NoLogo "C:\nxp\LPCXpresso_4.2.2_275\lpcxpresso\configuration\org.eclipse.osgi\bundles\5\1\.cp\Data\dfu.vbs"
VID_0471&PID_DF55Done
cscript //E:vbscript //NoLogo "C:\nxp\LPCXpresso_4.2.2_275\lpcxpresso\configuration\org.eclipse.osgi\bundles\5\1\.cp\Data\vidpid.vbs"
ACPI_HALPNP0C08PNP0A08VEN_8086&DEV_0100&SUBSYS_00000000&REV_09VEN_8086&DEV_0101&SUBSYS_00000000&REV_09VEN_1002&DEV_68F9&SUBSYS_03741043&REV_00PHLC082SAM07ADVEN_1002&DEV_AA68&SUBSYS_AA681043&REV_00FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_04ROOT_HUB20VID_8087&PID_0024VID_046D&PID_C312VID_046D&PID_C312VID_046D&PID_C05BVID_046D&PID_C05BVID_046D&PID_C05B&REV_5400&MOUFILTVID_046D&PID_C05B&REV_5400&HIDFILTVID_046D&PID_C05B&REV_5400&USBFILTVEN_8086&DEV_1C20&SUBSYS_84361043&REV_04FUNC_01&VEN_10EC&DEV_0892&SUBSYS_10438436&REV_1003VEN_8086&DEV_1C10&SUBSYS_00000000&REV_B4VEN_1A0E&DEV_0860&SUBSYS_00000000&REV_00VEN_8086&DEV_1C18&SUBSYS_00000000&REV_B4VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00VID_040E&PID_0100VID_09FB&PID_6001VEN_8086&DEV_1C1A&SUBSYS_00000000&REV_B4VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06VEN_8086&DEV_244E&SUBSYS_00000000&REV_B4VEN_1B21&DEV_1080&SUBSYS_00000000&REV_01VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10VEN_8086&DEV_1C1E&SUBSYS_00000000&REV_B4VEN_11AB&DEV_6121&SUBSYS_82A21043&REV_B2ARRAY&VEN_MARVELL&PROD_VIRTUAL_DEVICE&REV_1.00VEN_8086&DEV_1C26&SUBSYS_844D1043&REV_04ROOT_HUB20VID_8087&PID_0024VEN_8086&DEV_1C4A&SUBSYS_00000000&REV_04READDATAPORTPNP0C02PNP0000PNP0200PNP0100PNP0B00PNP0800PNP0C02PNP0C04PNP0501VEN_8086&DEV_1C00&SUBSYS_844D1043&REV_04IDECHANNELDISKST31000524AS____________________________JC45____CDROMOPTIARC_DVD_RW_AD-7261S_________________1.03____IDECHANNELVEN_8086&DEV_1C22&SUBSYS_844D1043&REV_04VEN_8086&DEV_1C08&SUBSYS_844D1043&REV_04IDECHANNELIDECHANNELPNP0C01PNP0C01INT3F0DPNP0103PNP0C0CPNP0C02PNP0C01PNP0C14FIXEDBUTTONGENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42DMIOFTDISKVOLUMELEGACY_AFDLEGACY_ALTERABYTEBLASTERLEGACY_ALTIOLEGACY_ARP1394LEGACY_BEEPLEGACY_DMBOOTLEGACY_DMLOADLEGACY_DS1410DLEGACY_FIPSLEGACY_GIVEIOLEGACY_GPCLEGACY_HARDLOCKLEGACY_HASPNTLEGACY_HTTPLEGACY_INETLOCKLEGACY_IOMAPLEGACY_IPNATLEGACY_IPSECLEGACY_KSECDDLEGACY_MNMDDLEGACY_MODEMLEGACY_MOUNTMGRLEGACY_NDISLEGACY_NDISTAPILEGACY_NDISUIOLEGACY_NDMSHLPLEGACY_NDPROXYLEGACY_NETBTLEGACY_NPFLEGACY_NULLLEGACY_PARTMGRLEGACY_PARVDMLEGACY_RASACDLEGACY_RDPCDDLEGACY_RTNDPT5XLEGACY_SERMONLEGACY_SPEEDFANLEGACY_TCPIPLEGACY_VGASAVELEGACY_VOLSNAPLEGACY_WANARPLEGACY_WDF01000LEGACY_WUDFPFMEDIAMEDIAMEDIAMEDIAMEDIAMS_L2TPMINIPORTMS_NDISWANIPMS_PPPOEMINIPORTMS_PPTPMINIPORTMS_PSCHEDMPMS_PSCHEDMPMS_PSCHEDMPMS_PTIMINIPORTRDPDRRDP_KBDRDP_MOUSYSTEM{CD171DE3-69E5-11D2-B56D-0000F8754380}{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}SYSTEMSYSTEMSYSTEMDTCDROM&REV1Done
cscript //E:vbscript //NoLogo "C:\nxp\LPCXpresso_4.2.2_275\lpcxpresso\configuration\org.eclipse.osgi\bundles\5\1\.cp\Data\vidpid.vbs"
ACPI_HALPNP0C08PNP0A08VEN_8086&DEV_0100&SUBSYS_00000000&REV_09VEN_8086&DEV_0101&SUBSYS_00000000&REV_09VEN_1002&DEV_68F9&SUBSYS_03741043&REV_00PHLC082SAM07ADVEN_1002&DEV_AA68&SUBSYS_AA681043&REV_00FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_04ROOT_HUB20VID_8087&PID_0024VID_046D&PID_C312VID_046D&PID_C312VID_046D&PID_C05BVID_046D&PID_C05BVID_046D&PID_C05B&REV_5400&MOUFILTVID_046D&PID_C05B&REV_5400&HIDFILTVID_046D&PID_C05B&REV_5400&USBFILTVEN_8086&DEV_1C20&SUBSYS_84361043&REV_04FUNC_01&VEN_10EC&DEV_0892&SUBSYS_10438436&REV_1003VEN_8086&DEV_1C10&SUBSYS_00000000&REV_B4VEN_1A0E&DEV_0860&SUBSYS_00000000&REV_00VEN_8086&DEV_1C18&SUBSYS_00000000&REV_B4VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00VID_040E&PID_0100VID_09FB&PID_6001VEN_8086&DEV_1C1A&SUBSYS_00000000&REV_B4VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06VEN_8086&DEV_244E&SUBSYS_00000000&REV_B4VEN_1B21&DEV_1080&SUBSYS_00000000&REV_01VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10VEN_8086&DEV_1C1E&SUBSYS_00000000&REV_B4VEN_11AB&DEV_6121&SUBSYS_82A21043&REV_B2ARRAY&VEN_MARVELL&PROD_VIRTUAL_DEVICE&REV_1.00VEN_8086&DEV_1C26&SUBSYS_844D1043&REV_04ROOT_HUB20VID_8087&PID_0024VID_1FC9&PID_0009VEN_8086&DEV_1C4A&SUBSYS_00000000&REV_04READDATAPORTPNP0C02PNP0000PNP0200PNP0100PNP0B00PNP0800PNP0C02PNP0C04PNP0501VEN_8086&DEV_1C00&SUBSYS_844D1043&REV_04IDECHANNELDISKST31000524AS____________________________JC45____CDROMOPTIARC_DVD_RW_AD-7261S_________________1.03____IDECHANNELVEN_8086&DEV_1C22&SUBSYS_844D1043&REV_04VEN_8086&DEV_1C08&SUBSYS_844D1043&REV_04IDECHANNELIDECHANNELPNP0C01PNP0C01INT3F0DPNP0103PNP0C0CPNP0C02PNP0C01PNP0C14FIXEDBUTTONGENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42GENUINEINTEL_-_X86_FAMILY_6_MODEL_42DMIOFTDISKVOLUMELEGACY_AFDLEGACY_ALTERABYTEBLASTERLEGACY_ALTIOLEGACY_ARP1394LEGACY_BEEPLEGACY_DMBOOTLEGACY_DMLOADLEGACY_DS1410DLEGACY_FIPSLEGACY_GIVEIOLEGACY_GPCLEGACY_HARDLOCKLEGACY_HASPNTLEGACY_HTTPLEGACY_INETLOCKLEGACY_IOMAPLEGACY_IPNATLEGACY_IPSECLEGACY_KSECDDLEGACY_MNMDDLEGACY_MODEMLEGACY_MOUNTMGRLEGACY_NDISLEGACY_NDISTAPILEGACY_NDISUIOLEGACY_NDMSHLPLEGACY_NDPROXYLEGACY_NETBTLEGACY_NPFLEGACY_NULLLEGACY_PARTMGRLEGACY_PARVDMLEGACY_RASACDLEGACY_RDPCDDLEGACY_RTNDPT5XLEGACY_SERMONLEGACY_SPEEDFANLEGACY_TCPIPLEGACY_VGASAVELEGACY_VOLSNAPLEGACY_WANARPLEGACY_WDF01000LEGACY_WUDFPFMEDIAMEDIAMEDIAMEDIAMEDIAMS_L2TPMINIPORTMS_NDISWANIPMS_PPPOEMINIPORTMS_PPTPMINIPORTMS_PSCHEDMPMS_PSCHEDMPMS_PSCHEDMPMS_PTIMINIPORTRDPDRRDP_KBDRDP_MOUSYSTEM{CD171DE3-69E5-11D2-B56D-0000F8754380}{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}{B7EAFDC0-A680-11D0-96D8-00AA0051E51D}SYSTEMSYSTEMSYSTEMDTCDROM&REV1Done
cscript //E:vbscript //NoLogo "C:\nxp\LPCXpresso_4.2.2_275\lpcxpresso\configuration\org.eclipse.osgi\bundles\5\1\.cp\Data\dfu.vbs"
Done

The console output: http://pastebin.com/zERNfemU

That goes 355, 356, 357... etc.

bothered to wait, I hit STOP:

362 
363-gdb-exit

Now a window appears, the details are:

An internal error occurred during: "Launching my_project_name_here Debug".
java.lang.NullPointerException

Sometimes, the error shown up is talking about timeout or something.

Basically, it is impossible to work with the debugger, when I have to restart my PC up to 10 times per 2 hours.

Now when enabled HID.
Console output: http://pastebin.com/cubF7rq0

Debug log adds fallowing lines: http://pastebin.com/gR5DsgP7
Final thing: when I run "Program Flash", it doesn't work, when I've selected LPC-Link in HID mode, but it [U]always[/U] work, when I use the default setup.

Version: LPCXpresso v4.2.2 [Build 275] [03/04/2012]

P.S. Character limitations didn't allow to post all logs here, so I've used pastebin.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by dadalolo on Mon Sep 24 15:22:29 MST 2012
Thanks, I will try this when the comms problem occurs again. Now all works fine so I don't want to break it.

But this will address the timeout issue only I guess. Do you know may be how to fully uninstall whatever drivers to unlock the USB port / DFU that does not work with LPC link anymore (i.e. if I change USB cable from a 'locked out USB port' to a new USB port then DFU etc get installed and port works fine with LPC link). I have only 2 potrs left that are not 'DFU locked out' yet ...

lpcware · ‎06-15-2016

Content originally posted in LPCWare by SteveClevenger on Sat Aug 25 21:22:30 MST 2012
It's not clear to me (and perhaps others) whether this thread is solely about DFU failures (i.e. DFU of the LPC-Link probe failed), or if there are debug connection problems after the LPC-Link probe has successfully booted on the LPCXpresso. To eliminate DFU failures as a cause, note that 9 times out of 10 a DFU failure can be resolved by increasing the timeout value used by dfuapp.exe. The following presumes you have the DFU driver installed on your computer, and your LPCXpresso board is in working order:

1, Disconnect and reapply power to your LPC-Link.
2. In <install>\lpcxpresso\bin, you'll find the dfuapp.exe utility. Use a command such as the following:

C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin\dfuapp.exe /f LPCXpressoHS.enc /tl 250

to see if the LPC-Link HID probe enumerates. You should hear it connect. If you do not hear it, use one of the debug utilities to see if the probe installed.

C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>crt_emu_cm3_nxp.exe -info-emu -wire=hid
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
1 Emulators available:
0. T1S6RGRIA LPC-Link Probe v1.0 (Code Red - LPCXpresso)

If it did not, the debug utility would report the following:

C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>crt_emu_cm3_nxp.exe -info-emu -wire=hid
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
0 Emulators available:

If the debug utility did not report a connected probe, increase the timeout value, and retry. You can also experiment with the full speed version of the HID probe (LPCXpressoFS.enc) for comparison purposes, and also the WinUSB probe (LPCXpressoWIN.enc). The debug utility command-line is slightly different for the WinUSB probe:

C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>crt_emu_cm3_nxp.exe -info-emu -wire=winusb
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
1 Emulators available:
0. T1S6RGRIA LPC-Link Probe v1.1 (Code Red - LPCXpresso)

You'll also find a convenient script file in the Scripts sub-directory to <install>\lpcxpresso\bin\Scripts which operates the dfuapp.exe utility. The name of this script is bootLPCXpresso.cmd. I believe the default timeout is 250 ms. If you find a higher timeout is suitable for your PC, modify the settings in this file.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by dadalolo on Fri Aug 24 01:30:30 MST 2012
I have a dual core PC and I still get very inreliable performance with LCP-link.
I do not changee anything is a setup, all of it sudden XPRESSO faild to connect to the LPC-link board (can;t provide the LOG because, watch it :L the LOG file is empty (fancy nake though: dfuApp7950791037844026556.log).

One of the error messages in 4 windows that pop up after the failure says :
" No emulator/board available.
This could be because it is unpowered, disconnected or already in use"

It is clearly an issue in the USB driver for the LPC-link, especially then now and then after such fsilure it locks out the particular USB port for good - XPRESSSO would NEVER work on that USB poprt again. Isn't this crazy !

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Thu May 10 05:12:21 MST 2012

Quote: CodeRedSupport
Can you be more explicit? "Stops somewhere at initialization" doesn't tell us anything. Send us the debug log at least.

Did You read my first post of this thread?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 10 02:33:03 MST 2012
Can you be more explicit? "Stops somewhere at initialization" doesn't tell us anything. Send us the debug log at least.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Thu May 10 00:49:52 MST 2012

Quote: CodeRedSupport
Are you using LPC-Link as HID (Window->preferences, LPCXpresso/Debug Emulator/Initialise LPC-Link as HID)

Whichever mode you are using, can you switch it, and then try your testing again.

HID/WinUSB use two entirely different drivers (both provided by Microsoft). If you still have problems, this implies to me that you have a hardware or driver problem with your USB ports.

Note that we have fast machines here, and experience no problems whatsoever.

That was almost the first thing I've tried. When using as HID, the debugger doesn't work at all. Stops somewhere at initialization.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 10 00:44:20 MST 2012
Are you using LPC-Link as HID (Window->preferences, LPCXpresso/Debug Emulator/Initialise LPC-Link as HID)

Whichever mode you are using, can you switch it, and then try your testing again.

HID/WinUSB use two entirely different drivers (both provided by Microsoft). If you still have problems, this implies to me that you have a hardware or driver problem with your USB ports.

Note that we have fast machines here, and experience no problems whatsoever.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Wed May 09 22:56:06 MST 2012

Quote: CodeRedSupport
Lets take a step back here to see if we can help you.

First of all, I see you are using your own custom LPC1227 board together with LPC-Link. It is quite possible that the LPC1227 debug circuit is designed incorrectly, or that in separating the LPC-Link you have broken something. You should also check power (how are your powering your custom board?)

So, can you please try with a standard (unmodified) LPCXpresso LPC1227 board and report your results.

The standard LPCXpresso works exactly the same. I've tried on LPCXpresso LPC1769 Rev. B.

Now I am working with two computers, because it is impossible to use a debugger with the current one.
The current PC (on which the debugger almost doesn't work) has:
CPU: Intel i7-2600 (8 cores @ 3.40GHz)
MB: ASUS P8H67-M EVO
RAM: 4GB DDR3
The debugger doesn't work _at_all_ when connected to USB3 port and if I disconnect the USB cable when JTAG is trying to initialize, it results in BSOD. Also it doesn't matter if I connect to front USB2 or back USB2.

Now the interesting part. I've got a second PC to program my CPU. No matter what I do: reconnect USB, reconnect target, reset, use short or long USB cable, use LPCXpresso target CPU or the CPU on my custom board, IT ALWAYS WORK! The debug has never failed - it's just working perfectly.
The older PC specs:
CPU: E2160 (2 cores @ 1.80GHz)
MB: ASRock G31M-S
RAM: 2GB DDR2

Both systems run Windows XP with latest updates.
And even more interesting part:
We have more PCs with high-end hardware, running Windows XP or Windows 7 - all of them have problems with the debugger, but the older PCs work fine. I doubt it could be my PC hardware, because the debugger behaves exactly the same on two other newer hardware computers.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed May 09 00:09:30 MST 2012
Lets take a step back here to see if we can help you.

First of all, I see you are using your own custom LPC1227 board together with LPC-Link. It is quite possible that the LPC1227 debug circuit is designed incorrectly, or that in separating the LPC-Link you have broken something. You should also check power (how are your powering your custom board?)

So, can you please try with a standard (unmodified) LPCXpresso LPC1227 board and report your results.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Tue May 08 23:20:12 MST 2012

Quote: TheFallGuy
Have you ever thought that it could be a problem with your hardware or drivers? USB3 is backwards compatible, so if it is crashing your PC, it must be a problem with either the driver, or the hardware. Why do you think it is a problem with LPCXpresso?

Well, I don't connect it to USB3 port, only USB2, since it works sometimes.

I believe it's LPCXpresso problem, because we (not me alone) have issues with all the newer PCs (that has quad core cpus), but no problems with PCs, that are a bit older (dual core, 3-4 years old). Plus no other hardware, including other USB CPUs, FTDI chips, Cypress USB SOCs, etc fail so much, like LPCXpresso.

What is more strange: the LOG is empty and support can't help here. Google the same problem - many engineers have the same issue, so You still think, it's the PC? I doubt.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by TheFallGuy on Tue May 08 06:02:51 MST 2012
Have you ever thought that it could be a problem with your hardware or drivers? USB3 is backwards compatible, so if it is crashing your PC, it must be a problem with either the driver, or the hardware. Why do you think it is a problem with LPCXpresso?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Tue May 08 04:09:09 MST 2012
Support? Gone? LOL.

It is impossible to work with such debugger. Useless hardware, which work on old computers and doesn't on newer ones... DO NOT connect it to USB3 port, it will crash the PC easily.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Socrates on Tue Apr 24 22:24:46 MST 2012

Quote: CodeRedSupport
Double check your debug/reset circuitry with reference to :

http://support.code-red-tech.com/CodeRedWiki/HardwareDebugConnections

If that doesn't help provide more detailed description of your board (with reference to the above), and post the debug log from a failed connection....

The connections are correct - I've double checked that. ISP and RESET pins are pulled high through 10k. The confirmation of correct connection is that I am rarely able to do the debug.

Quote: CodeRedSupport

http://support.code-red-tech.com/CodeRedWiki/DebugLog

Not so much to see:

LPCXpresso Debug Driver v4.0 (Mar 24 2012 17:40:11)

And nothing more.

Quote: CodeRedSupport

Might also be worth knowing if you could debug the MCU portion of your LPCXpresso board from the same PC before you split the LPC-Link off (and whether you still can if you wire the two halves back up again)?

Yes, I've connected them back together and it acts exactly the same. Maybe an issue here is that the project path has spaces? E.g. \...\My Projects\... ?

P.S. Today, I've got an error popped up after JTAG timeout:
"timeout waiting for mon ondisconnect cont"

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue Apr 24 08:01:25 MST 2012
Double check your debug/reset circuitry with reference to :

http://support.code-red-tech.com/CodeRedWiki/HardwareDebugConnections

If that doesn't help provide more detailed description of your board (with reference to the above), and post the debug log from a failed connection....

http://support.code-red-tech.com/CodeRedWiki/DebugLog

Might also be worth knowing if you could debug the MCU portion of your LPCXpresso board from the same PC before you split the LPC-Link off (and whether you still can if you wire the two halves back up again)?

Regards,
CodeRedSupport.