LPC18xx and LPCXpresso with LPC-Link 2

[lpcware]

Content originally posted in LPCWare by hamu on Thu Mar 06 00:59:54 MST 2014
Hello,

Till now I used LPCXpresso v6.0.2_151 with the LPC-Link debugger to flash/debug my LPC18xx target. All worked fine for many month.

Now I bought a LPC-Link 2 debugger and I can´t flash/debug my target!. I Always get the error message

Flash driver "UnInit" return code 0x0
15: Target error from Commit Flash write
System rejected access at location 0x10001A10 - verity Population of memory and peripherals


Here are the Debug messages:
LPCXpresso RedlinkMulti Driver v6.0 (Sep 17 2013 18:02:04 - crt_emu_cm_redlink build 244)
Looked for chip XML file in C:/nxp/LPCXpresso_6.0.2_151/lpcxpresso/bin/LPC1833.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_6.0.2_151/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_6.0.2_151/lpcxpresso/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: (null)
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Loaded LPC18x3_43x3_2x256_BootA.cfx: LPC18x3/LPC43x3 Flash 2x256KB @0x1A000000 (Boot Bank A) Jul 22 2013 10:38:30  On-chip Flash Memory
Connected: was_reset=true. was_stopped=false
v LPCXpresso Free License - Download limit is 256K
driver "UnInit" return code: 0x0
Target error from Commit Flash write: Em(12). System rejected access at location 0x10001A10 - verify Population of memory and peripherals
Stopped: Halt

The adress location changes every time...

I have already tried all posibilities mentioned in this forum (enabling vector catch, ....) but nothing works.


If I switch back to the old LPC-Link all works fine again.

Can anybody help me with this issue?

Thanks
Thomas

[lpcware]

Content originally posted in LPCWare by pm33aud on Mon Nov 16 18:22:57 MST 2015
Thanks,

We did finally get the LPC-Link2 with CMSIS-DAP working under 7.9.2 and our intermittent debug relaunch issues we were having in 7.5.0 have also disappeared.

The solution (we really thought we did this but maybe we didn't try it on 7.9.2 properly) was to delete the project's .launch files and rebuild the project.  Now the emulator will connect and we can reliably debug our projects.  So far so good! 

We do need to be more thorough in our testing and not skip steps documenting our troubleshooting processes.  I apologise for any wasted time!

[lpcware]

Content originally posted in LPCWare by pm33aud on Mon Nov 16 13:47:38 MST 2015
I will compose a new thread with details as it relates to our experience.  I suppose if the CMSIS-DAP driver can be made to work, maybe some of these other issues simply dissappear... So maybe we will start there.  I will also work with my colleague as he has done some testing as well (most of that 4 days was his; the unfortunate soul :))

Please keep posted!

Thanks,
Phil

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Nov 16 12:11:37 MST 2015
@pm33aud

So based on the fact that this thread is > 18 months old and related to a much older version of LPCXpresso - I suggest that you create a new thread and provide us with some details of your exact host computers, target MCUs, the actions that you are carrying out and the actual errors that you are seeing.

Please also provide some information of what you have actually been doing and trying during the 4 days that you have tried using LPCXpresso v7.9.2. Any suggestions we make are going to be based on this version, not on LPCXpresso 7.5.0.

If you can provide us with some details, we should then hopefully be able to provide you with some assistance. Note that generally under Mac OS X, we would expect LPC-Link2 to just work - as unlike Windows there aren't any specific drivers that need installing. There are some issues using LPC-Link1 under Mac OS X 10.11 El Capitan (as detailed at https://www.lpcware.com/content/forum/lpcxpresso-and-lpcscrypt-current-status-using-mac-osx-1011-el-... ) but we haven't seen any such issues using LPC-Link2.

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by pm33aud on Mon Nov 16 11:12:12 MST 2015
I wanted to revive this thread instead of creating another to keep the information consolidated.  We are also having some very problematic issues with the LPC-Link2 being very intermittent in debugging our targets.  The problems we've faced are exactly those outlined here in the OP.

