Error launching debug

[lpcware]

Content originally posted in LPCWare by unnati on Tue Mar 09 03:16:41 MST 2010
i am using LPC1114.

i have created a project named "porttest".when i try to debug it, an error occurs showing:

"Error launching Debug\porttest.axf
02:Failed on connect : Ee(02). Not connected to emulator."

also i want to know that is it necessary to use external crystal for 12MHz frequency.

plz help me out...

[lpcware]

Content originally posted in LPCWare by Brinkand on Thu Mar 18 07:37:58 MST 2010
I finally found the solution to the problem, which I report in the hope that it will help others.

The problem has the following symptoms:
- The Xpresso is not detected by windows when plugged in - or it disapears when launching debug mode.
- The Xpresso cannot be seen in device manager
- After the bug appears, no new USB devices (e.g. mouse) are detected,
but already running USB devices keeps running.
- Windows has problems shutting down.
- Problem is intermeddiant. No trigger mechanism has been identified.
- If Xpresso has been successfully launched, it keeps working.

I used the following Microsoft fix to remove the problem:
http://support.microsoft.com/kb/817900

I use a Lenovo W500 Thinkpad with Windows XP SP3.

[lpcware]

Content originally posted in LPCWare by Brinkand on Thu Mar 11 04:08:37 MST 2010
Thank You igorsk for the DFU explanation and CodeRedSupport for the DFU checking method. Using those I made some progress:

[SIZE=2]This morning, the connection worked at first attempt. Since I did not change anything since yesterday, I took the chance to check through my equipment.

The USB voltage is down to 5.05V before programming the LPC3154 and 5.02V when programmed. (LCP1114 running full speed in both cases with 1 timer and 1 led flashing 50% of the time.) on the new cable. The old cable has slightly lower voltage drop.

I checked both cables with Your FDU programming procedure. They both work.
I checked both the LPC1343 and LPC1114 Xpresso with DFU too. They both work. The LPC1114 Xpresso has no circuitry connected; the LPC1343 Xpresso has circuitry on PIO_1_9 and PIO_1_11.

With the LPC1343 I get the Error 03: Failed on chip setup: Et: Flash driver not ready. The error comes only at first attempt to enter debug efter connecting the cable. All other times, it connects without flaws. LPC1114 Xpresso never fails to connect.[/SIZE]

Then suddenly the error state from yesterday reappeared with no way of getting in contact with the device. But I noted that the device list no longer got updated. Neither when I plugged the Xpresso in or out or when doing the manual DFU-trick.

For some reason windows stops detecting when I plug the Xpresso in or out. when it fails to do so, the DFU trick sometimes can bring it back into working state again. But the process seemed unreliable. I proceeded troubleshooting the USB connection by upgrading BIOS and USB-drivers. So far this brought me back on track with unsurpassed response speed of the debug start up.

Currently the system is running and I will return if I learn more about the situation.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Mar 10 12:32:39 MST 2010
The power is still suspect. Based on the fact you've replaced your USB cable, I'll presume it's ok. Have you made any modifications to the LPCXpresso hardware (e.g added push button or other)?  I know we caution against using external hubs, but if you have access to an external hub with it's own power supply, you should plug into it and see if there's a difference in behavior. This may help to pinpoint a potential problem with the power supplied by your port.

Given the fact you've seen an entry for the DFU device in the Device Manager, please attempt to manually download a probe image to the LPCXpresso. For the purpose of this test, please use the LPCXpressoWIN.enc probe image.

Example:
C:\nxp\lpcxpress_3.2\bin>DFUAPP.exe /f LPCXpressoWIN.enc

Open the Windows Device Manager. If the probe has downloaded correctly, and initialized (regardless of what DFUAPP.exe reports), you'll notice the "USB Device with DFU Capabilities" entry is replaced with "LPC-Link Debug Probe v1.1".

Please report back.

Regards,

CodeRedSupport

---

Quote: Brinkand
I am not using any hub. And the cable is less than 1m.

---

[lpcware]

Content originally posted in LPCWare by Brinkand on Wed Mar 10 10:31:24 MST 2010
I am not using any hub. And the cable is less than 1m.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Mar 10 09:49:14 MST 2010
Brinkand,

Can you confirm whether you are connecting the LPCXpresso board directly to your PC, or if you connecting via a usb hub?

Usage through a hub is not recommended, and we have certainly seen cases where a particular hub will sometimes work, and at other times won't.  Other hubs will not work at all.

Regards

CodeRedSupport.

[lpcware]

Content originally posted in LPCWare by igorsk on Wed Mar 10 09:21:39 MST 2010
I can't help you with the problem but I think I can answer a question...
Even though DFU means "Device Firmware Upgrade", it's not actually used to "upgrade" firmware in LPC-Link. The LPC315x chip does not have any built-in flash, so the firmware has to be loaded into RAM every time after it's powered up. The DFU protocol is used for that.
After the firmware is loaded, LPC-Link becomes a debugger dongle, handles requests from IDE and drives SWD pins to the target chip to program and debug it.

[lpcware]

