After monitoring for half an hour via Serial, the connection dropped and dmesg got me: To speed up the PHY’s auto-negotiation, you can: Home Questions Tags Users Unanswered. By using our site, you acknowledge that you have read and understand our Cookie Policy , Privacy Policy , and our Terms of Service. Sign up using Email and Password. Sign up or log in Sign up using Google. It seems to be a gigabit-speed problem, and is even easier to reproduce in u-boot, probably because u-boot doesn’t handle errors in the same way as Linux.

Uploader: Akinolmaran
Date Added: 3 June 2010
File Size: 26.26 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 94163
Price: Free* [*Free Regsitration Required]

I connected my device by serial to my desktop and found had some issues with eth0, the device was not up.

LXR linux/drivers/net/ethernet/freescale/fec.c

By using our site, feeescale acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. This can be solved by resetting the server.

Finally, could someone point me in the direction of some material that describes the boot process and how the kernel tries to setup networking when it is booted?

Return to Software – Yocto. Wired connection being dropped Ask Question. If I put the rootfs on the SD card, the kernel will load and I can run dhcpcd to initialize the USB-ethernet dongle and everything works so it seems like the drivers are loaded correctly.


To quickly look at the latest items in dmesg just run dmesg tail. Board index All times are UTC. Because I can’t attach the files to my post, so I put all of my configuration files in the link below: I’ll keep the device connected by serial a couple of hours to see if can replicate the dropout and then check again dmesg.

Home Questions Tags Users Unanswered. If I get a chance to troubleshoot this, I’ll post any updates. I’m guessing it is an issue of marginal signal quality.

No such device RTcfg: I had the same issues with the Yocto image available specifically for Wandboard from the website. It is also printed on the module label. You could go through the standard Ethernet trouble shooting steps like making sure it’s not your cable, your switch.

If I boot the Freescale kernel I see it try eth0 and eth1 before moving on to USB0, and eth2 where it finds my dongle: I found nothing but “device is not ready” on dmesg. It supports half- or full-duplex operation on ohy, Mbps, and Mbps Ethernet networks.

I did many search but still can not figure out how to fix it. Can you post the download link for the image you’re using?

But here ffc ethernet is extremely slow. I’ve read about a different board with similar problems, where the solution was to tweak the passives around the magnetics. Got DHCP answer from Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge phu you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.


If I boot the Freescale kernel I see it try eth0 and eth1 before moving on to USB0, and eth2 where it finds my dongle:. Email Required, but gec shown. Does any of you know what to do, or has some suggestions for me to try out? No such device ioctl add: New stuff added guys.

Porting i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821)

Do you have any idea how to solve this issue? To speed up the PHY’s tec, you can:. Select all root wandboard-quad: This guy has a similar issue, but solves it by removing some udev rules from his Debian image.

Then I looked into rtnet script and did some minor change.