[ECOS] Adding a 82544 driver Package to redboot

[ECOS] Adding a 82544 driver Package to redboot

[Muruga Ganapathy]

Hello, 

We are trying to include the 82544 driver package from ecos 2.0 
to 1.24 Version of redboot. 

The redboot Ver 1.24 is the release from Intel for IXP2400. 
It has the driver package for 82559. We would like to remove 
this package and add the 82544 support. 

Could some one list of steps that we need to go through to 
include driver package for 82544 in the redboot.

Thanks in advance
G.Muruganandam


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

Re: [ECOS] Adding a 82544 driver Package to redboot

[Nick Garnett]

"Muruga Ganapathy" <gmuruga@gdatech.com> writes:

> Hello, 
> 
> We are trying to include the 82544 driver package from ecos 2.0 
> to 1.24 Version of redboot. 
> 
> The redboot Ver 1.24 is the release from Intel for IXP2400. 
> It has the driver package for 82559. We would like to remove 
> this package and add the 82544 support. 
> 
> Could some one list of steps that we need to go through to 
> include driver package for 82544 in the redboot.
> 

You will need to add a new target to the ecos.db file.
Take a look at the pc and pc_giga targets for an example where the
same transition has been made. You will need to create a
board-specific package to map the generic driver on to the board
itself. Take a look at the CYGPKG_DEVS_ETH_I386_PC_I82544 and
CYGPKG_DEVS_ETH_ARM_IQ80321 packages for examples.


-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


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

Re: [ECOS] Adding a 82544 driver Package to redboot

[G.Muruganandam]

Hello,

Issue:

I am unable to ping using the GIGE ethernet interface under readboot.
The ethernet interface is based on Intel's ethernet MAC 82540.

Please find below the steps that I followed.


I have added the 82544 driver package to redboot and
I am able to build it.

Actually I am using 82540 in the target board. Its features are derived from
82544. It is like 82546 except for the fact that it(82540) has
single ethernet port where as 82546 has dual ethernet port.

(In the driver code, I have included the device ID for 82540
which is 0x100E.)

The ethernet driver is coming up and I am able to read the PHY resisters 
correctly.


Redboot Output:
============

PHY 1 regs:
1140 7949 0141 0C23 0DE1 0000 0004 2001
0000 0300 0000 0000 0000 0000 0000 3000
0368 8100 0000 0040 0C60 0000 0000 0000
4100 0000 000A 808F 0000 0000 0000 0000

Also I am able to read the EEPROM values correctly.


Redboot Output:
============

Valid EEPROM checksum
eth_set_mac_address
setting: lo FF48DEAC hi 80000006
Set MAC Address = AC DE 48 FF 06 00 (ok 1)
i82544_init: MAC Address = AC DE 48 FF 06 00
i82544_start
CTRL 03FC0261
STATUS 0000CB80
Ethernet eth0: MAC address ac:de:48:ff:06:00
IP: 192.168.200.198, Default server: 192.168.200.165


I have also captured below the "fconfig" command output under redboot
to show that ethernet port is assigned with proper IP address.

Redboot Output:
============

Master-RedBoot_2800> fconfig -l
Run script at boot: false
Use BOOTP for network configuration: false
Master's Local Ethernet address: 0xAC:0xDE:0x48:0xFF:0x06:0x00
Master's Local IP address: 192.168.200.198
Default server IP address: 192.168.200.165
Slave's Local IP address: 0.0.0.0
GDB connection port: 9000
Network debug at boot time: true
Master-RedBoot_2800>


ISSUE:
======

Even though the ethernet driver is coming up with out any  the error 
message, I am
unable to ping using the ethernet interface. Redboot throws up the 
following error
message when I am trying to ping.

(I have connected the target board and my host system using a 10/100 
ethernet switch.
And I am trying to ping the host ( 192.168.200.165) from the target( 
192.168.200.198))

Master-RedBoot_2800> ping -h 192.168.200.165
Ethernet send:
0x00043974: FFFF FFFF FFFF ACDE  48FF 0600 0806        |........H.....  |
0x00145FDC: 0001 0800 0604 0001  ACDE 48FF 0600 C0A8   |..........H.....|
0x00145FEC: C8C6 0000 0000 0000  C0A8 C8A5             |............    |
PING: Can't find address of server '192.168.200.165'
Master-RedBoot_2800>

Could some one help me to fix this ethernet issue and do let me know
if you need more information.


Thanks in advance.
G.Muruganandam


At 11:23 AM 8/28/2003 +0100, Nick Garnett wrote:
>"Muruga Ganapathy" <gmuruga@gdatech.com> writes:
>
> > Hello,
> >
> > We are trying to include the 82544 driver package from ecos 2.0
> > to 1.24 Version of redboot.
> >
> > The redboot Ver 1.24 is the release from Intel for IXP2400.
> > It has the driver package for 82559. We would like to remove
> > this package and add the 82544 support.
> >
> > Could some one list of steps that we need to go through to
> > include driver package for 82544 in the redboot.
> >
>
>You will need to add a new target to the ecos.db file.
>Take a look at the pc and pc_giga targets for an example where the
>same transition has been made. You will need to create a
>board-specific package to map the generic driver on to the board
>itself. Take a look at the CYGPKG_DEVS_ETH_I386_PC_I82544 and
>CYGPKG_DEVS_ETH_ARM_IQ80321 packages for examples.
>
>
>--
>Nick Garnett                    eCos Kernel Architect
>http://www.ecoscentric.com      The eCos and RedBoot experts
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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

Re: [ECOS] Adding a 82544 driver Package to redboot

[Andrew Lunn]

