AnsweredAssumed Answered

imx6s custom board flashing failed

Question asked by Souleymane Conte on Jun 29, 2018
Latest reply on Jun 29, 2018 by igorpadykov

Hi,

I'm trying to flash my imx6s custom board using Mfgtools-TX6-2018-01 but i get the following error:

"Boot" body="Recovery" error, file="C:\Users\f.pasquier\Desktop\Mfgtools-TX6-2018-01\Profiles\TX6\OS Firmware\files\u-boot\mfg\u-boot-tx6s-8035_mfg.bin"

 

The entire Mfgtool.log file is shown below:

DLL version: 2.7.0

Friday, June 29, 2018 16:45:16   Start new logging

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

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[036D9CB0]

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[005D8A78]

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[005D8EB0]

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[10]: new MxHidDevice[03733B80]

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 4

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:2

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 03709C88

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 7

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 4

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:4

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:4, Volume->_diskNumber:4

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 03732FA0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 7

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 4

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:4, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 038B0478

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 7

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 4

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:3

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:4, Volume->_diskNumber:3

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:3

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:3, Volume->_diskNumber:3

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 038D0B38

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 7

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]: CmdOperation[0] device chagned and reset to state 0

ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is C:\Users\f.pasquier\Desktop\Mfgtools-TX6-2018-01\Mfgtools-TX6-2018-01\Profiles\TX6\OS Firmware\files\u-boot\mfg\u-boot-tx6s-8035_mfg.bin

ModuleID[2] LevelID[1]: MxHidDevice::Write() Error writing to device 0x1f.

ModuleID[2] LevelID[1]: Failed to initialize memory!

ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed

ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)

 

It seems that the mfgtool detect many hid devices and cannot choose which device is the good one

Do you have any suggestions?

 

Best regards,

Vladzouth

Outcomes