The following table contains known issues, scheduled bug fixes, and feature improvements for the SMARC iMX95.
For other information, click on the below links:
Customer Impact: JTAG debugging and Boundary Scan not working.
Description: There is a conflict on the TCK and TDI signals because they are shared with the BT UART signals. JTAG debugging and Boundary Scan only work if the R59 and R60 resistors are removed.
Workaround: This issue will be fixed in SMARC iMX95 V1.2.
Customer Impact: Customers using SMARC iMX95 V1.0 with SMARC Development Board V1.0 or V1.1A will find that connected DisplayPort monitors are not detected.
Description: A design issue in the DisplayPort interface of the SMARC iMX95 V1.0 employs a pull-down resistor that is too low to provide the required signal level, when combined with SMARC Development Board V1.0 or V1.1A. In the SMARC Development Board V1.1B, the pull-up strength has been increased to mitigate the issue. The next SMARC iMX95 V1.1 will comply with the SMARC Standard.
Workaround: Customers could replace the 100k Pull-up resistor - R59 with a 10K resistor in the SMARC Development Carrier board V1.0 and V1.1 to get the interface to work with SMARC iMX95 V1.0.
Customer Impact: The GPIO pins connected to SoM's GPIO expander are missing pull-up resistors.
Description: Some GPIO expander pins on the module lack the recommended pull-up resistors, potentially leaving I/Os floating and causing unpredictable behavior. Those pins are not in line with the SMARC requirements.
Workaround: These pull-up resistors were implemented in the SMARC iMX95 V1.1.
Customer Impact: The over current feature is missing in the USB Interfaces.
Description: Because of a mistake in the footprint for USB_EN_OC# buffer/line driver, the over current feature in the USB interfaces for SMARC iMX95 V1.0.
Workaround: No workaround is available; the issue is fixed in the SMARC iMX95 V1.1.
Customer Impact: The PCIe reference clock (Ethernet oscillator) is not working on SMARC iMX95 V1.0 .
Description: The LMK6HA15625ADLER oscillator does not generate any output due to wrong supply voltage. Correct voltage is provided in the SMARC iMX95 V1.1.
Workaround: There is no identified workaround.
Customer Impact: On SMARC iMX95 V1.0, Ethernet interface ETH_PHY1 and ETH_PHY0 interrupts will not work. On SMARC iMX95 V1.1, the Ethernet interface ETH_PHY0 continues to operate normally with interrupt support while ETH_PHY1 must rely on polling mode instead of interrupts.
Description: On the SMARC iMX95 V1.0 module, both Ethernet PHYs share the interrupt signal connection to the onboard I/O expander, which prevents Ethernet interrupts from functioning correctly. In the updated SMARC iMX95 V1.1, the CTRL_ENET_INT# signal has been disconnected from ETH_PHY1, enabling interrupt-based operation for ETH_PHY0, while ETH_PHY1 now operates in polling mode.
