Undocumented error

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

Undocumented error

970 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MindBender on Fri Jun 12 01:41:27 MST 2015
My freshly installed LPCXpresso (v7.8.0 [Build 426] [2015-05-28]) is reporting an error in red in in the bottom status bar:
[color=#f00]Target error from Register ...Ee(FF). Undocumented error.[/color]
I was just single-stepping my code when it occured.

Cat you:
1. Please solve this error.
2. Document the error.
0 Kudos
Reply
5 Replies

960 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Mon Jun 15 01:42:02 MST 2015
I use LPC-Link2 (originally with Redlink, but now with CMSIS-DAP) and can build/debug all day and very rarely have to unplug it. It is all pretty solid to me. The only time I get problems is when putting the target into various sleep modes (which takes SWD away).

If you don't think CMSIS-DAP is stable, try try J-Link.
https://www.segger.com/nxp-lpcxpresso.html

There is a J-Link image for LPC-Link2, so you don't need to buy anything else. Latest J-Link image is supplied with (and can be programmed using LPCScrypt)
http://www.lpcware.com/content/forum/lpcscrypt-latest-release

If you have similar issues, start looking at exactly what your s/w is doing (e.g. are you disabling debug, or re-using the debug signals?)
0 Kudos
Reply

960 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MindBender on Mon Jun 15 01:18:31 MST 2015

Quote: LessThanZero
Here's a couple of things to try. First, select the SWD protocol if, in fact, you're using the JTAG protocol. If you don't need to access other devices on the JTAG scan chain, SWD is sufficient.


I don't have any other devices on my scan chain, so that applies. Can you please tell me where that setting is hidden?
I'm still using J7 on my LPC-Link2 interface, since it says: "SWD/JTAG".

Quote: LessThanZero
Second, you can use the Redlink probe in place of the CMSIS-DAP one. This can be changed at Preferences -> LPCXpresso -> Redlink Options -> Redlink boot type.


[s]Did that, changed emulator to Redlink Server, but got an error while downloading now: "Error in final launch sequence". Details indicate Wire Ack Fault and recommendations stretch to power-cycling.
I've been going through the schematic, to see if my EA LP1788 board supports SWD, but it's a bit messy: Signal wires end up in what appear to be tags and it's a puzzle to figure out where they go. Perhaps they overlap with JTAG, perhaps I need to put the interface in SWD mode, but I feel I'm debugging the environment now and I just don't have time for that.[/s]
That seems to work, but it's no improvement: RedLink looses the processor much more frequently. Stepping over sdram_init always fails.

On a side note: I find myself unplugging and replugging the LPC-Link2 a lot. I'm not complaining here; It's a $15 debugger and what you pay is what you get. But I wonder if there are any non-hobby-grade, more stable debuggers available on this platform? For example, I was very happy with my BDI2000 form the i.MX28 ARM9.

Thanks for the hints so far!
0 Kudos
Reply

960 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by LessThanZero on Fri Jun 12 14:52:44 MST 2015
Here's a couple of things to try. First, select the SWD protocol if, in fact, you're using the JTAG protocol. If you don't need to access other devices on the JTAG scan chain, SWD is sufficient. Second, you can use the Redlink probe in place of the CMSIS-DAP one. This can be changed at Preferences -> LPCXpresso -> Redlink Options -> Redlink boot type.

LessThanZero
0 Kudos
Reply

960 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MindBender on Fri Jun 12 04:37:58 MST 2015
Thank you for picking this up so quickly! I really appreciate it.

The board is an Embedded Artists LPC1788 board, with an Embedded Artists 4.3" display board. I was using a LPC-Link2 JTAG interface and the application I was running was the Embedded Artists demo application that came with the board.

What I was doing, was stepping through the code, from the top, using 'step over'. One function took a little long, so I suspended execution and continued 'stepping over' in the slow function (Decode PNG) and after a couple of steps I lost control over the target with the reported error.

I have tried to reproduce this taking the exact same steps, but it (un)fortunately it didn't go wrong the three times I have tried.

Is there a log somewhere I can post?
0 Kudos
Reply

960 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Jun 12 03:39:51 MST 2015
"Undocumented error" means exactly what it says - we received an error from the Cortex-M3 target that is undocumented. That is, it is not documented by ARM - we can't document it!

To help us understand how this occured, please provide as much information as possible:
- what is the board
- what is the application
- what exactly are you doing when you receive this error. Do you get it every time, or just once.
- please post the Debug Log (http://www.lpcware.com/content/faq/lpcxpresso/debug-log)
- please provide the contents of the "gdb traces" console.


0 Kudos
Reply