Skip to contentSkip to conversation

FEC driver: rcv is not +last

DISCUSSION Matthias Kaehlcke 3 participants 7 messages Apr 8, 2010 – Apr 9, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
...
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
...

the PHY of the board is a DP83840, which is not supported by the driver. could this be the problem? i tried to make the kernel think the DP83840 is a DP83848, which is supported, but the behaviour is the same except the 'unknown PHY' warning.

any idea what could be wrong?

Signature · 11 lines
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

              You can't separate peace from freedom because no
               one can be at peace unless he has his freedom
                              (Malcolm X)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
#1 lore raw
Quoted 8 lines · Matthias Kaehlcke

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

Quoted 10 lines

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
...
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
...

No idea, I have never seen this message. Does the controller work besides these messages?

Quoted 5 lines

the PHY of the board is a DP83840, which is not supported by the driver. could this be the problem? i tried to make the kernel think the DP83840 is a DP83848, which is supported, but the behaviour is the same except the 'unknown PHY' warning.

This should be solved by the phylib patches recently posted for the fec driver.

Sascha

Signature · 4 lines
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
#2 lore raw

El Thu, Apr 08, 2010 at 03:20:33PM +0200 Sascha Hauer ha dit:

Quoted 20 lines · Matthias Kaehlcke
Quoted 8 lines

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

Quoted 10 lines

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
...
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
...

Quoted 2 lines

No idea, I have never seen this message. Does the controller work besides these messages?

nope

Quoted 7 lines
Quoted 4 lines

the PHY of the board is a DP83840, which is not supported by the driver. could this be the problem? i tried to make the kernel think the DP83840 is a DP83848, which is supported, but the behaviour is the same except the 'unknown PHY' warning.

This should be solved by the phylib patches recently posted for the fec driver.

thanks for the pointer!

i just applied the patch. it actually makes the 'unkown PHY' and even the 'FEC ENET: rcv is not +last' messages disappear, but networking still doesn't work

Signature · 11 lines
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

  Control over the use of one's ideas really constitutes control over other
  people's lives; and it is usually used to make their lives more difficult.
                          (Richard Stallman)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
#3 lore raw
Quoted 32 lines · Matthias Kaehlcke

El Thu, Apr 08, 2010 at 03:20:33PM +0200 Sascha Hauer ha dit:

Quoted 20 lines · Matthias Kaehlcke
Quoted 8 lines

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

Quoted 10 lines

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
...
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
...

Quoted 2 lines

No idea, I have never seen this message. Does the controller work besides these messages?

nope

Quoted 5 lines
Quoted 4 lines

the PHY of the board is a DP83840, which is not supported by the driver. could this be the problem? i tried to make the kernel think the DP83840 is a DP83848, which is supported, but the behaviour is the same except the 'unknown PHY' warning.

Quoted 8 lines
Quoted 2 lines

This should be solved by the phylib patches recently posted for the fec driver.

thanks for the pointer!

i just applied the patch. it actually makes the 'unkown PHY' and even the 'FEC ENET: rcv is not +last' messages disappear, but networking still doesn't work

AFAIK there is nothing special about the fec in the i.MX25 except the RMII mode, so just some more things you can check:

- Does it work in the bootloader? (Are you using barebox?)
- Are packets transmitted/received at all?
- Have you configured the MAC address? currently the fec driver relies on finding a valid MAC address in the FEC_ADDR_LOW/FEC_ADDR_HIGH registers

Sascha

Signature · 4 lines
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
#4 lore raw
In reply to Matthias Kaehlcke

El Thu, Apr 08, 2010 at 04:53:24PM +0200 Matthias Kaehlcke ha dit:

Quoted 32 lines

El Thu, Apr 08, 2010 at 03:20:33PM +0200 Sascha Hauer ha dit:

Quoted 20 lines · Matthias Kaehlcke
Quoted 8 lines

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

Quoted 10 lines

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
...
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
FEC ENET: rcv is not +last
...

Quoted 2 lines

No idea, I have never seen this message. Does the controller work besides these messages?

nope

Quoted 5 lines
Quoted 4 lines

the PHY of the board is a DP83840, which is not supported by the driver. could this be the problem? i tried to make the kernel think the DP83840 is a DP83848, which is supported, but the behaviour is the same except the 'unknown PHY' warning.

Quoted 8 lines
Quoted 2 lines

This should be solved by the phylib patches recently posted for the fec driver.

thanks for the pointer!

i just applied the patch. it actually makes the 'unkown PHY' and even the 'FEC ENET: rcv is not +last' messages disappear, but networking still doesn't work

i just received a mail from our distributor:

the PDK board they gave us for evaluation is a preliminary version, with a slightly different hardware than the official one. they suppose that's the reason of our problem

sorry for the noise

Signature · 10 lines
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

      Debugging is like alien abduction. Large blocks of time disappear,
                    for which you have no explanation
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-
#5 lore raw
In reply to Matthias Kaehlcke
Quoted 11 lines · Matthias Kaehlcke

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...

Matt,

please try this patch on your hardware, it introduced phylib supporting in fec.c driver:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012214.html

Thanks

Signature · 5 lines
Bryan Wu <[email protected]>
Kernel Developer    +86.138-1617-6545 Mobile
Ubuntu Kernel Team | Hardware Enablement Team
Canonical Ltd.      www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
#6 lore raw

Hi Bryan,

El Fri, Apr 09, 2010 at 01:42:47PM +0800 Bryan Wu ha dit:

Quoted 9 lines · Matthias Kaehlcke
Quoted 8 lines

hi,

i have problems with the FEC on a i.MX25 3-Stack board. the kernel is v2.6.34-rc2 plus the following patch:
http://patchwork.ozlabs.org/patch/41235/

the following traces are generated at boot time:

Quoted 7 lines
Quoted 3 lines

FEC Ethernet Driver
fec: PHY @ 0x1, ID 0x20005ce1 -- unknown PHY!
...

please try this patch on your hardware, it introduced phylib supporting in fec.c driver:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012214.html

sascha pointed me yesterday to your patch, i tried it with v2
(http://lkml.org/lkml/2010/3/31/130), but without success.

our distributor informed us that the board they let us is a preliminary hardware version and that this is probably the cause of the problem :/

i hope i'll get soon my hands on an offical board release and can verify that the FEC just works ;)

thanks for your help!

Signature · 10 lines
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

               If sharing a thing in no way diminishes it,
               it is not rightly owned if it is not shared
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-