Debug Error

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

Debug Error

12,592 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Ex-Zero on Fri Dec 04 05:25:17 MST 2009
Hi all,
just received my new LPCXpresso, but after importing and building LPCXpresso1343_blinky example clicking "Debug 'LPCXpresso1343_blinky' (Debug)" in Quickstart panel "Initializing LPC-Link..." stops while "Checking Emulator" and shows
"LPCXpresso:Error
Error received while booting LPC-Link:
Timeout waiting for LPC-Link initialization: Timeout for LPC-Link drivers to load"
after a few seconds.
Of course I checked my USB cable and USB Device Driver in Vista. LED2 of the target board is flashing 2 times every second, but I'm not able to start debugging.
Any suggestions are welcome,
Zero
0 Kudos
Reply
25 Replies

12,327 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Tue Mar 02 12:09:17 MST 2010
To follow up on this issue.

The problem turned out to be DB's ant-virus software blocking execution of our license checking code.
DB's anti-virus software offered no way to enable access for a "trusted" list, nor did it warn of an "attack". It did log the error which was how the problem was identified.

Regards,

CodeRedSupport
0 Kudos
Reply

12,327 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Fri Feb 26 00:23:35 MST 2010
Please contact us directly at http://www.code-red-tech.com/contact.php so we can help resolve the problem.

Regards,

CodeRedSupport
0 Kudos
Reply

12,327 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dbudurea on Thu Feb 25 23:52:12 MST 2010
Hi there,

The same result! Crash @ 65%.
Just for the record, I tried the third driver (HS) and the same result.
In my attempt to narrow down the problem I found that this app (crt_emu_lpc11_13_nxp.exe) and the dll it is using (crt_hid_probe.dll) are the cause of my problem.
Replacing them with the ones from v3.0.10, I get passed the error and be able to debug. Just to be clear: all files from v3.2.3 installation but with the two files mentioned above replaced with older versions works. I have tested only the LPC1343 board.

Thanks,
DB  

PS. I really appreciate all the help and quick response but I think I had enough for today. We will continue tomorrow.

The whole "eclipse" folder was replaced with the one from v3.0.10. I forgot about it.Was a long day.....
0 Kudos
Reply

12,327 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Feb 25 22:38:33 MST 2010
From what you posted, am I to understand the crt_emu_lpc11_13_nxp.exe utility has crashed? Let's repeat the '-info-target' experiment once more, but this time we're going to use a different USB driver. From a DOS command prompt, change to the <install>\bin directory once more.

1. Cycle the LPCXpresso Power.
2. DFU the HID probe to the LPCXpresso:
C:\nxp\lpcxpresso_3.2\bin>dfuapp /f LPCXpressoFS.enc
3. Re-issue the '-info-target' command-line, but specify the HID wire option:
C:\nxp\lpcxpresso_3.2\bin>crt_emu_lpc11_13 -g -2 -pLPC1343 -wire=hid -info-target

Please post the results.

Regards,

CodeRedSupport
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dbudurea on Thu Feb 25 22:23:47 MST 2010
Sorry for the confusion. I did not say that is a License check failure error but a "No error" error which I found it mentioned in this thread. It seemed reasonable to me to add to the same thread instead of starting a new one, thinking that they are related.

