PATCH: fix FEC problems on MPC5200
Hi everybody,
The attached patch fixes the FEC problems on my Lite5200 board. The network is working without any problems at 10 and 100Mb. The auto-negociation works too.
If CONFIG_FEC_10MBIT is defined, the FEC works at 10Mb with Half-Duplex. If CONFIG_FEC_10MBIT is undefined, the MII reads its configuration from hardware
and uses the auto-negociation for determining network speed. The patch undefines CONFIG_FEC_10MBIT for the Lite5200.
Does it work for the other MPC5xxx boards ?
CHANGELOG:
* Patch by Pierre Aubert 25 Mar 2004
Fix FEC problems on MPC5xxx: suppress timeouts on tftp.
Best regards
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-fec-mpc5xxx.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040325/a25acb7a/attachment.txt
Quoted 12 lines · In message <[email protected]> you wrote:
The attached patch fixes the FEC problems on my Lite5200 board. The network is working without any problems at 10 and 100Mb. The auto-negociation works too.
If
CONFIG_FEC_10MBITis defined, the FEC works at 10Mb with Half-Duplex. IfCONFIG_FEC_10MBITis undefined, the MII reads its configuration from hardware
and uses the auto-negociation for determining network speed. The patch undefinesCONFIG_FEC_10MBITfor the Lite5200.Does it work for the other MPC5xxx boards ?
Quoted 13 lines · Wolfgang Denk
Quoted 10 lines · In message <[email protected]> you wrote:
The attached patch fixes the FEC problems on my Lite5200 board. The network is working without any problems at 10 and 100Mb. The auto-negociation works too.
If
CONFIG_FEC_10MBITis defined, the FEC works at 10Mb with Half-Duplex. IfCONFIG_FEC_10MBITis undefined, the MII reads its configuration from hardware
and uses the auto-negociation for determining network speed. The patch undefinesCONFIG_FEC_10MBITfor the Lite5200.
Quoted 4 lines
Quoted 3 lines
Does it work for the other MPC5xxx boards ?
From what we saw, the FEC driver in U-Boot used to work quite stably,
Quoted 6 lines
until the IDE support was added. May be that was just a coincidence, but it seems obvious to me that something changed in U-Boot recently that broke the FEC driver. It is possible that "something" was not the IDE support in fact, but yet something else.
On my side, I had the timeouts problems on tftp transferts from the begining.
IDE support didn't change anything, the problem exists before.
Quoted 6 lines
The MII initialization code used to work fine for us, as far as we were able to tell. Without having investigated this more closely, I will not check in this patch as I feel it might just fix some symptoms.
For me, this init is useless, the MII takes its configuration from hardware. On MPC8xx boards, there's no such init sequence and FEC works fine for all boards.
Quoted 7 lines
Best regards,
Wolfgang Denk
Best regards
Quoted 3 lines · In message <[email protected]> you wrote:
On my side, I had the timeouts problems on tftp transferts from the begining. IDE support didn't change anything, the problem exists before.
It would be interesting to know if there were some components in your setup that you were not able to replace:
LITE5200 board network cable(s) switch(es) / hub(s) TFTP server
Only if you were able to replace each of them, and the problem persisted, I am convinced of a problem with the code.
We had several boards, both with MGT5100 and MPC5200, with SDRAM and DDR, in several layour versions of the IceCube / LITE board, and additionally some custom boards. Never had that sort of problem until around the time the IDE stuff was checked in.
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de I cannot draw a cart, nor eat dried oats; If it be man's work I will do it.
Quoted 8 lines · Wolfgang Denk
Quoted 4 lines · In message <[email protected]> you wrote:
On my side, I had the timeouts problems on tftp transferts from the begining. IDE support didn't change anything, the problem exists before.
Quoted 9 lines
It would be interesting to know if there were some components in your setup that you were not able to replace:
LITE5200 board network cable(s) switch(es) / hub(s) TFTP server
I've made some tests with several tftp servers (Unix servers and PC servers). Of course,
I've tried several cables and severals ports on several switches. I've also made some tests
with a direct connection between a PC and my Lite5200 with same results (in this case, timeouts
are rare, but it happens sometimes).
Unfortunately, I've got only one Lite5200 board but other people have same problems
(see thread
http://sourceforge.net/mailarchive/forum.php?thread_id=4080201&forum_id=12898)
I think that my board is OK because I don't have any problem with the FEC under my
operating system.
Quoted 14 lines
Only if you were able to replace each of them, and the problem persisted, I am convinced of a problem with the code.
We had several boards, both with MGT5100 and MPC5200, with SDRAM and DDR, in several layour versions of the IceCube / LITE board, and additionally some custom boards. Never had that sort of problem until around the time the IDE stuff was checked in.
Best regards,
Wolfgang Denk
Best regards