LPC Link timeout

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Sat Feb 26 05:43:13 MST 2011
Hello!

Today I've got my lpcxpresso board and installed the lpcxpresso IDE. Connected with a usb cable I'm trying now to build and flash the device. But it doesn't really work: LPC Link v1.1 Timeout.

The log file is attached. I'm using WinXP with SP3, not in a VM. LPC Driver seems to be installed..

Can you help me?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Sun Apr 24 20:48:39 MST 2011

Quote: be80be
Larry I posted what happens with the old board

The new board works fine the old one will not boot the debugger here the setupapi.log

It appears that you did not read or understand the previous post or the information at the link I provided.:mad: This is an alternate method to recover your board.

I also asked you to continue your replies in the thread that you originally posted your problem to. Now your problem is split up in two threads. Please only post to the other thread.:eek:

I can not help you if you do not follow the instructions or advice I have given you.:(

Do not reply here. Reply in the other thread only.:)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by be80be on Sun Apr 24 20:38:16 MST 2011
Larry I posted what happens with the old board

The new board works fine the old one will not boot the debugger here the setupapi.log

Larry the post here look more in line with what is going on LPC Link timeout figure we could save some head acks

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Sun Apr 24 20:22:26 MST 2011

Quote: be80be
This is what I get I running Xp pro ser.pack3 it works with new board
this is what it said

I know your new board works fine.

This is not what I was talking about in my previous post.

Your non-working board may be in a state that will not let you use the LPC-Link or the diagnostics.

If you carefully read the information provided at the link and use that method you may be able to regain access to the LPC-Link.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by be80be on Sun Apr 24 20:06:12 MST 2011
This is what I get I running Xp pro ser.pack3 it works with new board
this is what it said

Quote:
Error received while booting LPC-Link v1.1
Timeout waiting for LPC-Link to initalization
Timeout waiting for LPC-Link to initialize

Quote:
*****************************************************
*** DFU LOG FILE ***
Creation Time : C:\DOCUME~1\burt\LOCALS~1\Temp\dfuApp3505052416556064582.log
*****************************************************

Open Device
Get Device Descriptor successful
Get Configuration Descriptor successful
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is operating in the DFU mode and is waiting for requests.

Device Descriptor
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0200
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40
idVendor: 0x0471
idProduct: 0xdf55
bcdDevice: 0x0001
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

