uboot Autonegotiation timed out
Home › Forums › MultiConnect OCG › uboot Autonegotiation timed out
- This topic has 4 replies, 2 voices, and was last updated 11 years, 7 months ago by Jesse Gilles.
-
AuthorPosts
-
April 16, 2013 at 5:57 am #2910Sean HurleyParticipant
I have been working this issue for a couple of days now. Checking to make sure that I have my TFTP server set correctly (XINETD). I have checked the ARP settings and all parameters that I can think of. Went through all of the forums and can’t find a fix. Connection times out at boot and I can not Boot tftp_kernel. printenv shows every thing that is there should correct according to the developer page.
I am using Minicom ubuntu 10.4
printenv 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
ipaddr=192.168.2.1
netmask=255.255.255.0
hostname=MTCDP
serverip=192.168.2.2
dnsip=192.168.2.3
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: 2468/131067 bytes
U-Boot> printenv
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
ipaddr=192.168.2.1
netmask=255.255.255.0
hostname=MTCDP
serverip=192.168.2.2
dnsip=192.168.2.3
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: 2468/131067 bytes
U-Boot> run tftp_kernel
macb0: Starting autonegotiation…
macb0: Autonegotiation timed out (status=0x7849)
macb0: link down (status: 0x7849)
NAND erase: device 0 offset 0xa0000, size 0x760000
Erasing at 0x7e0000 — 100% complete.
OK
Usage:
nand – NAND sub-system
sorry for the long post this is all the info I know to give at this point.
April 16, 2013 at 2:03 pm #4511Jesse GillesBlockedmacb0: Starting autonegotiation…
macb0: Autonegotiation timed out (status=0x7849)
macb0: link down (status: 0x7849)
If the autonegotiation is timing out, then no Ethernet link is being detected at all.
Perhaps a bad Ethernet cable? If the unit is properly connected to an Ethernet switch, it should get a successful link, regardless of any other settings.
April 16, 2013 at 5:02 pm #4512Sean HurleyParticipantSorry 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.
April 17, 2013 at 5:19 am #4513Sean HurleyParticipantU-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
April 17, 2013 at 9:28 pm #4514Jesse GillesBlocked> 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.
To flash the kernel and rootfs via u-boot, you need to have an Ethernet connection to a TFTP server that is hosting the files. You do need the 3-pin debug connection to control u-boot and initiate the flashing, but the file transfer of occurs over TFTP and Ethernet.
-
AuthorPosts
- You must be logged in to reply to this topic.