9 Replies Latest reply: Feb 26, 2014 11:52 AM by JASON JIANG RSS

Cannot boot my iMX6 Quad SABRE board from SD card programmed by MFGTOOL2

JASON JIANG Level 1
Visibility: Open to anyone

Hi,

 

I used MFGTOOL2 (Mfgtools-Rel-4.1.0_130816_MX6Q_UPDATER) to program a Samsung SD card (8G) successfully. No error from MFGTOOL2. But when I tried to boot the iMX6 Quad SABRE board, u-boot is running fine, but after the three-second count down, I got the error saying "FEC: Link is down 7949". I noticed

 

This is the log in detail. I noticed there's a CRC error (in red). Don't know whether it matters or not.

U-Boot 2009.08 (Aug 16 2013 - 12:04:20)

 

CPU: Freescale i.MX6 family TO1.2 at 792 MHz

Thermal sensor with ratio = 180

Temperature:   44 C, calibration data 0x5744b77d

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock     : 66000000Hz

ipg per clock : 66000000Hz

uart clock    : 80000000Hz

cspi clock    : 60000000Hz

ahb clock     : 132000000Hz

axi clock   : 264000000Hz

emi_slow clock: 132000000Hz

ddr clock     : 528000000Hz

usdhc1 clock  : 198000000Hz

usdhc2 clock  : 198000000Hz

usdhc3 clock  : 198000000Hz

usdhc4 clock  : 198000000Hz

nfc clock     : 24000000Hz

Board: i.MX6Q-SABRESD: unknown-board Board: 0x63012 [POR ]

Boot Device: SD

I2C:   ready

DRAM:   1 GB

MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3

*** Warning - bad CRC or MMC, using default environment

In:    serial

Out:   serial

Err:   serial

i2c: I2C3 SDA is low, start i2c recovery...

I2C3 Recovery success

Found PFUZE100! deviceid=10,revid=11

Net:   got MAC address from IIM: 00:04:9f:02:6e:c4

FEC0 [PRIME]

Hit any key to stop autoboot:  0

PHY indentify @ 0x1 = 0x004dd074

FEC: Link is down 7949

Using FEC0 device

TFTP from server 192.168.1.101; our IP address is 192.168.1.103

Filename 'uImage'.

Load address: 0x10800000

Loading: FEC: Link is down 7949

FEC: Link is down 7949

 

Under u-boot, my env are:

bootdelay=3

baudrate=115200

ipaddr=192.168.1.103

serverip=192.168.1.101

netmask=255.255.255.0

loadaddr=0x10800000

rd_loadaddr=(0x1300000)

netdev=eth0

ethprime=FEC0

uboot=u-boot.bin

kernel=uImage

nfsroot=/opt/eldk/arm

bootargs_base=setenv bootargs console=ttymxc0,115200

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp

bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm

bootargs_mmc=setenv bootargs ${bootargs} ip=dhcp root=/dev/mmcblk0p1 rootwait

bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 3; mmc read ${loadaddr} 0x800 0x2000; bootm

bootcmd=run bootcmd_net

stdin=serial

stdout=serial

stderr=serial

ethact=FEC0

 

So I guess my bootcmd should not be "run bootcmd_net". I then ran "bootcmd_mmc" directly, but got the error below:

MX6Q SABRESD U-Boot > run bootcmd_mmc

mmc3(part 0) is current device

 

MMC read: dev # 3, block # 2048, count 8192 ... 8192 blocks read: OK

Wrong Image Format for bootm command

ERROR: can't get kernel image!

 

Can anybody point it out where it's wrong?

Thank you so much.

Jason

  • Reply