Here are the results of running the crt_emu_lpc11_13_nxp (the actual exe name has the suffix _nxp // an easy one!!)
2-3 seconds after 65% Chip Setup Complete was displayed, the app encountered a problem and Windows killed it.

I have tried this on two other machines trying to solve the problem myself but I am starting to think, that is not something I can do(old v3.0.10 works fine).
One has Vista Home and it worked fine, the other XP Pro (like the one I am struggling with) that failed too.
I have tried to even shorten the path variable just in case a very long path (from various installed apps) will cause any problem and disable the AVirus. Nothing seems to change anything.


Thanks, I am still trying a few more things on my own.....

DB
 
 


Quote: CodeRedSupport
This isn't a "License check failure (CheckLicense)", so let's back up. It's possible there's been a problem with the driver installation. Cycle the power to the LPCXpresso evaluation board. The following instructions pertain to the LPCXpresso v3.2 IDE.
......
C:\nxp\lpcxpresso_3.2\bin>crt_emu_lpc11_13 -g -2 -pLPC1343 -wire=winusb -info-target

Please post the results from this capture.

Regards,

CodeRedSupport

0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Feb 25 20:59:38 MST 2010
This isn't a "License check failure (CheckLicense)", so let's back up. It's possible there's been a problem with the driver installation. Cycle the power to the LPCXpresso evaluation board. The following instructions pertain to the LPCXpresso v3.2 IDE.

1. Open a DOS cmd window, and  change to the LPCXpresso <install>\bin directory.
2. Issue the following command-line:
    C:\nxp\lpcxpresso_3.2\bin>dfuapp /f LPCXpressoWIN.enc
 
3. From the Windows Control Panel, open the Device Manager and confirm Windows has recognized the LPCXpresso.

If you're using the LPCXpresso v3.2 IDE, you should see an entry for "LPC-Link Debug Probe v1.1"  under "Universal Serial Bus controllers". If there is an installation issue, Windows will notify you to install the driver. The installation file is <install>\Drivers\LPC-Link\LPC-Link.inf

Once you see evidence in the Device Manager the probe has installed, issue the following command:

C:\nxp\lpcxpresso_3.2\bin>crt_emu_lpc11_13 -g -2 -pLPC1343 -wire=winusb -info-target

Please post the results from this capture.

Regards,

CodeRedSupport
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dbudurea on Thu Feb 25 18:26:02 MST 2010
Hi,
Thank you for the quick reply but this solution does not work for me.
In the mean time I have tested v3.1.4 that is supposed to have this fixed and I get the same "No error" error as with all the other later versions.
I have gone back and forth numerous times between all newer versions and v3.0.10 and all fail while the oldest v3.0.10 works just fine.
I would not have a problem and wait for a solution but I am testing  both LPC1114 and LPC1343 boards and this old version does not support the LPC1114. This path solution does not seem to affect anything.
Maybe support fo LPC1100 has caused this in all the newer versions???

I have attached a screen shot of failure while trying to debug/download using v3.2.3. While this screen shot was taken when using the LPC1114 board, the same error comes up with LPC1343.

Thanks again,
DB



Quote: CodeRedSupport
Last week, a Windows XP user encountered an issue where the target debug utility (in a separate process) not able to interrogate the PC in order to validate the license. For an unknown reason, the system path was not available to this process. This was worked around by[FONT=Times New Roman] adding the "C:\Windows\system32" path in the LPCXpresso IDE "Additional  Path directories". From the menu:[/FONT]
[FONT=Times New Roman]Windows ->  Preferences -> LPCXpresso -> Common[/FONT]

[FONT=Times New Roman]enter the  "C:\Windows\system32" path in the dialog. This presumes Windows is installed  on drive "C:". Otherwise, use the appropriate drive/path designation, and post your results.

Regards,

CodeRedSupport
[/FONT]

0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Feb 25 17:06:22 MST 2010
Last week, a Windows XP user encountered an issue where the target debug utility (in a separate process) not able to interrogate the PC in order to validate the license. For an unknown reason, the system path was not available to this process. This was worked around by[FONT=Times New Roman] adding the "C:\Windows\system32" path in the LPCXpresso IDE "Additional  Path directories". From the menu:[/FONT]
[FONT=Times New Roman]Windows ->  Preferences -> LPCXpresso -> Common[/FONT]

[FONT=Times New Roman]enter the  "C:\Windows\system32" path in the dialog. This presumes Windows is installed  on drive "C:". Otherwise, use the appropriate drive/path designation, and post your results.

Regards,

CodeRedSupport
[/FONT]



Quote: dbudurea
Hi to everybody,

I just got my lpcxpresso board and tried it when I run into the same problems as you guys mentioned here and seemed to be fixed in version v3.1.4. This thread was indeed very helpful, especially the one that pointed that an old version worked fine.
I have tested the latest V3.2.3 and v3.2.1. Both failed. This is when I downloaded and installed (all in different folders) v3.0.10 that was proven to work and indeed it worked.
With the latest two versions I get the "No error" error. Is this back?
I have not tested v3.1.4 and v3.1.2 (yet...).
Any comments?

Thanks,
DB

0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by dbudurea on Thu Feb 25 15:10:02 MST 2010
Hi to everybody,

I just got my lpcxpresso board and tried it when I run into the same problems as you guys mentioned here and seemed to be fixed in version v3.1.4. This thread was indeed very helpful, especially the one that pointed that an old version worked fine.
I have tested the latest V3.2.3 and v3.2.1. Both failed. This is when I downloaded and installed (all in different folders) v3.0.10 that was proven to work and indeed it worked.
With the latest two versions I get the "No error" error. Is this back?
I have not tested v3.1.4 and v3.1.2 (yet...).
Any comments?

Thanks,
DB
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Doctor N. Gin on Tue Dec 29 12:20:06 MST 2009
great it works!

now let us find the other bugs...

… I mean in my software ;-)
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Tue Dec 29 01:10:08 MST 2009
We have just released v3.1.4 that fixes the 'License check' errors reported by a number of users in this list.

