Re: [ECOS] ecos remote debugging

[Jonathan Larmour <jifl at eCosCentric dot com>]

Steve Strublic wrote:
> Hi jifl, long time no see. :)

Hey Steve!

> We're currently including GDB stubs in our application, no Redboot resident.

I forgot to say that as well as calling something like breakpoint() to 
enter the GDB stub, you could enable ctrl-c handling on a serial channel 
and enter the GDB stub that way.

>  It works well as long
> as you realize that you can only debug via a serial channel,  and don't enable 'save minimum thread
> context' so that all registers are preserved.

Yeah, that save context one's been fixed in CVS now.

> It would be nice to have Ethernet connectivity to GDB when Redboot is not resident...  any thoughts?

It's software so of course it's possible ;). It's fairly self-contained in 
the redboot code, but what's missing and would need doing if it was moved 
alongside the gdb stub code more generally is the glue. By that I meant the 
stuff that provides things like IP address info (or whether to use bootp), 
ESA maybe, an idle loop equivalent to allow the stack to be polled. 
Essentially most of the stuff in redboot/current/src/net_io.c.

Most of the basic stack code itself is fairly standalone and independent of 
redboot.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
>>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss