Simon
My problem here had been my own carelessness combined with HW trouble: I had an incorrect bit in RCW, and we had voltage levels wrong to PHY. Nothing to do with u-boot code.
Our PHY is also not explicitly supported; so i submitted a patch to support un-recognized PHYs as 'generic'; like the linux gianfar driver does. But it has languished uncommitted; I dunno why.
Have you resolved this now? Now I am also working with 83xx TSEC, but we also meet the problem,in MDIO and MDC there isn't any signal, I wonder if you meet the same problem in your board and whether you can give me some comment on this!
Best Regards,
Simon
2005/9/15, David Updegraff dave@cray.com:
Hi.
Anyone know of any registers to look at in the TSEC stuff that might tell a guy why a frame is not moving?
Our PHY looks fine; 'mii dump' is fine, link up, etc. but in tsec_send() the buffer of a ping is loaded up, and simply never goes anywhere. ->tstat remains clear (no halt bit), but rtx.txbd[txIdx].status never changes from assigned value.
Stats claim no frames; which is correct. I need some help in understanding why TSEC feels it cannot feed anything out the inerface.
Thanx.
-dbu.
SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id%16865&op=click