how to use imx6q sabreauto mfgtools

cancel
Showing results for 
Search instead for 
Did you mean: 

how to use imx6q sabreauto mfgtools

280 Views
Contributor III

hi

i'm used imx6q-sabreauto.

and yocto morty 4.9.11.

I downloaded L4.9.11-ga_mfg-tools.
I want to fuse to eMMC using mfgtools.
However, there is no mx6q-sabreauto-emmc file in the VBS file.
Can not fuse to IMX6Q-sabreauto eMMC using mfgtools?
regards.
Labels (3)
0 Kudos
9 Replies

46 Views
Contributor III

This is the error log output from mfgtools.

run windows 10

DLL version: 2.7.0
Monday, June 17, 2019 17:19:17 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[1]: Can't set m_hStopEvent before it initialized or it already stop

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]: Device Manager thread is closed

0 Kudos

46 Views
Contributor III

I tried it on the IMX6Q sabreauto board.

USB recognition is possible, but the board is not recognized by MFGTOOLS. What is the problem?

0 Kudos

46 Views
NXP TechSupport
NXP TechSupport

refer to the AI board schematic, imx6q auto board doesn't support emmc, supports mmc only, if you use mmc, can use the same sdcard mfgtool vbs as download to the sd card

0 Kudos

46 Views
Contributor III

I confirmed the eMMC boot in IMX6Q.

The sd3 of IMX6Q is used as eMMC.

I set mfgtools VBS file as follows.

Set wshShell = CreateObject("WScript.shell")
wshShell.run "mfgtool2.exe -c ""linux"" -l ""eMMC"" -s ""board=sabreauto"" -s ""sxdtb=sdb"" -s ""mmc=3"" "
Set wshShell = Nothing

On the PC, IMX6Q is recognized on the HID device, and mfgtools displays only the No Device Connected message.

I do not know how to solve it.

0 Kudos

46 Views
NXP TechSupport
NXP TechSupport

yes, refer to the schematic, SD3 can be used for emmc, but current AI board use SD3 for SD card, so you use your own emmc on that? because I don't have this board to test for you, since you use sd3 for EMMC, you can refer o the  "mfgtool2-yocto-mx-sabreauto-sdcard-sd3.vbs" or "mfgtool2-yocto-mx-sabreauto-sdcard-sd3-cpu3.vbs"? it seems that your sxdtb=sabreauto and mmc=2

0 Kudos

46 Views
Contributor III

I still see the HID device on my PC, but mfgtools is output as "no device connected".
Does mfgtool not recognize the board?

I'm using windows10.

regards!

0 Kudos

46 Views
NXP TechSupport
NXP TechSupport

I don't have this board, if the device manage can see the HID device, the mfgtool would recognize the board, you try to open other vbs file, any other output besides of "no device connected"?

0 Kudos

46 Views
Contributor III

Clicking start button has no response.

The mfgtool.log file is the same as the output we posted above.

mfgtool.log

DLL version: 2.7.0
Monday, June 27, 2019 14:23:17 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[1]: Can't set m_hStopEvent before it initialized or it already stop

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]: Device Manager thread is closed

On the IMX8MQ EVM board, mfgtool works properly.

Mfgtool does not work on my IMX6Q sabreauto board (sd mode) -> "no device connected"

regards!

0 Kudos

46 Views
NXP TechSupport
NXP TechSupport

don't insert any sdcard, then use "mfgtool2-android-mx6q-sabreauto-sdcard.vbs", could you see the device in the mfgtool? mfgtools couldn't detect your board anyway or just when you use emmc? and for imx6 AI board, don't forget set S3 to OFF ON OFF OFF

0 Kudos