LPCXpresso LPC1114 Debug-"Error"

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Thu May 06 04:48:57 MST 2010
When I start a debug session I always get the following error message box first:

Errors from: 'crt_emu_lpc11_13_nxp -mi -info-emu' Premature end of file.Ni: LPCXpresso Debug Driver v2.0 (Jan 23 2010 11:18:57)

When I press the OK button (the only option) the launch process resumes and the debugger seems to work properly.

Is this just some annoying misconfiguration error which has no real meaning for debbuging or is there some trouble lurking? And how can I fix this?

Context:
- unmodified LPCXpresso LPC1114 board
- LPCXpresso v3.3.4
- XP Pro
- blinky example (or any other)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Mon May 10 01:58:14 MST 2010
OK, I have contacted Code Red directly. If there is a solution, I´ll post it here.

Update 2010-05-11:

This "error" is no real error, at least for those, who are not using Red Probe as debug interface.

<snip>
The error message is reported while LPCXpresso IDE is looking for possible debug targets. The one that is 'failing' is looking for a Red Probe, so as you do not have a Red Probe it is irrelevant.
</snip>

They are going to investigate this, so maybe it will be fixed in some future version. Till then click OK and don´t worry.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Sat May 08 21:11:32 MST 2010
Until it abruptly ends, nothing seems out of the ordinary in your debug log. The last operation that can be verified is a read of the xPSR register. The IDE should next issue a series of monitor commands for further setup, but I see nothing happen. It was mentioned earlier Code Red has not seen this before. Please contact our support site directly, so we can help to resolve this.

http://www.code-red-tech.com/support.php

Regards,

CodeRedSupport

Quote: trazoni
Please see the appended file for the MCU debug log console content.

When the error occurs, the console window is still empty. Only after acknowledging both of the error message boxes (first the Windows crash report and then the error message of the program itself), the appended log file builds up.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Fri May 07 01:20:21 MST 2010
Please see the appended file for the MCU debug log console content.

When the error occurs, the console window is still empty. Only after acknowledging both of the error message boxes (first the Windows crash report and then the error message of the program itself), the appended log file builds up.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 06 15:48:46 MST 2010
The output from your command-line experiments is correct. If you didn't need to DFU the probe image to your board, it means the LPCXpresso IDE is configured to use WinUSB and had already configured the probe. The next thing to do is turn up the "Debug Level" setting to capture more information. This is found:

Run -> Debug Configurations... -> C/C++ MCU Application -> <your project> -> Debugger (tab) -> Target configuration (tab) -> Debug Level

Set it to 4, and attempt to connect. After you see the problem, copy the contents of the Console MCU Debug Log and post it in an attachment. It would be best to ensure the console is cleared beforehand, so only the log data from the last run is included.

Thanks,

CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Thu May 06 10:41:23 MST 2010
[FONT=Courier New][FONT=Arial]Here is the output of the first command (WinUSB seemed to work):
[/FONT]
c:\nxp\lpcxpresso_3.3\bin>crt_emu_lpc11_13_nxp.exe -g -2 -pLPC1114/301 -wire=winusb -info-target
Pc: ( 0) Reading remote configuration
Ni: LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:57:58)
Nc: Looked for chip XML file in C:/nxp/lpcxpresso_3.3/bin/LPC1114/301.xml

Nc: Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.3/bin/nxp_directory.xml

Nc: Found generic directory XML file in C:/nxp/lpcxpresso_3.3/bin/crt_directory.xml

Pc: ( 5) Remote configuration complete
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: NXP: LPC1114/301 Part ID: 0444102B
Pc: ( 65) Chip Setup Complete
Chip=LPC1114/301, from NXP (formerly Philips), in family LPC11xx, version=unknown
Chip Description: NXP LPC1114/301
ClockFreq=48.0MHz (Accurate). Clock can be changed after reset.
System reset doesn't cause power cycle. Last reset cause(s): Unknown
Does have Flash and is programmable. 128M pop Mask: 0001
Mem MFlash32 of type Flash from 0000 for 32768 bytes. RO
Mem RamLoc8 of type RAM from 10000000 for 8192 bytes.
PrgFlash from 0000 to 8000 (32768 bytes). 1 Variable sized page rules (8 4K)
'Word' width: 4. Cannot read after programming starts
Peripheral PMU at 0x40038000, size=24. Is part of LM3sxxx
Power management Unit
Peripheral UART0 at 0x40008000, size=85. Is part of LM3sxxx
UART
Peripheral WDT at 0x40004000, size=20. Is part of LM3sxxx
Watchdog Timer
Peripheral TMR161 at 0x40010000, size=128. Is part of LM3sxxx
Timer16
Peripheral TMR160 at 0x4000C000, size=128. Is part of LM3sxxx
Timer16
Peripheral I2C0 at 0x40000000, size=64. Is part of LM3sxxx
I2C Interface
Peripheral ADC at 0x4001C000, size=56. Is part of LM3sxxx
Analog to Digital Converter
Peripheral SSP1 at 0x40058000, size=40. Is part of LM3sxxx
SPI Interface
Peripheral SSP0 at 0x40040000, size=40. Is part of LM3sxxx
SPI Interface
Peripheral TIMER1 at 0x40018000, size=120. Is part of LM3sxxx
Timer
Peripheral TIMER0 at 0x40014000, size=120. Is part of LM3sxxx
Timer
Peripheral IOCON at 0x40044000, size=176. Is part of LM3sxxx
IO Configuration Block
Peripheral GPIO3 at 0x50030000, size=49176. Is part of LM3sxxx
GPIO
Peripheral GPIO2 at 0x50020000, size=49176. Is part of LM3sxxx
GPIO
Peripheral GPIO1 at 0x50010000, size=49176. Is part of LM3sxxx
GPIO
Peripheral GPIO0 at 0x50000000, size=49176. Is part of LM3sxxx
GPIO
Peripheral SYSCTL at 0x40048000, size=1016. Is part of LM3sxxx
System control block
Peripheral NVIC at 0xE000E000, size=3844. Is part of LM3sxxx
NVIC M3 Control/Status Regsiters
<link href="file:///C:/nxp/lpcxpresso_3.3/bin/nxp_lpc11_13_peripheral.xme" type
="simple" show="embed" />
CPUID=0x410CC200, Little-Endian. Name=CM0, Chip=LPC1114/301,
CpuNum=0, Rev=0.0, MaxInts=32, SysTickCal=0004
State is: Stopped (stop cause: Step)
Emulator support: 'Code Red WinUSB emulator support for Cortex-M3', version: 2.0

