I need a bit of support - failed debug

[lpcware]

Content originally posted in LPCWare by mard on Wed Jun 30 06:32:22 MST 2010
I use CodeRed v3.3.4. When I try to Debug a code sometimes I see notice:
Windows: Problem Occurrd
'Launching program.axf' has encoutered a problem.
[I]Plug-in "com.crt.ctrlcenter" was unable to instantiate class "com.crt.ctrlcenter.misc.CRTEmbeddedCommandFactory".
com.crt.ctrlcenter.misc.CRTEmbeddedCommandFactory[/I]

Have somebody the same problem? I have to restart a Windows OS a few times to get a possibility to debug a code. What type of debugger have you set (gdb Debugger or gdb/mi)? THX you v.m. Mard

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Mon Sep 06 07:49:23 MST 2010

---

Quote: nacrisp
Within the project properties, I had inadvertently created a run/debug launch configuration, and the settings within this were causing the problem. I deleted this launch config, and can now debug the application.

---

Glad you have it sorted. Deleting the launch configuration was going to be my first suggestion ;)

Regards,
CodeRedSupport

[lpcware]

Content originally posted in LPCWare by nacrisp on Mon Sep 06 07:43:28 MST 2010
My Apologies, I have sorted the problem (although the error message wasn't very helpful).

Within the project properties, I had inadvertently created a run/debug launch configuration, and the settings within this were causing the problem. I deleted this launch config, and can now debug the application.

Nick

[lpcware]

Content originally posted in LPCWare by nacrisp on Mon Sep 06 07:14:04 MST 2010
I am also seeing this pop-up:


when I try to debug (even from the quickstart panel).
My code compiles with the following output and runs when I download trhough drag2flash or use the Program Flash button.
[SIZE=2][I]Performing post-build steps
arm-none-eabi-size RDB1768cmsis_UART.axf;  arm-none-eabi-objcopy -O binary -S  RDB1768cmsis_UART.axf RDB1768cmsis_UART.bin ;  arm-none-eabi-objdump -h -S RDB1768cmsis_UART.axf >RDB1768cmsis_UART.lss; checksum -p LPC1768 -d RDB1768cmsis_UART.bin;
   text       data        bss        dec        hex    filename
  56020       1328       1152      58500       e484    RDB1768cmsis_UART.axf
Created checksum 0x6a78ffef in RDB1768cmsis_UART.bin at offset 0x1c [/I][/SIZE]


I am using a heavily modified version of the RDB1768cmsis_UART example.. which compiles with a few warnings. The axf file is about 387KB, but the bin file is just 57K.

Im using LPCExpresso 3.5.0.
(I can debug the unaltered examples - so is this my code size or some other issue (since I dont get a license-related error message ?)

Thanks,
Nick

---

Quote: mard
I use CodeRed v3.3.4. When I try to Debug a code sometimes I see notice:
Windows: Problem Occurrd
'Launching program.axf' has encoutered a problem.
[I]Plug-in "com.crt.ctrlcenter" was unable to instantiate class "com.crt.ctrlcenter.misc.CRTEmbeddedCommandFactory".
com.crt.ctrlcenter.misc.CRTEmbeddedCommandFactory[/I]

Have somebody the same problem? I have to restart a Windows OS a few times to get a possibility to debug a code. What type of debugger have you set (gdb Debugger or gdb/mi)? THX you v.m. Mard

---

[lpcware]

Content originally posted in LPCWare by bbolo1 on Fri Aug 06 14:27:21 MST 2010
Hi,

I googled for the same problem and this is how I have found this post. It seems I get the same error. I am unable to debug any of the example projects.
I alos installed the CodeRed IDE on a different machine and everything works fine on that machine. The only difference between them (machines) is the fact that the one having problems had Eclipse Ganymede installed on it more than a year ago. Can this create some sort of interference between Eclipse IDEs?
I just freshly installed the CodeRed IDE, then imported the examples and try to run the adc demo. After successfully building the project I hit the Debug icon and then a window appeared asking me to choose from MCU debugger or GDB debugger. I chose MCU debugger and I got the error. So, I didn't messed up any settings in the IDE. It seems to me like a side effect of Eclipse.

Ok, some update. I used only the Quickstart Pan(very useful) and it worked fine. Then I saw one of the Debug configuration was causing the trouble. I put some filtering onto the the available Debug configurations. Now everything works fine.

Hope this helps some other people having similar issues.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Jun 30 09:23:08 MST 2010
Hmm. What are you doing? The debug configurations that we supply do not provide an option to select the GDB type...

To debug, just press the Debug (project) button in the Quickstart panel. It sets up everything for you.

If you really want to do it by defining your own Debug Configuration, you need to choose "C/C++ MCU Application" to get the correct type of debug configuration for LPCXpresso.