[U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
Stephen: I tried with 0x123c in MSC2, LEDs in the Ethernet connector is glowing and I am getting following error message. Using SMC91111-0 device ping failed; host 10.100.144.245 is not alive
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER: -----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0
After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
#################################################################
#################################################################
###########################################T ######################
#############
done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
#################################################################
#################################################################
##########################################T ##
done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
#################################################################
#################################################################
###########################################T ######################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################
done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER: -----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
Dne Čt 26. srpna 2010 17:06:08 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
Test some bigger area then ... at best the one where you're downloading the image.
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 26, 2010 9:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 26. srpna 2010 17:06:08 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
Test some bigger area then ... at best the one where you're downloading the image.
I changed the board/myboard/config.mk to load the u-boot at the 0xa7F00000 location in the SDRAM. The environment variable is placed at the 0xa7e00000 loation.
Memory test with: 1. start address a0000000 & end address a3ffffff is successful. 2. start address a4000000 & end address a7dfffff is successful. 3. start address a3500000 & end address a5000000 is successful.
But the memory test with start address a0000000 and end address a5000000 misbehaved. Check my observation 4: (mtest a0000000 a5000000 a55aa55a 3)
The giving pattern (a55aa55a) is written only once into the memory but the u-boot read the pattern from the memory 3 times (iteration count). The write loop is not executed. I don't know the reason. I executed the (mtest a0000000 a5000000 a55aa55a 3) command several times and every time the write loop is not executed and the mtest result also not displayed.
Kindly find the memory test observation below: Observation 1: MDT-Boot> mtest a0000000 a3ffffff a5a55a5a 5
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading... Pattern 5A5AA5A7 Writing... Reading... Pattern A5A55A58 Writing... Reading...Tested 5 iteration(s) with 0 errors.
Observation 2: MDT-Boot> mtest a4000000 a7dfffff a5a5a5a5 3
Pattern A5A5A5A5 Writing... Reading... Pattern 5A5A5A5B Writing... Reading... Pattern A5A5A5A4 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 3: MDT-Boot> mtest a3500000 a5000000 a5a55a5a 3
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 4: MDT-Boot> mtest a0000000 a5000000 a55aa55a 3
Pattern A55AA55A Writing... Reading...Reading...Reading...MDT-Boot>
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Dne Pá 27. srpna 2010 10:52:45 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 26, 2010 9:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 26. srpna 2010 17:06:08 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
Test some bigger area then ... at best the one where you're downloading the image.
I changed the board/myboard/config.mk to load the u-boot at the 0xa7F00000 location in the SDRAM. The environment variable is placed at the 0xa7e00000 loation.
Memory test with:
- start address a0000000 & end address a3ffffff is successful.
- start address a4000000 & end address a7dfffff is successful.
- start address a3500000 & end address a5000000 is successful.
But the memory test with start address a0000000 and end address a5000000 misbehaved. Check my observation 4: (mtest a0000000 a5000000 a55aa55a 3)
The giving pattern (a55aa55a) is written only once into the memory but the u-boot read the pattern from the memory 3 times (iteration count). The write loop is not executed. I don't know the reason. I executed the (mtest a0000000 a5000000 a55aa55a 3) command several times and every time the write loop is not executed and the mtest result also not displayed.
Kindly find the memory test observation below: Observation 1: MDT-Boot> mtest a0000000 a3ffffff a5a55a5a 5
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading... Pattern 5A5AA5A7 Writing... Reading... Pattern A5A55A58 Writing... Reading...Tested 5 iteration(s) with 0 errors.
Observation 2: MDT-Boot> mtest a4000000 a7dfffff a5a5a5a5 3
Pattern A5A5A5A5 Writing... Reading... Pattern 5A5A5A5B Writing... Reading... Pattern A5A5A5A4 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 3: MDT-Boot> mtest a3500000 a5000000 a5a55a5a 3
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 4: MDT-Boot> mtest a0000000 a5000000 a55aa55a 3
Pattern A55AA55A Writing... Reading...Reading...Reading...MDT-Boot>
Just run ... mtest 0xa0000000 0xa7000000
and see if it screams. If it does, your memory's misconfigured. (I assume you have at least 0x08000000 bytes of RAM and uboot is loaded past 0xa7000000).
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Friday, August 27, 2010 3:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Pá 27. srpna 2010 10:52:45 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 26, 2010 9:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 26. srpna 2010 17:06:08 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
Test some bigger area then ... at best the one where you're downloading the image.
I changed the board/myboard/config.mk to load the u-boot at the 0xa7F00000 location in the SDRAM. The environment variable is placed at the 0xa7e00000 loation.
Memory test with:
- start address a0000000 & end address a3ffffff is successful.
- start address a4000000 & end address a7dfffff is successful.
- start address a3500000 & end address a5000000 is successful.
But the memory test with start address a0000000 and end address a5000000 misbehaved. Check my observation 4: (mtest a0000000 a5000000 a55aa55a 3)
The giving pattern (a55aa55a) is written only once into the memory but the u-boot read the pattern from the memory 3 times (iteration count). The write loop is not executed. I don't know the reason. I executed the (mtest a0000000 a5000000 a55aa55a 3) command several times and every time the write loop is not executed and the mtest result also not displayed.
Kindly find the memory test observation below: Observation 1: MDT-Boot> mtest a0000000 a3ffffff a5a55a5a 5
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading... Pattern 5A5AA5A7 Writing... Reading... Pattern A5A55A58 Writing... Reading...Tested 5 iteration(s) with 0 errors.
Observation 2: MDT-Boot> mtest a4000000 a7dfffff a5a5a5a5 3
Pattern A5A5A5A5 Writing... Reading... Pattern 5A5A5A5B Writing... Reading... Pattern A5A5A5A4 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 3: MDT-Boot> mtest a3500000 a5000000 a5a55a5a 3
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 4: MDT-Boot> mtest a0000000 a5000000 a55aa55a 3
Pattern A55AA55A Writing... Reading...Reading...Reading...MDT-Boot>
Just run ... mtest 0xa0000000 0xa7000000
and see if it screams. If it does, your memory's misconfigured. (I assume you have at least 0x08000000 bytes of RAM and uboot is loaded past 0xa7000000).
Executed the mtest axa0000000 0xa7000000, the memory test is successful, there is no errors.
I connect the board to the linux server directly using cross Ethernet cable and tried to transfer 47MB size file through tftp, it is downloaded successfully, but 53MB size file is getting downloaded.
Is that I need to look into something (LAN91C111 configurations) while connecting the board to companies network?
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################# ################################################################# ###########################################T ###################### ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Dne Ne 29. srpna 2010 16:28:45 StephenPaulraj Chinnadurai-ERS,HCLTech napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Friday, August 27, 2010 3:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Pá 27. srpna 2010 10:52:45 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 26, 2010 9:00 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 26. srpna 2010 17:06:08 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
-----Original Message----- From: Marek Vasut [mailto:marek.vasut@gmail.com] Sent: Thursday, August 26, 2010 5:56 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de; Wolfgang Denk Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne St 25. srpna 2010 11:03:30 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I increased the memory clock speed from 104 MHz to 208 MHz in the PXA270 controller by including the following lines of in the .macro pxa_clock_setup (macro.h file)
ldr r0, =0x8 mcr p14, 0, r0, c6, c0, 0After increasing the memory clock speed, I can download the zImage (2.8MB) through tftp without any timeout.
Your memory seems misconfigured. Can you run "mtest" on it ?
I executed the mtest command and waited for an hour, u-boot doesn't displayed any error.
The memory start and end address is defined as follow in the include/configs/myboard.h file.
#define CONFIG_SYS_MEMTEST_START 0xa0400000 /* memtest works on */ #define CONFIG_SYS_MEMTEST_END 0xa0800000 /* 4 ... 8 MB in DRAM */
#define CONFIG_SYS_LOAD_ADDR (0xa1000000)
Pattern 000004BF Writing... Reading... Pattern FFFFFB40 Writing... Reading... Pattern 000004C0 Writing... Reading... Pattern FFFFFB3F Writing... Reading... Pattern 000004C1 Writing... Reading...
Test some bigger area then ... at best the one where you're downloading the image.
I changed the board/myboard/config.mk to load the u-boot at the 0xa7F00000 location in the SDRAM. The environment variable is placed at the 0xa7e00000 loation.
Memory test with:
- start address a0000000 & end address a3ffffff is successful.
- start address a4000000 & end address a7dfffff is successful.
- start address a3500000 & end address a5000000 is successful.
But the memory test with start address a0000000 and end address a5000000 misbehaved. Check my observation 4: (mtest a0000000 a5000000 a55aa55a 3)
The giving pattern (a55aa55a) is written only once into the memory but the u-boot read the pattern from the memory 3 times (iteration count). The write loop is not executed. I don't know the reason. I executed the (mtest a0000000 a5000000 a55aa55a 3) command several times and every time the write loop is not executed and the mtest result also not displayed.
Kindly find the memory test observation below: Observation 1: MDT-Boot> mtest a0000000 a3ffffff a5a55a5a 5
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading... Pattern 5A5AA5A7 Writing... Reading... Pattern A5A55A58 Writing... Reading...Tested 5 iteration(s) with 0 errors.
Observation 2: MDT-Boot> mtest a4000000 a7dfffff a5a5a5a5 3
Pattern A5A5A5A5 Writing... Reading... Pattern 5A5A5A5B Writing... Reading... Pattern A5A5A5A4 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 3: MDT-Boot> mtest a3500000 a5000000 a5a55a5a 3
Pattern A5A55A5A Writing... Reading... Pattern 5A5AA5A6 Writing... Reading... Pattern A5A55A59 Writing... Reading...Tested 3 iteration(s) with 0 errors.
Observation 4: MDT-Boot> mtest a0000000 a5000000 a55aa55a 3
Pattern A55AA55A Writing... Reading...Reading...Reading...MDT-Boot>
Just run ... mtest 0xa0000000 0xa7000000
and see if it screams. If it does, your memory's misconfigured. (I assume you have at least 0x08000000 bytes of RAM and uboot is loaded past 0xa7000000).
Executed the mtest axa0000000 0xa7000000, the memory test is successful, there is no errors.
I connect the board to the linux server directly using cross Ethernet cable and tried to transfer 47MB size file through tftp, it is downloaded successfully, but 53MB size file is getting downloaded.
Is that I need to look into something (LAN91C111 configurations) while connecting the board to companies network?
Can you restart this thread in u-boot@lists.denx.de please, state correct mail "Subject" (like "TFTP load for file over 50MB fails") and state also all the facts so far (that it's not a memory error).
It's getting mess and also, with proper subject, someone will likely look into it.
Cheers
But I can't download system.img (android system image file of 55MB) into the SDRAM.
Our customize board has LAN91C111Ii-NU controller connected to the static memory 4 (nCS4) of PXA270, and uses 32 bit connection.
Below are my observations while using tftpboot command:
Observation 1: Exactly after downloading 3498200 bytes the first timeout is occurring, sometimes it is recovering and most of the times it is not recovering, and "Retry count exceeded" message is displayed.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################ # ################################################################ # ###########################################T ###################### #############done
Bytes transferred = 4000000 (3d0900 hex)
MDT-Boot>
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################ # ################################################################ # ##########################################T ##done
Observation 2: I analyzed the reason for continues timeout and found that the LAN91c1111 fifo is full, some 44 byte, 48 byte, 60 byte, 78 byte packet are filling the fifo. PXA270 customize board is connected to our company network.
Got IP len=78, v=45 packet received packet received Receive from protocol 0x800 Got IP len=44, v=45 packet received packet received Receive from protocol 0x0 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=60, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x800 Got IP len=48, v=45 packet received packet received Receive from protocol 0x806
Observation 3: I splited the 55 MB system.img file to 9 MB each and then tried to download it through tftp.
I found I can able to download 9 MB files with one or two timeouts.
MDT-Boot> tftp a1300000 aaaa
SMC91111: MAC 00:00:70:26:1e:01
TFTP blocksize = 1468, timeout = 5 s
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.90
Filename 'aaaa'.
Load address: 0xa1300000
Loading: * #################################################################
################################################################ # ################################################################ # ###########################################T ###################### ################################################################ # ################################################################ # ################################################################ # ################################################################ # ################################################################ # #############################done
Bytes transferred = 9000000 (895440 hex)
Why I can't download the 50 MB files into the SDRAM through tftp? Is that I need to still look into the cpu register configuration?
Whether I need to look and debug the net.c and tftp.c? But the same files net.c and tftp.c which is working fine in the Littleton board.
How to stop the 44 byte, 48 byte, 60 byte and 78 byte packets entering into the LAN91C controller? Is there any way to filter those packets.
What is the reason for the first timeout after downloading exactly 3498200 bytes through tftp?
Kindly help to solve this problem. Kindly suggest some ways, so that I will debug the source code.
Thanks and Regards Stephen Paulraj C
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Marek Vasut Sent: Thursday, August 12, 2010 11:05 PM To: StephenPaulraj Chinnadurai-ERS,HCLTech Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] TFTP timeout issue while downloading the linux kernel in openpxa vpac270 u-boot source code
Dne Čt 12. srpna 2010 19:11:29 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
I am using a customize board which has PXA270 controller. SMCS LAN91C111Ii-NU is connected to the static memory 4 (nCS4).
I see, so it's not vpac270 bug.
I have defined following macro value in the include/configs/<myboard.h> file.
#define CONFIG_SYS_GPDR2_VAL 0x70DF3FFF GPIO 80 is configured as output
#define CONFIG_SYS_GPSR2_VAL 0x10010000 /*nCS4*/ GPIO 80 is set
You don't really need to configure these if you then set it to AF2.
#define CONFIG_SYS_GAFR2_U_VAL 0x1504A176 Alternate function 2 is selected for GPIO 80
#define CONFIG_SYS_MSC2_VAL 0x0000B884
Zylonite 300 uses value 0x3c for the SMC91111 in the corresponding part of MSCx register in original Marvell sources, Zylonite320 uses 0x123c ... maybe you should review the MSCx configuration here. For pxa27x, I guess it might be something like 0x123c too.
From the log below, it really seems the ethernet chip is choking.
Cheers
RT4 = 4 Variable Latency I/O (VLIO)
ROM4 Bus Width 0 = 32 Bits
RDF4 = 8
RDN4 = 8
RRR4 = 3
RBUFF4 = 1 Faster device
#define CONFIG_SMC91111 #define CONFIG_SMC91111_BASE 0x10000300 /*nCS4*/ #define CONFIG_SMC_USE_32_BIT #undef CONFIG_SMC_91111_EXT_PHY
Ethernet controller is working fine. I can able to ping the machines connected to the network.
tftpboot command is also working fine, I can able to download the u-boot.bin to SDRAM.
But I have issue in downloading bigger files (zImage which is 2.5 MB) to the SDRAM. I am getting the following timeout messages and the download is not getting completed.
Loading: *########T T T T T T T T T T T T T T T T T T T T Retry count exceeded; starting again
Please help me to come out of this issue.
Kindly find the complete log below:
__
U-Boot 2010.06-rc1 (Aug 13 2010 - 09:11:31)
DRAM: 128 MiB
Flash: 64 MiB
In: serial
Out: serial
Err: serial
Net: SMC91111-0
Hit any key to stop autoboot: 2 ___ 0
MDT-Boot> print
bootargs=console=tty0 console=ttyS1, root=/dev/sda1 rootdelay=15
bootcmd=if mmc init && fatload mmc 0 0xa0000000 uImage; then bootm 0xa0000000; fi; if usb reset && fatload usb 0 0xa0000000 uImage; then bootm 0xa0000000; fi; bootm 0x150000;
bootdelay=2
baudrate=115200
ethaddr=00:00:70:26:1E:01
netmask=255.255.255.0
ethact=SMC91111-0
ipaddr=10.100.144.42
serverip=10.100.144.245
gatewayip=10.100.144.255
stdin=serial
stdout=serial
stderr=serial
Environment size: 445/32764 bytes
MDT-Boot> ping 10.100.144.245
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
host 10.100.144.245 is alive
MDT-Boot> tftp a3000000 u-boot.bin
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'u-boot.bin'.
Load address: 0xa3000000
Loading: *_############
done
Bytes transferred = 335280 (51db0 hex)
MDT-Boot> tftp a3000000 zImage
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_####################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######T ##T #T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
SMC91111: MAC 00:00:70:26:1e:01
Using SMC91111-0 device
TFTP from server 10.100.144.245; our IP address is 10.100.144.42
Filename 'zImage'.
Load address: 0xa3000000
Loading: *_#######################T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Thanks and Regards Stephen Paulraj C
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
DISCLAIMER:
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect.
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
participants (2)
-
Marek Vasut -
StephenPaulraj Chinnadurai-ERS,HCLTech