Can't load u-boot by mfgtoolcli on i.MX6UL

cancel
Showing results for 
Search instead for 
Did you mean: 

Can't load u-boot by mfgtoolcli on i.MX6UL

1,672 Views
kaa
Contributor II

Hello I'm working on custom board based on i.MX6UL cpu, I have working u-boot and kernel - but stuck with MFGTool.

Execution mfgtoolcli

$ sudo ./mfgtoolcli
Your Options:
Ready to flash.
 1      Done! [===========================================>] Starting

MfgToolLibLog.txt

Thu Feb  2 15:27:15 2017
   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[10]: Add USB device
ModuleID[2] LevelID[10]: Create Device 0x7f5144002730
ModuleID[2] LevelID[10]: new MxHidDevice[0x7f5144002730]
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/u-boot.imx
ModuleID[2] LevelID[10]:  Trans Data address is 877ff400
ModuleID[2] LevelID[1]: RunPlugIn(): TransData(0x877FF400, 0x59C00,0x55A95010) failed.
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed

At the same time I have successful loading of my u-boot by imx_usb:

$ imx_usb u-boot.imx
...

15a2:007d(mx6_qsb) bConfigurationValue =1
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
Setting boot_data_ptr to 0
main dcd length 1f0
sub dcd length 1ec

loading binary file(u-boot.imx) to 877ff400, skip=0, fsize=59c00 type=aa

<<<367616, 367616 bytes>>>
succeeded (status 0x88888888)
jumping to 0x877ff400

What is wrong?

Labels (1)
0 Kudos
5 Replies

165 Views
kaa
Contributor II

Solution found!

Please don't add this settings into imximage.cfg, it's cause a lot of problems:

//=============================================================================
// Disable    WDOG    
//=============================================================================
setmem /16    0x020bc000 =    0x30

165 Views
m4l490n
Contributor V

kaa‌ the mfgtoolcli is poorly documented, actually, there is no documentation about how to use it. Instead, you can take a look into https://community.nxp.com/message/863693 that works with imx_usb_loader and utp_com utilities. It's working 100% since that's the method I use almost every day.

If you have questions you can let me know.

0 Kudos

165 Views
kaa
Contributor II

The same behavior is observed in MFGTool2.exe

0 Kudos

165 Views
jimmychan
NXP TechSupport
NXP TechSupport

gary_bisson‌ Would you help this? Thanks.

0 Kudos

165 Views
gary_bisson
Senior Contributor III

Hi jimmychan‌,

I can certainly help with imx_usb_loader which is a Boundary Devices tool, but it is already working.

The question above is about mfgtools which is provided by NXP:

GitHub - NXPmicro/mfgtools: Freescale/NXP I.MX Chip image deploy tools. 

Note that I've had success in the past with mfgtools on Linux with our i.MX6Q platforms but I don't have any i.MX6UL platform to test with.

Regards,

Gary

0 Kudos