[U-Boot-Users] Problem with TFTP in u-boot 1.1.4

Hi,
I am new at embedded design and I have some problems with u-boots.
I downloaded a patched version of the u-boot 1.1.4 for the board AT91RM9200EK from a FTP Atmel site. To run it I had to make some changes in the configuration file of the u-boot source code at91rm9200ek.h. Basically this changes were about to define the CONFIG_SKIP_LOWLEVEL_INIT, CFG_ENV_IS_IN_FLASH instead of dataflash and other values related to the Flash memory addresses. I only modified this file.
When I crosscompile it with a cross toolchain from codesourcery, everything goes well and once downloaded in the board everything works perfectly. However one thing doesn't work. When I try to download image files using TFTP protocol it doesn't work, it seems like disabled, a lot of unsuccessful tries and bad checksums. The IP addresses of the board and of my PC are corrects and the ethernet cables are plugged. When I remove this u-boot and I download the u-boot image file provided with the Atmel CD and try to use TFTP without changing the IP addresses, everything works fine.
I don't know how to solve this problem. If someone knows, please let me know.
Thanks,
Javier

Javier,
On Sun, 2007-02-11 at 17:06 +0200, Javier Gracia Castro wrote:
Hi,
When I crosscompile it with a cross toolchain from codesourcery, everything goes well and once downloaded in the board everything works perfectly. However one thing doesn't work. When I try to download image files using TFTP protocol it doesn't work, it seems like disabled, a lot of unsuccessful tries and bad checksums. The IP addresses of the board and of my PC are corrects and the ethernet cables are plugged. When I remove this u-boot and I download the u-boot image file provided with the Atmel CD and try to use TFTP without changing the IP addresses, everything works fine.
I don't know how to solve this problem. If someone knows, please let me know.
Please verify that the Ethernet controller has a unique, unicast address. In particular, bit 40 (01:00:00:00:00:00) must NOT be set.
u-boot> printenv ethaddr
If this is OK, try to ping your PC from the board.
I apologize if this seems basic, but it is the most common reason for not connecting.
Also, please read the U-boot FAQ. There's lots of good information there.
http://www.denx.de/wiki/DULG/Faq
regards, Ben
participants (3)
-
Ben Warren
-
Javier Gracia Castro
-
Raúl Sánchez Siles