imx28evk and eth1

[CH1z]

Hello all-

I'm using the i.MX28EVK, and I'm having a hard time bringing up the second NIC consistently. I initially ran into this was the ltib build I made, but then I grabbed the included Linux SD card, and it results in the same behavior. The frustrating thing is that every 4-5 boots or so it works (using the reference image), but the rest of the time it doesn't. When it doesn't work, I get the following in the serial session (from the reference image marked "MX28EVK Linux 110-77224 Rev c"):

/***********************/

eth1: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
PHY: 0:01 - Link is Up - 100/Full
PHY: 0:01 - Link is Down
PHY: 0:01 - Link is Up - 100/Full
PHY: 0:01 - Link is Down
PHY: 0:01 - Link is Up - 100/Full

/***********************/

I thought for a while that it might be a hardware issue, but the the Windows CE reference build works every time I boot it. Any suggestions?

[CraigMcQueen]

I'm having this same issue. I'm testing with the standard 2.6.35 images from Freescale, booting from 4 GB SD card.

I boot the board, and then log-in via the debug serial port. To start eth0 and eth1, I issue the commands:

udhcpc -b -i eth0

udhcpc -b -i eth1

We have two imx28evk boards. On one board, it works fine. On the other board, eth0 works, but eth1 endlessly prints:

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

PHY: 0:01 - Link is Up - 100/Full

PHY: 0:01 - Link is Down

The LEDs flash momentarily, periodically, which isn't the behaviour of the functional board.

What could be different between the functional board and the non-functional board? Both boards have stickers saying:

700-26241 REV A

SCH-26241 REV D

[tcmichals]

https://groups.google.com/forum/#!topic/meta-fsl-arm/eQW7vTobZ00

I had the same problem... Had to move to a new kernel.

[CH1z]

Forgot to mention, eth0 comes up fine in all cases, just eth1 that is troublesome