The following table contains known issues, scheduled bug fixes, and feature improvements for the Verdin iMX8M Plus.
For other information, click on the below links:
Customer Impact: The 0058 Verdin iMX8M Plus Quad 4GB WB IT V1.0C does not support the full industrial temperature range and is only usable between 0°C and +70°C.
Description: The 0058 Verdin iMX8M Plus Quad 4GB WB IT V1.0C is a special development version that features a Consumer temperature range SoC part. As a consequence, the product version does not support the full industrial temperature range and is only usable between 0°C and +70°C.
Workaround: There is no workaround to this limitation. If full industrial temperature range support is required, consider using the 0058 Verdin iMX8M Plus Quad 4GB WB IT V1.0D instead.
Customer Impact: The Bluetooth solution is not accessible by the system as the host interface strapping signal of the Bluetooth solution is unintentionally influenced by a stitching capacitor on the SoM. This leaves the Bluetooth solution in the UART interface mode instead of SDIO.
Description: The signal used for strapping the HCI (Host Controller Interface) configuration of the Bluetooth solution at the time of powering up the SoM is also available on the Module-specific pin MSP_8 (#104) of the SoM edge connector. Module-specific pins feature stitching capacitors for providing current return paths for cases when those pins are being used for accommodating high-speed signals. The Verdin iMX8M Plus V1.0B configurations equipped with a Wi-Fi/Bluetooth solution feature one such capacitor (C210) on the MSP_8 signal. During powering up the system, the stitching capacitor is delaying the transition of the related signal to the intended state and thus results in a wrong configuration being strapped. Instead of SDIO mode, the host interface of the Bluetooth solution gets configured to UART mode. As a result, the Bluetooth solution is not accessible by the system.
Workaround: Remove the stitching capacitor C210 from the SoM. This makes the Bluetooth interface work in case the SoM is connected to a Dahlia V1.1A carrier board. If the SoM is connected to a Verdin Development Board V1.1A, then other stitching capacitors need to be removed from the carrier board as well. For more information, please refer to HAR-8342 in the Verdin Development Board errata. The issue will be resolved in future HW versions of these products.
Customer Impact: The USB OTG port cannot dynamically switch between host and client function, depending on the OTG cable that is plugged in. The Toradex BSP sets the USB_1 port permanently to the client mode. It is also possible to set the USB_1 port permanently to host mode. The recovery mode is not affected by this restriction. In the recovery mode, the USB_1 port is always set to client mode, independently of the state of the ID pin.
Description: NXP has renamed the USB1_ID pin to USB1_DNU (do not use). With that, they have removed the USB ID function from this pin. The USB ID signal is intended to be used for the USB OTG receptacle to distinguish whether a type A (module act as a USB client) or type B (module act as a USB host) cable is plugged in. On the Verdin iMX8M Plus, the SoC pin USB1_ID is available on the module edge connector pin 161 as USB_1_ID. It is intended to be used as the USB ID for a USB OTG implementation on the carrier board. Unfortunately, the SoC pin USB1_ID does not serve any GPIO functionality. With the degradation to USB1_DNU, the pin cannot be used anymore. Without the USB_1_ID signal, the USB OTG port can only be set permanently to host or client mode by changing the device tree settings.
Workaround: In the device tree, it is possible to set the USB_1 port permanently to host mode. By default, the port is set to client mode. If the dynamic role switching between host and client modes is required, any free GPIO can be used. This solution requires further changes in the device tree. Please note that this breaks compatibility with other modules in the Verdin family. In case of custom carrier boards employing this workaround, it is highly recommended to add an assembly option for using the Verdin standard pin 161 as USB ID for keeping compatibility with other Verdin modules.
Customer Impact: The optional master clock output of the CSI_1 interface (CSI_1_MCLK) is not usable. Most of the CSI camera modules supported by Toradex feature an on-board crystal/oscillator and thus do not require this clock for functioning properly.
Description: The Verdin pinout contains an optional master clock output for the CSI_1 interface. The SAI3_MCLK SoC pin is used for providing the optional Verdin camera interface master clock CSI_1_MCLK output. This signal is available on the module edge connector pin 91. The SoC pin can provide clock signals from the SAI3 and SAI5 audio interfaces. Therefore, a dummy audio driver with a dummy audio stream would be required for enabling the clock output. The current Toradex BSP does not support the CSI_1_MCLK option.
Workaround: Instead of using the CSI_1_MCLK, use an external crystal or oscillator for the camera. The i.MX 8M Plus SoC features two general-purpose clock outputs that can be used independently from the audio interfaces. Those clock signals are only available as alternate functions of other signal pins. Therefore, the clock signals are not compatible with other Verdin modules. If one of the general purposes clock outputs are used, adding an assembly option for using the CSI_1_MCLK pin is highly recommended. This ensures compatibility with existing and future versions of the Verdin iMX8M Plus and other Verdin modules.
Customer Impact: The Bluetooth audio feature cannot be used. The rest of the Bluetooth and Wi-Fi features are not affected by this issue.
Description: The RX and TX signals of the I2S audio interface between the i.MX 8M Plus SoC and the Wi-Fi module are swapped.
Workaround: There is no workaround for making the Bluetooth audio feature of the Wi-Fi module available.
