Hai,
we designed a custom board same as iMX6SLEVK.
In this board both sdcard boot and eMMC boot are using sd2 interface same as iMX6SLEVK design .
we successfully compiled and flashed Marshmallo images to the sdcard using Mfgtools and the board is booting without any issues from sdcard.
Now we want to flash images to the eMMC .we added changes to be required for eMMC in u-boot and in kernel.
for Normal images we used "make mx6slevkandroid_defconfig" and "make imx_v7_android_defconfig" and compiled whole filesystem and we got normal images in the myandroid/out/...../evk_6sl folder.
Then,
for Mfg images we used the following commands to build uboot.bin & zImage:
uboot:
make mx6slevk_defconfig
kernel:
make imx_v7_mfg_defconfig
Replaced only uboot.bin & zImage in the Mfgtools/......./firmware/ folder
and Replaced respective normal images in the Mfgtools/......./files/android/evk folder .
when we run the mfgtool.exe, it is getting stop at "starting kernel"
i.e:
"
U-Boot 2015.04-dirty (Dec 16 2016 - 09:52:10)
CPU: Freescale i.MX6SL rev1.2 at 792 MHz
CPU: Temperature 42 C
Reset cause: POR
Board: MX6SLEVK
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc1(part 0) is current device
Net: Phy 0 not found
PHY reset timed out
FEC [PRIME]
Error: FEC address not set.
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};
Hit any key to stop autoboot: 0
Kernel image @ 0x80800000 [ 0x000000 - 0x5a6bd8 ]
## Loading init Ramdisk from Legacy Image at 83800000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7565864 Bytes = 7.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300bf7a
switch to ldo_bypass mode!
Starting kernel ...
"
Please tell us how to solve this issue.