DFU Get State successful
---> DFUState: Device is operating in the DFU mode and is waiting for requests.
Download Block Nb 0 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 1 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 2 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 3 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 4 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 5 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 6 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 7 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 8 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 9 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 10 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 11 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 12 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 13 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 14 (1544 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 15 (0 Bytes)
DFU Get State successful
---> DFUState: Device has received the final block of firmware from the host and is waiting for receipt of DFU_GETSTATUS to begin the Manifestation phase; or device has completed the Manifestation phase and is waiting for receipt of DFU_GETSTATUS. (Devices that can enter this state after the Manifestation phase set bmAttributes bit bitManifestationTolerant to 1.)
DFU Get Status successful
---> DFUStatus: Device’s firmware is corrupt. It cannot return to run-time (non-DFU) operations.
---> DFUState: Device has programmed its memories and is waiting for a USB reset or a power on reset. (Devices that must enter this state clear bitManifestationTolerant to 0.)
Close Device

*** END OF FILE ***

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Sun Apr 24 19:31:24 MST 2011

Quote: be80be

I was wondering if there is some way to reprogram the LPC-Link with my good one.

Probably not as the LPC-Link is proprietary and preprogrammed.

But I posted a suggestion in the other thread that you should try. You shouldn't have given up so soon on us helping you. We should be able to guide you through the process of getting your board working. Just keep your questions related to this in that thread only please.

http://knowledgebase.nxp.com/showpost.php?p=7895&postcount=21

Larry

lpcware · ‎06-15-2016

Content originally posted in LPCWare by be80be on Sun Apr 24 19:00:53 MST 2011
Maybe this will will help you to not go crazy I have a LPC-Link with the LPCXpresso LPC1114 No matter what tried it would not work and about a week ago I got my second one in the mail It worked find on all of my computers

Windows XP , Vista , and 7 The dang LPC-Link on the first one is not booting
the software it should to program and debug the LPC1114

I was wondering if there is some way to reprogram the LPC-Link with my good one.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Sun Mar 27 12:33:10 MST 2011
One other thing; The script defaulted to one of the HID probes. You could find the LPC-Link device in the list of "Human Interface Devices", but you'd need to identify it by the VID/PID. As an experiment, try the WinUSB probe. Run the script as before, but include the winusb command-line argument.

C:\nxp\lpcxpress_3.6\bin\Scripts>bootLPCXpresso.cmd winusb

This probe registers in the Device Manager under "Universal Serial Bus controllers", and you should see an entry like:

"LPC-Link Debug Probe v1.1"

If this probe doesn't register, the board is defective in some way. It could be something as simple as the LPC3154 fuse configuration.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Sun Mar 27 11:41:24 MST 2011
I don't think NXP, CodeRed or Embedded Artists want any dissatisfied customers, even those that received free boards. It wouldn't hurt to ask for a replacement.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Sun Mar 27 11:29:38 MST 2011

Quote: CodeRedSupport
Reading thelogs, it looks like you have a malfunctioning board. You will need to contact your supplier and ask for a replacement.

I've got the board for free in the last NXP campaign. I think no one will replace it..

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Sun Mar 27 11:20:10 MST 2011
Reading thelogs, it looks like you have a malfunctioning board. You will need to contact your supplier and ask for a replacement.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Sun Mar 27 07:14:44 MST 2011
I have installed the IDE and drivers now on a win 7 laptop. Connected the lpcexpresso with a usb cable and the same problem: Timeout.

What the hell I'm doing wrong?

I'm glad I didn't pay for this board and the software. Compared to CrossWorks or AVRStudio it is not the best choice.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Mon Feb 28 11:41:29 MST 2011
I am using the lpclink with the xpresso board. Without a hub, just a usb cable (tried two different cables). Doesn't work.

Booting over command line doesn't help too.

cd <install>\bin\scripts
bootLPCXpresso
--> Booting LPC-Link with LPCXpressoFS.enc
--> Press a key to continue...

lpc link doesn't appear in the list of tasks.

the log file is attached below..

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Feb 28 01:35:50 MST 2011

Quote: twols

Is this a kind of xp-related problem? Would switching to Windows 7 help?

It is not XP related. More than 50% of the thousands of LPCXpresso users are using XP.

Some more suggestions:
- try using a different USB cable. We have had the occasional report where a broken USB cable causes some unusual behavior.
- are you connecting through a hub? Connect LPC-Link directly to the PC.
- are you using a baseboard? If so, remove it and use the LPC-Link/LPCXpresso board standalone
- try booting from the comand line, and then looking to see if your LPC-Link appears in Device Manager

cd <install>\bin\scripts
bootLPCXpresso

- if it does, then start LPCXpresso

lpcware · ‎06-15-2016

Content originally posted in LPCWare by larryvc on Sun Feb 27 20:10:29 MST 2011
I don't know if switching to Win7 would fix your problem or not with your LPCXpresso11xx.

I am running Win7 64-bit and have no problems with an LPCXpresso1769.

You would probably be very happy with Win7 and Micosoft just released Service Pack 1 for Win7 as well.

Make sure your computer and software are compatible with Win7 before making the switch.

I am a little bit biased in this regard. Look at my location.:):):)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Sun Feb 27 11:57:29 MST 2011
Deactivating the firewall and antivir doesn't help. When I start the debugging tool, cscript.exe appears in the list of tasks in the task manager. But the lpc-link doesn't work..

Is this a kind of xp-related problem? Would switching to Windows 7 help?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Sun Feb 27 01:52:42 MST 2011
OK, the most likely reason for this is that your firewall (or perhaps system admin) is preventing LPCXpresso from running 'cscript'. We use this to look for the LPC-Link to become visible on USB. LPCXpresso (as well as the executables in the bin directory) need to be able to run cscript for a variety of reasons.

You will find more information on this by googling:
site:knowledgebase.nxp.com cscript

lpcware · ‎06-15-2016

Content originally posted in LPCWare by twols on Sat Feb 26 14:33:51 MST 2011
I hope it can help.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Sat Feb 26 07:12:02 MST 2011
Can you post your <workspace>/.metadata/.log file?