Re: Re: [ECOS] How to debug a Ethernet Device Driver via network

Re: Re: [ECOS] How to debug a Ethernet Device Driver via network

[Tianjun-ZDK]

 >On Mon, 2005-08-08 at 09:42 +0800, Tianjun-ZDK wrote:
>> Hi, all
>> 
>> 	I'm in progress of developing a Ethernet Device Driver.
>> And I want to connect the target Via Ethernet,but it seems 
>> the network will down as long as my own NIC driver call 
>> 	
>> 	(sc->funs->eth_drv->init)( sc, unsigned char *enaddr );
>
>I don't understand what you are saying here.  This function needs
>to initialize your hardware and then tell the upper level driver
>that it's ready.  Look at the existing drivers to see how it's done.
of cource I know this. I mean after my driver initialized,i cannot 
debug via the ethernet(I use a intel i82559 NIC),it seems the network is down.

>
>> 
>> can somebody tell me that whetherr eCos can support more than 
>> one NIC or not.And if it supports,how to config the network. 
>
>eCos certainly can support more then one interface.  The builtin
>defaults easily handle a system with two and the simplified call
>"init_all_network_devices()" (called from a user application) will
>fully initialize and configure those devices.
>
>-- 
>------------------------------------------------------------
>Gary Thomas                 |  Consulting for the
>MLB Associates              |    Embedded world
>------------------------------------------------------------
>
>
>-- 
>Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>


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

Re: Re: [ECOS] How to debug a Ethernet Device Driver via network

[Gary Thomas]

On Mon, 2005-08-08 at 10:29 +0800, Tianjun-ZDK wrote:
>  >On Mon, 2005-08-08 at 09:42 +0800, Tianjun-ZDK wrote:
> >> Hi, all
> >> 
> >> 	I'm in progress of developing a Ethernet Device Driver.
> >> And I want to connect the target Via Ethernet,but it seems 
> >> the network will down as long as my own NIC driver call 
> >> 	
> >> 	(sc->funs->eth_drv->init)( sc, unsigned char *enaddr );
> >
> >I don't understand what you are saying here.  This function needs
> >to initialize your hardware and then tell the upper level driver
> >that it's ready.  Look at the existing drivers to see how it's done.
> of cource I know this. I mean after my driver initialized,i cannot 
> debug via the ethernet(I use a intel i82559 NIC),it seems the network is down.
> 

Using a network debug connection to debug network drivers is quite
problematic (using networking debugging itself is pretty tricky and
has limitations).  I'd suggest that you use serial debugging until
you get your network driver [at least mostly] working.

Note: you can still use the network to download your code, then
switch to serial.  e.g.
  (gdb) tar rem target:9000
  (gdb) lo
  (gdb) det
  (gdb) tar rem /dev/ttyS0
  ...

> >
> >> 
> >> can somebody tell me that whetherr eCos can support more than 
> >> one NIC or not.And if it supports,how to config the network. 
> >
> >eCos certainly can support more then one interface.  The builtin
> >defaults easily handle a system with two and the simplified call
> >"init_all_network_devices()" (called from a user application) will
> >fully initialize and configure those devices.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


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