imx8qxp-mek uuu fail

[475143463]

hi sir,

After I got bootloader(2018.03-r0) and kernel(4.14.98-r0) from yocto,I also successfully compiled the BootLoader using imx8qxp_mek_defconfig and generated u-boot.bin.

Next, I use the cmd-command line on win10 to execute “uuu.exe SDPS: boot-f u-boot.bin”. But it was a failure.

The error message is as follows:

uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.3.102-0-gb078bd0

Success 0    Failure 1

1:513    1/ 1 [HID(W):LIBUSB_ERROR_IO                ] SDPS: boot -f u-boot.bin

Error: HID(W):LIBUSB_ERROR_IO

Now, I have no idea to solve it, can you give some advice？

[joanxie]

did you change anything in uboot? if no, you can try to use demo uboot image to replace your own uboot.bin, you can use like "imx-boot-imx8qxpmek-sd.bin-flash" to replace your own uboot.bin

[475143463]

Thank you Mr Xie.

This way has been tested, it can be.

But in the future,I need change BootLoader to match my hardware.

Now, I can compile it with default-config file named imx8qxp_mek_defconfig.
But after compiled,it can not be burn into development board and uuu show this issue.

so,I have no idea to check this issue.

Can you give me some suggests?

[joanxie]

try to build uboot with the commands like below:

"bitbake -c clean u-boot-imx

bitbake -c compile -f u-boot-imx

bitbake -f u-boot-imx“

[475143463 · Accepted solution]

Thank you Mr Xie,

I am so sorry about this issue.

I forgot to use imx-mkimage tool to add some bins(spl,cswf,..etc) into flash.bin. so it can't bootup.

Now it is ok.

But, I can't start M4.bin during bootloader startup.

can you give me some suggests or guidance document  to achieve it?

[SerdarKantarci]

Hello,

I have the same problem.

I could boot an android image on the eMMC but not a pre-built linux image.

How exactly did you use the imx-mkimage tool?

[joanxie]

you need to download specific m4 bin file to board by UUU tools.

[475143463]

Thank you Mr Xie,

But，what is specific m4 bin file ？

And, how can I get it.

Now,I got bootloader(2018.03) and kernel(4.14.98) through yocto with default config(UBOOT_CONFIG = "sd").

After I compiled bootloader,I build flash.bin through imx-mkimage using flash_spl.

flash.bin is ok.And it can be burn into imx8qxpmek and run.

But I build flash.bin with flash_linux_m4,bin file is not good running.

and the err log is as follow:

U-Boot SPL 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df (Dec 15 2019 - 04:58:35 +0000)
Normal Boot
Trying to boot from USB SDP
1 setufp mode 0
1 cdns3_uboot_initmode 0
SDP: initialize...
SDP: handle requests...
Downloading file of size 1009664 to 0x80400000... done
Jumping to header at 0x80400000
Header Tag is not an IMX image
Found header at 0x80400000
U

U-Boot 2018.03 (Dec 25 2019 - 10:17:44 +0800)

CPU: Freescale i.MX8QXP revB A35 at 1200 MHz at 18C
Model: Freescale i.MX8QXP MEK
Board: iMX8QXP MEK
Boot: USB
DRAM: 2.8 GiB
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
imx_vservice_connect: Timeout to connect peer, -110
VService: Connection is failed, ret -110
virt_i2c: Faild to setup vservice
setup_typec lookup gpio@1a_7 failed ret = -19
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... MMC: no card present
*** Warning - No block device, using default environment

Failed (-5)
[pcie_ctrlb_sata_phy_init_rc] LNK DOWN 8600000
In: serial
Out: serial
Err: serial

BuildInfo:
- SCFW f83a2bed, SECO-FW 92ef1143, IMX-MKIMAGE dd023400, ATF 1cb68fa
- U-Boot 2018.03

MMC: no card present
Detect USB boot. Will enter fastboot mode!
Net:
Warning: ethernet@5b040000 using MAC address from ROM
eth0: ethernet@5b040000 [PRIME]
Warning: ethernet@5b050000 (eth1) using random MAC address - c2:c6:3a:cc:7a:c5
, eth1: ethernet@5b050000
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot: 0

## Checking Image at 83100000 ...
Legacy image found
Image Name: fsl-image-mfgtool-initramfs-imx8
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 10798591 Bytes = 10.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Run fastboot ...
dev_get_parent_platdata: null device
"Synchronous Abort" handler, esr 0x96000007
elr: 0000000080045720 lr : 0000000080052358 (reloc)
elr: 0000000087e9b720 lr : 0000000087ea8358
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 000000000000000a x3 : 000000005a060014
x4 : 00000000ffffffff x5 : 0000000000000000
x6 : 0000000000000000 x7 : 0000000000000003
x8 : 0000000000001fc0 x9 : 0000000000000008
x10: 00000000ffffffd0 x11: 0000000085668208
x12: 0000000000001fbe x13: 0000000000000011
x14: 0000000000000001 x15: 0000000000000008
x16: 0000000000002080 x17: 0000000000000000
x18: 0000000085673da8 x19: 0000000000000000
x20: 0000000000000001 x21: 0000000085667dcf
x22: 0000000000000000 x23: 000000000000001d
x24: 0000000000000002 x25: 0000000000000001
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000856b9150 x29: 0000000085667d00

Resetting CPU ...

resetting ...

can you give me some suggests or guidance document  to achieve it?