ppcboot 8260 LXT971A

ppcboot 8260 LXT971A

[greggiraud]

Hi,
I installed a ppcboot and a linux 2.4 on a MPC8260ADS card.

Now, I am working on a custom card such as an MPC8260ADS card. The difference between those two cards is the ethernet: my custom card has two ethernet port, and uses two LXT971A.

So, I compile a ppcboot for 8260ads. PPCBOOT can't download a kernel with tftp. Is someone has a source code to support the LXT971?

I compile a new kernel, which support LXT971A. PPCBOOT can run it from memory. But the kernel doesn't have network.

please can someone help me?

grego
greggiraud@netcourrier.com


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

RE: ppcboot 8260 LXT971A

[ARIBAUD Albert]

> Hi,
> I installed a ppcboot and a linux 2.4 on a MPC8260ADS card.
>
> Now, I am working on a custom card such as an MPC8260ADS
> card. The difference between those two cards is the ethernet:
> my custom card has two ethernet port, and uses two LXT971A.
>
> So, I compile a ppcboot for 8260ads. PPCBOOT can't download a
> kernel with tftp. Is someone has a source code to support the LXT971?
>
> I compile a new kernel, which support LXT971A. PPCBOOT can
> run it from memory. But the kernel doesn't have network.
>
> please can someone help me?

Hi,

My own experience was with a TQM855L-like setup, using an LX971A, so it's an 8xx, not an 82xx context.

However : I had no problem with PPCBoot (and U-Boot now), but at first the kernel would not work with Ethernet. I traced that down to the MPC8XX CPM Options : once the "use MDIO for PHY configuration" option was UNSET (but "Support LXT971 PHY" was SET, of course), everything worked OK.

My problem had something to do with MII state change interrupts not being detected properly, so the Ethernet driver was not told when the line went up after autonegociation, and thus never sent any packet.

Maybe with your 8260 you hit the same kind of problems?

HTH,

Albert.

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

Re: ppcboot 8260 LXT971A

[Wolfgang Denk]

Dear Grego,

in message <mnet1.1056960730.12133.greggiraud@netcourrier.com> you wrote:
>
> I installed a ppcboot and a linux 2.4 on a MPC8260ADS card.

There are some things you should change:

First, PPCBoot is a dead project; development has  been  discontinued
more  than half a year ago. For new development the successor project
"U-Boot" should be used instead.

Second, U-Boot (and PPCBoot) related questions are  off  topic  on  a
LInux  mailing  list.  Please post such questions to the u-boot-users
mailing list instead.

> Now, I am working on a custom card such as an MPC8260ADS card. The difference between those two cards is the ethernet: my custom card has two ethernet port, and uses two LXT971A.
>
> So, I compile a ppcboot for 8260ads. PPCBOOT can't download a kernel with tftp. Is someone has a source code to support the LXT971?

Third, if you have a custom card, you should adapt ("port") U-Boot to
your hardware. Using a configuration that was designed for  different
hardware will always cause some sort of problems.

Finally, both PPCBoot and U-Boot have been supporting the LXT971  for
a long time.

> I compile a new kernel, which support LXT971A. PPCBOOT can run it from memory. But the kernel doesn't have network.

Well, this is a  different  issue,  then.  The  Linux  driver  should
perform  all  required  initialization itself, so no interaction with
U-Boot should happen.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Another megabytes the dust.

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

Re: ppcboot 8260 LXT971A

[Wolfgang Denk]

In message <30C145E544071F4FB8B627789F7910BD32BE35@csy-exchange1.giat.intra> you wrote:
>
> My problem had something to do with MII state change interrupts not being detected properly, so the Ethernet driver was not told when the line went up after autonegociation, and thus never sent any packet.

Assuming your hardware is OK this means you  have  misconfigured  the
Linux kernel (wrong MII interrupt?)

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Certainly there are things in life that money  can't  buy,  but  it's
very funny - Did you ever try buying them without money? - Ogden Nash

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

RE: ppcboot 8260 LXT971A

[ARIBAUD Albert]

>
> > My problem had something to do with MII state change
> interrupts not being detected properly, so the Ethernet
> driver was not told when the line went up after
> autonegociation, and thus never sent any packet.
>
> Assuming your hardware is OK this means you  have  misconfigured  the
> Linux kernel (wrong MII interrupt?)
>
> Best regards,
>
> Wolfgang Denk

Hi Wolfgang,

As far as I remember, the hardware designer and I had checked that: we were using the right interrupt, it was triggered and the interrupt driver received it, but somehow in the driver the line state evolution from 'init' to 'up' was lost.

Unfortunately, we did not have enough time for messing with the kernel then (1), so we tried alternatives, and disabling MDIO worked, so we did not investigate further. If you think it could be useful, I could reproduce that setting and do some tracing.

All the best,

Albert.

(1) I can't believe I just wrote that, considering that I have just modified i2c-algo-8xx.c extensively (and i2c-rpx.c also, but more slightly) to get I2C_RDWR ioctl working, two days before project deadline. :)

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