Hello Team,
We purchased the i.MX95 V1.3A boards in October 2025, and they have been functioning correctly across multiple assignments and use cases since then.
However, starting yesterday, we have encountered an issue with one of the boards. The board is currently not booting with any of the images we flash. Specifically:
We have already performed initial troubleshooting steps, including testing with different assignments and configurations, but the issue remains unresolved.
For your reference, we have attached the purchase invoice.
We request your support in diagnosing and resolving this issue at the earliest. Please let us know if any additional logs, debug steps, or hardware checks are required from our side.
Thank you for your assistance.
Below are steps we tried:
admin:~/mfgtools/build$ sudo uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.243-5-g124d086
Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion Serial_no
====================================================================
3:3 MX95 SDPS: 0x1FC9 0x015D 0x0001 DA76A714E8984460
admin:~/imx-build/bld-xwayland/tmp/deploy/images/imx95-19x19-verdin$ sudo uuu -b spl imx-boot
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.243-5-g124d086
Success 1 Failure 0
3:3-DA76A714 4/ 4 [Done ] SDPV: done
So we kindly request you to help on this as we are working on some critical delivery.
Thank you for the quick response. Our setup is actually based on the i.MX95 Verdin 19x19 module, version 1.3A.
After emmc failed we thought of trying the tezi image to recover the board. For additional information, we also tried flashing the TEZI images with versions 7.7, 7.4, 7.5, and 7.6 from the below link: https://developer.toradex.com/easy-installer/toradex-easy-installer/download-tezi/#version-7 .
We downloaded the tar files under the Verdin iMX95 section and attempted the flashing process. However, in all cases, we ended up facing the following issue: HID(W): LIBUSB_ERROR_NO_DEVICE (-4).
Iam attaching the Screenshots of the result below.
Hi @Harsha13,
Thank you for contacting NXP Support!
Could you please confirm the following details so we can better assist you?
Which exact commands are you using during the flashing process?
Which BSP version are you trying to flash?
After flashing, did you change the boot switches to boot from the programmed device?
Which silicon revision are you using: A1 or B0?
Please note that A1 silicon revisions are not compatible with the latest BSP versions, while B0 silicon is required for these releases.
Once we have this information, we will be able to guide you more accurately.
Best regards,
Chavira
Hi,
Thank you for the quick response.
Currently, the board appears to be bricked due to some development activity, and we are trying to recover it. As of now, we are only able to access the eMMC flashing mode.
Could you please suggest:
We are also in parallel contact with Toradex regarding this issue. From your side, if you have any suggestions, recovery procedures, or debugging methods, it would be very helpful for us in resolving this issue.
Looking forward to your guidance and support.
Hi @Harsha13,
A similar behavior can be observed on EVK boards when attempting to flash the latest BSP versions on older silicon revisions.
At this point, I am not certain what might be causing the issue on your board. Since the software you are using is not provided by NXP, I recommend reaching out to Toradex support for more detailed assistance specific to your platform.
They should be able to provide guidance tailored to your board configuration and software stack.
Best regards,
Chavira
Hi @Harsha13,
Please contact Toradex support for further assistance with this issue, as they will be able to provide more detailed support specific to your platform.
Best regards,
Chavira