AnsweredAssumed Answered

unable to flash yocto images to eMMC using MFGTool-iMX6SL

Question asked by Jansi Rani on Oct 3, 2016
Latest reply on Aug 4, 2017 by Srikanth Medisetty

Hai,

we are having a custom board same as iMX6SLEVK but difference is , in our custom board we mounted eMMC also.

So according to the schematic ,SD2 channel is used for boot purpose for both SDcard and eMMC.

As CD and WP pins are not required for the eMMC we commented those pin configuration in imx6sl-evk.dts

i.e

&usdhc2 {
    pinctrl-names = "default", "state_100mhz", "state_200mhz";
    pinctrl-0 = <&pinctrl_usdhc2_1>;
    pinctrl-1 = <&pinctrl_usdhc2_1_100mhz>;
    pinctrl-2 = <&pinctrl_usdhc2_1_200mhz>;
    //cd-gpios = <&gpio5 0 0>;
    //wp-gpios = <&gpio4 29 0>;
    keep-power-in-suspend;
    enable-sdio-wakeup;
    status = "okay";
};

Then compiled the images (uboot.bin,uImage and rootfs.tar).

Inorder to flash images to eMMC using Mfgtools compiled Mfg firmware images also .

when we start the Mfgtool.exe , it is getting stop at Starting Linux..... without any errors in the Mfgtools.exe.

i.e

"U-Boot 2013.04 (Oct 03 2016 - 15:23:09)

 

CPU:   Freescale i.MX6SL rev1.2 at 792 MHz
CPU:   Temperature 38 C, calibration data: 0x5aa51e69
Reset cause: POR
Board: MX6SLEVK
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Entered into mmc_init()
*** Warning - bad CRC, using default environment

 

In:    serial
Out:   serial
Err:   serial
Found PFUZE100! deviceid=10,revid=11
Entered into mmc_init()
mmc1(part 0) is current device
Net:   FEC [PRIME]
Warning: failed to set MAC address

 

Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;bootm ${loadaddr} ${initrd_addr} ${fdt_addr};
Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.10.17-1.0.0_ga+g232293e
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5182880 Bytes = 4.9 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 83800000 ...
   Image Name:   initramfs
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4399687 Bytes = 4.2 MiB
   Load Address: 12c00000
   Entry Point:  12c00000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image ... OK
OK
switch to ldo_bypass mode!
   Using Device Tree in place at 83000000, end 8300b484

 

Starting kernel ...

"

for reference please find the attached Mfgtool logs also.

 

why Mfgtool is getting stop showing "No Device Connected"

How to rectify this?

 

Thanks and regards,

D.Jansirani

Original Attachment has been moved to: MfgTool.log.zip

Outcomes