topic Re: Writing eMMC with MFGTOOL2 is fail in i.MX Processors

Writing eMMC with MFGTOOL2 is fail

JHY — Fri, 27 Mar 2015 05:53:01 GMT

I tried to write eMMC in i.MX6Q SABRE-SDP using IMX6_L3.10.53_MFG_TOOL.

And example operation in 'Manufacturing Tool V2 Quick Start Guide.docx' is not working.

It looks like suitable for only old type.

Please tell me other reference describing cfg.ini and ucl2.xml for eMMC writing in SABRE-SDP for MFGTOOL2 not old type.

Re: Writing eMMC with MFGTOOL2 is fail

lifusong — Fri, 27 Mar 2015 06:41:49 GMT

Download linux BSP from this URL i.MX 6 Series Software and Development Tool R|Freescale

and follow the BSP porting guide. and Manufacturing Tool V2 Linux or Android Firmware Development Guide V2.docx

but I still fail to build the u-boot.bin.

can't found the yocto build command.(I can't found ,

/opt/poky/1.4.1/sysroots/i686-pokysdk-linux/usr/bin/cortexa9hf-vfp-neon-poky-linux-

gnueabi/arm-poky-linux-gnueabi- alsotry to download follow Yocto Project Reference Manual,)

do you success please tell me.

thanks.

Re: Writing eMMC with MFGTOOL2 is fail

igorpadykov — Fri, 27 Mar 2015 10:43:02 GMT

Hi JHY

in attached ucl2.xml IMX6_L3.10.53_MFG_TOOL

there is profile for eMMC:

so in cfg.ini one needs to set

[LIST]

name = eMMC

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: Writing eMMC with MFGTOOL2 is fail

JHY — Tue, 31 Mar 2015 01:58:00 GMT

I set cfg.ini but still have error.

MfgTool.log is here.

DLL version: 2.3.3

Tuesday, March 31, 2015 10:52:40 Start new logging

ModuleID[2] LevelID[1]: Load command--file C:\work\02_freescale\01_i.MX6\08_sabre_platform\imx-3.10.53_1.1.0_ga-mfg-tools\mfgtools-with-rootfs\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage-imx6sx-17x17-arm2-emmc.dtb failed to open.errcode is 2

ModuleID[2] LevelID[1]: Parse ucl script failed, error code: 4

Re: Writing eMMC with MFGTOOL2 is fail

igorpadykov — Tue, 31 Mar 2015 08:02:31 GMT

if you are using i.MX6Q SABRE-SDP, then

how "zImage-imx6sx-17x17-arm2-emmc.dtb" appeared in your log ?

Re: Writing eMMC with MFGTOOL2 is fail

JHY — Thu, 02 Apr 2015 03:46:04 GMT

My last log is below. Have you ever seen this error?

DLL version: 2.3.3

Thursday, April 02, 2015 12:43:19 Start new logging

ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:2

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 0078C810

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 3

ModuleID[2] LevelID[10]: Device Manager thread is running

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ tar xf $FILE

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ sh mksdcard.sh /dev/mmcblk0

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=/dev/zero of=/dev/mmcblk0 bs=1k seek=384 conv=fsync count=129

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ echo 0 > /sys/block/mmcblk0boot0/force_ro

ModuleID[2] LevelID[1]: PortMgrDlg(0)--MSCDevice--Command Push(no file) 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]: 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]: Device Manager thread is closed