MPC860T FEC problem

MPC860T FEC problem

[o_y]

Hello to all.
I'm trying to port linux 2.2.14 on MPC860T and busybox as initrd.
The eth0 device is working so i have network capability.
Now i'm trying to get the FEC device working.
In the booting process the FEC is initialized ok (or so i belive),
IRQ(FEC)=3.
The problem is : when i use the FEC as my network device there is no
interrupts
from this device (unlike when i use the eth0 device as my net device).
The LINK led and the TX led are on constantly when i connect the FEC to a
100TXBase switch.
I have not seen any initializetion of the BCSR4 so i initialize it with the
value
that ppcboot uses , so the ENABLE led is on too.
The device isn't working even when i use ppcboot (i configured ppcboot to
use it).

1. Why there is no initializetion of BCSR4 in the original code?
2. If BCSR4 must be initialized , what is the correct value?
3. Is any one have a code that succeeded getting FEC device to work?
4. IVEC(ILEVEL) bits of the FEC are initialized but when i read the value of
this
   register i get 0x00000000 . Is this the problem ? and if so how can i fix
it ?

thank you for your help
oshri.
o_yahav@netvision.net.il


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: MPC860T FEC problem

[Wolfgang Denk]

Hi,

in message <MBBBIOFIICDAPDMKHBDEKEDLCAAA.o_yahav@netvision.net.il> you wrote:
>
> I'm trying to port linux 2.2.14 on MPC860T and busybox as initrd.

2.2.14 is prehistoric stuff. Don't waste your time on  all  the  bugs
and problems that have been fixed since.

> I have not seen any initializetion of the BCSR4 so i initialize it with the
> value
> that ppcboot uses , so the ENABLE led is on too.

Ummm... What's BCSR4? If PPCBoot initializes it, why do you  have  to
initialize it again?

> The device isn't working even when i use ppcboot (i configured ppcboot to
> use it).

Sic! So get PPCBoot running first.

> 1. Why there is no initializetion of BCSR4 in the original code?
> 2. If BCSR4 must be initialized , what is the correct value?
> 3. Is any one have a code that succeeded getting FEC device to work?

Among all the things you don;t care to mention is which  bard  you're
working  on.  My  guess is that it simply never was really working in
that old kernel version.

As I said before: you are wasting your time. Use a current kernel.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
The faster I go, the behinder I get.                 -- Lewis Carroll

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: MPC860T FEC problem

[Michael Habermann]

o_y wrote:
> that ppcboot uses , so the ENABLE led is on too.
> The device isn't working even when i use ppcboot (i configured ppcboot to
> use it).

If you use a FADS, you need to check that the dip switches belonging to
the FEC are in the default position according to the users manual.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: MPC860T FEC problem

[o_y]

Dear Wolfgang Denk
You are right ! i didn't specify importent stuff about my work :
The board i'm working on is MPC860TFADS.
I'm using the 2.2.14 kernel because at the moment it's working just fine( i
have not bump into any bugs so far ) . The kernel is stable ,busybox is
working and
so is the network services .
BCSR's are the Board & Statuse Control Registers of the FADS.
The ppcboot-0.8.3 can work only with one of the tow : the scc_enet or the
fec.
Since the scc_enet is working ( and the fec isn't) , ppcboot dont initialize
the BCSR4 register
that (on the mpc860FADS) controls the fec so if i want to use it i have to
initialize it
during the booting process.
The second thing is that i'm not planing to use ppcboot as boot loader in
the future.
I'm only using ppcboot so i coul'd download the image to the memory .
The actual bootloader is mbxboot with some modifications.
When the fec will work i'll burn the image on the flash memory .

If any one succeded to get the fec device to work on this board with
the 2.2 kernel PLEASE tell me how

Thank you for your help and your attention.
oshri.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: MPC860T FEC problem

[Rod Boyce]

 -----Original Message-----
From: 	Wolfgang Denk [mailto:wd@denx.de]
Sent:	Saturday, September 07, 2002 10:15 AM
To:	o_y
Cc:	linuxppc-embedded@lists.linuxppc.org
Subject:	Re: MPC860T FEC problem


Hi,

in message <MBBBIOFIICDAPDMKHBDEKEDLCAAA.o_yahav@netvision.net.il> you
wrote:
>
> I'm trying to port linux 2.2.14 on MPC860T and busybox as initrd.

2.2.14 is prehistoric stuff. Don't waste your time on  all  the  bugs
and problems that have been fixed since.

We are using this kernel and it is working find for us.

> I have not seen any initializetion of the BCSR4 so i initialize it with
the
> value
> that ppcboot uses , so the ENABLE led is on too.

Ummm... What's BCSR4? If PPCBoot initializes it, why do you  have  to
initialize it again?

Like Wolfgang said why reinvent the wheel

> The device isn't working even when i use ppcboot (i configured ppcboot to
> use it).

