• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 739 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

am335x uboot mii

Caspar Cai
Prodigy 140 points
Other Parts Discussed in Thread: AM3354, DM3730

Hi, all

sdk package: ti-sdk-am335x-evm-05.06.00.00-Linux-x86-Install

uboot version： u-boot-2012.10-psp05.06.00.00

cpu：am3354 zcz80

Compilation： make am335x_evm

ethernet: use "mii",  the PHY links correctly at 100Mbit/s

phy company：micrel  ks8041

question: tftp download mirrors very slow, estimated not to  100Mbit/s? What is the reason?


log：

U-Boot 2012.10 (Jun 24 2013 - 17:46:02)

I2C: ready
DRAM: 256 MiB
NAND: 512 MiB
Press "RESET" down for 5sec. to reset to factory settings: 0
Net: cpsw
Hit any key to stop autoboot: 0

link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.5.75; our IP address is 192.168.5.115
Filename '15.17.0.100.ext2'.
Load address: 0x88000000
Loading: #################################################################
#########################################

  • 0
    TI__Mastermind 25235 points

    Hi Caspar,

    The TFTP interface is a simple one: get request, send a packet, wait for acknowledge, send another block. If there are timeouts, you should see "T" characters printed, but still, I would suggest checking the tftp server side - do a tcpdump. It should be something like:

    sudo tcpdump -vvv -i any -n host 172.20.1.223

    where 172.20.1.223 is the IP of my board - you should replace it accordingly.

    Best regards,
    Miroslav

  • 0 in reply to Miroslav Kiradzhiyski XID
    Prodigy 140 points

    Hi Miroslav

    Thanks for your help!

    I use DM3370 to tftp mirror for same the tftp server. DM3730(TI8168 for 100M)  much faster rate than AM335X for same the tftp server.

    am335x and dm3730 tcp caught log seems like.Time difference between the two packages is not the same!

    Consider the following red part:

    tcpdump log for (DM3730):

    09:24:59.101958 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.5.75 is-at 1c:6f:65:67:25:cc, length 28
    09:24:59.102345 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 75)
    192.168.5.115.3156 > 192.168.5.75.69: [no cksum] 47 RRQ "15.17.0.100.ext2" octet timeout 5 blksize 512
    09:24:59.157654 IP (tos 0x0, ttl 64, id 12773, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.55125 > 192.168.5.115.3156: [bad udp cksum b521!] UDP, length 516
    09:24:59.158107 IP (tos 0x0, ttl 255, id 1, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.3156 > 192.168.5.75.55125: [no cksum] UDP, length 4
    09:24:59.158181 IP (tos 0x0, ttl 64, id 12774, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.55125 > 192.168.5.115.3156: [bad udp cksum 905!] UDP, length 516
    09:24:59.158628 IP (tos 0x0, ttl 255, id 2, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.3156 > 192.168.5.75.55125: [no cksum] UDP, length 4
    09:24:59.158687 IP (tos 0x0, ttl 64, id 12775, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.55125 > 192.168.5.115.3156: [bad udp cksum 229e!] UDP, length 516

    tcpdump log for (AM335X):

    09:26:54.234253 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.5.75 is-at 1c:6f:65:67:25:cc, length 28
    09:26:54.237415 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 75)
    192.168.5.115.4014 > 192.168.5.75.69: [no cksum] 47 RRQ "15.17.0.100.ext2" octet timeout 5 blksize 512
    09:26:54.241031 IP (tos 0x0, ttl 64, id 41544, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum cb5a!] UDP, length 516
    09:26:54.244071 IP (tos 0x0, ttl 255, id 1, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4
    09:26:54.244175 IP (tos 0x0, ttl 64, id 41545, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum 1f3e!] UDP, length 516
    09:26:54.247529 IP (tos 0x0, ttl 255, id 2, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4
    09:26:54.247591 IP (tos 0x0, ttl 64, id 41546, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum 38d7!] UDP, length 516
    09:26:54.250992 IP (tos 0x0, ttl 255, id 3, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4
    09:26:54.251074 IP (tos 0x0, ttl 64, id 41547, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum 4a66!] UDP, length 516
    09:26:54.254466 IP (tos 0x0, ttl 255, id 4, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4
    09:26:54.254534 IP (tos 0x0, ttl 64, id 41548, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum 34b3!] UDP, length 516
    09:26:54.257920 IP (tos 0x0, ttl 255, id 5, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4
    09:26:54.257955 IP (tos 0x0, ttl 64, id 41549, offset 0, flags [DF], proto UDP (17), length 544)
    192.168.5.75.39653 > 192.168.5.115.4014: [bad udp cksum 56a2!] UDP, length 516
    09:26:54.261379 IP (tos 0x0, ttl 255, id 6, offset 0, flags [DF], proto UDP (17), length 32)
    192.168.5.115.4014 > 192.168.5.75.39653: [no cksum] UDP, length 4

    Best regards,

    Caspar