I have two imx8qxp dev boards.
Board 1 is labeled SCH-29683 Rev D5 / 700-39683 Rev C2
Board 2 is labeled SCH-29683 Rev C2 / 700-29683 Rev C2
I am attempting to image the boards with the Android image I downloaded from NXP:
md5sum ~/Downloads/android-10.0.0_2.6.0_image_8qmek.tar.gz
f5083fd8c356c79edc13dbe4243d9237 /home/eric/Downloads/android-10.0.0_2.6.0_image_8qmek.tar.gz
I am using Ubuntu 22.04 and have downloaded versions of UUU that match the 'validated' line in the update scripts as well as the latest version of uuu with the same results.
For Board 1:
$ sudo ./uuu_imx_android_flash.sh -f imx8qxp
This script is validated with uuu 1.3.124 version, it is recommended to align with this version.
dtbo is supported
dual slot is supported
dynamic parttition is supported
generate lines to flash u-boot-imx8qxp.imx to the partition of bootloader0
generate lines to flash partition-table.img to the partition of gpt
generate lines to flash dtbo-imx8qxp.img to the partition of dtbo_a
generate lines to flash boot.img to the partition of boot_a
generate lines to flash vbmeta-imx8qxp.img to the partition of vbmeta_a
generate lines to flash dtbo-imx8qxp.img to the partition of dtbo_b
generate lines to flash boot.img to the partition of boot_b
generate lines to flash vbmeta-imx8qxp.img to the partition of vbmeta_b
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition system_a will resize from 0 bytes to 921604096 bytes
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition system_b will resize from 0 bytes to 921604096 bytes
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition vendor_a will resize from 0 bytes to 536858624 bytes
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition vendor_b will resize from 0 bytes to 536858624 bytes
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition product_a will resize from 0 bytes to 335147008 bytes
lpmake I 03-29 16:40:28 7315 7315 builder.cpp:937] [liblp]Partition product_b will resize from 0 bytes to 335147008 bytes
generate lines to flash super.img to the partition of super
uuu script generated, start to invoke uuu with the generated uuu script
uuu (Universal Update Utility) for nxp imx chips -- lib1.3.124-0-gee3f09a
Success 0 Failure 1
3:13 1/ 1 [HID(W):LIBUSB_ERROR_IO ] SDPS: boot -f u-boot-imx8qxp-mek-uuu.imx
and board 2 reports the same but a slightly different error:
3:13 1/ 1 [HID(W):LIBUSB_ERROR_TIMEOUT ] SDPS: boot -f u-boot-imx8qxp-mek-uuu.imx
Is there a known solution to this issue? I've looked at some similar looking issues on the forum but they all seem to be regarding making a custom image while I'm just trying to use a stock image.
Thanks in advance.
已解决! 转到解答。
Hello,
Researching a little bit more I found that it is necessary to use other command to flash C0 board revisions that you have. Please follow this steps:
1. Download the image.
2. Decompress the image.
3. On console go to the decompressed directory path.
4. Put your board on serial download mode and turn it on.
5. Run this command: sudo ./uuu_imx_android_flash.sh -f imx8qxp -e -u c0
6. Wait until finish.
7. Turn off the board and change boot configuration to boot from eMMC.
8. Turn on the board and you should be able to boot android on your board.
I hope this helps.
Best regards.
This results in the same output:
sudo ./uuu_imx_android_flash.sh -f imx8qxp -e
This script is validated with uuu 1.3.124 version, it is recommended to align with this version.
dtbo is supported
dual slot is supported
dynamic parttition is supported
generate lines to flash u-boot-imx8qxp.imx to the partition of bootloader0
generate lines to flash partition-table.img to the partition of gpt
generate lines to flash dtbo-imx8qxp.img to the partition of dtbo_a
generate lines to flash boot.img to the partition of boot_a
generate lines to flash vbmeta-imx8qxp.img to the partition of vbmeta_a
generate lines to flash dtbo-imx8qxp.img to the partition of dtbo_b
generate lines to flash boot.img to the partition of boot_b
generate lines to flash vbmeta-imx8qxp.img to the partition of vbmeta_b
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition system_a will resize from 0 bytes to 921604096 bytes
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition system_b will resize from 0 bytes to 921604096 bytes
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition vendor_a will resize from 0 bytes to 536858624 bytes
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition vendor_b will resize from 0 bytes to 536858624 bytes
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition product_a will resize from 0 bytes to 335147008 bytes
lpmake I 04-06 14:02:38 267203 267203 builder.cpp:937] [liblp]Partition product_b will resize from 0 bytes to 335147008 bytes
generate lines to flash super.img to the partition of super
uuu script generated, start to invoke uuu with the generated uuu script
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.21-0-g1f42172
Success 0 Failure 1
3:123112 1/ 1 [HID(W):LIBUSB_ERROR_IO ] SDPS: boot -f u-boot-imx8
Hello,
Could you please share me a detailed step list that you are following to flash your board? (Including boot switch configuration)
Is your board getting detected as serial download mode?
Did you try flashing the board on Windows?
Are you using a USB hub?
Best regards.
power cycle board.
dip switches:
4 3 2 1
0 0 0 1
Plug directly into Dell 7760 laptop
Check dmesg:
[384800.043105] usb 3-9: New USB device found, idVendor=1fc9, idProduct=012f, bcdDevice= 0.04
[384800.043116] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[384800.043119] usb 3-9: Product: SE Blank 8QXP
[384800.043122] usb 3-9: Manufacturer: NXP SemiConductor Inc
[384800.047022] hid-generic 0003:1FC9:012F.0241: hiddev4,hidraw10: USB HID v1.10 Device [NXP SemiConductor Inc SE Blank 8QXP ] on usb-0000:00:14.0-9/input0
[384800.107639] usb 3-9: USB disconnect, device number 49
[384800.457841] usb 3-9: new high-speed USB device number 50 using xhci_hcd
[384800.607063] usb 3-9: New USB device found, idVendor=1fc9, idProduct=012f, bcdDevice= 0.04
[384800.607073] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[384800.607077] usb 3-9: Product: SE Blank 8QXP
[384800.607080] usb 3-9: Manufacturer: NXP SemiConductor Inc
[384800.610944] hid-generic 0003:1FC9:012F.0242: hiddev4,hidraw10: USB HID v1.10 Device [NXP SemiConductor Inc SE Blank 8QXP ] on usb-0000:00:14.0-9/input0
No Hub. No Windows machine available.
Hello,
Got it, thank you for the information.
The error: HID(W):LIBUSB_ERROR_IO is causes because the board is not getting detected in serial download mode.
Could you please share me what do you get if use the command?
sudo uuu -lsusb
Also, could please share me a photo of your switch boot configuration?
Best regards.
▪ sudo uuu -lsusb
[sudo] password for eric:
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.21-0-g1f42172
Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
3:9 MX8QXP SDPS: 0x1FC9 0x012F 0x0004
Hello,
Researching a little bit more I found that it is necessary to use other command to flash C0 board revisions that you have. Please follow this steps:
1. Download the image.
2. Decompress the image.
3. On console go to the decompressed directory path.
4. Put your board on serial download mode and turn it on.
5. Run this command: sudo ./uuu_imx_android_flash.sh -f imx8qxp -e -u c0
6. Wait until finish.
7. Turn off the board and change boot configuration to boot from eMMC.
8. Turn on the board and you should be able to boot android on your board.
I hope this helps.
Best regards.
Thanks for your help Jorge. I was able to get one of the devices to load the image and boot.
The second one has degraded since the start of this thread and is no longer recognized by the host.