* [ECOS] Re: Establishing ethernet support, ping failure
@ 2004-05-06 3:51 Aniket S Joshi
0 siblings, 0 replies; 6+ messages in thread
From: Aniket S Joshi @ 2004-05-06 3:51 UTC (permalink / raw)
To: klawson; +Cc: ecos-discuss
>I couldn't see any debug from the ISR. Are you sure you have:
>a. Interrupts working in your system
>b. The Ethernet driver pointing to the correct interrupt
>I suggest you fire up your debugger and try to get the Ethernet driver
>handling receive/transmit interrupts.
Yes, I am also doing the same debuging of Network Interrupt....
Till the time I found that Network interrupt is initialiseing but Network interrupt routine is not getting executed...
I will debug & Let you know...
Thanks for your support
Aniket
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Re: Establishing ethernet support, ping failure
2004-05-05 7:28 Aniket S Joshi
@ 2004-05-05 8:54 ` Kelvin Lawson
0 siblings, 0 replies; 6+ messages in thread
From: Kelvin Lawson @ 2004-05-05 8:54 UTC (permalink / raw)
To: ecos-discuss
Aniket S Joshi wrote:
> Hi All,
>
> I am tring to build ethernet support for Sh-7729 Board +ECOS.
> Pls find attached file with debug Otpion enable.
> I am still not able to ping my target system.
>
> Pls look at the debug messageds & Help me.
>
> PING server 192.168.174.47
> dp83902a_can_send
> dp83902a_send
> TX prep page 128 len 64
> sg buf 8c085e56 len 0000002a
> ffff ffff ffff 000b dbc1 c4fe 0806 0001
> 0800 0604 0001 000b dbc1 c4fe c0a8 ae6a
> 0000 0000 0000 c0a8 ae2f
> + 22 bytes of padding
> dp83902a_start_xmit
> Tx pkt 128 len 64
> dp83902a_can_send
> recvfrom: Operation timed out
I couldn't see any debug from the ISR. Are you sure you have:
a. Interrupts working in your system
b. The Ethernet driver pointing to the correct interrupt
I suggest you fire up your debugger and try to get the Ethernet driver
handling receive/transmit interrupts.
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Re: Establishing ethernet support, ping failure
@ 2004-05-05 7:28 Aniket S Joshi
2004-05-05 8:54 ` Kelvin Lawson
0 siblings, 1 reply; 6+ messages in thread
From: Aniket S Joshi @ 2004-05-05 7:28 UTC (permalink / raw)
To: klawson; +Cc: ecos-discuss
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
Hi All,
I am tring to build ethernet support for Sh-7729 Board +ECOS.
Pls find attached file with debug Otpion enable.
I am still not able to ping my target system.
Pls look at the debug messageds & Help me.
Thanks in Advance
Aniket
>>> Kelvin Lawson <klawson@ad-holdings.co.uk> 04/29/04 08:45PM >>>
Hi Aniket,
> Section2: ECOS SH7729 Hardware to server ARP request (But no response from Server)
>
> 192.168.174.106 (Board) to 192.168.174.47 ARP Request
> MAC of 192.168.174.107 (C0 A8 AE 6A) is : 00 0B DB C1 C4 FE
>
> 0000: FF FF FF FF FF FF 00 0B DB C1 C4 FE 08 06 00 01 ................
> 0010: 08 00 06 04 00 01 00 0B DB C1 C4 FE C0 A8 AE 6A ...............j
> 0020: 00 00 00 00 00 00 C0 A8 AE 2F 00 00 00 00 00 00 ........./......
> 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 0040:
>
> No response
According to this you're not getting any response from the server. It's
more likely, however, that you're just not seeing the ARP response
because you're running Spynet on a different machine. Unless you're
using a hub or running Spynet on 192.168.174.47, the Spynet machine
won't capture the ARP responses.
I suspect that the ARP response is actually being sent by the server,
but it is not being passed up to the eCos stack by your Ethernet driver.
Could you put some debug statements in the Ethernet driver to find out
if you're actually receiving any interrupts at all ? You seem to be
using DP83902A - you can set the debug level in the file dp83902a.h.
Using the debug you should be able to find out whether the ARP response
from the server is actually being received at all by the Ethernet
driver. If you're not receiving any packets at all, then adding the ARP
entry for the server won't help you.
Cheers,
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
[-- Attachment #2: ping_lo_output.txt --]
[-- Type: text/plain, Size: 6045 bytes --]
ADMIN@JOSHI /ecos-c/ecos-work/MDM
$ sh-elf-gdb -nw a.out
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=sh-elf"...
(gdb) set remotebaud 38400
(gdb) target remote com1
Remote debugging using com1
0x8000a1ae in ?? ()
(gdb) load
Loading section .vectors, size 0x890 lma 0x8c020000
Loading section .text, size 0x46390 lma 0x8c020890
Loading section .rodata, size 0x2b5c lma 0x8c066c20
Loading section .data, size 0x153c lma 0x8c069780
Start address 0x8c020000, load size 306360
Transfer rate: 28833 bits/sec, 449 bytes/write.
(gdb) c
Continuing.
[cyg_net_init] Init: mbinit(0x00000000)
[cyg_net_init] Init: cyg_net_init_devs(0x00000000)
Init device 'dp83902a_eth0'
dp83902a_init
154
DP83902A - static ESA: 00:0b:db:c1:c4:fe
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
IFP: 0x8c069b5c, next: 0x8c0b7bcc
IFP: 0x8c0b7bcc, next: 0x00000000
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x8c06a6cc)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x8c06a0e4)
New domain route at 0x00000000
[cyg_net_init] Init: cyg_route_init(0x00000000)
[cyg_net_init] Done
Start PING test
BOOTP[eth0] op: REPLY
htype: Ethernet
hlen: 6
hops: 0
xid: 0x0
secs: 0
flags: 0x0
hw_addr: 00:0b:db:c1:c4:fe
client IP: 192.168.174.106
my IP: 192.168.174.106
server IP: 192.168.6.1
gateway IP: 192.168.174.47
options:
subnet mask: 255.255.255.0
IP broadcast: 192.168.174.255
gateway: 192.168.174.47
dp83902a_start
dp83902a_can_send
dp83902a_send
TX prep page 128 len 64
sg buf 8c085fd6 len 0000002a
ffff ffff ffff 000b dbc1 c4fe 0806 0001
0800 0604 0001 000b dbc1 c4fe c0a8 ae6a
0000 0000 0000 c0a8 ae6a
+ 22 bytes of padding
dp83902a_start_xmit
Tx pkt 128 len 64
dp83902a_can_send
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
dp83902a_start
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
dp83902a_can_send
dp83902a_send
TX prep page 128 len 64
sg buf 8c085f56 len 0000002a
ffff ffff ffff 000b dbc1 c4fe 0806 0001
0800 0604 0001 000b dbc1 c4fe c0a8 ae6a
0000 0000 0000 c0a8 ae6a
+ 22 bytes of padding
dp83902a_start_xmit
Tx pkt 128 len 64
dp83902a_can_send
dp83902a_stop
dp83902a_start
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
PING server 127.0.1.1
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
recvfrom: Operation timed out
Sent 16 packets, received 0 OK, 0 bad
PING server 192.168.174.47
dp83902a_can_send
dp83902a_send
TX prep page 128 len 64
sg buf 8c085e56 len 0000002a
ffff ffff ffff 000b dbc1 c4fe 0806 0001
0800 0604 0001 000b dbc1 c4fe c0a8 ae6a
0000 0000 0000 c0a8 ae2f
+ 22 bytes of padding
dp83902a_start_xmit
Tx pkt 128 len 64
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_send
TX prep page 136 len 64
sg buf 8c085dd6 len 0000002a
ffff ffff ffff 000b dbc1 c4fe 0806 0001
0800 0604 0001 000b dbc1 c4fe c0a8 ae6a
0000 0000 0000 c0a8 ae2f
+ 22 bytes of padding
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
Sent 16 packets, received 0 OK, 0 bad
PING server 127.0.1.1
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
dp83902a_can_send
dp83902a_can_send
recvfrom: Operation timed out
Sent 16 packets, received 0 OK, 0 bad
PING server 192.168.174.47
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
sendto: Host is down
Sent 16 packets, received 0 OK, 0 bad
dp83902a_can_send
dp83902a_can_send
dp83902a_can_send
dp83902a_can_send
PASS:<Done pinging loopback>
EXIT:<done>
[-- Attachment #3: Type: text/plain, Size: 148 bytes --]
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Re: Establishing ethernet support, ping failure
2004-04-29 9:53 Aniket S Joshi
@ 2004-04-29 15:46 ` Kelvin Lawson
0 siblings, 0 replies; 6+ messages in thread
From: Kelvin Lawson @ 2004-04-29 15:46 UTC (permalink / raw)
To: ecos-discuss
Hi Aniket,
> Section2: ECOS SH7729 Hardware to server ARP request (But no response from Server)
>
> 192.168.174.106 (Board) to 192.168.174.47 ARP Request
> MAC of 192.168.174.107 (C0 A8 AE 6A) is : 00 0B DB C1 C4 FE
>
> 0000: FF FF FF FF FF FF 00 0B DB C1 C4 FE 08 06 00 01 ................
> 0010: 08 00 06 04 00 01 00 0B DB C1 C4 FE C0 A8 AE 6A ...............j
> 0020: 00 00 00 00 00 00 C0 A8 AE 2F 00 00 00 00 00 00 ........./......
> 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 0040:
>
> No response
According to this you're not getting any response from the server. It's
more likely, however, that you're just not seeing the ARP response
because you're running Spynet on a different machine. Unless you're
using a hub or running Spynet on 192.168.174.47, the Spynet machine
won't capture the ARP responses.
I suspect that the ARP response is actually being sent by the server,
but it is not being passed up to the eCos stack by your Ethernet driver.
Could you put some debug statements in the Ethernet driver to find out
if you're actually receiving any interrupts at all ? You seem to be
using DP83902A - you can set the debug level in the file dp83902a.h.
Using the debug you should be able to find out whether the ARP response
from the server is actually being received at all by the Ethernet
driver. If you're not receiving any packets at all, then adding the ARP
entry for the server won't help you.
Cheers,
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Re: Establishing ethernet support, ping failure
@ 2004-04-29 9:53 Aniket S Joshi
2004-04-29 15:46 ` Kelvin Lawson
0 siblings, 1 reply; 6+ messages in thread
From: Aniket S Joshi @ 2004-04-29 9:53 UTC (permalink / raw)
To: klawson; +Cc: ecos-discuss
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
Hi,
Sorry for the late reply.
Pls find attched file
1. gdb.txt : Debug output
2. ecos_arp.txt : Arp request captured using Spynet
Still we are not able to ping the h/w from PC...
Can you pls tell us thet How to add ARP entry in Ecos Application?
Thanks & Regards
Aniket Joshi
>>> Kelvin Lawson <klawson@ad-holdings.co.uk> 04/23/04 06:46PM >>>
Aniket S Joshi wrote:
> Hello,
>
> We are trying to add the networking support for Hitachi 7729 hardware. we have removed the network support from Redboot and downloading application through serial port.
>
> Application is built with network support configuration (freeBSD)
>
> We testing the network support added with ping command.
>
> Loopback test on the board with ping command works fine.
> (ping 127.0.0.1 works fine on the board)
>
> But there is no response, when we ping the board from host PC or ping host PC from the board.
> (ping timeout)
>
> pls give us the solution
Have you enabled any debug messages in your build ? What do they say ?
You can turn on debug in the Common Ethernet Support package
(CYGDBG_IO_ETH_DRIVERS_DEBUG). You may also be able to enable extra
debug in the Ethernet driver itself.
Have you checked with Ethereal/tcpdump whether any traffic is actually
leaving your board ? Do you have any LEDs on the Ethernet port, and do
they light up when you start your application ?
Can you see any messages like "client IP: 10.0.0.1" when you start your
application ? Depending on your configuration it may be necessary to
call init_all_network_interfaces() in your applicaiton. However, if
loopback is working then maybe this isn't necessary.
Without more information like this it is difficult to guess what your
problem might be.
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
[-- Attachment #2: gdb.txt --]
[-- Type: text/plain, Size: 2261 bytes --]
ADMIN@JOSHI /ecos-c/ecos-work/MDM
$ sh-elf-gdb -nw a.out
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=sh-elf"...
(gdb) set remotebaud 38400
(gdb) target remote com1
Remote debugging using com1
0x8000a13e in ?? ()
(gdb) load
Loading section .vectors, size 0x890 lma 0x8c020000
Loading section .text, size 0x586b0 lma 0x8c020890
Loading section .rodata, size 0x8354 lma 0x8c078f40
Loading section .data, size 0x3b7c lma 0x8c081298
Start address 0x8c020000, load size 413200
Transfer rate: 28496 bits/sec, 449 bytes/write.
(gdb) continue
Continuing.
[cyg_net_init] Init: mbinit(0x00000000)
[cyg_net_init] Init: cyg_net_init_devs(0x00000000)
Init device 'dp83902a_eth0'
DP83902A - static ESA: 08:88:12:34:56:78
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
IFP: 0x8c083cb4, next: 0x8c0cdca4
IFP: 0x8c0cdca4, next: 0x00000000
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x8c084744)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x8c084180)
New domain route at 0x00000000
[cyg_net_init] Init: cyg_route_init(0x00000000)
[cyg_net_init] Done
Entering twothreads' cyg_user_start() function
BOOTP[eth0] op: REPLY
htype: Ethernet
hlen: 6
hops: 0
xid: 0x0
secs: 0
flags: 0x0
hw_addr: 00:0B:DB:C1:C4:FE
client IP: 192.168.174.106
my IP: 192.168.174.106
server IP: 192.168.172.55
gateway IP: 192.168.174.47
options:
subnet mask: 255.255.255.0
IP broadcast: 192.168.174.255
gateway: 192.168.174.47
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
Initiligation done
Delay com
Get data of Screen no = 4
Print text of Screen no = 4
Screen:19202122 Printed
No data has to print in Screen no:4
[-- Attachment #3: ecos_arp.txt --]
[-- Type: text/plain, Size: 1273 bytes --]
Section1: PC to server ARP request & Response captured in spynet
192.168.174.107 to 192.168.174.47 ARP Request
MAC of 192.168.174.107 (C0 A8 AE 6B) is : 00 0B DB C2 44 72
0000: FF FF FF FF FF FF 00 0B DB C2 44 72 08 06 00 01 ..........Dr....
0010: 08 00 06 04 00 01 00 0B DB C2 44 72 C0 A8 AE 6B ..........Dr...k
0020: 00 00 00 00 00 00 C0 A8 AE 2F ........./
Response
0000: 00 0B DB C2 44 72 00 01 F4 11 C6 B1 08 06 00 01 ....Dr..........
0010: 08 00 06 04 00 02 00 01 F4 11 C6 B1 C0 A8 AE 2F .............../
0020: 00 0B DB C2 44 72 C0 A8 AE 6B 00 00 00 00 00 00 ....Dr...k......
0030: 00 00 00 00 00 00 00 00 00 00 00 00 ............
----------------------------------------------------------------------------
Section2: ECOS SH7729 Hardware to server ARP request (But no response from Server)
192.168.174.106 (Board) to 192.168.174.47 ARP Request
MAC of 192.168.174.107 (C0 A8 AE 6A) is : 00 0B DB C1 C4 FE
0000: FF FF FF FF FF FF 00 0B DB C1 C4 FE 08 06 00 01 ................
0010: 08 00 06 04 00 01 00 0B DB C1 C4 FE C0 A8 AE 6A ...............j
0020: 00 00 00 00 00 00 C0 A8 AE 2F 00 00 00 00 00 00 ........./......
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040:
No response
[-- Attachment #4: Type: text/plain, Size: 148 bytes --]
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
* [ECOS] Re: Establishing ethernet support, ping failure
2004-04-21 17:42 [ECOS] " Aniket S Joshi
@ 2004-04-23 14:17 ` Kelvin Lawson
0 siblings, 0 replies; 6+ messages in thread
From: Kelvin Lawson @ 2004-04-23 14:17 UTC (permalink / raw)
To: ecos-discuss
Aniket S Joshi wrote:
> Hello,
>
> We are trying to add the networking support for Hitachi 7729 hardware. we have removed the network support from Redboot and downloading application through serial port.
>
> Application is built with network support configuration (freeBSD)
>
> We testing the network support added with ping command.
>
> Loopback test on the board with ping command works fine.
> (ping 127.0.0.1 works fine on the board)
>
> But there is no response, when we ping the board from host PC or ping host PC from the board.
> (ping timeout)
>
> pls give us the solution
Have you enabled any debug messages in your build ? What do they say ?
You can turn on debug in the Common Ethernet Support package
(CYGDBG_IO_ETH_DRIVERS_DEBUG). You may also be able to enable extra
debug in the Ethernet driver itself.
Have you checked with Ethereal/tcpdump whether any traffic is actually
leaving your board ? Do you have any LEDs on the Ethernet port, and do
they light up when you start your application ?
Can you see any messages like "client IP: 10.0.0.1" when you start your
application ? Depending on your configuration it may be necessary to
call init_all_network_interfaces() in your applicaiton. However, if
loopback is working then maybe this isn't necessary.
Without more information like this it is difficult to guess what your
problem might be.
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-05-06 3:51 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-06 3:51 [ECOS] Re: Establishing ethernet support, ping failure Aniket S Joshi
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 7:28 Aniket S Joshi
2004-05-05 8:54 ` Kelvin Lawson
2004-04-29 9:53 Aniket S Joshi
2004-04-29 15:46 ` Kelvin Lawson
2004-04-21 17:42 [ECOS] " Aniket S Joshi
2004-04-23 14:17 ` [ECOS] " Kelvin Lawson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).