[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] JTAG (was: The fate of the current GDB suppor t inCDT)
|
Good point. Something I'll take into consideration. What I'm starting to
think is that the gdb target config file needs properties (and UI to set
them) and can then use the properties in the gdb script that it runs. The
target command could then be part of the script.
Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead
http://cdtdoug.blogspot.com
-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx
[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Lott, Jeremiah
Sent: Friday, September 01, 2006 2:07 PM
To: CDT Debug developers list
Subject: RE: [cdt-debug-dev] JTAG (was: The fate of the current GDB support
inCDT)
Doug Schaefer wrote:
> My first thoughts is to do something similar to Oyvind's work
> where the user
> can specify a list of gdb commands that are run after hooking
> up to the
> 'target remote' and before setting breakpoints and continuing.
The existing gdbserver stuff is not good enough for all gdb-based jtag
devices. For ones that emulate gdb server (like Abatron BDI 2000),
we've been able to use the gdbserver CDT panel and just issue monitor
commands via the gdb console. However, there are a number gdb-based
jtag solutions that use a specially patched version of gdb. Often the
command is not 'target remote', but instead 'target <custom>' where
<custom> is a completely new type that the jtag vendor added in their
gdb patches. To support these you need a launch configuration where
"target remote" is not issued at all and instead the user may enter
commands to run, including the "target" command.
Jeremiah Lott
TimeSys Corporation
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
