Be sure to still support separate gdb servers for each separate device on the 
scan chain. For example, the nVidia Tegra II has a dual core A9 and an arm7 
peripheral/ power controller.

Øyvind Harboe <oyvind.har...@zylin.com> wrote:


Just some thoughts on multicore interface to debuggers...

GDB server: Today OpenOCD has support for multiple CPUs that lends itself
towards heterogeneous multiprocessor systems. I don't think there
are many of those that OpenOCD can support.

Also the current support creates one GDB server for each CPU.
This would be terribly awkward to work with.

I think a better approach would be to represent each CPU as
a thread via the gdb remote protocol. GDB GUI interfaces
know how to deal with multiple threads for a single processor,
thus it should be possible to add support for multicore systems
without changing the GDB GUI's.

Use case: presumably the goal is to debug multicore Linux
kernels. Is there realistically any other operating system that
would run on a Cortex A9 w/4 cores and gigabytes of memory?
I think it would be healthy to set aside some time to do Linux kernel
debugging with single core systems and document best practices
there and outline the most annoying problems and the best tricks.
In addition to target support, can OpenOCD "do more" towards
making kernel debugging smoother? An interesting feature would
be to be able to step into kernel fn's from user space and back
again, all with source code :-)

Some links:

http://elinux.org/BeagleBoardOpenOCD
http://www.eetimes.com/design/embedded/4207333/Debugging-the-Linux-kernel-with-JTAG
http://elinux.org/DebuggingTheLinuxKernelUsingGdb

--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to