MFGTool hangs on "Loading U-Boot"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MFGTool hangs on "Loading U-Boot"

1,106 Views
coline_couturas
Contributor I

Hi,

I am working on a i.MX6UL. My board is a roadlinkv2.

I am currently trying to flash the image on my board using mfgtool, but it hangs on "Loading U-Boot", while I am using the original files (precompiled mfgtool binaries in the img/ directory).

My problem seem to be close to this one : MfgTool Hang Issue , but the answer there is to rebuild some files (which I haven't succeeded in doing btw), and I don't get why this needs to be done as the files I have seem to specifically correspond to my board.

My question is do I have to keep trying rebuilding these files or is there another explanation more specific to my problem ?

Here is my "MfgToolLibLog.txt" file's content :

Start new logging
ModuleID[2] LevelID[10]: address from XML 0x80800000

ModuleID[2] LevelID[10]: address from XML 0x83800000

ModuleID[2] LevelID[10]: address from XML 0x83000000

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[10]: Add USB device

ModuleID[2] LevelID[10]: Create Device 0x7f1330003d90

ModuleID[2] LevelID[10]: new MxHidDevice[0x7f1330003d90]
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is ./Profiles/roadlinkv2/OS Firmware/firmware/u-boot-mfgtool.imx
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/roadlinkv2/OS Firmware/firmware/zImage_mfgtool, address is 0x80800000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/roadlinkv2/OS Firmware/firmware/fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot, address is 0x83800000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/roadlinkv2/OS Firmware/firmware/zImage-mfgtool-imx6ul-v2x.dtb, address is 0x83000000
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[0x7f1330003d90] Jump to Ramkernel successfully!**********
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is ./Profiles/roadlinkv2/OS Firmware/firmware/u-boot-mfgtool.imx
ModuleID[2] LevelID[1]: RunPlugIn(): TransData(0x877FF400, 0x58C00,0x34002640) failed.
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed

BR,

Coline

Labels (1)
0 Kudos
1 Reply

879 Views
igorpadykov
NXP Employee
NXP Employee

Hi Coline

>My question is do I have to keep trying rebuilding these files or is there another

>explanation more specific to my problem ?

yes for other board mfg tools firmware should be rebuild, as default files were built

for i.MX6UL EVK board. Note mfg tool is small linux image running on board.

So changes for board ddr configuration and other differencies compared with EVK should be

introduced with rebuilding mfg tools firmware. Rebuilding steps are described in Yocto Guide

in linux documentation found on i.MX Software | NXP 

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

0 Kudos