[ECOS] Debugging via Ethernet. (on i386 platform)

[ECOS] Debugging via Ethernet. (on i386 platform)

[Fabrice Gautier]

Hi,

I now have an ethernet driver that seems to work ok with the eCos tests.

Now that I have this driver I would like to use it as a debug channel. (at
least for download and/or diagnostic output)
I think this is already possible on some platform. At least the RedBoot demo
at ESC was showing that.

But how do I do it with my i386?
Is there some tcp/ip support in the gdb stub (that i should port) ? Or does
RedBoot provide the stub with a channel (serial or ip) transparently (so
porting redboot will give me that - and lot more ) ?
Does converting the i386 port to use the eCos/ROM Monitor Calling Interface
would help ?

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 

Re: [ECOS] Debugging via Ethernet. (on i386 platform)

[Jesper Skov]

>>>>> "Fabrice" == Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:

Fabrice> Hi, I now have an ethernet driver that seems to work ok with
Fabrice> the eCos tests.

Fabrice> Now that I have this driver I would like to use it as a debug
Fabrice> channel. (at least for download and/or diagnostic output) I
Fabrice> think this is already possible on some platform. At least the
Fabrice> RedBoot demo at ESC was showing that.

Fabrice> But how do I do it with my i386?  Is there some tcp/ip
Fabrice> support in the gdb stub (that i should port) ? Or does
Fabrice> RedBoot provide the stub with a channel (serial or ip)
Fabrice> transparently (so porting redboot will give me that - and lot
Fabrice> more ) ?  Does converting the i386 port to use the eCos/ROM
Fabrice> Monitor Calling Interface would help ?

Yes, AFAIK you need to do this since RedBoot does all its IO via the
comm channel tables. That's how it allows you to switch between serial
and ethernet debugging channels. It should all come automatically with
the conversion to the calling interface... I think :)  Gary may want
to add further comments...

Jesper

Re: [ECOS] Debugging via Ethernet. (on i386 platform)

[Andrew Lunn]

> Now that I have this driver I would like to use it as a debug channel. (at
> least for download and/or diagnostic output)
> I think this is already possible on some platform. At least the RedBoot demo
> at ESC was showing that.
> 
> But how do I do it with my i386?

You need to make redboot work. I don't know how the i386-PC target
does its booting. Can it have built in stubs? If it can you can do a
two phase port.

First port redboot and have RAM applications using built in
stubs. That allows you to concentrate on redboot and not worry about
the application. With that working you should be able to load the
application using the TCP/IP stack in the redboot stub. When the
application takes over it will than go back to using the serial port
stub. 

The second stage is to add the virtual vector support. That will then
allow your application to be debugged by the stub in redboot and use
redboot for diagnostic output.

        Andrew

RE: [ECOS] Debugging via Ethernet. (on i386 platform)

[Gary Thomas]

On 07-Oct-2000 Fabrice Gautier wrote:
> Hi,
> 
> I now have an ethernet driver that seems to work ok with the eCos tests.
> 
> Now that I have this driver I would like to use it as a debug channel. (at
> least for download and/or diagnostic output)
> I think this is already possible on some platform. At least the RedBoot demo
> at ESC was showing that.
> 
> But how do I do it with my i386?
> Is there some tcp/ip support in the gdb stub (that i should port) ? Or does
> RedBoot provide the stub with a channel (serial or ip) transparently (so
> porting redboot will give me that - and lot more ) ?

RedBoot is the solution here.  Perhaps we (you and I) can work together to
get this going.  If you're up to it [as I think you are], I'll help you get
RedBoot working in this environment [take that as you do the work, I tell you
how to fix it :-)]

> Does converting the i386 port to use the eCos/ROM Monitor Calling Interface
> would help ?

This is an absolutely necessary first step.

RE: [ECOS] Debugging via Ethernet. (on i386 platform)

[Gary Thomas]

On 09-Oct-2000 Fabrice Gautier wrote:
>> -----Original Message-----
>> From: Gary Thomas [ mailto:gthomas@redhat.com ]
>> Sent: Monday, October 09, 2000 7:13 AM
>> Subject: RE: [ECOS] Debugging via Ethernet. (on i386 platform)
> 
>> [...]
>> > Does converting the i386 port to use the eCos/ROM Monitor 
>> Calling Interface
>> > would help ?
>> 
>> This is an absolutely necessary first step.
> 
> 
> And then ? Do you have un mind the following steps ?
> 
> It is Not that I already have completed this step, but just to know what I'm
> going into... 

Actually, once you have this and an ethernet driver in place (which you've
already said was basically working), then you should be nearly "home free."

RE: [ECOS] Debugging via Ethernet. (on i386 platform)

[Fabrice Gautier]

> -----Original Message-----
> From: Gary Thomas [ mailto:gthomas@redhat.com ]
> Sent: Monday, October 09, 2000 7:13 AM
> Subject: RE: [ECOS] Debugging via Ethernet. (on i386 platform)

> [...]
> > Does converting the i386 port to use the eCos/ROM Monitor 
> Calling Interface
> > would help ?
> 
> This is an absolutely necessary first step.


And then ? Do you have un mind the following steps ?

It is Not that I already have completed this step, but just to know what I'm
going into... 

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com