Can't set m_hStopEvent before it initialized or it already stop [android_O8.0.0_1.0.0_tools]

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Can't set m_hStopEvent before it initialized or it already stop [android_O8.0.0_1.0.0_tools]

1,523 Views
ttttttx
Contributor III

How to use MFGTOOL to burn Android mirror ? my board is  imx6q-sabresd  ,  the info:

0.  My previous question :

How to download imx6Q android source code  :   Android O8.0.0_1.0.0 (Linux 4.9 kernel)

1.   mfgtools version

android_O8.0.0_1.0.0_tools.tar.gz/mfgtools/

2.  choose a *.vbs file

use mfgtool2-android-mx6q-sabresd-emmc.vbs to start  MfgTool2.exe :

Set wshShell = CreateObject("WScript.shell")
wshShell.run "mfgtool2.exe -c ""linux"" -l ""eMMC-Android"" -s ""board=sabresd""  -s ""folder=sabresd"" -s ""soc=6q"" -s ""mmc=3"" -s ""data_type="""
Set wshShell = Nothing

3.   mirror :    (come from "android_build/out/target/product/sabresd_6dq/")

files/android/sabresd/u-boot-imx6q.imx         
files/android/sabresd/partition-table.img 
files/android/sabresd/boot-imx6q.img            
files/android/sabresd/system.img
files/android/sabresd/vendor.img
files/android/sabresd/recovery-imx6q.img        

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

I am sure that the hardware is set to boot from otg ,but When my board is connected to MFGTOOL, the board is not recognized , like :

But when I reset the board, the software crashed , like :

this is the MfgTool.log :

{

DLL version: 2.7.0
Saturday, August 15, 2020 00:57:50 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[00BDA3E8]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[00BDA848]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[0617E550]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[061B1458]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[06186950]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[06186CF0]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[061B18B8]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[061B1C58]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[061B1FF8]
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]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0054#5&340f1a3e&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0054#5&340f1a3e&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1

}

why ?

It seems to be a problem with the burning software, because it simply cannot work .

my windows host pc :

__________________________________________________________________________________________

I have used another version of mfgtool (L4.1.15_2.0.0-ga_mfg-tools.tar.bz2/mfgtools-with-rootfs.tar.gz/mfgtools)but this is not the case, it is okay !

Set wshShell = CreateObject("WScript.shell")
wshShell.run "mfgtool2.exe -c ""linux"" -l ""eMMC-new"" -s ""board=sabresd"" -s ""mmc=3"" -s ""version=version_for_test"""
Set wshShell = Nothing

________________________________________________________________________________________

why ?

Did I choose a correct burning software?  or something else ...

Labels (4)
0 Kudos
2 Replies

1,325 Views
igorpadykov
NXP Employee
NXP Employee

Hi tianxiang

in general android_O8.0.0_1.0.0 should support mfg tool, one can try

it with linux demo image on i.MX6 Sabre SD board

i.MX 6QuadPlus, i.MX 6Quad, i.MX 6DualPlus, i.MX 6Dual, i.MX 6DualLite, i.MX 6Solo, i.MX 6SoloX

i.MX Series Manufacturing Toolkit for Linux 4.9.11_1.0.0 Release

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

0 Kudos

1,325 Views
ttttttx
Contributor III

Thank you very much!

At this moment,  I can not download the demo image (L4.9.11_1.0.0_MX6QDLSOLOX) due to network reasons. I use mfgtool (IMX6_L4.9.11_1.0.0_MFG_TOOL) and the phenomenon is exactly the same as the version android_O8.0.0_1.0.0_tools.

But now I found a way to solve this problem, this is:

1. choose  L4.1.15_2.0.0-ga_mfg-tools.tar.bz2/mfgtools-with-rootfs.tar.gz/mfgtools 

2. Replace the content in L4.1.15_2.0.0-ga_mfg-tools with android_O8.0.0_1.0.0_tools/mfgtools/Profiles/Linux/OS Firmware/*  , and delete all statements related to MX6SLL and MX7ULP in ucl2.xml

Now,  Android has been downloaded to my board , and the system seems to be running normally. 

so ,  i.MX Series Manufacturing Toolkit for Linux 4.9.11_1.0.0 Releaseand      android_O8.0.0_1.0.0_tools  are both still not suitable for my board.    Please find where the problem is , thank you!

0 Kudos