> Master-RedBoot_2800> ping -h 192.168.200.165
> Ethernet send:
> 0x00043974: FFFF FFFF FFFF ACDE  48FF 0600 0806        |........H.....  |
> 0x00145FDC: 0001 0800 0604 0001  ACDE 48FF 0600 C0A8   |..........H.....|
> 0x00145FEC: C8C6 0000 0000 0000  C0A8 C8A5             |............    |
> PING: Can't find address of server '192.168.200.165'
> Master-RedBoot_2800>
> 
> Could some one help me to fix this ethernet issue and do let me know
> if you need more information.

This looks like an ARP message to me, which is what i would expect.

Use a network sniffer like tcpdump to see if the packet is actually
making it onto the network. If there is no packet on the network its
probably an issue with PHY configuration or cabling.

Then check to see if the host your are trying to ping responds with an
ARP reply. If there is no arp reply sent there may be something wrong
with the ARP request, like its been truncated, CRC is wrong etc. 

Then see if they ARP response is being received and then dropped for
some reason.

Basically, keep debugging....

           Andrew

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

Re: [ECOS] Adding a 82544 driver Package to redboot

[G.Muruganandam]

Hello Andrew,

Thanks for the input. I'll keep you posted.

regards
G.Muruganandam


At 01:53 PM 1/5/2004 +0100, Andrew Lunn wrote:
> > Master-RedBoot_2800> ping -h 192.168.200.165
> > Ethernet send:
> > 0x00043974: FFFF FFFF FFFF ACDE  48FF 0600 0806        |........H.....  |
> > 0x00145FDC: 0001 0800 0604 0001  ACDE 48FF 0600 C0A8   |..........H.....|
> > 0x00145FEC: C8C6 0000 0000 0000  C0A8 C8A5             |............    |
> > PING: Can't find address of server '192.168.200.165'
> > Master-RedBoot_2800>
> >
> > Could some one help me to fix this ethernet issue and do let me know
> > if you need more information.
>
>This looks like an ARP message to me, which is what i would expect.
>
>Use a network sniffer like tcpdump to see if the packet is actually
>making it onto the network. If there is no packet on the network its
>probably an issue with PHY configuration or cabling.
>
>Then check to see if the host your are trying to ping responds with an
>ARP reply. If there is no arp reply sent there may be something wrong
>with the ARP request, like its been truncated, CRC is wrong etc.
>
>Then see if they ARP response is being received and then dropped for
>some reason.
>
>Basically, keep debugging....
>
>            Andrew
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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

Re: [ECOS] Adding a 82544 driver Package to redboot

[G.Muruganandam]

Hello Andrew,

I have made some progress in integrating and testing the 82544 based driver 
on a IXP platform.

I have the following issue on the driver.

When I ping the host from IXP platform using the Giga bit ethernet 
interface, the tcpdump software
displays following information on the screen.


G:\Temp\WinDump.exe: listening on \Device\NPF_{BDE6BD48-A7D4-4F2C-9011-F3E
E9F}
18:16:36.863101 0:0:0:0:0:0 > 0:0:0:0:0:0 null I (s=0,r=0,C) len=42


This means that it (host)  is not getting the valid mac address from the 
target board.

I have verified the statistics counter for the reception and transmission 
of the packet in and out of the
interface.

I am seeing the non zero values on both counters. It means to me that it is 
there is no issue with basic
transmission or reception of packets.  Please correct me if I am wrong.


Also I tried to ping the target board from the host and executed the 
command arp -a at the
dos prompt, it displayed the following information.


DOS-PROMPT>arp -a

Interface: 192.168.200.165 on Interface 0x1000003
Internet Address      Physical Address      Type
192.168.200.198       00-00-00-00-00-00     invalid

It shows that host has received a invalid mac address for the ip address 
192.168.200.198.

I have verified the mac address read from EEPROM by including the printfs. 
it looks fine.

Valid EEPROM checksum
eth_set_mac_address
setting: lo FF48DEAC hi 80000006
Set MAC Address = AC DE 48 FF 06 00 (ok 1)
i82544_init: MAC Address = AC DE 48 FF 06 00


So please let me know how do I proceed further in terms of debugging this 
issue?

Thanks in advance.
G.Muruganandam



At 08:17 PM 1/5/2004 -0800, G.Muruganandam wrote:
>Hello Andrew,
>
>Thanks for the input. I'll keep you posted.
>
>regards
>G.Muruganandam
>
>
>At 01:53 PM 1/5/2004 +0100, Andrew Lunn wrote:
>> > Master-RedBoot_2800> ping -h 192.168.200.165
>> > Ethernet send:
>> > 0x00043974: FFFF FFFF FFFF ACDE  48FF 0600 0806        |........H.....  |
>> > 0x00145FDC: 0001 0800 0604 0001  ACDE 48FF 0600 C0A8   |..........H.....|
>> > 0x00145FEC: C8C6 0000 0000 0000  C0A8 C8A5             |............    |
>> > PING: Can't find address of server '192.168.200.165'
>> > Master-RedBoot_2800>
>> >
>> > Could some one help me to fix this ethernet issue and do let me know
>> > if you need more information.
>>
>>This looks like an ARP message to me, which is what i would expect.
>>
>>Use a network sniffer like tcpdump to see if the packet is actually
>>making it onto the network. If there is no packet on the network its
>>probably an issue with PHY configuration or cabling.
>>
>>Then check to see if the host your are trying to ping responds with an
>>ARP reply. If there is no arp reply sent there may be something wrong
>>with the ARP request, like its been truncated, CRC is wrong etc.
>>
>>Then see if they ARP response is being received and then dropped for
>>some reason.
>>
>>Basically, keep debugging....
>>
>>            Andrew
>>
>>--
>>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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