Sic! So get PPCBoot running first.

> 1. Why there is no initializetion of BCSR4 in the original code?
> 2. If BCSR4 must be initialized , what is the correct value?
> 3. Is any one have a code that succeeded getting FEC device to work?

Most of this depends on your hardware.  We are using the FEC with this
kernel version and it is working fine.  Get the 2.2.14 kernel from
Wolfgang's FTP site if it is still on there the FEC code and lots of other
goodies work with this kernel version.

Sometimes you cannot upgrade to a new kernel version this is possibly
political and not a design decision.  Sometime there is also no reason to
upgrade to a newer kernel version and have to retest all possible variants
of device with the new kernel version.

Regards,
Rod Boyce

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: MPC860T FEC problem

[Wolfgang Denk]

Dear Rod,

can you please use a standard way to quote text? In this  message  it
is impossible for the reader to decide what was _my_ text, and which
is yours.

In message <8D7C5F56B409554D9D46AC22195807F3061A2F@exchwenz01.smtp.dmcwave.co.nz> you wrote:
>
>  -----Original Message-----
> From: 	Wolfgang Denk [mailto:wd@denx.de]
> Sent:	Saturday, September 07, 2002 10:15 AM
> To:	o_y
> Cc:	linuxppc-embedded@lists.linuxppc.org
> Subject:	Re: MPC860T FEC problem
>
>
> Hi,
>
> in message <MBBBIOFIICDAPDMKHBDEKEDLCAAA.o_yahav@netvision.net.il> you
> wrote:
> >
> > I'm trying to port linux 2.2.14 on MPC860T and busybox as initrd.
>
> 2.2.14 is prehistoric stuff. Don't waste your time on  all  the  bugs
> and problems that have been fixed since.

This was me.

> We are using this kernel and it is working find for us.

But this isn't my text!

> > I have not seen any initializetion of the BCSR4 so i initialize it with
> the
> > value
> > that ppcboot uses , so the ENABLE led is on too.
>
> Ummm... What's BCSR4? If PPCBoot initializes it, why do you  have  to
> initialize it again?

[me]

> Like Wolfgang said why reinvent the wheel

[not me]

> > The device isn't working even when i use ppcboot (i configured ppcboot to
> > use it).
>
> Sic! So get PPCBoot running first.
>
> > 1. Why there is no initializetion of BCSR4 in the original code?
> > 2. If BCSR4 must be initialized , what is the correct value?
> > 3. Is any one have a code that succeeded getting FEC device to work?
>
> Most of this depends on your hardware.  We are using the FEC with this
> kernel version and it is working fine.  Get the 2.2.14 kernel from
> Wolfgang's FTP site if it is still on there the FEC code and lots of other
> goodies work with this kernel version.

[not me]

But the 2.2.14 kernel is still there, unused and  unmaintained  since
November 2000.

> Sometimes you cannot upgrade to a new kernel version this is possibly
> political and not a design decision.  Sometime there is also no reason to
> upgrade to a newer kernel version and have to retest all possible variants
> of device with the new kernel version.

Sure. But there comes a point in time when it just doesn't make sense
to add more new features to old software - especially when  you  find
that  you  spend more effort on fixing old bugs that it would take to
switch to a new version.

Our 2.4.4 kernel is a good example for this problem.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
As long as we're going to reinvent the wheel again, we might as  well
try making it round this time.                        - Mike Dennison

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/