This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Debugging thread application with gdb and MacRaigor ICE JTAG
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Jaws <jaws75 at tiscali dot it>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Thu, 6 Apr 2006 12:59:09 +0200
- Subject: Re: [ECOS] Debugging thread application with gdb and MacRaigor ICE JTAG
- References: <003e01c63d1d$578e3040$80a9fe90@emea.cisco.com> <000501c65963$0c548d60$6402a8c0@emea.cisco.com>
On Thu, Apr 06, 2006 at 12:15:36PM +0200, Jaws wrote:
> Hi all,
> I am using to debug a multi-thread application a Macraigor JTAG ICE
> mpDemon by
> on my platform based on AT91M55800A.
> I'm using the gdb version 6.1 provided by Macraigor and I enabled the
> option
> "Include GDB multi-threading debug support" in eCos Hal and in eCos Kernel.
This will not work with JTAG. Enabling this adds a couple of functions
to the gdb stub to allow access to thread info. But when using JTAG
the gdb stub is not used, it directly reads/writes to memory and CPU
registers.
> Trying to enable the 'Support GDB thread operations via ICE/Multi-ICE' the
> appplication doesn't start and this output appear on the serial console:
> $O5B6379675F6E65745F696E69745D20496E69743A206D62696E6974283078303030303030303029
> 0A#60
gdb con the serial port can probably decode this message. It is
probably the output of your program bug mangled in gdb format.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss