Can't get ethernet connected on rpi400.
71 posts, 17 voices
Fredrik Olsson (9165)
23 posts
|
is what my 400 v1.1 is reporting. |
|
Fredrik Olsson (9165)
23 posts
|
Well, the firmware was old, but there was no change after updating it to a recent one (December 2021) and switching out the above mentioned files from my Raspbian install (both updated two days ago obviously). Still no network in RISC OS, same output from RMLoad. |
David Pitt (3386)
1248 posts
|
On the RPi400 1.0 the PHY address is different and the MAC address is shown. *rmrun EtherGENETD PHY addr 1, id=84A2600D EUI48 xx:xx:xx:xx:xx:xx CMOS restored from 0x3C as 0xFC Total of 1 EtherGE interfaces Got mbufs, going online Configuring PHY on MAC 0 from CMOS 0xFC Setting PHY for autonegotiate NIC on MAC 0 running Malloc filter 10800 at 202171f4 Reviewed ege0, new alevel=2, new elevel=0 Malloc filter 10806 at 202171d4 Reviewed ege0, new alevel=2, new elevel=0 Malloc filter 18035 at 20217dd4 Reviewed ege0, new alevel=2, new elevel=0 Announced ege0 is starting * |
Sprow (202)
1158 posts
|
Patting myself on the back for the PHY scanning code working at least – that’s the right id (164x and 0022 where x = silicon revision) for a Micrel KSZ9131.
The comment about the PHY being at address 4 as a tell is a bit unusual, since by probing we’ve found the PHY. I also looked at the bootloader commit messages from Feb-Apr 2021 which is the date of the start4.elf suggested, but there’s zero mentions of anything KSZ/PHY/Ethernet related. Perhaps it was sneaked in on the quiet so as not to pre-announce it? Anyway, another roll of the dice is here since the Broadcom LED control register happens to be the Micrel auto MDI-X control register, which might be an issue. The other 3 writes are all to IEEE standard ones. |
|
Fredrik Olsson (9165)
23 posts
|
No change except for the Mallocs. Just to verify that I’m not doing anything stupid here, RISC OS isn’t something I’m familiar with. |
Rob Andrews (112)
164 posts
|
Why are you reloading etherGENETD it in the rom so should be loaded already. |
Stuart Swales (8827)
1357 posts
|
@Rob: It’s a different PHY chip on this revision of the board so there are issues with the module in the ROM |
|
Fredrik Olsson (9165)
23 posts
|
@Rob: I’m trying Sprow’s test versions of the module. Still no luck though, it’s still reporting that the ethernet cable isn’t connected. :-/ |
|
Sprow (202)
1158 posts
|
Bah, so it wasn’t those LED writes then. I’ve added a loop to print out all 32 registers (there are some banked registers too but their defaults look sane so can probably be left alone), it’d be helpful if you could try this twice – once with cable plugged in and once without so that it’s possible to compare any status bits relating to a live link. |
Chris James (9185)
6 posts
|
I’ve had the same problem as @Fredrik, so I’m happy this isn’t some weird issue with my setup, cables or a dodgy Pi400. The board reports as v1.1. I have current FIXUP4.DAT and START4.ELF on the boot device. RISC OS 5.28 DIRECT installed. I just tried @Sprow’s latest EtherGENETD module, with the outputs below. There are some minor changes in the line starting: FA207EC4. I’m happy to test further iterations of the module. [Cable disconnected]
[Cable connected]
|
|
Fredrik Olsson (9165)
23 posts
|
And this is the output from my 400. [Cable disconnected] [Cable connected] Edit: It seems I ran this with the old start4.elf and fixup4.dat, after fixing that the only thing that changed was the PHY address. (From 7 to 4). |
|
Sprow (202)
1158 posts
|
To Chris James: To Fredrik Olsson:
It was a bit odd that the PHY address changed! That doesn’t seem important since all the other MII registers come out OK, unless there’s some errata in the MAC which only works with certain addresses. |
Steve Pampling (1551)
8170 posts
|
Half duplex on an auto-neg is usually fixed duplex at the other end, giving no auto-neg response, so the NIC fails down to the lowest common denominator. Always useful to check the cable with a known good device on the end. |
|
Chris James (9185)
6 posts
|
Unfortunately no, it didn’t connect. I revised my config and *status reports:
Interface was set to DHCP, and rmload-ing reported this:
Still no luck connecting. I tried using a fixed IP address. No luck. Reverting to DHCP still no luck. Interfaces GUI reports Activity at 10Mbps, OK [X] Full duplex [X] Active [ok] Polarity [ok]. Not sure if this provides any more info:
I note the SIMPLEX on both USB and EtherGENET interfaces – I’ll check again from Raspberry Pi OS and see whether that reports the same i.e. whether the wireless bridge I’m using has issues. UPDATE: from Pi OS
|
|
Fredrik Olsson (9165)
23 posts
|
@Sprow And here’s the result from my tests, still no connection. :-/ |
|
Fredrik Olsson (9165)
23 posts
|
@Steve: After each test I move the ethernet cable and sd card to my Pi4 to write the report, so I’d imagine that it rules out everything but the Pi400. |
|
Sprow (202)
1158 posts
|
Does Pi OS come with |
|
David Pitt (3386)
1248 posts
|
From Raspberry Pi OS bullseye 64bit on RPi4 :-
pi@bullseye64:~ $ sudo mii-tool -v -v eth0
Using SIOCGMIIPHY=0x8947
eth0: negotiated 1000baseT-HD flow-control, link ok
registers for MII PHY 1:
1140 796d 600d 84a2 0de1 c1e1 006d 0000
0000 0300 0c00 0000 0000 0000 0000 3000
0000 0000 0000 0000 ffff 0180 0180 0000
71e7 871c 0030 fff1 34aa 0000 0000 0000
product info: vendor 18:c0:86 or 18:03:61, model 10 rev 2
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
pi@bullseye64:~ $
|
|
Fredrik Olsson (9165)
23 posts
|
Same OS, no cable connected though. Have to run, will run it again with a cable connected this weekend. |
|
Chris James (9185)
6 posts
|
From Raspberry Pi OS Bullseye (32-bit) on Pi 400, connected and online:
|
|
Fredrik Olsson (9165)
23 posts
|
So, here we have Raspbian 64-bit on Pi 400, online. And just for good measure: |
Michael Grunditz (8594)
259 posts
|
Are you from Sweden? I live in Uppsala. Anyway.. I have used RISC OS with ethernet on pi400 , but not on a Swedish one. |
|
Fredrik Olsson (9165)
23 posts
|
What a kind offer, however I’ve got RISC OS running perfectly on a Pi 4. Anyway, if you’re willing to part with your pi400 I’d be happy to buy it since I need another Pi 400 for a little project (where the keyboard is of no consequence). Contact me at {redacted :-)} if you’re interested. |
|
Sprow (202)
1158 posts
|
It arrived but has the traditional Broadcom PHY, so that’s no help. Chris – are you in the UK? I could post you a UK layout Pi 400 in exchange for yours if so (email address at the top level page on the website the debug driver is on). Otherwise I might try again and get a non-UK layout in the hope of striking it lucky. There are some bit differences between the dumps from Linux and RISC OS, but none of them strike me as significant or reasons that autonegotiate would fall over. |
|
Fredrik Olsson (9165)
23 posts
|
@Sprow If you’re unable to switch the complete unit with someone, we could switch motherboards. Let’s call it Plan B, since I imagine postage would be a bit higher. |
