On Sunday, February 25, 2007 4:04 PM John Williams wrote:
I remember we had a bit of trouble getting the ethernet lite going
under
u-boot at all.
{Leonid] But do you observe the same I do on Spartan-3e Starter Kit or
it works fine for you? Note that I use Petalogix stuff for Spartan-3e,
both EDK project and u-boot. I have EDK 8.1.03 though (but I see the
same even if I use pre-compiled download.bit from Petalogix site).
What is bothering me that many people shall observe the same yet nobody
complains (unless they don't use Spartan-3e). I would prefer to use EMAC
core and it works for me indeed if microblaze clock is 64MHz (not
packets' drops). However we couldn't meet certain timing requirements
with 64MHz and were forced to move to 50MHz (like in reference design).
We couldn't use EMAC anymore. Were other folks more lucky?
One thing to try, maybe hack on u-boot and change the
NET timeout parameter (I forget where it's defined, just go grepping
and
you'll find it). Basically it tells u-boot how long to wait between
retries. Maybe if you reduce it a little, you'll get a faster
recovery
after a packet is dropped.
[Leonid] I have tried that already, see my change:
90a91
#define CONFIG_NET_RETRY_COUNT 20
157c158
Remember u-boot is using TFTP over UDP (no error correction) on top of
the emac_lite which itself has very simplistic packet receive and
error
handling.
[Leonid] Understood. Yet I don't expect any real network troubles or
errors - the board and server are in the same room, behind same L2
switch. I even connected them back to back - no difference.
It could be worth checking in the mainline u-boot repository, or any
of
the other u-boot versions distrbuted in support of Xilinx boards.
[Leonid] Will do.
Regards,
Leonid.
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/