AnsweredAssumed Answered

Issue with conga-QMX6 WEC7 image deployment from uSD

Question asked by freescalewec7 on Oct 1, 2014

Using a congatec conga-QMX6 SOM (PN: 016104, Quad), I am trying to load the stock WEC7 image (downloaded from Adeneo) onto a uSD and boot from it. I burned the eboot.nb0/NK.nb0 using cfimager, but upon boot the U-Boot console gives the following:



U-Boot 2009.08-00671-g5e573f0 QMX6Rx07 pn016104 (Jan 15 2014 - 14:20:15)


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

Temperature:   19 C, calibration data 0x5594d069

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-QMX6: Board: 0x63012 [POR ]

Boot Device: SPI NOR

I2C:   ready

DRAM:   2 GB


JEDEC ID: 0xbf:0x25:0x4a

Reading SPI NOR flash 0xc0000 [0x2000 bytes] -> ram 0x27600ae0

*** Warning - bad CRC, using default environment


Reading SPI NOR flash 0x3fc000 [0x40 bytes] -> ram 0x275fff10

In:    serial

Out:   serial

Err:   serial

PFUZE100 Rev. 21 detected

Net:   got MAC address from IIM: 00:13:95:12:71:53

configure Atheros AR8035 Ethernet Phy


Hit any key to stop autoboot:  0

mmc0 is current device

** Partition 1 not valid on device 0 **


** Unable to use mmc 0:1 for fatload **

** Bad partition 1 **

mmc1(part 0) is current device


** Unable to use mmc 1:1 for fatload **

** Bad partition 1 **

Card did not respond to voltage select!

mmc2(part 0) is current device

MMC: block number 0x1 exceeds max(0x0)

** Can't read from device 2 **


** Unable to use mmc 2:1 for fatload **

** Bad partition 1 **


When a uSD with Linux is inserted, it boots correctly from mmc0 but it complains when it's loaded with WEC7 instead. Do I need to copy uboot, rootfs, etc. over to the uSD in order to have it boot properly? I'm not the most familiar with this U-boot configuration, so don't know if it's compatible to have U-boot run from SPI NOR. I also tried populating the uSD with a 6q_bootscript (dropping it into the FAT partition created during image burn) but it doesn't seem to find it (and truthfully the syntax may not be correct). I was hoping to be able to perform this activity without using MFG Tools (as I didn't want to permanently change the SPI NOR on the SOM and run anything outside of my control), but perhaps this is my only option.


Any thoughts would be greatly appreciated.