Connected to emu0: 'T1S6RGRIA'
Connection state: ConnAndReset. DP ID=BB11477. Sticky=10
Speed=4. Frequency=1500KHz. Packet delay=0, Poll delay=0. Info from speed test.
Retries=0. Since last Info request: 0
AP is_sel=SEL. AP rel idx=0 for ID=4770021
ROM table @E00FF003. Debug is OK. Bank=0, CtrlBase=23000000
1 devices:
!0. IN_USE Device is connected already (Code Red - LPCXpresso)[/FONT]

[U]And this is the output of the erase command:
[/U]
[FONT=Courier New]c:\nxp\lpcxpresso_3.3\bin>crt_emu_lpc11_13_nxp.exe -g -2 -pLPC1114/301 -wire=winusb -flash-erase
Pc: ( 0) Reading remote configuration
Ni: LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:57:58)
Nc: Looked for chip XML file in C:/nxp/lpcxpresso_3.3/bin/LPC1114/301.xml

Nc: Looked for vendor directory XML file in C:/nxp/lpcxpresso_3.3/bin/nxp_directory.xml

Nc: Found generic directory XML file in C:/nxp/lpcxpresso_3.3/bin/crt_directory.xml

Pc: ( 5) Remote configuration complete
Pc: ( 30) Emulator Connected
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: NXP: LPC1114/301 Part ID: 0444102B
Pc: ( 65) Chip Setup Complete
Nt: Connected: was_reset=false. was_stopped=true
Cr:v Registered license, download limit of 128K
Pc: ( 70) License Check Complete
Nt: Mass Erase
Nt: Erase completed
[/FONT]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 06 10:18:59 MST 2010
trazoni,

Please exercise the crt_emu_lpc11_13_nxp.exe debug utility standalone, to see if anything is possible. I don't know whether the LPCXpresso is used as a HID or WinUSB device, so the '-wire=' arguments show below may differ (e.g '-wire=hid' or '-wire=winusb').

This command will print to the console various chip details related to your target connectino. You can post your results.

C:\nxp\lpcxpresso_3.3\bin\crt_emu_lpc11_13_nxp.exe -g -2 -pLPC1114/301 -wire=winusb -info-target

This command erases the flash:

C:\nxp\lpcxpresso_3.3\bin\crt_emu_lpc11_13_nxp.exe -g -2 -pLPC1114/301 -wire=winusb -flash-erase

Let us know your results.

CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Thu May 06 08:56:42 MST 2010
The newly imported projects in a new workspace showed the same behaviour.

Further investigations:

1. Default path
- removed LPCXpresso again and installed it in the default path
- created new workspace and imported the example projects
-->
same behaviour

2. Different machine
- installed LPCXpresso on a Laptop (XP pro 32 bit, SP3)
- created new workspace and imported the example projects
-->
the same error message box shows up, but before this happens, Windows brings the crash report window:
"crt_emu_lpc11_13_nxp.exe hat ein Problem festgestellt und muss beendet werden."
(which should translate to something like "crt_emu_lpc11_13_nxp.exe noticed a problem and has to be finished")

Then I enabled the MS crash report mechanism on my desktop, too. And now I see this error report here, too.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 06 07:05:33 MST 2010
Can you try creating a new workspace and importing the examples again? We have never seen this error and so are trying to narrow down where the problem lies.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Thu May 06 06:22:10 MST 2010
After removing both LPCXpresso versions and installing v3.3.4 the error message still persists.
Just the date in the message is now as you expected it to be (Apr 8 2010 14:57:58)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 06 05:42:45 MST 2010
We do recommend that you un-install your existing version before installing the new version. If any files were open when you installed 'over the top' then they will not have been updated.

I suggest that you remove your existing installation (and make sure the directory is deleted when you have done this) and then install 3.3.4 again.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by trazoni on Thu May 06 05:20:52 MST 2010
"About LPCXpresso" says v3.3.4.
But I recently upgraded to this version, so maybe the debug driver of the older version is used.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Thu May 06 04:50:50 MST 2010
Are you really using v3.3.4? Mine reports: LPCXpresso Debug Driver v2.0 (Apr 8 2010 14:57:58)