the problem when using mfgtool 2.7.0

张松源 — Tue, 13 Nov 2018 09:38:18 GMT

I download android_O8.0.0_1.0.0_tools in NXP, to update fw to my imx6sl evk board.

if I using mfgtool 2.2.3, it can identify hid device.

but using mfgtool 2.7.0 can't identify hid device, before hid device show in windows device manager, the mfgtool 2.7.0 dialog will crash, here is the log:

DLL version: 2.7.0
Tuesday, November 13, 2018 17:24:46 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]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_093A&PID_2510#5&376aba2d&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_093A&PID_2510#5&376aba2d&0&6#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_0D8C&PID_013C#5&376aba2d&0&11#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_0D8C&PID_013C#5&376aba2d&0&11#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0063#5&376aba2d&0&7#{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_0063#5&376aba2d&0&7#{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_1a2c&pid_4094&mi_00#7&25dd3299&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_1a2c&pid_4094&mi_01&col01#7&205f4d7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 2
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_1a2c&pid_4094&mi_01&col02#7&205f4d7&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 3
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath:
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_1a2c&pid_4094&mi_00#7&25dd3299&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_1a2c&pid_4094&mi_01&col01#7&205f4d7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 2
ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&pid_0063#6&16c6aef1&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
ModuleID[2] LevelID[10]: new MxHidDevice[03E8CE98]

attach is the screencap when I using mfgtool.

Re: the problem when using mfgtool 2.7.0

jimmychan — Thu, 15 Nov 2018 06:34:08 GMT

Have you try this on other computer?

Re: the problem when using mfgtool 2.7.0

张松源 — Thu, 15 Nov 2018 07:09:26 GMT

hi I have try win10 and win7 system, it still can't work. problem is my win10 computer can use mfgtool 2.2.3.

Re: the problem when using mfgtool 2.7.0

jimmychan — Fri, 16 Nov 2018 02:28:50 GMT

We don't meet this problem on our side.

could you try to remove the driver and then re-install it?

maybe also try the different usb port on your computer.

Re: the problem when using mfgtool 2.7.0

m919040_cheng — Fri, 28 Jun 2019 05:20:26 GMT

All,

I meet the same problem on sabresd board and our customized board based on 2.7.0 MFG GUI.

Does anyone has been solved the problem?

Eric

Re: the problem when using mfgtool 2.7.0

张松源 — Fri, 28 Jun 2019 09:23:42 GMT

hello Eric

你是中国人吧，那我就用中文回复了，我用xp系统的电脑就能够烧录了。这个问题应该要官方重新编译适合各个系统的可执行文件才能最终解决，你可以试试xp系统的电脑。

Re: the problem when using mfgtool 2.7.0

Danube — Mon, 08 Jul 2019 10:03:33 GMT

Hi Eric,

Please add USB 2.0 Hub...

It can fixed this issue.

If you want to Trace MFGtool Source code , you can see this link

GitHub - NXPmicro/mfgtools at windows

Re: the problem when using mfgtool 2.7.0

Danube — Mon, 08 Jul 2019 10:06:31 GMT

Hi Jimmy,

We had test many NB like X280 and ASUS Gaming NB.

More New NB is USB 3.0 function.

I add USB HUB and connect to i.MX6Q SabreSD , MFGTool Can find i.MX6Q EVK.

Just let you know I use this way to fixed this issue.

topic Re: the problem when using mfgtool 2.7.0 in i.MX Processors

the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0

Re: the problem when using mfgtool 2.7.0