[ECOS] problem running network tests on viper

[ECOS] problem running network tests on viper

[Paul Randall]

Hi all,

I am trying to run some of the networking tests on the viper.  When I
try to run the ping_test from Insight, I get the following output:

0xfe00a5fc in ?? ()
Loading section .text, size 0x42738 lma 0x20000
Loading section .rodata, size 0x2e57c lma 0x62738
Loading section .data, size 0x1140 lma 0x90cb8
Start address 0x20000, load size 466420
Transfer rate: 27639 bits/sec, 511 bytes/write.

(gdb) Start PING test
BOOTP[eth0] op: REPLY
       htype: Ethernet
        hlen: 6
        hops: 0
         xid: 0x0
        secs: 0
       flags: 0x0
       hw_addr: ff:ff:ff:ff:ff:ff
     client IP: 206.234.219.88
         my IP: 206.234.219.88
     server IP: 206.234.219.89
    gateway IP: 0.0.0.0
  options:
        subnet mask: 255.255.255.224
       IP broadcast: 206.234.219.255
            gateway: 0.0.0.0
SIOCIFADDR: Bad file handle
Network initialization failed for eth0
SIOCIFADDR: Bad file handle
PASS:<Ping test OK>
EXIT:<done>[New Thread 5]

Program received signal SIGINT, Interrupt.
[Switching to Thread 5]
cyg_test_exit () at
/ecos-c/cygwin/src/ecos/packages/infra/current/src/tcdiag.cxx:129

Why is the ethernet initialization failing and why is the MAC address
set to all ones?  I am using the "Address setups for eth0" option in the
eCos Configuration Tool to initialize the ethernet interface, but I
don't see any place to enter the MAC address.

Any help would be appreciated.

Paul Randall
Delta Information Systems



-- 
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] problem running network tests on viper

[Paul Randall]

Hi everyone,

I just discovered what the problem was.  I didn't have the POSIX File IO
compatibility layer package included in the eCos configuration.  After I
added this package, the pings to the server worked, although four of the
pings timed out and a few were around 1-2 seconds before they got a
response.  The output of the ping_test was:

(gdb) Start PING test
BOOTP[eth0] op: REPLY
       htype: Ethernet
        hlen: 6
        hops: 0
         xid: 0x0
        secs: 0
       flags: 0x0
       hw_addr: ff:ff:ff:ff:ff:ff
     client IP: 206.234.219.88
         my IP: 206.234.219.88
     server IP: 206.234.219.89
    gateway IP: 0.0.0.0
  options:
        subnet mask: 255.255.255.224
       IP broadcast: 206.234.219.255
            gateway: 0.0.0.0
PING server 206.234.219.89
recvfrom: Operation timed out
recvfrom: Operation timed out
64 bytes from 206.234.219.89: icmp_seq=2, time=10ms
recvfrom: Operation timed out
recvfrom: Operation timed out
64 bytes from 206.234.219.89: icmp_seq=5, time=10ms
310 bytes from 206.234.219.89: icmp_seq=6, time=10ms
310 bytes from 206.234.219.89: icmp_seq=3, time=2060ms
64 bytes from 206.234.219.89: icmp_seq=4, time=1070ms
1048 bytes from 206.234.219.89: icmp_seq=9, time=10ms
1294 bytes from 206.234.219.89: icmp_seq=10, time=10ms
556 bytes from 206.234.219.89: icmp_seq=7, time=70ms
802 bytes from 206.234.219.89: icmp_seq=8, time=90ms
1786 bytes from 206.234.219.89: icmp_seq=12, time=30ms
1540 bytes from 206.234.219.89: icmp_seq=11, time=70ms
2278 bytes from 206.234.219.89: icmp_seq=14, time=30ms
Sent 16 packets, received 12 OK, 0 bad
PING server 206.234.219.121
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
sendto: Can't assign requested address
Sent 16 packets, received 0 OK, 0 bad
PASS:<Ping test OK>
EXIT:<done>

Paul Randall
Delta Information Systems

Paul Randall wrote:

> Hi all,
>
> I am trying to run some of the networking tests on the viper.  When I
> try to run the ping_test from Insight, I get the following output:
>
> 0xfe00a5fc in ?? ()
> Loading section .text, size 0x42738 lma 0x20000
> Loading section .rodata, size 0x2e57c lma 0x62738
> Loading section .data, size 0x1140 lma 0x90cb8
> Start address 0x20000, load size 466420
> Transfer rate: 27639 bits/sec, 511 bytes/write.
>
> (gdb) Start PING test
> BOOTP[eth0] op: REPLY
>        htype: Ethernet
>         hlen: 6
>         hops: 0
>          xid: 0x0
>         secs: 0
>        flags: 0x0
>        hw_addr: ff:ff:ff:ff:ff:ff
>      client IP: 206.234.219.88
>          my IP: 206.234.219.88
>      server IP: 206.234.219.89
>     gateway IP: 0.0.0.0
>   options:
>         subnet mask: 255.255.255.224
>        IP broadcast: 206.234.219.255
>             gateway: 0.0.0.0
> SIOCIFADDR: Bad file handle
> Network initialization failed for eth0
> SIOCIFADDR: Bad file handle
> PASS:<Ping test OK>
> EXIT:<done>[New Thread 5]
>
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 5]
> cyg_test_exit () at
> /ecos-c/cygwin/src/ecos/packages/infra/current/src/tcdiag.cxx:129
>
> Why is the ethernet initialization failing and why is the MAC address
> set to all ones?  I am using the "Address setups for eth0" option in the
> eCos Configuration Tool to initialize the ethernet interface, but I
> don't see any place to enter the MAC address.
>
> Any help would be appreciated.
>
> Paul Randall
> Delta Information Systems
>
> --
> 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] problem running network tests on viper

[Gary Thomas]

On Tue, 2002-05-21 at 12:02, Paul Randall wrote:
> Hi everyone,
> 
> I just discovered what the problem was.  I didn't have the POSIX File IO
> compatibility layer package included in the eCos configuration.  After I
> added this package, the pings to the server worked, although four of the
> pings timed out and a few were around 1-2 seconds before they got a
> response.  The output of the ping_test was:
> 

Glad to see that you made some progress here.

Please note that we've done quite a lot of work recently on this 
platform (at the behest of Analogue & Micro :-) and the upcoming
eCos version 2.0 will contain much improved networking support on
the Viper.



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