[ECOS] sharing the ethernet port for Redboot/GDB/diagnostics

Andrew Voelkel andy@bushtaxi.com
Fri Sep 23 16:39:00 GMT 2005


I been confused for some time now about what facilities are available for
sharing the Ethernet port, both (1) between redboot and an application, and
(2) between different redboot activities, namely redboot command interaction
and GDB debugging. 

The first issue confuses me because I don't understand the operation of
virtual vectors well enough, I think. I'm assuming that a fully threaded
application has to take over operation of the Ethernet and use it in an
interrupt driven fashion, and somehow allow redboot to get in and do its
thing too. If anyone who can shed some light on the mechanics of how all
this works, I'd much appreciate it.

The second issue confuses me because the documentation is all spread out and
I really don't understand what is being said as a result. From reading
Massa's book, it sounds as if I should be able to set up redboot to use
separate "channels" for redboot command interactions and gdb debugging. This
certainly sounds like a good idea to me, and avoid the GDB "mangling" issue,
which seems like something to avoid if one can. So I imagine a situation
where one uses two different TCP/IP ports to accomplish this goal, and it
makes good sense to me.

However, after reading the redboot docs, and trying to understand why the
configuration options in Massa's book (which are still a little confusing)
don't seem to correspond exactly to those that I see in configtool, I don't
know how to do this. In fact, I don't even know whether it is possible.

In short, it is possible to use different TCP/IP port numbers for redboot
command interaction and GDB operation? If so, how do I do it? Or do I have
the whole model mixed up in my head.

Thanks!

- Andy



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



More information about the Ecos-discuss mailing list