We have tried 2 different versions of OSX on 2 computers and are using LPCXpresso 7.5.0.  It will occasionally program/debug but when stopping the debug session and go to restart debug, we get these errors ... it's about 50% of the time.  We have to reset the debug by clicking 'Terminate and Remove' every time as well.

We can't use the latest LPCXpresso 7.9.2 because even after 4 days of trying all sorts of things found here and NXP, we couldn't get the LPC-Link2 to connect (with the CMSIS-DAP firmware)... we figured we'd stop attempting to muck around with the latest since the older version works somewhat and we can continue

Any help would be appreciated.  We are considering which IDE and debuggers to use going forward for our startup so we really do need something reliable.  So far it has be quite the contrary, unfortunately!  Maybe it's operator error, I don't know.

Thanks,
Phil

[lpcware]

Content originally posted in LPCWare by robert hulsebos on Mon May 12 00:09:10 MST 2014
I tried USB 3.0 ports as well as legacy USB ports. Did not help...
Anyway, the good news is that all my problems seem to have been resolved with version v7.1.1 of LCPXpresso...finally!

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Sat Mar 15 13:50:24 MST 2014


Do you know which (if any) of the failed debug sessions were associated with USB 3.0 ports? I suspect the trouble is not related to core frequency. Microsoft has fielded a number of Windows 7/8 support issues related to USB 3.0. Can you describe the LPC-Link2 behavior when connected strictly to a USB 2.0 port/hub?

Regards,

LPCXpresso-Support

[lpcware]

Content originally posted in LPCWare by robert hulsebos on Fri Mar 14 07:26:57 MST 2014
I have similar experiences with a custom board that is built around the LPC1769. Same kind of weird (flash) errors. Errors seem to happen about 50% of the time. So with a bit of re-trying I am able to debug ... every now and then - which is sort of very annoying...

I already checked the following:
- Checked debug design considerations at http://www.lpcware.com/content/faq/lpcxpresso/debug-design
- Verified SWD signals with logic analyzer. Signals do seem all ok/normal. SWD clock measured at about 1.4 MHz. So nothing ludicrous.
- Grounding of LPC-link2 and target board
- Different, non-switching power supply.
- Latest version of LPCXpresso IDE (v7.0.2)
- Switching from SWD to JTAG. (which does not seem to work)
- Tried LCP-Link1 - no problems there.
- Tried different (direct) USB ports, USB hubs. Did not help.
This all on 64-bit Windows 8.1 PC. (Core-i7, 3.4 GHz) Which is a beast, I must admit...

Finally, I tried using same hardware but different development PC. A slower, Windows 7 machine. (Core i3 @ 2.4 Ghz)
Observed the following:
- Errors are rare, less than 1 out of 10.
- Flashing is a lot slower, some times up to 1 second / 32 KB page.
- Verified SWD signals with analyzer, same 1.4 MHz SWD clock. So LCP-Link2 to target is a constant factor here.

Also tried with a Core i3 laptop. Was not able to reproduce the problem there at all...

So my current guess is it has something to do with the speed of the PC / or PC <-> LCP-Link2 USB handling.

Hope this helps (you helping me...)

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 13 12:20:18 MST 2014

The log suggests the flash driver failed almost immediately. Do you have a way to boot your part into the ISP? The ISP offers a stable boot configuration, as explained in this FAQ:

Regaining debug access to target MCU

Double check, but I believe the ISP pin is P2_7 on the LPC1833.

Once you do this, retry the flash operation on your part.

Regards,

LPCXpresso-Support

[lpcware]

Content originally posted in LPCWare by hamu on Wed Mar 12 22:29:35 MST 2014
Here is the log...

LPCXpresso RedlinkMulti Driver v6.0 (Feb 19 2014 23:01:47 - crt_emu_cm_redlink build 33)
Looked for chip XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/LPC1833.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: (null)
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Loaded LPC18x3_43x3_2x256_BootA.cfx: LPC18x3/LPC43x3 Flash 2x256KB @0x1A000000 (Boot Bank A) Jul 22 2013 10:38:30  On-chip Flash Memory
Connected: was_reset=true. was_stopped=false
v LPCXpresso Free License - Download limit is 256K
Writing 35080 bytes to 1A000000 in Flash (assumed clock: unknown)
driver "ProgramPage" return code: 0x1
Target error from Commit Flash write: Ef(38). Flash operation has returned an error (see log).
Stopped: Halt


