Skip to contentSkip to conversation

Problem using tftp whith ColdFire 5282

U-Boot-Users Javier Ruiz de Munain 2 participants 2 messages Sep 3, 2004

lore
Share & tools
lore
#0 lore raw

Hello.

I ported the U-BOOT for the ColdFire MCF5282. I have written the routines that are needed to initialise the processor, and it works properly. The platform what I working with, is the AVNET platform.
The code can be easily ported to the M5282EVB platform, by doing fews modifications.

U-BOOT starts properly, and I write:

-> setenv ethaddr xx:xx:xx:xx:xx:xx (AVNET MAC address)
-> setenv ipaddr yy.yy.yy.yy (the AVNET IP address)
-> setenv serverip zz.zz.zz.zz (server IP address)

the problem is when I write:

-> tftp 10000 /tftpboot/image.bin

and the answer is:

	TX timeout
	 fec.c[124] eth_send: cycles: 100    status: 8c00  retry cnt: 0

	TX timeout
	 fec.c[124] eth_send: cycles: 100    status: ac00  retry cnt: 0

	 TX timeout
	 fec.c[124] eth_send: cycles: 100    status: 8c00  retry cnt: 0

			.

			.

			.

until I press CTRL+C, to escape. Does anybody know how to solve this problem? When i do "ping yy.yy.yy.yy", it does not wok!!!
I think the driver contained on /u-boot-1.1.1/cpu/mcf52x2/fec.c, works properly, but I would like tho know if it should initialise the PHY or not.

Thanks

#1 lore raw
Quoted 2 lines · In message <[email protected]> you wrote:

Hello.

Why are you sending the same message 3 times ???

Quoted 11 lines

I ported the U-BOOT for the ColdFire MCF5282. I have written the routines that are needed to initialise the processor, and it works properly. The platform what I working with, is the AVNET platform.
The code can be easily ported to the M5282EVB platform, by doing fews modifications.

U-BOOT starts properly, and I write:

-> setenv ethaddr xx:xx:xx:xx:xx:xx (AVNET MAC address)
-> setenv ipaddr yy.yy.yy.yy (the AVNET IP address)
-> setenv serverip zz.zz.zz.zz (server IP address)

What are the EXACT paramters you used here?

Quoted 3 lines

When i do "ping yy.yy.yy.yy", it does not wok!!!
I think the driver contained on /u-boot-1.1.1/cpu/mcf52x2/fec.c, works properly, but I would like tho know if it should initialise the PHY or not.

Answer yourself: do you think you can send data through an uninitialized PHY?

Best regards,

Wolfgang Denk

Signature · 5 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Dealing with failure is easy: work hard to improve. Success  is  also
easy  to  handle:  you've  solved  the  wrong  problem.  Work hard to
improve.