hi
i'm used imx6q-sabreauto.
and yocto morty 4.9.11.
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
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.
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
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!
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