I got a module from Kontron based on iMX8QM.
Here is what U-boot shows :
U-Boot 2019.04-4.19.35-1.1.0+g4d37753 (Jun 02 2022 - 21:24:12 +0000)
CPU: NXP i.MX8QM RevB A53 at 1200 MHz at 33C
BuildInfo:
- SCFW 4e91f37b, SECO-FW d7523fe8, IMX-MKIMAGE 1c2277b9, ATF 70fa7bc
- U-Boot 2019.04-4.19.35-1.1.0+g4d37753
I'm trying to burn in / update Linux image - or actually at the moment any image, U-boot or /and Linux - using the UUU utility, with no success.
I can set to board/COM into the manufacturing mode per board doc, where supposedly it should be ready to use for UUU.
This is what the dev shows up as when I plug it into Win10 PC when the module is in "recovery" or manufacturing mode:
uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51
Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:83114 MX8QM SDPS: 0x1FC9 0x0129 0x0002
And from here I cannot get anywhere ... E.g:
>uuu -b emmc kontron-image-qt5-validation-samx-kontron-samx8-qm.sdcard.bz2/*
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51
Success 0 Failure 1
1:83114 1/ 1 [HID(W):LIBUSB_ERROR_PIPE ] SDPS: boot -f kontron-image-qt5-validation-samx-kontron-samx8-qm.
uuu -b emmc imx-boot-kontron-samx8-qm-fspi-8GB.bin
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.243-0-ged48c51
Success 0 Failure 1
1:83114 1/ 1 [HID(W):LIBUSB_ERROR_PIPE ] SDPS: boot -f imx-boot-kontron-samx8-qm-fspi-8GB.bin
There is just a delay, then device resets and back into the default internally programmed u-boot shell.
Always ends up in that.
There is very little helpful messages from uuu. Is the device correct, why does it always end into libusb error ... ?
Please assist with the following issue I'm having.
Firstly, I can flash flash_scfw.bin - that is, my own built image of the scfw from the official sources, it is flashed and started Ok as I can very by seing SCFW traces on a UART (built with debug enabled).
But anything seems large in size - like image with U-boot - FAILS to be uploaded & started, at least per the UUU traces.
In my test I try to upload the "flash" image (without linux) with U-boot as was created by Yocto imx8qm (my soc) build. In this case I get same error trace from UUU as I have originally posted, and the board re-starts:
So why ... ? Is this a USB transfer problem or ..?
I'm attaching the firmware blob - this was generated by Yocto , under ... imx-boot/0.2-r0/git/iMX8QM/, file flash.bin
