Community
Participate
Working Groups
I have an Eclipse/CDT (zylin plugin) system set up for ARM cross development. Specifically, Eclipse 3.2 CDT 3.1 (Zylin plug-in) and the YAGARTO ARM tool chain. I use a USB-based JTAG debugger using the OpenOCD JTAG debugger. Breakpoints set in C source files work great. Breakpoints set in an assembler source file are ignored, even though the little blue circle appears in the margin denoting a breakpoint has been set. If I single step into an assembler routine, I can set a breakpoint in the disassembler window and hit "continue" and it will stop on that breakpoint! Michael Fischer has investigated this and determined that the GDB serial protocol is incomplete for an assembler source file breakpoint setting. Oyvind Harboe offered the opinion that this was a GDB problem and thus should be investigated by the CDT team. Cheers, Jim Lynch
If this is a GDB problem, shouldn't it be investigated by the GDB team? Sorry, just sounded funny to me. In particular, is the CDT sending the right commands to gdb and then gdb not sending the right serial protocol commands to OpenOCD? If the CDT isn't sending the right commands to gdb, then we can try and do something about that. But the CDT has no visibility into connection between gdb and a remote target. BTW, thanks Jim for the great tutorial on ARM/JTAG development. I think it's been openning new doors for embedded users who want to use the CDT.
