i.MX6DP MfgTool Stuck at Loading uboot

[disheng]

Hello,

We have designed a new custom board with i.MX6DP and done the DDR calibration and updated the cfg file in the uboot and made a new android build, our android version is android_L5.0.0_1.0.0, thus generated the new u-boot-imx6q-h5.imx and boot-imx6q-h5.img and replaced them in the mfgtool foders accordingly, but when try to flash the image to the target, we are stuck at Loading U-boot.

The log is here:

DLL version: 2.6.2
Tuesday, March 30, 2021 16:50:07 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[008E46D0]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[008F17C0]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[008D9DF0]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[04CD7218]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[04CD4E18]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[04CD51D8]
ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1
ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:2
ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 04D35758
ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 4
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\pereira\Documents\New PF300 & Citrex\MfgTool\Profiles\linux\OS Firmware\firmware\u-boot-imx6q-h5.imx
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is C:\Users\pereira\Documents\New PF300 & Citrex\MfgTool\Profiles\linux\OS Firmware\firmware\uImage, address is 0x10008000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is C:\Users\pereira\Documents\New PF300 & Citrex\MfgTool\Profiles\linux\OS Firmware\firmware\fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot, 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:\Users\pereira\Documents\New PF300 & Citrex\MfgTool\Profiles\linux\OS Firmware\firmware\imx6q-h5.dtb, address is 0x10C00000
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[04CD51D8] 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]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is C:\Users\pereira\Documents\New PF300 & Citrex\MfgTool\Profiles\linux\OS Firmware\firmware\u-boot-imx6q-h5.imx

[igorpadykov · Accepted solution]

Hi Di

in addition to described changes in image, it is also necessary to update

Mfg Tool firmware files (files in ../firmware folder, fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot)

with updated uboot cfg file.
For rebuilding please use sect.6.2 Manufacturing Tool, MFGTool Yocto Guide from

Documentation

Best regards
igor

[disheng]

Hello Igor,

Thanks for the hint. 

We have the Android 5.0 BSP build environment, is it possible to get the fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot rebuilt under that environment, or the rebuild must happen under Yocto project build environment? 

Regards,

Di

[igorpadykov]

Hi Di

unfortunately fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot is not part of android build.

It is built separately as described in Yocto Guide, please use appropriate linux version, for

Android 5.0 seems it is L3.10.53 GA.

Best regards
igor

[disheng]

Hi Igor,

From the answer of this post:

https://community.nxp.com/t5/i-MX-Processors/imx6q-%E5%9F%BA%E4%BA%8E%E5%AE%89%E5%8D%93%E7%B3%BB%E7%...

It seems that the  fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot does not need to be rebuilt, and it is possible to build the rest of the firmware files under Android build environment, could you confirm this?

I have check some other questions regarding this topic and it seems many people are looking for ways to generate necessary and correct firmware files under Android environment but unfortunately there is no official consolidated knowledge sharing about this(or maybe just I have not found it yet). This is not a complain but it would be really helpful for android/linux newbies like myself.

Thanks,

Di

[igorpadykov]

>It seems that the fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot does not need to be rebuilt, and >it is possible to build the rest of the firmware files under Android build environment, could you confirm

>this?

not sorry. For different board (memory) than NXP EVK reference board it should be rebuilt.

However in some cases when custom board uses the same memory as EVK it can use default firmware files.

Best regards
igor