Hi,
We are using the SMARC IMX95 SOM, currently we have upgraded the iMX95 SOC alone with our rework. After this the board is perfectly reset out and we have the usb uart console and the board is successfully into the recovery mode also, but there is no output in the console for the normal boot as well as in loading the toradex easy installer. What will be the issue, from our side Hardware side it is fine.. What we can debug this from the SW side and how to resolve this?
Original SoC marking:
P1MX9596 AVZXNAB
Replacement SoC marking:
MIMX9596 XVZXNAC
UUU detects MX95 ROM (0x1fc9:0x015d),
but fails during SDPS boot of imx-boot-recoverytezi with LIBUSB_ERROR_NO_DEVICE.
Is XVZXNAC a newer silicon revision requiring a different TEZI/U-Boot/OEI image than the AB revision used on the original module?
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Hello,
I understand you’re experiencing boot issues with your SMARC iMX95 after replacing the SoC from PIMX9596AVZXNAB to MIMX9596XVZXNAC. This is indeed related to silicon revision differences.
Silicon Revision Issue
You’ve correctly identified the core issue - the silicon revision change from A1 (AB marking) to B0 (AC marking) requires different firmware. The SMARC iMX95 documentation confirms this transition(1).
According to the revision history, there was a specific update to address this silicon change:
- V1.0A used the A1 silicon (PIMX9596AVZXNAB)
- V1.1A uses the B0 silicon (PIMX9596XVZXNAC)(1)
The documentation specifically mentions: “SoC part number changed to NXP PIMX9596XVZXNAC (B0 silicon)”(1) and references an “i.MX95 A1 to B0 Silicon Revision Update Guide”(1).
Recovery Mode and UUU Issues
The LIBUSB_ERROR_NO_DEVICE error during SDPS boot is consistent with using incompatible firmware for the B0 silicon revision. The ROM detection works (0x1fc9:0x015d), but the imx-boot-recoverytezi image is likely built for A1 silicon.
Resolution Steps
-
Update to Compatible TEZI Version: You need a TEZI image built specifically for the B0 silicon revision (V1.1A hardware)
-
Serial Console Setup: For debugging, ensure your serial console is properly configured. The SMARC Development Board uses a USB-C connector for debug access(2). The serial parameters are:
- Baud Rate: 115200
- Parity: none
- Bits: 8
- Stop bits: 1
- Flow control: none(2)
-
Recovery Mode Verification: Since UUU detects the ROM correctly, your recovery mode setup is working. The issue is the firmware compatibility.
Next Steps
You’ll need to obtain a TEZI image compatible with the B0 silicon revision. The hardware changes between V1.0A and V1.1A include fixes for “ETH reference oscillator supply voltage issue enabling SGMII/USXGMII/XFI” and other improvements specific to the B0 silicon(1).
The fact that you have no console output during normal boot confirms the firmware incompatibility - the U-Boot and kernel images need to match the silicon revision.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
es, your suspicion is correct. The MIMX9596 XVZXNAC is the newer B0 silicon revision, and it requires a different software image than the A1 revision you started with.
The core of the issue is that the bootloader and other low-level firmware for the i.MX95 are not compatible between the A1 and B0 silicon revisions. The ROM-detection stage works, but the first software upload (SDPS) fails because it was built for the older chip. The A1 version is supported up to Toradex’s Yocto BSP release 7.3.0, while the B0 version requires release 7.6.0 or newer.
Hi Alex,
We are using the latest BSP only 7.7.0. We are using the SD card boot with this image, but nothing from the UART console. After that only we tried the EMMC flashing, for this we are facing this error LIBUSB_ERROR_NO_DEVICE. We are stucked in this. Could please help us to resolve this?
Please note that we do not support booting from an SD card. You may use it if you wish, but should you encounter any issues, you will need to resolve them on your own. We recommend using TEZI for module flashing. Please load TEZI v7.6.0 or higher and use it for flashing.
Sorry, I did not understand how the provided screenshot relates to the “LIBUSB_ERROR_NO_DEVICE” error. Please check the recovery-linux.README file included in the TEZI package and follow the instructions provided there.
Please do not post screenshots anymore if the information displayed can be collected as text. Instead, share the text as an attached .txt file.
