|
Message
From: "Robert Cragie" <rcc@j...>
Date: Wed, 29 Oct 2003 14:59:45 -0000
Subject: RE: [openrisc] gdb stub instead of JTAG?
I have used the GDB stubs supplied with eCos successfully over a UART
communicating with GDB 5.3 and DDD running GDB 5.3 being able to set
breakpoints, single step etc. The only problems I have encountered are that
global variables are somehow not visible to the debugger - haven't got to
the bottom of that one yet.
The drawbacks are the obvious ones: Intrusive code has to run; speed.
However there are some advantages like thread-aware debugging (not tried
this though).
Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
http://www.jennic.com Tel: +44 (0) 114 281 2655
_______________________________________________________________
> -----Original Message-----
> From: owner-openrisc@o...
> [mailto:owner-openrisc@o...]On Behalf Of Heiko Panther
> Sent: 29 October 2003 13:01
> To: openrisc@o...
> Subject: [openrisc] gdb stub instead of JTAG?
>
>
> I was looking into alternatives to JTAG/DSU. It looks like it should be
> possible to create a gdb debugger stub, which would be linked into the
> firmware and connect to gdb using an UART.
> Has anyone looked into this? Any work going on? Any bigger problems or
> drawbacks to expect? Maybe feature limitations compared to JTAG?
>
> Regards,
> Heiko Panther
>
>
>
|
 |
Browse
