Ee(02) on custom board after programming sample UART code

lpcware · ‎06-15-2016

Content originally posted in LPCWare by victorpau on Mon Jul 12 00:29:20 MST 2010
Hello

I've been developing and debugging some code with LPCXpresso for a custom board with a LPC1114/201. I was programming it many time and it was working great, but then I programmed both of my custom boards with different code for a test, and I cannot program them anymore. (But I can programm the sample LPC1114/301 that comes with the LPC-Link)

The LPC1114/201 is working properly (I can test in my custom board using serial communication with the main processor of the board) but I'm always getting the error:

Quote:
02: Failed on connect: Ee(02). Not connected to emulator.
Emu(0): Connected. Was: None. DpID: EDB6. Info=T1S6RGRIA
Err 0: (null)

I've tried the solutions from http://lpcxpresso.code-red-tech.com/LPCXpresso/node/44 . But the ISP mode doesn't solve the problem neither the Vector catch does. I'm sure I'm getting into the ISP mode because the serial port of the processor stops replying as I programmed it, so the LPC1114 is not working anymore until I restart the board.

And some extra info: Windows 7 32 bits Spanish. Software version 3.3.4 (version 3.4 doesn't even work for me on the sample LPC1114/301)

If you have any idea or suggestion about why this can be happening I'll be really grateful.

Victor Pau

lpcware · ‎06-15-2016

Content originally posted in LPCWare by micrio on Tue Jul 20 07:34:58 MST 2010
If you have not provided a backdoor that erases the security word then you are dead.

If you wnat to protect yourself in the future, you should implement a backdoor erase function. You could examine certain input pins and look for a special pattern and then erase all flash. You want to erase all flash, not just the security fuse. This should maintain security for your code.

If someone inadvertantly hits your secret I/O pin pattern then the device becomes useless to him so make sure that it will not happen in normal use.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by victorpau on Tue Jul 20 05:48:09 MST 2010
Hello

I found the problem. It seems that while I was programming the chip I activated accidentally the CRP3, so the LPC1114 is completely isolated now. I've been using other micro-controllers before and I was expecting that the protection only avoided other people to read the code, not myself to program it again (As it's called Code Read Protection I didn't expect it to avoid writing)

So I think the only way that I have is to change the chip from the board for a new one, isn't it?

It would be nice if LPCXpresso showed some warning when you choose to program the device with CRP3 so people doesn't do it by mistake.

Regards,

Victor Pau

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Mon Jul 12 01:28:44 MST 2010
This message is reporting that the debugger is unable to connect to the target. The most obvious reasons for this are:
- you have run code on the target that has disabled the debug access or incorrectly set he clock (PLL)
- the target is crashing very early in the startup code
(these problems should be resolved by the solutions you said you had tried)
- the SWD pins are not correctly connected.

If you say the standard solutions don't work (and we have never known them to fail on correctly designed hardware) I would suggest that you review your SWD circuit.

Also, you mentioned v3.4 doesn't work for you. What errors were reported?