crt_emu_cm3_nxp and CRP1

[gogamoga]

Originally Posted by blasiis

...The error messagge "Ed:02: Failed on connect: Ep(01). Target marked as not debuggable" is misleading

The errors reported by IDE are totally useless. And, targets are marked non-debugable returned by crt_emu_cm3_nxp all the time (at least on my lpc11u14)

check this out:

./crt_emu_cm3_nxp -info-target -wire=winusb

All the error codes come from there

[blasiis]

check this out:

./crt_emu_cm3_nxp -info-target -wire=winusb

All the error codes come from there [/QUOTE]
This command reply same:
Ed:02: Failed on connect: Ep(01). Target marked as not debuggable.
Et: Emu(0): Connected. Was: None. DpID: EDB6. Info: T1S6RGRIA

Anyway now I have understood the problem and is OK !
----------------------------------------------------------------------------------------
Let me give you another little question: In my production, can I use the executable crt_emu_cm3_nxp without installing lpcxpresso ?

[gogamoga]

You can as long as you include dependencies such as libLPC_Link.so and LPCXpressoWIN.enc and probably the dfu-util and the old libusb-0.1
(not sure about the license of nxp and CodeRed software)

Generally, the required dependencies are just 2 thing: the libLPC_Link.so and LPCXpressoWIN.enc, you can get along with dfu-util that is already present on the system (I have one on FreeBSD and i am using it actually)

And... take a look at my thread

I have made open version of libLPC_Link (as a part of my effort porting this shit to FreeBSD)

You might find something usefull in the source code.
crt emu communicates with the devboard via this solib.

Lol, just remembered some extras. there are xme and xml files that are also required dependencies.
the ones you need depend on your board. Just make a copy of crt_emu_cm3_nxp somewhre outside the lpcxpresso/bin, copy the libLPC_Link.so into it and try running the crt_emu_cm3_nxp and see what it complains about.

PS.
Eventually i am planning to make opensource out of all the lpcxpresso toolset, but it will take quite a while (too much reversing to be done)

[ju2low]

Hello everyone,

I recently received my new LPCLINK and its Cortex M3 1769, and unfortunately I have this recurrent message.

I'm rookie with all this NXP & XPRESSO stuff so I'm looking for your help !!!

My situation:
Plugged on front USB port on my computer with LPCLINK

I have tried to erase memory but I received this
---------------------------------------------------------------------------------------------------------
PROGRAM FLASH
crt_emu_cm3_nxp -g -2 -vendor=NXP -pLPC1751 -s250 -flash-mass -wire=hid

Pc: ( 0) Reading remote configuration
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
Nc: Looked for chip XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpresso/bin/LPC1751.xml

Nc: Looked for vendor directory XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpresso/bin/nxp_directory.xml

Nc: Found generic directory XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpresso/bin/crt_directory.xml

Pc: ( 5) Remote configuration complete
Xe:
Pc: ( 15) nSRST assert (if available)
Ed:02: Failed on connect: Ep(01). Target marked as not debuggable.
Et: Emu(0): Connected. Was: None. DpID: EDB6. Info: T1S6RGRIA
Error 0: (null)
Last sticky: 0. AIndex: 0
---------------------------------------------------------------------------------------------------

I have FLASHMAGIC but also with this program, I can't establish communication for read ISP security... something about autobaud with ALL Baudrate...

Sorry for the long post...

Keep looking for solutions....

[TheFallGuy]

"Target marked as not debuggable" normally means that you have set CRP in your target. That will have disabled debug and so LPC-Link (or any other debugger) cannot connect. Depending on which CRP you have set, you may be able to erase the flash by using FlashMagic through a serial port and recover your chip.

[ju2low]

Originally Posted by TheFallGuy

"Target marked as not debuggable" normally means that you have set CRP in your target. That will have disabled debug and so LPC-Link (or any other debugger) cannot connect. Depending on which CRP you have set, you may be able to erase the flash by using FlashMagic through a serial port and recover your chip.

If I have used CP3, is it possible to reset LPC1769 ? How ?

[Zero]

CRP3 0x43218765 This is similar to CRP2, but ISP entry by pulling P2.10 LOW is disabled if a valid user code is present in flash sector 0.
This mode effectively disables ISP override using the P2.10 pin. It is up to the user’s application to provide for flash updates by using IAP
calls or by invoking ISP with UART0. Caution: If CRP3 is selected, no future factory testing can be performed on the device

If you haven't provided IAP / or ISP functions in your code, your LPC is now locked successfully and just pulling low P2.10 isn't working

[ju2low]

Originally Posted by Zero

If you haven't provided IAP / or ISP functions in your code, your LPC is now locked successfully and just pulling low P2.10 isn't working

So, Did I break my LPC Board?

[Serge]

Yes, if you have set CRP3 and did not provide the IAP calls in your program then you succesfully brought your LPC1769 to his end.

Was indeed a 1769. My mistake Zero. I own you a case of beer. Would a nice Belgium Kriek beer be ok?

[Zero]

Originally Posted by Serge

...your LPC1343...

LPC1343