If I start a debug session immediately after the first one, it works

Thomas

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Tue Mar 11 01:25:00 MST 2014
Please post the whole Debug Log so we can see the context.

[lpcware]

Content originally posted in LPCWare by hamu on Mon Mar 10 23:56:19 MST 2014
I have double checked my target board and I found the problem!
Pin 1 of the 10pin debug connector wasn´t connected to 3.3V. Now I´m able to flash the LPC1833. The old LPC-Link might not need this so flashing the target worked with it. I have also checked the board with the LPC1768 and there pin 1 of the debug connector is also not connected to 3.3V - but the LPC-Link 2 can flash it.

Now if I start a debug session with the LPC1833 I get the error

driver "ProgramPage" return code: 0xFFFFFFFF
Target error from Commit Flash write: Ef(38). Flash operation has returned an error (see log).

After starting the debug session once again it works. What does this message say?

Thanks support for your previous hints concerning my issue.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Mar 10 04:52:25 MST 2014
The error being reported:
Target error from Commit Flash write: Em(12). System rejected access at location 0x10001874 - verify Population of memory and peripherals

is normally associated with a power problem on your target. Flash programming takes a lot more power than 'steady state'.

I know that you said that this works with LPCXpresso v6, but if the power on your target is marginal, it could be that changes to the debug driver in v7 is exposing this marginality.

We certainly do not experience any problems with LPC-Link2 with the LPC18xx boards we have in the lab, and so I think the problem is likely to be related to the design of your target board.

[lpcware]

Content originally posted in LPCWare by hamu on Sun Mar 09 22:40:02 MST 2014
I have tried the issue with the spacings in path, but I can´t flash my LPC1833. Same error situation.

The good news are that breakpoints are working now after attaching to the already running target.

[lpcware]

Content originally posted in LPCWare by rocketdawg on Thu Mar 06 09:29:26 MST 2014
there seems to be an issue when there are spaces in the path or file name

[lpcware]

Content originally posted in LPCWare by hamu on Thu Mar 06 07:40:57 MST 2014
Thanks Support,

I did all your suggestions already in the past, but nothing helps. I did it now again and here is the debug log:

DEBUG LOG (after deleting launch configurations)
------------------------------------------------------------------------
LPCXpresso RedlinkMulti Driver v6.0 (Feb 19 2014 23:01:47 - crt_emu_cm_redlink build 33)
Looked for chip XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/LPC1833.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: (null)
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Loaded LPC18x3_43x3_2x256_BootA.cfx: LPC18x3/LPC43x3 Flash 2x256KB @0x1A000000 (Boot Bank A) Jul 22 2013 10:38:30  On-chip Flash Memory
Connected: was_reset=false. was_stopped=false
v LPCXpresso Free License - Download limit is 256K
driver "UnInit" return code: 0x0
Target error from Commit Flash write: Em(12). System rejected access at location 0x10001874 - verify Population of memory and peripherals
Stopped: Halt
(crt_emu_cm_redlink) terminating due to request from GDB


I have investigated this problem the whole day now and I have some new information for you. I used LPCXpresso 7.0.0_92 and the LPC-Link 2 with the LPC1833:

1) Flashing the LPC1833 definitively fails. Therefore the debug session also fails. I think that the problem is the "crt_emu_cm_redlink.exe". This is the only difference in comparison to the older LPC-Link which uses "crt_emu_cm3_nxp.exe". Flashing from the command line with "crt_emu_cm_redlink.exe" also fails with same errors.

2) Flashing with the older LPC-Link and afterward attaching the LPC-Link 2 to the running target works correctly.

3) The flash driver for LPC1833 (LPC18x3_43x3_2x256_BootA.cfx) seems to be correct because flashing with the older LPC-Link and this driver works correctly.

4) Either way, LPCXpresso 7.0.0 is unuseable for debugging! Breakpoints are not working. I don´t explain this now because there is already an other post dealing with this.


Thanks
Thomas

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 06 07:09:36 MST 2014
There are no known LPC18 specific issues like this.

One possibility might be that this is a launch configuration settings issue - if your launch configurations were created in version 6 and you are using version 7.

When moving between versions, we recommend deleting any launch configurations within your project which were created by an earlier version. These files are typically named "projectname Debug.launch" and "projectname Release.launch"). The easiest way to do this is to right click on the project in Project Explorer and select

Launch Configurations -> Delete Launch Configurations

from the context sensitive menu. The IDE will then automatically create a fresh set of launch configurations the next time that you start a debug session.

[In fact when moving LPCXpresso versions, rather than just using the existing workspace, we would generally recommend creating a new workspace in the new version, and using import to pull over your projects from the old workspace].

If you are still having problem, then please post your latest debug log:

http://www.lpcware.com/content/faq/lpcxpresso/debug-log

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by hamu on Thu Mar 06 04:43:29 MST 2014
Hello Support

I have now tried the LPC-Link 2 with an other project where the target is a LPC1768 and it works correctly. LPCXpresso was also the latest version 7.0.0_92.

So it seems that LPCXpresso doesn´t support the combination LPC1833 / LPC-Link 2 correctly.
Are there any workarounds?

Thanks
Thomas

[lpcware]

Content originally posted in LPCWare by hamu on Thu Mar 06 01:57:49 MST 2014
Support, thanks for your fast response!

I have also tried it with the actual version (7.0.0_92) now, but there is the same problem.

I have running a Win7x64 and the target CPU is a LPC1833. The board itself is self developed. I´m working with this board for approx. half a year with the old LPC-Link and I never had troubles with flashing/debugging.



Debug messages:
----------------------------------------
LPCXpresso RedlinkMulti Driver v6.0 (Feb 19 2014 23:01:47 - crt_emu_cm_redlink build 33)
Looked for chip XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/LPC1833.xml
Looked for vendor directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/NXP_directory.xml
Found generic directory XML file in C:/nxp/LPCXpresso_7.0.0_92/lpcxpresso/bin/crt_directory.xml
Emu(0): Conn&Reset. DpID: 2BA01477. CpuID: 410FC230. Info: (null)
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Loaded LPC18x3_43x3_2x256_BootA.cfx: LPC18x3/LPC43x3 Flash 2x256KB @0x1A000000 (Boot Bank A) Jul 22 2013 10:38:30  On-chip Flash Memory
Connected: was_reset=false. was_stopped=false
v LPCXpresso Free License - Download limit is 256K
driver "UnInit" return code: 0x0
Target error from Commit Flash write: Em(12). System rejected access at location 0x1000179C - verify Population of memory and peripherals
Stopped: Halt

RedlinkServer console:
-------------------------------------------
[Started server]
[Connected on port 3025]
redlink>
redlink>
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#7&4d934e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPCLINK2 Redlink
VID = 21BD, PID=0006
Path = \\?\hid#vid_21bd&pid_0006#7&4d934e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 64
Probe Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = REDLINK
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Handle = 0x00000001 = 1
redlink>WireIsConnected 1
FALSE
redlink>WireSwdConnect 1
DpID = 2BA01477
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>close
[Closed]
[Connected on port 3025]
redlink>close
[Closed]
redlink>
[Started server]
[Connected on port 3025]
redlink>ProbeStatus
redlink>exit
[Closed]

