Hello again,
here come the recent insights.
On Tue, Nov 11, 2014 at 10:06:49AM +0100, Uwe Kleine-König wrote:
> shouldn't it? It has the address 192.168.77.1). Running "ping 192.168.77.1"
> seems to result in packages like this:
>
> 10:01:30.233928 42:40:00:10:40:60 > 00:00:00:34:00:12, ethertype MOP RC (0x6002), length 60:
> 0x0000: 0000 0034 0012 4240 0010 4060 6002 4000 ...4..B@..@``.@.
> 0x0010: 0054 8080 0012 4100 0002 c095 08e8 01a0 .T....A.........
> 0x0020: 1420 0020 8001 1020 0000 0000 0000 0000 ................
> 0x0030: 0000 0000 0000 0000 0000 0000 ............
>
> which is utter nonsense.
I sprinkled printfs over the network driver. The packet that is intended
to be sent looks ok:
Send a packet (len = 42, txdesc=0x01f15000):
01f12040: ff ff ff ff ff ff 28 c6 8e 36 df 57 08 06 00 01 ......(..6.W....
01f12050: 08 00 06 04 00 01 28 c6 8e 36 df 57 c0 a8 4d 85 ......(..6.W..M.
01f12060: 00 00 00 00 00 00 c0 a8 4d 01 ........M.
That's an ARP request asking for the address of 192.168.77.1 which is
expected. After that, both the descriptor and the data buffer look ok:
barebox:/ md 0x01f15000+32
01f15000: fefeffff 002a6fef 01f12040 f7effff4 .....o*.@ ......
01f15010: fcfefcfa ff2fbff6 fdfbffef 01f14ff8 ....../......O..
barebox:/ md -b 0x01f12040+42
01f12040: ff ff ff ff ff ff 28 c6 8e 36 df 57 08 06 00 01 ......(..6.W....
01f12050: 08 00 06 04 00 01 28 c6 8e 36 df 57 c0 a8 4d 85 ......(..6.W..M.
01f12060: 00 00 00 00 00 00 c0 a8 4d 01 ........M.
And I don't see what this has to do with the packet that enters my router:
10:26:31.133258 fe:bf:f7:f3:fb:7f (oui Unknown) > da:74:f7:fc:fb:fa (oui Unknown), ethertype Unknown (0xdfbf), length 60:
0x0000: da74 f7fc fbfa febf f7f3 fb7f dfbf fffb .t..............
0x0010: dffd ffea 7ffd c6e7 fffb faff febd fb5f ..............._
0x0020: fefb effc fefc eff5 0000 0000 0000 0000 ................
0x0030: 0000 0000 0000 0000 0000 0000 ............
The size looks OK (it was increased from 42 to 60 because that's the
minimal size that is supported by ethernet). So my theory is that either
the phy or some setting in the ethernet address range is broken.
The output of
md -s /dev/phy1
looks sane, too:
barebox:/ md -s /dev/phy1
00000000: 796d1140 0e900141 cde101e1 2001000f @.myA..........
00000010: 03004502 00003800 00000000 30000000 .E...8.........0
00000020: bc083060 1c400080 00000020 00000000 `0....@. .......
00000030: 00000000 00000040 00000000 00000000 ....@...........
It seems to be not possible to easily dump the register space in both
U-Boot and barebox for comparison. md 0xf1074000+0x4000 just hangs
somewhere in the middle.
A difference between U-Boot and barebox is the location where the
internal registers are mapped. Maybe something that depends on U-Boot's
memory layout leaks into barebox because I do 2nd stage booting?
Out of ideas at the moment. :-(
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