To obtain this new version, visit the Downloads page on http://lpcxpresso.code-red-tech.com/LPCXpresso (login required).
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by domen on Sat Dec 26 10:59:34 MST 2009
I too get an "LPCXpresso: Error" dialog
with contents:
Error launching Debug\blinky.axf
License check failure (CheckLicense)

I also tried downloading firmware as described before in this thread... all worked fine, (I see the hid device in device manager) except the LPCXpresso still does not want to cooperate with me.

Operating system Windows XP pro 32-bit, all updates, installed yesterday.

Also let me bitch about this for a bit.
This is the third day I'm wasting to run the hello world app?!!
First I fought with various virtualized Windows, reinstalling them, trying different virtualization software etc. Then I carried the board to a friend with native Win XP, and it even worked, but I obviously can't just take her computer. Now I tried it at another computer at parents, and of course (!) it didn't work with 64-bit Windows, so I had to reinstall it with 32-bit, and now it still DOESN'T WORK :-(
Am I really that spoiled with non-proprietary development tools just working?!
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Doctor N. Gin on Sat Dec 19 03:30:23 MST 2009
I have found a workaround für my problem.

First, I uninstalled the LPCXpresso v3.1 (lpcxpresso_3.1.2_132.exe).
Then I installed the old version LPCXpresso v3.0 (lpcxpresso_3.0.10_110.exe).
Now debugging works without problems.
In a second step, I have installed the new version in another directory.
Result: The old version works, the new do not (same error as before).
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Fri Dec 18 09:56:33 MST 2009
Hi,

Can you email us at support at code-red-tech.com and we will try to get you through this.

Thanks
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by anders@trebax on Fri Dec 18 09:12:54 MST 2009
Hi all,

Same problem here.
I get "[B]Licence check failure (CheckLicense)[/B]" when I try to debug the example blinky project.

If I try to debug a second time without dissconnecting the board or restarting LPCxpresso I also get:
[FONT=Courier New][SIZE=2]
No symbol "new" in current context.
set remotetimeout 60000[/SIZE][/FONT]

from [B]arm-none-eabi-gdb[/B] in the console window

Mail sent to Code Red.

/Anders
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Dec 17 01:19:10 MST 2009
Hi Dr Gin,
Could you email your details to support at code-red-tech.com and somebody will deal directly with your issue. This is not a known problem, so we will need some closer interaction with you to try to resolve the problem you are having. This will be a lot quicker if we can deal with you directly, rather than through this forum.

When we resolve the issue, we will report back to this forum.
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Wed Dec 16 13:49:09 MST 2009
Can you provide *exact* details of the error you are getting please? That is, all of the text that is being displayed?

Thanks
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Doctor N. Gin on Wed Dec 16 13:34:03 MST 2009
Hello!

I have a similar problem.
But the error message is "License check failure".
The device seems to work properly.
I've followed the steps 1 to 11.
The firmware "LPCXpressoFS.enc" is loaded because
my LPCXpresso v3.1 (lpcxpresso_3.1.2_132.exe) is installed under WindowsXP.
In addition, the software is "fully activated".

Do you  know how to get along here?
Thank you for your trouble.

Yours faithfully,
Doctor N. Gin
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Wed Dec 09 10:19:59 MST 2009
Hi,

We think we have found the issue that is causing this problem (and Zeros). If you send an email to support at code-red-tech.com we can make a new installer available that should resolve this issue.
0 Kudos
Reply

12,326 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by iccy on Wed Dec 09 02:37:49 MST 2009
Hi,
I've also encounter debug error which shows "Error launching Debug\LPCxpresso1343_blinky.axf.  Remote communication error: No error" .  I have check thru' the Debug Configuration but found nothing wrong.

I have also done "dfuapp /s gui" and able to detect the hid, but it doesn't seem to help.  Is there other configuration that I have missed out? 

iccy
0 Kudos
Reply