Hi, On Thursday, 15.03.2018 at 15:22, Andre Przywara wrote: > Briefly - while compiling ;-) - looked at the schematics. There is a > jumper (PHYRST1) that needs to be empty, also PD24 must not be tied low. > PD14 is used for that on the Pine64, and so far we get away with doing > nothing there. The pin is not configured, so High-Z, and a pull-up does > the right thing. Not sure if we need any special handling on the > Olinuxino. If you can measure 3.3V over the pins of that jumper, we > should be good. > There does not seem to be a special voltage rail required.
Both boards shipped with PHYRST1 empty. Unfortunately I don't have any equipment here to measure voltage on the jumper, can try next week when I'm back at my office. > Out of curiosity, did you change the sun50i-a64-olinuxino.dts from the > kernel? I don't see any emac or phy node in there, so with this .dtb it > can't actually work. You're right; I just assumed that sun50i-a64-olinuxino.dts was complete without looking at it. I've tried copying over the &emac and &mdio from the pine64 dts but while that results in the module loading the kernel doesn't see link status or a MAC address (all zeroes) and attempting to set the MAC address results in an immediate OOPS. However, lights do blink on the connector so it looks like its powered correctly. A friend checked the schematics for me and says that the Olimex uses a different PHY (KSZ9031RNXCC) from that of the Pine64 so this is probably expected. While browsing the Olimex github I also found this DTS [1]. Based on my (little) understanding of device trees it looks to be intended for a very different kernel and/or U-boot but nevertheless may be helpful in figuring out what should go in the mainline DTS. Cheers, -mato [1] https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A64/A64-ubuntu_built_preliminary_rel_2/a64-olinuxino.dts -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
