FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

LPC4357 can't debug anymore

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC4357 can't debug anymore

‎06-15-2016 11:36 AM
962 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgeloso on Thu Jun 04 09:40:24 MST 2015
Hi,
I've an embedded artist LPC4357 board and a LPC-Link2 programmer.
Suddenly I can't access the debug mode anymore.
I have also a second kit of embedded artists LPC4357 board and link2 but the problem is not related to the hw. The lpc4357 has the demo code and has never been programmed before, but still I cannot access it.
(I connect the board to a USB3 port and Link2 to a USB2 port.)

The error message refers to an hw transfer fail, but I didn't change the hw set up before the fail..

Do you know how to face this issue?

I'm reporting the error message:
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&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 = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>
redlink>
redlink>
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Handle = 1
redlink>WireIsConnected 1
FALSE
redlink>WireJtagConnect 1
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>
redlink>CoreList 1
RedlinkAPI: Hardware interface transfer error
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = TRUE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>exit
[Closed]


Regards
Pietro
Labels (1)
Labels
0 Kudos
Reply
5 Replies

‎06-15-2016 11:36 AM
890 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgeloso on Fri Jun 05 09:27:20 MST 2015

Ok, trying again the ISP mode worked! Now I'm connected. Probably I made a mistake in the previous trials.

Problem fixed!
Thank you for the support!
0 Kudos
Reply

‎06-15-2016 11:36 AM
890 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgeloso on Fri Jun 05 09:15:34 MST 2015

Hi,
unfortunately still no way to access the lpc4357 through the Link2.

To summarize, there's a list of things I tried.

- I've installed now LPCXpresso 7.8.0 
- I'm using "non-bridged" version of CMSIS-DAP (see picture)
- LPC-Link2 attached to a USB2 port (I also tried an external usb hub between the USB2 port and the link2, without success)
- EA-LPC4357 board powered externally with 5Volt source.
- I've tried to put lpc4357 into USART0 ISP mode, putting P2_9=P2_8=P1_2=P1_1=LOW at boot, while P2_7 is pulled down during reset.
- I've also used a second PC, still with Windows 8 and LPCXpresso 7.8.0, but without success.
- I can see activity on the oscilloscope of the JTAG. Considering I can see the activity on the JTAG I may suspect the issue is in the LPC4357 "locked"..is it correct?
- No Redlink processes in Task Manager
- I've tried 2link2 programmers and 2 EA-LPC4357 boards. The problem is in both harware kits.

The problem now is : RedlinkAPI: Wire Ack Fault. target connected?
Any other suggestions?

I'm attaching the log of 7.8.0:

[Started server]
[Connected on port 3025]
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.112 NB
VID = 1FC9, PID=0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.112 NB
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSISDAP
Probe Reference Count = 0
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Probe Handle 1 Open
redlink>WireIsConnected 1
FALSE
redlink>WireJtagConnect 1
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>CoreList 1
RedlinkAPI: Wire Ack Fault - target connected?
redlink>ProbeCloseByIndex 1
Probe Handle 1 Closed
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.112 NB
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = TRUE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSISDAP
Probe Reference Count = 0
redlink>exit
[Closed]
Preview file
78 KB
Preview file
46 KB
0 Kudos
Reply

‎06-15-2016 11:36 AM
890 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Jun 05 03:39:39 MST 2015
Please post your logs between "code" blocks (use the # icon on the toolbar)

To look for, and kill processes, use Windows Task Manager. You could also try rebooting.

Hardware Interface Transfer error typically means that an error has occurred while transferring data over USB. You can try the following things:
[list]
  [*]Use a different USB port. Try with, and without, USB hubs. If using a USB hub, make sure it is powered
  [*]Use the "non-bridged" version of the debug firmware. See this FAQ for selecting http://www.lpcware.com/content/faq/lpcxpresso/configuring-lpc-link2-firmware-soft-load
  [*]Power the EA-LPC4357 board externally (i.e. do not power it from a USB port on the same PC)
[/list]
0 Kudos
Reply

‎06-15-2016 11:36 AM
890 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgeloso on Fri Jun 05 02:39:05 MST 2015
Hi,
thank you for your quick reply.

Sorry, I don't know LPCXpresso so well. To kill the processes you suggest where should I look for?

I tried to boot pressing switch6 on the EA lpc4357 board, to keep PIO2_7 high during boot.
It didn't help.

I'm using lpcxpresso 7.6.2. I've downloaded also 7.7.2 but the problem is still there.

I'm attaching the Console log:
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&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 = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>
redlink>
redlink>
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Handle = 1
redlink>WireIsConnected 1
FALSE
redlink>WireJtagConnect 1
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>
redlink>CoreList 1
RedlinkAPI: Hardware interface transfer error
redlink>
redlink>
redlink>
redlink>
redlink>
redlink>ProbeStatus
Index = 1
Manufacturer = NXP
Description = LPC-LINK2 REDLINK
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006&mi_00#7&2461c7c3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = JTAG
CoresConfigured = TRUE
PacketSize = 1024
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>exit
[Closed]

Thanks
Regards
0 Kudos
Reply

‎06-15-2016 11:36 AM
890 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Thu Jun 04 10:38:08 MST 2015

Sorry to hear you're having trouble connecting a debug session. First, please provide the revision of your LPCXpresso installation.

Next, search through the task list and kill off any arm-none-eabi-gdb, crt_emu_cm_redlink, or redlinkserv processes you might see. Then, boot the LPC4357 into the ISP using the push buttons on the board, and retry the connection.

In the event this fails, please copy the contents of your console debug log, and post it in your response.

Regards,
LPCXpresso Support
0 Kudos
Reply