L4.9.11_1.0.0-ga_mfg-tools tools issue for flashing on SD card onto I.mX6ULL EVK board

[srishan]

Dear I.MX Community,

Am using fsl-yocto-L4.9.11_1.0.0 bsps with L4.9.11_1.0.0-ga_mfg-tools on windows machine for flashing onto SD card, I would like to get this mfg tools first working with SD card and move onto NAND but it is failing with SD card

But I try to flash the SD card withoutmfg tools using the below command it works fine and everything comes up fine on the board

sudo dd if=fsl-image-validation-imx-imx6ull14x14evk.sdcard of=/dev/sdb bs=1M && sync

I searched several links they say that ddr stress test needs to be performed but I dont think this is required for my case as sudo dd if=fsl-image-validation-imx-imx6ull14x14evk.sdcard of=/dev/sdb bs=1M && sync seems to be working fine

What I suspect is the cfg.ini file and ucl .xml, could you please share the appropriate configurations in cfg.ini and ucl.xml fiel configurations for i.mx6ull board

But I try to load images using Mfg tools, with the attached  cfg.ini am seeing the below errors

\mfgtools-with-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage-imx6ull-14x14-ddr3-arm2.dtb, address is 0x83000000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]
ModuleID[2] LevelID[10]: *********MxHidDevice[070194B0] Jump to Ramkernel successfully!**********
ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CmdOperation[0], skip current command, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is F:\new_renesas_platform\new_Srini\mfg_tool\L4.9.11_1.0.0-ga_mfg-tools\mfgtools-with-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot-imx6ull14x14ddr3arm2_sd.imx
ModuleID[2] LevelID[1]: MxHidDevice::Write() Error writing to device 0x79.
ModuleID[2] LevelID[1]: Failed to initialize memory!
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed
ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed
ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - EVENT_KILL
ModuleID[2] LevelID[10]: CMyExceptionHandler::OnMsgExceptionEvent() - KillExceptionHandlerThread
ModuleID[2] LevelID[10]: Exception Handler thread is closed
ModuleID[2] LevelID[1]: delete MxHidDeviceClass
ModuleID[2] LevelID[10]: delete MxHidDevice[070194B0]
ModuleID[2] LevelID[10]: Device Manager thread is closed

Logs

U-Boot 2017.03-imx_v2017.03_4.9.11_1.0.0_ga+ga2fea67 (Sep 17 2017 - 14:44:17 -0500)

CPU:   Freescale i.MX6ULL rev1.0 at 396 MHz

Reset cause: POR

Model: Freescale i.MX6 ULL DDR3 ARM2 Board

Board: MX6ULL 14X14 DDR3 ARM2

DRAM:  1 GiB

ERROR: read error from device: bef4c9a8 register: 0x0!

at /home/bamboo/build/4.9.11-1.0.0/fsl-imx-x11/temp_build_dir/build_fsl-imx-x11/tmp/work/imx6ull14x14ddr3arm2-poky-linux-gnueabi/u-boot-imx/2017.03-r0/git/drivers/power/pmic/pfuze100.c:46/pfuze100_read()

Not supported, id=11

initcall sequence bffa9110 failed at call 87804344 (err=-22)

### ERROR ### Please RESET the board ###

Could you please let me know how this issue can be resolved, as am stuck with this issue from past two days

Kindly do the needful as early as possible

Many Thanks in advance,

Eagerly awaiting for your replies

[joanxie]

which .vbs do you use? try to use "mfgtool2-yocto-mx-evk-sdcard-sd2.vbs"