IMX6DL MFGTOOL烧录失败

[likangmao]

针对i.MX6的板子，在烧录系统时，提示Jump to OS image后，随即便显示no device connected，不知具体原因是什么，以下为mfgtool的日志，请帮我分析一下，谢谢！

DLL version: 2.6.2
Wednesday, January 23, 2019 16:55:18 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[006C1B88]
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:\likangmao\imx6\L3.14.52_1.1.0_ga-mfg-tools\mfgtools\Profiles\Linux\OS Firmware\firmware\u-boot-imx6dlsabreauto_sd.imx
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is C:\likangmao\imx6\L3.14.52_1.1.0_ga-mfg-tools\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage, address is 0x12000000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is C:\likangmao\imx6\L3.14.52_1.1.0_ga-mfg-tools\mfgtools\Profiles\Linux\OS Firmware\firmware\fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot, address is 0x12C00000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is C:\likangmao\imx6\L3.14.52_1.1.0_ga-mfg-tools\mfgtools\Profiles\Linux\OS Firmware\firmware\zImage-imx6dl-sabreauto.dtb, address is 0x18000000
ModuleID[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[006C1B88] 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::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0061#6&2992a15b&0&3#{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_0061#6&2992a15b&0&3#{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&PID_0061\6&2992A15B&0&3, _deviceInstanceID: USB\VID_15A2&PID_0061\6&2992A15B&0&3
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0061, Hub:4-Port:3
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[006C1B88]
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_0000&PID_0000#6&2992a15b&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_0000&PID_0000#6&2992a15b&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_0000&PID_0000#6&2992a15b&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_0000&PID_0000#6&2992a15b&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
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

[igorpadykov]

Hi

for new board (or processor) recommended first to run ddr test and update Mfg Tool firmware
image with new ddr calibration coefficients found from test
https://community.nxp.com/docs/DOC-105652
Update coefficients in uboot/../mx6sabresd/mx6q_4x_mt41j128.cfg and
rebuild Mfg Tool firmware (files in  ../firmware folder, fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot).
Also refer to p.14 i.MX_6Dual6Quad_SABRE-SD_Linux_User's_Guide.pdf - it shows
which files are used by Mfg Tool.
For rebuilding use sect.6.2 Manufacturing Tool, MFGTool attached Yocto Guide.
Use NXP Linux repository:
https://source.codeaurora.org/external/imx/linux-imx/tree

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

[likangmao]

Hi:

我自己编译了MFGTOOL的媒介镜像u-boot.imx，通过MFGTOOL工具进行烧录，当界面跳转到Jumping to OS image.时，串口是有打印信息的，这里附上串口的打印信息：

U-Boot 2014.10-g26a7912-dirty (Jan 23 2019 - 09:09:32)

CPU: Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
hello world
DRAM: 512 MiB
NAND: 0 MiB
nand_init MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: Phy not found
PHY reset timed out
FEC [PRIME]
Error: FEC address 11:12:13:14:15:16 illegal value

Device nand0 not found!
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Kernel image @ 0x10008000 [ 0x000000 - 0x2ec708 ]
## Flattened Device Tree blob at 12000000
Booting using the fdt blob at 0x12000000
Loading Ramdisk to 2f336000, end 2f511e00 ... OK
Loading Device Tree to 2f329000, end 2f335a4e ... OK

Starting kernel ...

既然内核已启动成功，我认为我的u-boot.imx中DDR test应该是正确的，只是在烧录的过程中，并没有看到“Updater”过程的打印信息，USB就显示断开了，不知道我理解的对不对，谢谢！