uuu with imx8qxp not issuing FB commands

[gerard_salvatel]

Using an i.MX8X SoC and trying to boot and flash an image with uuu tool. After issuing command in USB boot mode:

# uuu -V -b emmc imx-boot.bin

I get the following output:

Wait for Known USB Device Appear...
New USB Device Attached at 3:24342
3:24342>Start Cmd:SDPS: boot -f imx-boot.bin
100%3:24342>Okay (0.011s)
libusb: error [udev_hotplug_event] ignoring udev action bind
New USB Device Attached at 3:24342
3:24342>Start Cmd:SDPV: delay 1000
3:24342>Okay (0s)
3:24342>Start Cmd:SDPV: write -f imx-boot.bin -skipspl
100%3:24342>Okay (0.066s)
3:24342>Start Cmd:SDPV: jump
6400%3:24342>Okay (0.001s)

After this, the output halts and the fastboot commands (FB: in lst file) from `-b emmc` option are not executed. On the SoC side I get the following U-Boot output:

U-Boot SPL 2020.04-51f329ecd0 (Nov 25 2020 - 16:16:33 +0000)
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...
Downloading file of size 674816 to 0x80400000... done
Jumping to header at 0x80400000
Header Tag is not an IMX image
Found header at 0x80400000


U-Boot 2020.04-51f329ecd0 (Nov 25 2020 - 16:16:33 +0000) ##v02.02

CPU:   NXP i.MX8QXP RevC A35 at 1200 MHz at 39C

Model: Siemens CXG3
Board: Capricorn Deneb
Boot:  USB
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial

 BuildInfo: 
  - SCFW 56682d58, SECO-FW 4f5b6919, IMX-MKIMAGE 8da5cd23, ATF c949a88
  - U-Boot 2020.04-51f329ecd0 

ERROR: PCA9552 probe failed
I2C LED init failed
Detect USB boot. Will enter fastboot mode!
flash target is MMC:0
Net:   eth1: ethernet@5b050000 [PRIME]
Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for                                mfgtools
, using default environment

Run bootcmd_mfg: run tftp_run_script
Autobooting in 0 seconds, press "<Esc><Esc>" to stop
ethernet@5b050000 Waiting for PHY auto negotiation to complete.... done
Using ethernet@5b050000 device
TFTP from server 192.168.251.2; our IP address is 192.168.251.1
Filename 'u-boot-commands.img'.
Load address: 0x80280000
Loading: *
ARP Retry count exceeded; starting again
U-Boot# 

So U-Boot seems to enter fastboot mode but still doesn't receive the commands from uuu... What am I missing?

[MistX]

I have just the same issue on

Kontron SMARC-sAMX8X
NXP i.MX8QXP RevC A35

U-Boot 2019.04(uboot_samx8x-R13) compiled with Fastboot and UUU support (see config)

MKIMAGE_BRANCH="imx_5.4.3_2.0.0"

SCFW_PK_VERSION="1.4.0"

SECO_VERSION="2.6.1"

ATF_BRANCH="imx_5.4.3_2.0.0"

UUU host - Ubuntu 20.04.2 (5.8.0-63-generic)

in UUU (1.4.139-0-g1a8f760) command "SDPS: boot -f flash.bin" executes successfully, uboot starts and stops on "Run fastboot ...
cdns3_uboot_initmode 0"

0x1fc9:0x012f - disapears, but no new USB device with FB VID:PID ever appears, so every UUU comand with prefix "FB: " just waits forever for apropriate USB device to appear.

So, how to fix this issue???

[MistX]

Are there any documents about enabling FASTBOOT for iMX8QXP?

I have found in uboot sources that loader just power off usb controller during fastboot procedure and sets environment variables for boot Linux initramfs... So may be there sould be a special Fastboot image on mmc flash? May be fsl-image-mfgtool-initramfs? It should boot special driver to set new device with apropriate VID:PID to execute UUU commands with FB: prefix?

[gerard_salvatel]

Thanks for the reply. The imx-boot.bin boot container I'm using is built exactly in this way. It indeed works up to starting U-Boot, so that doesn't seem to be the problem. I do not require any kernel/dtb/rootfs for now. The only thing I want is to boot the image in USB recovery mode through uuu and flash it to emmc. The first part seems to work (i.e. the SDPV commands delay, write and jump are correctly sent). However the FB commands are not sent to U-Boot.

I'm using a Capricorn i.MX8QXP module.

[Rita_Wang]

Frame Buffer is not supported on i.MX 8.

[gerard_salvatel]

Frame Buffer... Do you mean for video display? What does it has to do with the fastboot protocol?

[Rita_Wang]

 All the i.MX 8 boards require Arm Trusted Firmware.

To boot a Linux image on i.MX 8QuadMax, i.MX 8QuadXPlus, i.MX 8DXL, and i.MX 8DualX, four elements are needed:
• Bootloader (imx-boot built by imx-mkimage, which is a tool that combines firmware and U-Boot to create a bootloader for i.MX
8), which includes U-Boot, Arm Trusted Firmware, DCD file, System controller firmware, and the SECO firmware since B0.
• Arm Cortex-M4 image
• Linux kernel image (Image built by linux-imx)
• A device tree file (.dtb) for the board being used
• A root file system (rootfs) for the particular Linux image

[BiyongSUN]

FB here is FastBoot in u-boot for uuu.

customer need to check the BSP version and if it is from NXP official release. 

in u-boot console can use fastboot command if fastboot is enabled. 

you also can use ums command 

or using fastboot in u-boot and on the pc side uuu -s to attach and manual check the FB command in the uuu console on pc.

everything is in the uuu document 

Here is using uuu shell mode "uuu -s "

FB: ucmd pri

FB: ucmd echo check 

[Rita_Wang]

Could you tell us which version BSP and which board are you using?