Link2 Fails debug load on Windows 8.1

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

Link2 Fails debug load on Windows 8.1

826 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by santuitman on Wed Feb 05 15:33:19 MST 2014
Hello

I'm getting a  problem where I cannot load a debug example. It may work for a few loads when I first start the pc but then I start getting this message

[Connected on port 3025]
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#8&4d934e&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#8&4d934e&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = TRUE
PacketSize = 64
Probe Reference Count = 1
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
Core=0
CoreReferenceCount = 1
HighestPriority = 0
DPID = 4ba00477
CoreId = 0
redlink>ProbeIsOpen 1
TRUE
redlink>WireIsConnected 1
TRUE
redlink>WireGetProtocol 1
JTAG
redlink>CoresConfigured 1
TRUE
redlink>CoreList 1
RedlinkAPI: Hardware interface transfer error
redlink>close
[Closed]

It happens at 73% of the launch and you can see the Lpc Device disappear from the device manager as well as getting the"USB removed" tone from the pc. I have tried disabling the firewall and the antivirus but I am still having a problem. I can move the setup to a vista pc or xp pc and that work so it seems to be a setting somewhere in Windows 8.1 I am missing.
Any thoughts?

Thanks in advance!
0 Kudos
Reply
6 Replies

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Feb 11 11:17:34 MST 2014
You do not need to close down LPCXpresso or reboot your machine - all you need to do, is close the debug session before starting another.
0 Kudos
Reply

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by santuitman on Tue Feb 11 10:52:45 MST 2014

I've been using this for a while now and it appears that if I do not terminate the debug session as you said I will not be able to complete a debug session again unless I restart this windows 8 pc. Is this what you would expect? On my Vista machine I may have to restart  lpcxpresso to regain control of the link but I don't have to restart the machine.

I will admit to being very new to this so perhaps I am just missing something.


thanks!
0 Kudos
Reply

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Feb 06 15:08:29 MST 2014

Priority 0 connection to this core already taken.

This error normally means you have not terminated a debug session before starting another. Terminate your debug sessions before a starting another
0 Kudos
Reply

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Feb 06 12:47:06 MST 2014


Does your debug configuration reference a connect script? If so, remove it.

I would next  suggest you navigate to the Redlink Server console and explicitly kill any server process prior to starting your debug session to see if a defunct server is active. The "Priority 0 connection to this core already taken." message suggests the server still thinks it's connected to a debug session.

Regards,

LPCXpresso-Support
0 Kudos
Reply

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by santuitman on Thu Feb 06 07:17:29 MST 2014
Hello and thanks for the reply
I have tried both USB2 and USB3. I have tried powered and unpowered hubs. On starting my PC this morning I was able to get two debug loads and then I got these two errors.

First failure message Error reported by target

02: Failed on connect
  02: Failed on connect
  Priority 0 connection to this core already taken.
  31: No connection to emulator device
 
Second error message Failure in launch sequence

Error in final launch sequence
  Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=50807 -g -mi -2 -pLPC4357 -vendor=NXP -ResetScript=LPC18LPC43InternalFLASHBootResetscript.scp -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC18x7_43x7_2x512_BootA.cfx
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
  Remote communication error.  Target disconnected.: No error.


After this all I get is the symptoms from my original post with the USB disconnecting at the point where the debug would (I believe) load to the device. Disconnecting USB and restarting Xpresso doesn't make a difference. Restarting the PC may but I can't do that right now.
I hope this helps
0 Kudos
Reply

816 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Feb 06 01:37:00 MST 2014
I'm sorry that you are encountering issues. In the first place, please try the following:

[list]
  [*]Try a different USB port. If your PC has USB3 and USB2, then try a USB2 port

  [*]If you must use a USB3 port, make sure you have the very latest *firmware* for the USB port. There are lots of problems with firmware on USB3 ports and most manufacturers have issued firmware updates. Note this is not the Windows driver but the motherboard firmware in the USB3 port itself.

  [*]Try connecting via a USB Hub (preferably powered and preferably USB2). If you are using a hub already, try connecting directly to a port on your PC
[/list]

Regards,
LPCXpresso Support
0 Kudos
Reply