MFG tool flashing error reg

[sachusanal]

Dear Sir ,

When I am trying to boot image from emmc using mfgtool I get an error like this

Please help me to solve this issue.i here by attach my ucl2.xml script file.

DLL version: 2.3.3

Tuesday, April 21, 2015 14:14:23   Start new logging

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

ModuleID[2] LevelID[1]: new MxHidDeviceClass

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

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#6&27177e6b&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#6&27177e6b&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_0461&pid_4e22#7&19a6fc1e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 1

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&pid_0054#7&65f53e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[10]: new MxHidDevice[00947880]

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&PID_0054\6&27177E6B&0&6, _deviceInstanceID: USB\VID_15A2&PID_0054\6&27177E6B&0&6

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 6

ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&PID_0054#6&27177E6B&0&6#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:3-Port:6

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1

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

ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is E:\Sachu\sachu\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot.imx

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is E:\Sachu\sachu\mfgtools\Profiles\Linux\OS Firmware\firmware\uImage, address is 0x12000000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is E:\Sachu\sachu\mfgtools\Profiles\Linux\OS Firmware\firmware\fsl-image-mfgtool-initramfs-imx6qsabresd.cpio.gz.u-boot, address is 0x12C00000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is E:\Sachu\sachu\mfgtools\Profiles\Linux\OS Firmware\firmware\uImage-mfgtool--imx6q-sabresd-dtb, address is 0x18000000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]

ModuleID[2] LevelID[10]: *********MxHidDevice[00947880] 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]: ExecuteCommand--Boot[WndIndex:0], File is E:\Sachu\sachu\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot.imx

Original Attachment has been moved to: ucl2.xml.zip

Original Attachment has been moved to: cfg.ini.zip

[igorpadykov]

Hi sachu

MFG Tool has issue for executing "frf" command, please refer to attached

Release Notes p.24, Table 19. Known issues and workarounds.

Also it may be recommended to test all commands in Linux

(refer to attached Linux Guide for available options for eMMC programming).

Best regards

igor

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

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

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

[sachusanal]

Hi igor

Thanks for your reply

I commented the "frf" command portion in ucl2.xml script .then I try to falsh,that time also i get the same error before mentioned.

from that i confirmed that it is not the cause.

In my flashing only sucess up to firmware files loading i cant write even uboot file to emmc.

please help me what mistake i did?

I am using IM6 sabresd board .I take mfgtool build as per the freescale yocto project users guide.

then i add the extra configuration on mx6sabresd_mfg.h file as per the manufacturing tool v2 mfgtool document.

then change my device configuration .is this problem occured due to DDR configuration.

I also verified the ddr configuration

i here by attach my ddr configration file

Please help me to solve this error

[igorpadykov]

Hi sachu

had you tried to write eMMC just with "dd" command,

will it boot ? Usage is described in Linux Guide.

~igor

[sachusanal]

Hi igor

In ucl.xml script i try  (comment the script up to jumping to OS image portion)download image to  board without built initramfs.spio.gz.uboot, uImage and u-boot.bin for MFG. but it fails .In ucl.xml script i commented the partion creation portion  and just started with the "dd" command  execution part both time i got the same log

Monday, April 27, 2015 14:26:22  Start new logging

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

ModuleID[2] LevelID[1]: new MxHidDeviceClass

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

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#6&27177e6b&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#6&27177e6b&0&5#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_0461&pid_4e22#7&3070bb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 1

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&pid_0054#7&131fa5e3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[10]: new MxHidDevice[00B445A0]

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&PID_0054\6&27177E6B&0&5, _deviceInstanceID: USB\VID_15A2&PID_0054\6&27177E6B&0&5

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 5

ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&PID_0054#6&27177E6B&0&5#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:3-Port:5

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1

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

ModuleID[2] LevelID[10]: current state no command, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: DeviceCmd is NULL, just finished.

I here by attach my ucl.xml script for your refernce. I am using DDR as micron LPDDR2  part number: MT42L256M32D2,  its data sheet also i attached here. In the same im6qsabresd device i can load wince image from emmc without any issue.

from that i can analyse emmc have no problem .but y this occured in Linux os image loading.

[igorpadykov]

do you mean that you are using lpddr2 with i.MX6Q ?

Because "im6qsabresd" does not use lpddr2, it uses ddr3.

[sachusanal]

Hi Igor

