can't load tftp_kernel

[Sean Hurley]

went through several different approches on a tftp server.

cant load tftp_kernel. Really stuck bad. for Two weeks cant get out of this hole.

U-Boot> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0

Unknown command ‘AT’ – try ‘help’

U-Boot> run krb

macb0: link up, 100Mbps full-duplex (lpa: 0x4de1)

Using macb0 device

TFTP from server 192.169.2.2; our IP address is 192.169.2.3

Filename ‘oe_uImage.bin’.

Load address: 0x21400000

Loading: T T T T T T T T T T T T T T T 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

macb0: link up, 100Mbps full-duplex (lpa: 0x4de1)

Using macb0 device

TFTP from server 192.169.2.2; our IP address is 192.169.2.3

Filename ‘oe_uImage.bin’.

Load address: 0x21400000

Loading: *

Abort

U-Boot>

printenv

baudrate=115200

ethaddr=00:08:00:87:A6:18

boot_menu_timeout=[10]

autoload=no

gatewayip=192.169.2.1

bootfile=/tftpboot/oe_uImage.bin

bootargs=mem=64M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2

bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr}

bootdelay=3

ipaddr=192.169.2.3

netmask=255.255.255.0

hostname=MTCDP

serverip=192.169.2.2

dnsip=192.168.2.4

stdin=serial

stdout=serial

stderr=serial

ethact=macb0

loadaddr=0x21400000

bootstrap_file=oe_bootstrap.bin

uboot_file=oe_u-boot.bin

uboot_env1_file=oe_uboot_env1.bin

uboot_env2_file=oe_uboot_env2.bin

kernel_file=oe_uImage.bin

config_file=oe_config.tar.gz

oem_file=oe_oem.tar.gz

rootfs_file=oe_rootfs.jffs2

bootstrap_addr=0x00000000

uboot_addr=0x00020000

uboot_env1_addr=0x00060000

uboot_env2_addr=0x00080000

kernel_addr=0x000A0000

config_addr=0x00800000

oem_addr=0x01000000

rootfs_addr=0x01800000

bootstrap_size=0x00020000

uboot_size=0x00040000

uboot_env1_size=0x00020000

uboot_env2_size=0x00020000

kernel_size=0x00760000

config_size=0x00800000

oem_size=0x00800000

erase_bootstrap=nand erase ${bootstrap_addr} ${bootstrap_size}

erase_uboot=nand erase ${uboot_addr} ${uboot_size}

erase_uboot_env1=nand erase ${uboot_env1_addr} ${uboot_env1_size}

erase_uboot_env2=nand erase ${uboot_env2_addr} ${uboot_env2_size}

erase_kernel=nand erase ${kernel_addr} ${kernel_size}

erase_config=nand erase ${config_addr} ${config_size}

erase_oem=nand erase ${oem_addr} ${oem_size}

erase_rootfs=nand erase ${rootfs_addr}

tftp_bootstrap=tftp ${loadaddr} ${bootstrap_file}; run erase_bootstrap; nand wr}

tftp_uboot=tftp ${loadaddr} ${uboot_file}; run erase_uboot; nand write.jffs2 ${}

tftp_uboot_env1=tftp ${loadaddr} ${uboot_env1_file}; run erase_uboot_env1; nand}

tftp_uboot_env2=tftp ${loadaddr} ${uboot_env2_file}; run erase_uboot_env2; nand}

tftp_kernel=tftp ${loadaddr} ${kernel_file}; run erase_kernel; nand write.jffs2}

tftp_config=tftp ${loadaddr} ${config_file}; run erase_config; nand write.jffs2}

tftp_oem=tftp ${loadaddr} ${oem_file}; run erase_oem; nand write.jffs2 ${filead}

tftp_rootfs=tftp ${loadaddr} ${rootfs_file}; run erase_rootfs; nand write.jffs2}

krb=run tftp_kernel; run tftp_rootfs; boot

rb=run tftp_rootfs; boot

Environment size: 2535/131067 bytes

If some one could look over the env and let me know what I am doing wrong. NEED HELP BAD.

Thanks

[Bryan Tran]

Hi Sean,

It looks like it can not get the file from the tftp server. Would you try test your TFTP server first and see if it is working ok ?

1. Go to your PC where you have the TFTP server installed and type:

#echo “Hello, embedded world” > /tftpboot/hello.txt”

# tftp localhost

tftp> get hello.txt

Received 23 bytes in 0.1 seconds

tftp> quit

*Then do: ls command to make sure you can see hello.txt on your PC. This will confirm that – The tftp server is setting up correct. Other wise, you need to make sure your TFTP server is setting up correctly and running.

2. Otherwise, you can restart your device and get into the Uboot prompt, then do the command: run krb and let it run until you see what the error message is.

3. If you are still not able to get it to work, you may want to create a support portal case at https://support.multitech.com/support/login.html to get a quicker responses.

Regards,

BT

[Author]

Posts