topic Target marked as non debuggable ??? in LPCXpresso IDE

Target marked as non debuggable ???

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

Content originally posted in LPCWare by Rob65 on Sun Jun 24 10:13:00 MST 2012
Hm,

this is strange.
I just hooked up a custom board I had on my desk to an LPC-Link interface.
Never had any problems with these boards and guess what ...

I am getting a "02: Failed to connect: Ep(01). Target marked as non debuggable" error.

After looking at the board I discovered that I removed the 3.3V regulator ...
So just to test I removed my board completely. and guess what:
I am still getting "Target marked as non debuggable" :eek:

So the error is wrong. The target is not marked as non debuggable, it's just not reachable.

I fixed the problem (placing a new 3.3V regulator) but I do understand that this can be very confusing to other engineers having problems connecting to their board.

Rob

Re: Target marked as non debuggable ???

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

Content originally posted in LPCWare by FlySnake on Thu Jun 28 01:47:51 MST 2012
I have this problem all the time under openSUSE 11.4 :(
The debugger works only once, after terminating it I need to disconnect usb cable and connect it again. Otherwise debugger will not work with this error.
But OpenOCD + J-Link works pretty stable :)

Re: Target marked as non debuggable ???

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

Content originally posted in LPCWare by researchinnovation on Thu Jun 28 05:01:54 MST 2012

Quote: FlySnake
I have this problem all the time under openSUSE 11.4 :(
The debugger works only once, after terminating it I need to disconnect usb cable and connect it again. Otherwise debugger will not work with this error.
But OpenOCD + J-Link works pretty stable :)

Hi..!!

Sometime usb port number in PC keeps on changing, so select the right port.
Sometime we have to do frequency settings.
Are you able to burn the HEX file?

Thanks & Regards.....:)

Re: Target marked as non debuggable ???

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

Content originally posted in LPCWare by FlySnake on Fri Jun 29 06:53:12 MST 2012

Quote: researchinnovation
Hi..!!

Sometime usb port number in PC keeps on changing, so select the right port.
Sometime we have to do frequency settings.
Are you able to burn the HEX file?

Thanks & Regards.....:)

What frequency settings and port are you talking about?
I can burn hex file through ISP bootloader, but it is nothing to do with LPC-link.
Even "Program flash" via LPC-link sometimes gives me this error and reconnection is the only cure.
I've just tried LPCXpresso 4.2.3 in Windows XP. Guess what? It doesn't work at all with either "Target marked as non debuggable" or "Flash driver not ready" error

Re: Target marked as non debuggable ???

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

Content originally posted in LPCWare by TheFallGuy on Fri Jun 29 07:56:32 MST 2012

Quote: FlySnake

I've just tried LPCXpresso 4.2.3 in Windows XP. Guess what? It doesn't work at all with either "Target marked as non debuggable" or "Flash driver not ready" error

That implies there is something wrong with you hardware..

Have you booted your target into ISP?

Re: Target marked as non debuggable ???

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

Content originally posted in LPCWare by FlySnake on Fri Jun 29 14:36:02 MST 2012

Quote: TheFallGuy
That implies there is something wrong with you hardware..

Have you booted your target into ISP?

Yes, from ISP it works but, again, only 1 time. Start debug, terminate it, boot into ISP, start debugger and in GNU/Linux I get either "Target marked as non debuggable" or "Flash driver not ready" in Windows "No emulator/board available".
Hmm, maybe it's really problem with my LPCXpresso 1769 emulator board. Without Rob65's topic I would have never thought about it.