Timing out

Home Forums MultiConnect OCG Timing out

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #5897
    Mike Smith
    Participant

    Hello,
    I am a complete noob. I have trying to flash kernel and roofts from u-boot.

    It constantly has timed out.
    I have also tried ‘add an entry to the ARP cache manually.’ with no luck my.

    Does anyone have any suggestions.

    Here is a copy of whats happening so far.

    Welcome to minicom 2.6.1

    OPTIONS: I18n
    Compiled on May 1 2012, 13:36:18.
    Port /dev/ttyUSB0

    Press CTRL-A Z for help on special keys

    T RomBOOT
    *** AT91Bootstrap-2.13

    FAST slew rate
    NAND id:0x0000ECDA
    > From: [0x00020000] To: [0x23F00000] Size: [0x00040000]
    > SUCCESS
    > Start: [0x23F00000]

    U-Boot 1.3.4-mts (Sep 24 2012 – 18:33:19)

    DRAM: 64 MB
    NAND: 256 MiB
    In: serial
    Out: serial
    Err: serial
    Net: macb0
    macb0: Starting autonegotiation…
    macb0: Autonegotiation complete
    macb0: link up, 100Mbps full-duplex (lpa: 0x4de1)
    Hit any key to stop autoboot: 0

    Loading from NAND 256MiB 3,3V 8-bit, offset 0xa0000
    ** Unknown image type
    Wrong Image Format for bootm command
    ERROR: can’t get kernel image!
    U-Boot>

    U-Boot> printenv
    baudrate=115200
    bootargs=mem=64M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2
    bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr}
    bootdelay=3
    hostname=MTCDP
    dnsip=192.168.2.3
    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
    ethaddr=00:08
    ipaddr=192.168.2.1
    serverip=192.168.2.2
    netmask=255.255.255.0
    stdin=serial
    stdout=serial
    stderr=serial

    Environment size: 2433/131067 bytes
    U-Boot>

    U-Boot> run tftp_kernel
    macb0: link up, 100Mbps full-duplex (lpa: 0x4de1)
    Using macb0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.1
    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

    …………………………………………..

    However I have noticed that when trying to do this I do get a re-appearing notice that ‘Wired network is disconnected’.

    obviously I need help !

    Thanks,
    Mike

    #5898
    Mike Smith
    Participant

    I did try this to check out the TFTP and here was my response.

    mike@mike-Satellite-C655:~$ echo “Hello, embedded world” > /tftpboot/hello.txt”
    mike@mike-Satellite-C655:~$ tftp localhost
    tftp> get hello.txt
    Error code 1: File not found
    tftp>

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.