we are using LPDDR2 (MT42L256M32D2LG) we are using im6d processor (MCIMX6D5EYM10AC)

I here by attach my processor schematic . what you mean ?  is my error is related to ddr?

[sachusanal]

please help me to solve this issue ,..

[igorpadykov]

had you run DDR test and found new DDR settings ?

https://community.freescale.com/docs/DOC-96412

if yes, I would suggest to boot from SD and try to

execute MFG Tools commands from Linux.

[sachusanal]

Dear Igor

I run OBDS test to this device with the device by using the correct DDR configuration. Here also i used the same configuration for DDR (same register values).

so i hope DDR configuration is correct.in my board i have no option to boot from SD card . so I cant use SD card for boot purpose.

in the same board i can load the WInce OS image successfully. I here by attach the Wince OS image Mfg folder .

y this board reset scenario occured in  OS image loading

[igorpadykov]

what Mfg Tool are you using, what is link ?

[sachusanal]

For  Linux firmware upgrading i used the  mfgtool for yocto which is downloaded from freescale

I cant attach the file here.

so  will mail to you that file which i used currently for mfgtool flashing for linux formware

[igorpadykov]

is it L3.14.28_1.0.0 ?

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&nodeId=018rH3ZrDRB24A&fpsp=1&t...

[sachusanal]

no

http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&fpsp=1&tab=Design_Tools_Tab>.

I downloaded from here...

imx-3.10.53_1.1.0_ga-mfg-tools  downloaded version is using  not

[igorpadykov]

what is with unchanged ucl2.xml - will it work ok ?

[sachusanal]

no .... files mismatching occured (namewise) thats y i changed script as per my files

[sachusanal]

once i flashed the image without changing ucl2.xml script file up to Jumping to OS image is executing after that loading uboot ,uimage ,file system to emmc is failed.

so i changed the ucl2.xml script file.

i here bu attach the unchanged ucl2.xml script file and changed ucl2.xml scrpt file

[igorpadykov]

so you are using i.MX6D custom board with lpddr2

and it is booting only with SDK and WinCE, correct ?

It does not boot with any linux ?

[sachusanal]

ya it is loading with Wince os image and obds.bin file .

I builed the OBDS file in linux itself obds.bin is loading perfectly.

Now i try to load linux image that time i get an issue...

please help me.

[igorpadykov]

you can look at attached file sect.4.4.1.2 Using eMMC4.4 on SDHC4 (from L3.14.28_1.0.0_iMX6QDLS_BUNDLE),

Uboot can be loaded with MFG Tool or you can easily find other methods to load it with usb on web

<LIST name="SabreSD-SD" desc="USB SDP">

    <CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot-mx6q-sabresd_nopad.bin" >Loading image</CMD>

    <CMD state="BootStrap" type="jump" > Jumping to image. </CMD>

    <CMD state="Updater" type="push" body="$ echo Load Complete!">Done</CMD>

</LIST>

[sachusanal]

Hi Igor

<LIST name="SabreSD-SD" desc="USB SDP">

through this command  where we loading the u-boot.

In our device there is no ethernet connection so i cant transfer file(kernel image and file system) through TFTP.

let me know what is the exact issue of  device reset

1.I downloaded the L 3.10.53_1.1.0_ga-mfg-tools

2.I build mfgtool as per the freescale yocto project users guide , in configuration file  i add FSL_KERNEL_DEFCONFIG = "imx_v7_mfg_defconfig

then build by using bitbake fsl-image-mfgtool-initramfs

3. then I add some extra configuration on mxsabresd_mfg.h  as per Manufacturing Tool V2 Linux or Android Firmware Development Guide V2 

4.in mxsabresd.c file I change UART ,and USDHC configuration as per my board

5.Then build ,in kernel dts file also i cahnge device configuration

6.then build after that these file i copied to E:\mfgtools\Profiles\Linux\OS Firmware\firmware this folder

7.Again i build one another build for sbresd board for using bitbake core-image-sato-sdk command

8. in that build I change sabresd.c  file as per uart and SDHC configuration same as mfgtool build

9. in kernel configuration build also i did the same configuration of mfgtool build

10 .copied that files in  E:\mfgtools\Profiles\Linux\OS Firmware\files folder

then edit the ucl.xml script as per our configuration ,and files name.

these are the steps i followed for the mftool flashing

please help me what mistake i did