IMX6使用MFG无法烧写系统问题求助

Work-Tang

各位好，小弟新手，求教各位大大一些问题：
最近在使用自己制作的板子，想烧写Android系统到eMMC里面，但是始终无法下载成功，MFG卡在Loading U-Boot（就是在jumping to OS image之后那一步），串口无打印消息。下面小弟将cfg.ini文件配置及MfgTool.log内容粘贴如下：
cfg.ini文件：
[profiles]
chip = MX6Q Linux Update

[platform]
board = SabreSD

[LIST]
name = Android-SabreSD-eMMC



MfgTool.log内容如下：
DLL version: 2.2.2
Monday, October 24, 2016 11:06:23   Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[00921348]
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is F:\IMX6ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is F:\IMX6ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is F:\IMX6ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]
ModuleID[2] LevelID[10]: *********MxHidDevice[00921348] Jump to Ramkernel successfully!**********
ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&ID_0054#6&3b313210&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&ID_0054#6&3b313210&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&ID_0054\6&3B313210&0&2, _deviceInstanceID: USB\VID_15A2&ID_0054\6&3B313210&0&2
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:3-Port:2
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT, Notify
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Remove
ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceRemoveEvent.
ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device remove1
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set
ModuleID[2] LevelID[10]: delete MxHidDevice[00921348]
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&ID_0054#6&3b313210&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&ID_0054#6&3b313210&0&2#{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_09da&pid_c10a&col01#7&4aae317&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_09da&pid_c10a&col02#7&4aae317&0&0001#{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_0054#7&268b6789&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
ModuleID[2] LevelID[10]: new MxHidDevice[0092EE18]
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&ID_0054\6&3B313210&0&2, _deviceInstanceID: USB\VID_15A2&ID_0054\6&3B313210&0&2
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 2
ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&ID_0054#6&3B313210&0&2#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:3-Port:2
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive
ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.
ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is F:\IMX6ModuleID[2] LevelID[1]: MxHidDevice::Read() Error reading from device 0x48f.
ModuleID[2] LevelID[1]: Failed to read HAB type from ROM!!!
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)
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]: delete MxHidDevice[0092EE18]
ModuleID[2] LevelID[10]: Device Manager thread is closed

请高手指教啊。

我知道答案 目前已有14人回答

阅读全文

Work-Tang

上面有的地儿不造咋变成表情了。。。。给位大大直接忽视啊，重点的错误在后面

技术范儿

Work-Tang 发表于 2016-10-24 20:17
上面有的地儿不造咋变成表情了。。。。给位大大直接忽视啊，重点的错误在后面 ...

帖LOG用代码的方式贴

技术范儿

Work-Tang 发表于 2016-10-24 20:17
上面有的地儿不造咋变成表情了。。。。给位大大直接忽视啊，重点的错误在后面 ...

帖LOG用代码的方式贴

Work-Tang

LOG里面显示出错的应该是最后几行，这是咋回事啊。。

技术范儿

Work-Tang 发表于 2016-10-25 10:27
LOG里面显示出错的应该是最后几行，这是咋回事啊。。

描述清楚，谁家的板子那个软件版本

zhuzisxdx

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0

devices 需要工作在status “1”，看样子是没有用对应android版本的MFGtool。

Work-Tang

参考的是TQIMX6Q_COREC_V2板子，烧写的内核是Linux-3.0.35，烧写软件是Mfgtools-Rel-13.01.00_ER_MX6Q_UPDATER。应该不是软件问题，因为之前有一块一模一样的板子（也是自己做的），烧写成功了，这块应该是硬件原因，但是就是不知道硬件上哪个地方出错会导致这种问题。

技术范儿

Work-Tang 发表于 2016-10-25 15:09
参考的是TQIMX6Q_COREC_V2板子，烧写的内核是Linux-3.0.35，烧写软件是Mfgtools-Rel-13.01.00_ER_MX6Q_UPDA ...

检查一下USB端口软件是否识别了，然后就是用DDR测试工具跑下DDR有没有问题，最后检查下eMMC

小智MM

楼主你好，请问你这里自己设计的板子使用的DDR是和我们的开发板一样么？还是换了DDR？还有你这里使用的是哪个版本的BSP呢？