Image problem for imx95

[OlivierG]

Hi

I created an image for imx95 in full mode.

Once I had the image, to flash the image to an SD card, I ran:

sudo dd if=imx-image-full-imx95-95-19x19-verdin.rootfs.wic of=/dev/sda bs=1M $$ sync

The "root" volume is correct.

But the "boot" volume is incorrect.  Instead of being named "boot," it's named "268 MB volume" and it's empty.

Obviously, this SD card won't boot.

What's the problem?

Is there an existing full imx95 verdin image?

Greetings

Olivier

.

[OlivierG]

Hi

I use a IMX 95 verdin toradex A1 (not a B0)

The current Yocto on gitlab is made for B0

i get a prebuild image for A1 , it works

Olivier

[OlivierG]

finally the boot volume is present

But the image dos not boot , no log on the debug channel, no screen display

i have a Toradex  IMX95 Verdin EVk 

i build the kernel with

MACHINE=imx95-19x19-verdin

is it right ?

Olivier

[Manuel_Salas]

Hello @OlivierG 

I hope you are doing very well.

Could you please share your part number?

Also, Have you tried flashing the image with UUU tool instead with the direct dd command?

In our BSP we support the Machine imx95-19x19-verdin, so it is correct.

Best regards,

Salas.

[OlivierG]

Hi

i launch : sudo uuu -lsusb

i get

uuu (Universal Update Utility) for nxp imx chips -- lib1.5.141

Connected Known USB Devices

Path Chip Pro Vid Pid BcdVersion

==================================================

1:2 MX95 SDPS: 0x1FC9 0x015D 0x0001

i launch

sudo uuu -b sd imx-boot-imx95-19x19-verdin-sd.bin-flash_all

i get

uuu (Universal Update Utility) for nxp imx chips -- lib1.5.141

Success 0 Failure 1


1:2 1/ 1 [HID(W):LIBUSB_ERROR_NO_DEVICE ] SDPS: boot -f imx-boot-imx95-19x19-verdin-sd.bin-flash_all

These commands are launch from a Linux ubuntu 24

Where is the problem ?

Olivier

[Manuel_Salas]

Hello @OlivierG 

Please try with:

$ sudo uuu -b sd_all imx-boot-imx95-19x19-verdin-sd.bin-flash_all <your image.wic>

Best regards,

Salas.

[zhou1211]

Hello, we also encountered a similar issue when using IMX95. We compiled the image using the Android 15.0.0_1.2.0 source code, and initially it could be burned and used normally. However, when the hardware engineer replaced the CPU with a new one, we used the same burning command but encountered errors such as LIBUSB-ERRORD_IO (-1) or LIBUSB-ERRORD_DEVICED (-4),
The burning command is as follows:
sudo ./uuu_imx_android_flash.sh -f imx95 -e -u dual -d mipi-panel
We used Android 15.0.0_2.0.0 source code to compile the image, but when burning it, we received the same error message;
How to correctly burn and write