User forums > Embedded development

[solved]remote debug on arm

(1/3) > >>

eliot-sa:
Hi,

I want to use codeblocks for remote debug like ddd.
I'm working on a arm target (cortex-m3 stm32), I debug with arm-none-eabi-gdb from codeSourcery and openocd.

I have try 2 solutions:

* I make my binary with a custom makefile. In project option build target I chose type="console application" (I'm not sure what I have to chose)
When I start debug, codeblocks crash (see attachment for log).
I'm using codeblocks svn5857, build Oct 09 2009 - wx2.8.10 on Kubuntu 9.04, arm-none-eabi-gdb 6.8.50.20081022-cvs from codeSourcery.
I don't know what options I have to chose to configure my project
* I have see, a pluging under development to use openocd in codeblock (http://forums.codeblocks.org/index.php?topic=9904.0).
I download sources but compilation fail because I haven't codeblocks global variables cb and wx (I don't know what I have to put in)
I haven't found other solution to do remote debug wiht C:B.
if someone could help me, it would be great!

Thanks

[attachment deleted by admin]

oBFusCATed:
Have you tried Project -> properties -> debug -> remove debugging or something like that?
Although, I'm not sure if the debugging works at all with custom make files

Never tried to debug remotely, so I don't know if it works.

eliot-sa:
Tanks for answer, but I haven't understand what you want to do.
I have no option to remove debug. I have option to add sources directory and add command to gdb.

I have find a solution:
C::B crash with arm gdb 6.8.50 from codeSourcery but work fine with 6.7.50.

oBFusCATed:
I think to used the remote debugging you go to
Project -> Properties -> Debugger tab -> Remote connection

Than click on you debug target, so you make the GUI active and then enter the connection parameters for the debugging session - TCP (ip/port) or serial connection parameters
Have you tried that?

eliot-sa:
Yes, I have put tcp:localhost:3333 to connect gdb with openOCD. And it work fine.

The problem came from interaction with C::B and my version of gdb.
I had downgrade gdb and now the problem is solved.

Navigation

[0] Message Index

[#] Next page