[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[Ken.Fuchs at bench.com]

vijay vijay wrote:

> I am using Denx u-boot 1.1.3 for MPC 870 board.
> I ported it for our board with mpc870 processor and I got the
> u-boot (->) prompt.

> UART interface is working fine but Ethernet interface (motfec)
> is not up yet.

ub> ping 10.10.10.4

> TX timeout
> TX timeout
> ping failed; host 10.10.10.4 is not alive

There are at least two problems with your U-Boot 1.1.3 configuration:

> #define CONFIG_ETHADDR        OO:11:22:33:44:55    /* board MAC addr
*/

The first byte "OO" is two capital Os; perhaps "00" was the intended
first byte of the MAC address?:

#define CONFIG_ETHADDR        00:11:22:33:44:55    /* board MAC addr
*/

> #define CONFIG_IPADDR        10:10:10:2            /* board IP addr
*/ 

The bytes of a v4 IP number must be separated by "." (not ":"):

#define CONFIG_IPADDR        10.10.10.2            /* board IP addr
*/

Other than the above two suggestions, please try using a U-Boot version
more current than 1.1.3, such as 1.3.x.

Sincerely,

Ken Fuchs

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[Wolfgang Denk]

In message <AA28F077645B324881335614E4F7C4284A49A9@win-ex01.bench.com> you wrote:
> 
> There are at least two problems with your U-Boot 1.1.3 configuration:
> 
> > #define CONFIG_ETHADDR        OO:11:22:33:44:55    /* board MAC addr
> */
> 
> The first byte "OO" is two capital Os; perhaps "00" was the intended
> first byte of the MAC address?:

And of course even 00:11:22:33:44:55 is not a legal MAC address and
MUST NOT BE USED. Please see the FAQ.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"It's hard to believe that something which is neither seen  nor  felt
can do so much harm."
"That's true. But an idea can't be seen or felt. And that's what kept
the Troglytes in the mines all these centuries. A mistaken idea."
	-- Vanna and Kirk, "The Cloud Minders", stardate 5819.0

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[Ken.Fuchs at bench.com]

> Ken Fuchs wrote:

> > There are at least two problems with your U-Boot 1.1.3 
> > configuration:

> > vijays vijays wrote:

> > > #define CONFIG_ETHADDR        OO:11:22:33:44:55
> > >     /* board MAC addr */

> > The first byte "OO" is two capital Os; perhaps "00" was the intended
> > first byte of the MAC address?:

Wolfgang Denx wrote:

> And of course even 00:11:22:33:44:55 is not a legal MAC address and
> MUST NOT BE USED. Please see the FAQ.

Actually, 00:11:22:33:44:55 is a perfectly legal (universally
administered) MAC address:

http://standards.ieee.org/regauth/oui/index.shtml

Just enter 00-11-22 for the OUI (Organizationally Unique Identifier).

In any case, 00-11-22-33-44-55 is an often used as a
_locally administered_ MAC address.  Such usage is definitely
illegal as can be seen by referring to:

http://www.denx.de/wiki/view/DULG/WhereCanIGetAValidMACAddress

No doubt this is what you were referring to when you said
"00:11:22:33:44:55 is not a legal MAC address".  A better,
easy to remember locally administered MAC address would be
02:03:04:05:06:07.

Sincerely,

Ken Fuchs

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[Wolfgang Denk]

In message <AA28F077645B324881335614E4F7C4284A49AA@win-ex01.bench.com> you wrote:
> 
> > And of course even 00:11:22:33:44:55 is not a legal MAC address and
> > MUST NOT BE USED. Please see the FAQ.
> 
> Actually, 00:11:22:33:44:55 is a perfectly legal (universally
> administered) MAC address:

You are of course right - I was too terse. Thanks for adding the
missing details.

> No doubt this is what you were referring to when you said
> "00:11:22:33:44:55 is not a legal MAC address".  A better,
> easy to remember locally administered MAC address would be
> 02:03:04:05:06:07.

ACK - or use tools/genethaddr to generate a random locally
administered MAC address.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Ada is PL/I trying to be Smalltalk.                 - Codoso diBlini

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[vijay vijay]

Hi Ken,Wolfgang
    Thanks for the Reply 

I have updated the my configuration for the CONFIG_ETHADDR and CONFIG_IPADDR
But still getting same "TX timeout"  error. from function 
static int fec_send(struct eth_device* dev, volatile void *packet, int length) in defined in the cpu/mpc8xx/fec..c

-----
    while ((rtx->txbd[txIdx].cbd_sc & BD_ENET_TX_READY) && (j<TOUT_LOOP)) {
#if defined(CONFIG_ICU862)
        udelay(10);
#else
        udelay(100);
#endif
        j++;
    }
    if (j>=TOUT_LOOP) {
        printf("TX timeout..testing.\n");
    }
-----

When I am running VxWorks on the same board LEDs at RJ45 connector ( Ethernet interfaces) on the board are glowing but when u-boot is up
these LED are off.   It seems that ETH interface is not up yet.

Which board can be used as the reference board for the MPC870.

Thanks
Vijay






----- Original Message ----
From: Wolfgang Denk <wd@denx.de>
To: Ken.Fuchs at bench.com
Cc: vijays2010 at yahoo.co.in; u-boot-users at lists..sourceforge.net
Sent: Tuesday, 22 July, 2008 1:48:21 AM
Subject: Re: [U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

In message <AA28F077645B324881335614E4F7C4284A49AA@win-ex01.bench.com> you wrote:
> 
> > And of course even 00:11:22:33:44:55 is not a legal MAC address and
> > MUST NOT BE USED. Please see the FAQ.
> 
> Actually, 00:11:22:33:44:55 is a perfectly legal (universally
> administered) MAC address:

You are of course right - I was too terse. Thanks for adding the
missing details.

> No doubt this is what you were referring to when you said
> "00:11:22:33:44:55 is not a legal MAC address".  A better,
> easy to remember locally administered MAC address would be
> 02:03:04:05:06:07.

ACK - or use tools/genethaddr to generate a random locally
administered MAC address.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Ada is PL/I trying to be Smalltalk.                 - Codoso diBlini



      Explore your hobbies and interests. Go to http://in.promos.yahoo.com/groups/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20080723/75cc02bf/attachment.htm 

[U-Boot-Users] eth interface (motfec) is not woring with u-boot1.1.3

[Ken.Fuchs at bench.com]

Please stop sending HMTL encoded messages to the list.
Please use plain text.  (Using plain text is a requirement
for using this mailing list.)

vijays vijays wrote:

> I have updated the my configuration for the CONFIG_ETHADDR and
> CONFIG_IPADDR
> But still getting same "TX timeout"  error. from function 
> static int fec_send(struct eth_device* dev, volatile void *packet,
> int length) in defined in the cpu/mpc8xx/fec.c

> -----
>     while ((rtx->txbd[txIdx].cbd_sc & BD_ENET_TX_READY)
>         && (j<TOUT_LOOP)) {
> #if defined(CONFIG_ICU862)
>         udelay(10);
> #else
>         udelay(100);
> #endif
>         j++;
>     }
>     if (j>=TOUT_LOOP) {
>         printf("TX timeout..testing.\n");
>     }
> -----

> When I am running VxWorks on the same board LEDs at RJ45 connector
> (Ethernet interfaces) on the board are glowing but when u-boot is up
> these LED are off.   It seems that ETH interface is not up yet.

Perhaps, your Ethernet driver is not properly configured.  Recheck these
definitions in your include/configs/tc870.h file:

#define    CONFIG_NET_MULTI    1     /* the only way to get the FEC in
*/
#define    FEC_ENET        1    /* eth.c needs it that way... */
#define CONFIG_FEC_ENET      1
#undef CFG_DISCOVER_PHY
#define CONFIG_MII        1
#define CONFIG_RMII        1     /* use RMII interface */

I would pay special attention to CFG_DISCOVER_PHY.  Maybe the wrong
Phy is being configured?

> Which board can be used as the reference board for the MPC870.

Maybe someone with experience with Ethernet on the MPC870 can answer?

I don't have a tc870 board or an MPC870, so this is the last
time you'll hear from me on this topic.

Good luck!

Sincerely,

Ken Fuchs