GDB trace
-------------------------------------------------
438,330 2-environment-cd "E:/0540_Projekte/K6 Robotermodul iRIO/LPC_Workspace/iRIO"
438,337 2^done
438,337 (gdb)
438,337 3-gdb-set breakpoint pending on
438,347 3^done
438,347 (gdb)
438,347 4-enable-pretty-printing
438,357 4^done
438,357 (gdb)
438,357 5maintenance set python print-stack off
438,367 &"maintenance set python print-stack off\n"
438,367 &"Undefined maintenance set command: \"python print-stack off\".  Try \"help maintenance set\
\".\n"
438,367 5^error,msg="Undefined maintenance set command: \"python print-stack off\".  Try \"help main\
tenance set\"."
438,367 (gdb)
438,367 6-gdb-set print object on
438,377 6^done
438,377 (gdb)
438,377 7-gdb-set print sevenbit-strings on
438,387 7^done
438,387 (gdb)
438,387 8-gdb-set charset ISO-8859-1
438,397 8^done
438,397 (gdb)
438,397 9-gdb-set auto-solib-add on
438,407 9^done
438,407 (gdb)
438,414 10-file-exec-and-symbols --thread-group i1 "E:/0540_Projekte/K6 Robotermodul iRIO/LPC_Worksp\
ace/iRIO/Debug/iRIO.axf"
438,420 10^done
438,420 (gdb)
438,425 11set remotetimeout 60000
438,430 &"set remotetimeout 60000\n"
438,430 =cmd-param-changed,param="remotetimeout",value="60000"
438,430 11^done
438,430 (gdb)
438,456 12-target-select extended-remote | crt_emu_cm_redlink -msg-port=50767 -g -mi -2 -pLPC1833 -v\
endor=NXP -ResetScript=LPC18LPC43InternalFLASHBootResetscript.scp -ProbeHandle=1 -CoreIndex=0 -flash\
-driver=LPC18x3_43x3_2x256_BootA.cfx
439,214 =thread-group-started,id="i1",pid="42000"
439,214 =thread-created,id="1",group-id="i1"
439,215 13-list-thread-groups --available
439,246 *stopped,frame={addr="0x10000112",func="InterruptEnabled",args=[]},thread-id="1",stopped-thr\
eads="all"
439,246 12^connected
439,246 (gdb)
439,247 13^error,msg="Can not fetch data now."
439,247 (gdb)
439,247 14set mem inaccessible-by-default off
439,257 &"set mem inaccessible-by-default off\n"
439,257 =cmd-param-changed,param="mem inaccessible-by-default",value="off"
439,257 14^done
439,257 (gdb)
439,257 15mon ondisconnect cont
439,267 &"mon ondisconnect cont\n"
439,277 15^done
439,277 (gdb)
439,277 16set arm force-mode thumb
439,287 &"set arm force-mode thumb\n"
439,287 =cmd-param-changed,param="arm force-mode",value="thumb"
439,287 16^done
439,287 (gdb)
439,287 17-target-download
439,317 17+download,{section=".text",section-size="34136",total-size="1592151"}
439,337 17+download,{section=".data",section-size="820",total-size="1592151"}
439,450 18-list-thread-groups
439,537 17^error,msg="Error finishing flash operation"
439,537 (gdb)
439,537 19-interpreter-exec console "mon capabilities"
439,547 18^done,groups=[{id="i1",type="process",pid="42000",executable="E:\\0540_Projekte\\K6 Robote\
rmodul iRIO\\LPC_Workspace\\iRIO\\Debug\\iRIO.axf"}]
439,547 (gdb)
439,553 20-list-thread-groups i1
439,557 19^done
439,557 (gdb)
439,557 21-data-evaluate-expression __CR_SEMIHOST
439,587 20^done,threads=[{id="1",target-id="Thread <main>",frame={level="0",addr="0x10000112",func="\
InterruptEnabled",args=[]},state="stopped"}]
439,587 (gdb)
439,587 21^error,msg="No symbol \"__CR_SEMIHOST\" in current context."
439,587 (gdb)
439,588 22-data-evaluate-expression fclose
439,594 23-stack-info-depth --thread 1 11
439,607 22^done,value="{<text variable, no debug info>} 0x1a007038 <fclose>"
439,607 (gdb)
439,607 24-interpreter-exec console "mon semihost enable"
440,267 23^done,depth="3"
440,267 (gdb)
440,271 25-stack-list-frames --thread 1
440,277 24^done
440,277 (gdb)
440,277 25^done,stack=[frame={level="0",addr="0x10000112",func="InterruptEnabled"},frame={level="1",\
addr="0x1000029c",func="UartPort"},frame={level="2",addr="0x1000029c",func="UartPort"}]
440,277 (gdb)
440,277 26-interpreter-exec console "mon info,all"
440,297 26^done
440,297 (gdb)
440,549 27-data-list-register-names
440,557 27^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12",\
"sp","lr","pc","","","","","","","","","","xpsr","","","","","","","","","","","","","","","","","",\
"","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","","\
","","","","","","","","","","","","","","","cycles"]
440,557 (gdb)
440,559 28-data-evaluate-expression --thread-group i1 "sizeof (void*)"
440,570 29-list-thread-groups
440,570 30-thread-info 1
440,593 28^done,value="4"
440,593 (gdb)
440,594 31-interpreter-exec --thread-group i1 console "show endian"
440,603 29^done,groups=[{id="i1",type="process",pid="42000",executable="E:\\0540_Projekte\\K6 Robote\
rmodul iRIO\\LPC_Workspace\\iRIO\\Debug\\iRIO.axf"}]
440,603 (gdb)
440,603 30^done,threads=[{id="1",target-id="Thread <main>",frame={level="0",addr="0x10000112",func="\
InterruptEnabled",args=[]},state="stopped"}]
440,603 (gdb)
440,603 ~"The target endianness is set automatically (currently little endian)\n"
440,603 31^done
440,603 (gdb)
440,606 32-break-insert --thread-group i1 -t -f main
440,669 32^done,bkpt={number="1",type="breakpoint",disp="del",enabled="y",addr="0x1a001d5c",func="ma\
in",file="../src/main.c",fullname="E:\\0540_Projekte\\K6 Robotermodul iRIO\\LPC_Workspace\\iRIO\\src\
\\main.c",line="27",thread-groups=["i1"],times="0",original-location="main"}
440,669 (gdb)
440,671 33-exec-continue --thread-group i1
440,679 ~"Note: automatically using hardware breakpoints for read-only addresses.\n"
440,699 33^running
440,699 *running,thread-id="all"
440,699 (gdb)
440,739 *stopped,reason="signal-received",signal-name="SIGINT",signal-meaning="Interrupt",frame={add\
r="0x10000112",func="InterruptEnabled",args=[]},thread-id="1",stopped-threads="all"
440,739 (gdb)
440,750 34-stack-info-depth --thread 1 2
440,761 35-list-thread-groups
440,770 36-stack-info-depth --thread 1 11
441,109 34^done,depth="2"
441,109 (gdb)
441,109 35^done,groups=[{id="i1",type="process",pid="42000",executable="E:\\0540_Projekte\\K6 Robote\
rmodul iRIO\\LPC_Workspace\\iRIO\\Debug\\iRIO.axf"}]
441,109 (gdb)
441,109 37-thread-info 1
441,439 36^done,depth="3"
441,439 (gdb)
441,444 38-stack-list-frames --thread 1
441,444 39-stack-list-frames --thread 1 0 2
441,449 37^done,threads=[{id="1",target-id="Thread <main>",frame={level="0",addr="0x10000112",func="\
InterruptEnabled",args=[]},state="stopped"}]
441,449 (gdb)
441,449 38^done,stack=[frame={level="0",addr="0x10000112",func="InterruptEnabled"},frame={level="1",\
addr="0x1000029c",func="UartPort"},frame={level="2",addr="0x1000029c",func="UartPort"}]
441,449 (gdb)
441,449 39^done,stack=[frame={level="0",addr="0x10000112",func="InterruptEnabled"},frame={level="1",\
addr="0x1000029c",func="UartPort"},frame={level="2",addr="0x1000029c",func="UartPort"}]
441,449 (gdb)
638,619 40-gdb-exit
638,624 40^exit
638,634 =thread-exited,id="1",group-id="i1"
638,634 =thread-group-exited,id="i1"
638,647 41-list-thread-groups i1
638,649 42-list-thread-groups
638,660 43-list-thread-groups

Thanks
Thomas

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Thu Mar 06 01:26:09 MST 2014
In the first place, please try installing a more recent version of LPCXpresso - either 6.14 or preferably the current 7.0.0 and see if you see the same problem.

If this doesn't help, please confirm your host OS and the actual details of your board (and exact MCU).

Regards,
LPCXpresso Support