09-30-2016, 09:41 AM
(09-29-2016, 07:39 PM)stepw Wrote: Doesn't look like slave/master role is of any impact on RTL8211E PHY. I can force slave or master mode on the NIC of the connected PC and PINE64 PHY reports corresponding opposite role, but packet loss persists when pinging from PINE64 to the connected device. Forcing role on PINE64 PHY also results in correct role on both sides, also of no effect on the problem.smart thinking
1. PINE64 - Auto mode (PHY reg 0x9 = 0x0300), PC - Auto mode
PINE64 PHY reg 0xA = 0x3800 = Gigabit Slave
11 packets transmitted, 8 received, 27% packet loss, time 9999ms
2. PINE64 - Auto mode (PHY reg 0x9 = 0x0300), PC - Slave mode
PINE64 PHY reg 0xA = 0x7800 = Gigabit Master
14 packets transmitted, 9 received, 35% packet loss, time 13005ms
3. PINE64 - Master mode (PHY reg 0x9 - 0x1A00), PC - Slave mode
PINE64 PHY reg 0xA = 0x7800 = Gigabit Master
14 packets transmitted, 10 received, 28% packet loss, time 13008ms
4. PINE64 - Slave mode (PHY reg 0x9 - 0x1200), PC - Slave mode
PINE64 PHY reg 0xA = 0x0000 = Master/Slave fault, not capable of 1Gbps, up at 100Mbps
46 packets transmitted, 46 received, 0% packet loss, time 45001ms
5. PINE64 - Slave mode (PHY reg 0x9 - 0x1200), PC - Master mode
PINE64 PHY reg 0xA = 0x3800 = Gigabit Slave
13 packets transmitted, 11 received, 15% packet loss, time 12004ms
6. PINE64 - Slave mode (PHY reg 0x9 - 0x1200), PC - Auto
PINE64 PHY reg 0xA = 0x3800 = Gigabit Slave
19 packets transmitted, 6 received, 68% packet loss, time 18004ms
thanks for busting my dreams
Well, that takes us back to the fact that is seems these boards realy ARE broken from a HW point of view.
I'm starting to question the sanity of keeping production going at this point .... shouldn't this get fixed first ?
//waldo