topic Re: Error launching emulator in LPCXpresso IDE

Error launching emulator

lpcware — Thu, 16 Jun 2016 02:32:23 GMT

Content originally posted in LPCWare by LynnF on Sun Apr 11 13:45:41 MST 2010
Can you tell me what this error is and how to correct?

Error Launching Debug\program name.axf
02: Failed to connect: Ee(02). Not connected to emulator.

Re: Error launching emulator

lpcware — Thu, 16 Jun 2016 02:32:24 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Apr 12 01:19:03 MST 2010
It means it can't find the emulator... i.e. The LPC-Link.

You need to post some details of what you are trying to do, including what you host OS is, and what you are trying to connect to, if we are to be able to help further.

You might also want to read:
http://lpcxpresso.code-red-tech.com/LPCXpresso/node/47
http://lpcxpresso.code-red-tech.com/LPCXpresso/node/45
(login required)

Re: Error launching emulator

lpcware — Thu, 16 Jun 2016 02:32:24 GMT

Content originally posted in LPCWare by LynnF on Mon Apr 12 06:07:40 MST 2010
I am using a LPCXresso with a 1343. I have downloaded to this board many times without issue. Now I get the error. So I tried another board (always have spares) and it works perfectly without error.

However I need to use the first one as it has pins soldered to it for my application.

Re: Error launching emulator

lpcware — Thu, 16 Jun 2016 02:32:25 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Apr 12 07:28:51 MST 2010
In that case, this is likely caused because the last application you were running has tried to set the clock speed to an invalid value. This has been discussed a number of times on the forum. For example, see:
http://knowledgebase.nxp.com/showthread.php?p=1450#post1450

Re: Error launching emulator

lpcware — Thu, 16 Jun 2016 02:32:26 GMT

Content originally posted in LPCWare by LynnF on Mon Apr 12 08:37:43 MST 2010
Thanks, I will try some of these.

Thanks for the link; however I did search for information yesterday and that link I did not see.

Later update:
I was able to ground pin O_1 and recover.