Content originally posted in LPCWare by Brinkand on Wed Mar 10 08:20:54 MST 2010
Thank You for your quick replies so far.

I bougth a new USB 2.0 cable. No change.

I measure 5.09V at the USB connector on the Xpresso board and applied the oscillocope to check for voltage droops. The voltage is rock solid even though I am working from a labtop. Never drops under 4.88V.

I cannot enter debug mode at all. When I press debug, the splash screen (Initializes LPC-Link) shows up and the process just freezes. After a while, there is a meny box saying "timeout waiting for LPC-link to initialize. If this is the first time after installation, your drivers may not have finished loading." Progress percentage is 57.

It has worked fine on this PC before. The hardware is OK.

How do I find the problem or reset the system? I have reinstalled the LPC3.2.3_152 but it knew the licence key and workspace looked same as before, so I assume all settings were retained.

The LED on the LPC3154-part of the Xpresso is now off all the time. Previously it was flashing during debug.

What is this DFU? Are You compiling the flash of the target into the flash of the LPC3154?

Please provide me with ways to track down the problem or to restore the original configuration.

I have used all day on this problem. There's gotta be some kind of explanation.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Mar 10 05:16:00 MST 2010
Hi,

Yes, that is what I would expect. It could be a number of issues:
- there is not enough power being supplied to the board (USB ports are very very bad at providing the spec'ed power requirements)
- the cable is unreliable
- the cable is not correctly inserted

We have seen this many times, and in nearly every case, it is because of some issue with USB that is outside of our control.

Your logs all report
"Received DFU_DNLOAD with wLength = 0, but device does not think it has all of the data yet."
Which means there has been a problem transferring the data to the part. I suspect it is a power issue.

[lpcware]

Content originally posted in LPCWare by Brinkand on Wed Mar 10 02:38:23 MST 2010
Do you expect a USB problem with a cable and a port that previously worked? Clearly the USB bus can communicate as seen in the logs attached, but it is curious that the communication halts at exactly the same point in the communication. If I had spurious errors on the USB bus I would expect the errors to happen at random times.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Mar 10 02:17:08 MST 2010
Given your history, I would suspect a problem with either your USB cable or the USB port that you are using.

I see no point in reinstalling either LPCXpresso or the drivers.

[lpcware]

Content originally posted in LPCWare by Brinkand on Wed Mar 10 02:02:09 MST 2010
I am having the same problem.

I worked with Xpresso LPC1343 first, and had some problems with some of the USB ports - but found one which is working most of the time. I could build and debug with no problems.

I switched to Xpresso LPC1114 and I could build and debug for some time with no problem. Now, my connection is down - debug connections gets some kind of connection problem - Application on the LPC1114 stops toggling the LED, but after a minute or so (progress stalled at 80%-96%) [IMG]file:///C:/DOCUME%7E1/RASMUS%7E1.AND/LOKALE%7E1/Temp/moz-screenshot-2.png[/IMG]I get this:
Error launching Debug/filename.axf
02: Failed on connect: Ee(83). Device not opened (internal).

The build reports no errors or warnings.

The problem did not arrive at a time where I was doing some major change in my setup; I had the expresso connected to an external setup, which I supplied from an external supply for some time (5.1V at pin 1 and 2 of the extension header). It worked fine for a while and now I get no connection. Removing the external setup does not help connectivity.

I have seen similar problems on the Atmel Dragon development board, which has a DC-DC converter from 5V USB input voltage to 5V internal supply - probably to obtain more stable voltage. It burns when connected to USB output with too high internal resistance. I see no similar DC-DC converter on the Expresso, but the dependence on USB-parameters might be the explanation.

I double checked with the LPC1343 board - and now I cannot access it either.

How do I reinstall drivers or in any other way reconnect the Xpresso?

[lpcware]

Content originally posted in LPCWare by unnati on Wed Mar 10 00:42:44 MST 2010
i used an external 12MHz crystal and it started working perfectly..

so i think it is necessary to use external crystal for programming purpose.

[lpcware]

Content originally posted in LPCWare by NXP_Europe on Tue Mar 09 07:29:59 MST 2010
Hi unnati

---

Quote:
i have created a project named "porttest".when i try to debug it, an error occurs showing:

"Error launching Debug\porttest.axf
02:Failed on connect : Ee(02). Not connected to emulator."

---

It indeed seems that the project wasn't build correctly.
A other thing that might cause this error when the drivers for the LPClink wasn't installed yet.
If you could share your project, we could have a quick peek what the problem is.

---

Quote:
also i want to know that is it necessary to use external crystal for 12MHz frequency.

---

Nope, there is a 12MHz (+/- 1%) internal clock (IRC) on the LPC1100 family, so you can just use that one instead.

Kind regards,

[lpcware]

Content originally posted in LPCWare by wrighflyer on Tue Mar 09 04:07:06 MST 2010

---

Quote: unnati
"Error launching Debug\porttest.axf
02:Failed on connect : Ee(02). Not connected to emulator."

---

Isn't that the error you get when there's been a build error and porttest.axf simply has not ben created? I'd go back and look at the build output for errors.