Re: Trying to make usb networking work

Hello,

Here's my current status report, before going to bed and continue to
investigate tomorrow:

I added tcpdump from Familiar 0.7.2 to my initrd. I also had to copy
libc stuff and other dependencies
(http://michaelo.free.fr/pda/h2210/starterkit/initrd_minimum_usb_feb24tcpdump),
and enable CONFIG_PACKET in the kernel (my image is
http://michaelo.free.fr/pda/h2210/starterkit/zImage_minimum_usb_feb24).

The ipaq is 192.168.0.200 and the PC is 192.168.0.201. Both are trying
to ping each other.

Here's what I get on the iPAQ from /usr/sbin/tcpdump -i usb0:

device usb0 entered promiscuous mode
tcpdump: listening on usb0
12:11:45.481083 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:46.481081 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:47.501259 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:48.501083 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:49.501077 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:50.501778 arp who-has 192.168.0.201 tell 192.168.0.200
12:11:51.501083 arp who-has 192.168.0.201 tell 192.168.0.200
... (nothing different)

And on the PC:

22:56:58.099230 arp who-has 192.168.0.201 tell 192.168.0.200
22:56:59.098659 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:00.099087 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:01.100502 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:02.099948 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:03.100378 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:04.101789 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:05.101226 arp who-has 192.168.0.201 tell 192.168.0.200
22:57:05.120230 arp reply 192.168.0.201 is-at 3e:3a:93:d7:3b:f0
22:57:05.121221 arp reply 192.168.0.201 is-at 3e:3a:93:d7:3b:f0
... (the same sequence starts again).

It seems that the PC doesn't know where to reply to... I guess there
should be an IP address instead of "3e:3a:93:d7:3b:f0"

To be continued. I'm a novice in networking, so I still have lots of
things to learn.

Don't hesitate to reproduce this too and try not to reproduce it, of
course! If you have suggestions too, don't send them to your iPAQ
through the USB cable, but instead...

;-)

    Cheers,

    Michael.

>On Tue, 24 Feb 2004 15:00:12 +0100
>Michael Opdenacker <zumbi3_at_free.fr> wrote:
>
>
>
>># mount /proc
>># insmod
>>/lib/modules/2.6.1-rmk0-hh0/kernel/drivers/usb/gadget/pxa2xx_udc.ko (I
>>haven't installed modutils yet in my home made initrd)
>><6>pxa2xx_udc: version 7-Nov-2003
>>pxa2xx_udc: version 7-Nov-2003
>>
>>
>If you disable "Low-level kernel debugging" in kernel config, you won't
>get these funny duplicate messages. This option is good in the
>beginning, but as you have a working serial console there's no need to
>use it anymore.
>
>
>
>># ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0 broadcast
>>192.168.0.255
>># route add 192.168.0.201 dev usb0
>>
>>
>I think you don't have to add a explicit route since when a interface
>comes up, a line is automatically added to the route table.
>
>
>
>>Then I make ping tries on both sides. This is unsuccessful, but
>>re-running ifconfig is interesting:
>>
>>
>
>
>
>>There are more transmitted packets, but just because I couldn't run
>>both ifconfig commands at the same time. It seems that all transmitted
>>packets are received by the PC host.
>>
>>
>To better see it you can use tcpdump or something similar. It would be
>also very helpful to run tcpdump on iPAQ (get the ipk file and unpack it
>- it's either a .tar.gz file or an .a file (unpack with ar x)).
>
>Some thoughts: it is possible that some GPIO haven't been set up
>correctly, and this prevents UDC from receiving packets. A possible
>cause could be the H2200_GPIO_USB_PULL_UP_N signal, but if it is really
>a inverted signal, it looks like it is initialized correctly. However,
>if it is really a non-inverted signal, you can try to change
>SET_H2200_GPIO_N(USB_PULL_UP, 0); to SET_H2200_GPIO_N (..., 1) and vice
>versa - 1 to 0 in h2200.c, then see if this makes any difference.
>
>--
>Greetings,
> Andrew
>_______________________________________________
>H2200-port mailing list
>H2200-port_at_handhelds.org
>https://handhelds.org/mailman/listinfo/h2200-port
>
>
>
>

-- 
Michael Opdenacker
http://opdenacker.org/