You are not logged in.
Hey,
I have the following problem:
when i connect the WARP board over Ethernet to an Ethernet-switch and then to another device it works well and the LEDs show the regular behavior (D23 is on, D21 is off, D25 blinks on traffic). But when i directly connect the WARP board to a device (an RPI) the LEDs D21 and D23 are on D25 is off and there is no connection. Any guess why?
BR
Offline
See this thread - you probably need a crossover cable to connect the two devices that don't implement auto-crossover.
Offline
Ah ok thanks. I will try that, but i thought as the Marvel chips on the Warp boards and the Rpi both used to have auto mdi-x implemented the crossover would be handled automatically.
Offline
The Ethernet PHY on WARP v3 does support mdi/mdi-x, but it requires interaction with the MAC to actually monitor and configure the crossover logic. Our reference designs to not implement this behavior. The code for this is frustratingly complex (and, I think, requires the NDA-covered datasheet to implement), so we decided to omit it given the majority of WARP v3 setups use an Ethernet switch.
Offline
Ok, thank you very much murphpo! I will try a crossovercable.
Offline
Hey, actually using a crossover cable (for 10/100 Mb Ethernet) doesn't work. Might the problem come from the speed differences? RPI only has a 10/100 MB/s Ethernet-interface while the WARP boards support GB-Ethernet?
Offline
Hey,
i think i found the problem. The RPI also works with a straight through cable but does not allow auto-negotiation, so therefore the Ethernet-Speed at the WARP board has to be set to 100. At 100 the LEDs just operate otherwise than with a speed 1000 (at least in my configuration).
BR
Offline
Right, the WARPLab and 802.11 Ref Designs configure the WARP v3 Ethernet interfaces for 1Gb mode. You can change this to 100 in the C code.
Offline