[Sean Hurley]

U-Boot> reset�RomBOOT

*** AT91Bootstrap-2.13

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 timed out (status=0x7849)

macb0: link down (status: 0x7849)

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!

this is what I get connecting through minicom usb 2 serial.

baudrate=115200

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

boot_menu_timeout=[10]

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 write.jffs2 ${filead}

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

tftp_uboot_env1=tftp ${loadaddr} ${uboot_env1_file}; run erase_uboot_env1; nand write.jffs2 ${fil}

tftp_uboot_env2=tftp ${loadaddr} ${uboot_env2_file}; run erase_uboot_env2; nand write.jffs2 ${fil}

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

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

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

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

krb=run tftp_kernel; run tftp_rootfs; boot

rb=run tftp_rootfs; boot

ipaddr=192.168.2.1

serverip=192.168.2.2

netmask=255.255.255.0

stdin=serial

stdout=serial

stderr=serial

Environment size: 2468/131067 bytes

any suggestions would be wonderful

I have built corecdp 2.2.2

kinda stuck now. Would like to continue with development.

Thanks For reading

[Sean Hurley]

Sorry I was not specific enough. Late Night. I am using 3 pin debug Cable to connect to the unit. I am also using USB to serial to make the connection. If there are any suggestions or a recommend a different approach. I have followed what I believe to be all the steps on the developer site. I might be over looking something. Is it not recommended to use the 3 pin debug cable for loading coredcp and jar files. If there is anything else you need from me let me know I will gladly provide any info you might need.

[Author]

Posts