 HAR-11459 | Known Issue | Verdin IMX8M Mini USB1 OTG port Vbus detection error during unplugging and plugging USB cable to USB Host | | |
Customer Impact: Customers will see the following error message in the console: usbmisc_imx 32e40200.usbmisc: Error occurs during detection: -22
usbmisc_imx 32e40200.usbmisc: vbus is error
We have seen no impact on USB functionality. This error will only appear if customers are using USB in client mode. Description: On Verdin iMX8MM USB_1 port is operating as dual-role-port for both host and client functions. We have seen during client mode USB Vbus detection fails occassionally due to slow rise of 5V on VBus pin. This result in below error message:
usbmisc_imx 32e40200.usbmisc: Error occurs during detection: -22
usbmisc_imx 32e40200.usbmisc: vbus is error
We have seen no impact due to this on USB functionality in any way. Workaround: Not applicable as voltage stabilizes and there is no impact on USB functionality. |
| HAR-10469 | Known Issue | Verdin iMX8M Mini incorrect CTRL_PWR_BTN_MICO# behavior | Verdin iMX8M Mini V1.1A
Verdin iMX8M Mini V1.0A
Verdin iMX8M Mini V1.0B
Verdin iMX8M Mini V1.1B
Verdin iMX8M Mini V1.1C
Verdin iMX8M Mini V1.1D
Verdin iMX8M Mini V1.1E
Verdin iMX8M Mini V1.1F | |
Customer Impact: A sudden change in the computer module input voltage might involuntarily activate the CTRL_PWR_BTN_MICO# signal that, by default, will initiate the software shutdown or wake the system from the sleep state. Description: The circuit used to generate the CTRL_PWR_BTN_MICO# on the computer module is affected by a hardware bug that could cause this signal to be triggered involuntarily by a fast change in the input voltage. The Voltage needs to increase immediately by at least by 0.9V to trigger the signal. The CTRL_PWR_BTN_MICO# allows the implementation of a power button behavior like the ones used on regular personal computers and smartphones. Short pressing the power button powers up the system from the “Module OFF” state or wakes the system from the sleep state. If the module is running, short pressing the power button generates a software interrupt. Depending on the operating system settings, this starts a software shutdown or opens a menu that lets the customer decide what to do. Workaround: The best way to mitigate this issue is to configure the CTRL_PWR_BTN_MICO# differently in the software. If this is not possible and it is necessary to test the behavior of a module where this issue has been fixed, please contact the support team.
Future versions of this product will have a different assembly option that will solve this bug completely. |
| HAR-8214 | Known Issue | MIPI CSI camera optional master clock output not usable | Verdin iMX8M Mini V1.1A
Verdin iMX8M Mini V1.0A
Verdin iMX8M Mini V1.0B
Verdin iMX8M Mini V1.1B | |
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 Mini 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 Mini and other Verdin modules. |
| HAR-7203 | Known Issue | Double termination on the PCIe clock lines of the Verdin iMX8M Mini | Verdin iMX8M Mini V1.1A | Verdin iMX8M Mini V1.1B |
Customer Impact: The voltage level of the PCIe reference clock output (PCIE_1_CLK_N and PCIE_1_CLK_P) is too low and not PCIe compliant. For some PCIe peripheral devices, the voltage swing is too small for those devices to operate properly. Description: The PCIe reference clock available at the module edge connector pins 226 and 228 is generated by the i.MX 8M Mini SoC. The clock signals are unintentionally terminated twice. There are 49.9Ω termination resistors on the module, and the SoC pins have internal terminations as well. This double termination adds too much load on the reference clock, leading to a wrong output level. The V1.0B versions of the Verdin iMX8M Mini modules are not affected by this issue since those feature an external PCIe clock source that requires the external termination resistors. Workaround: Remove the two 49.9Ω termination resistors R28 and R29 on the Verdin iMX8M Mini module. The resistors are located on the top side of the module. For more information, please consult Errata #14 in the Verdin iMX8M Mini errata document. |
| HAR-5754 | Known Issue | The CTRL_FORCE_OFF_MOCI# signal type is push-pull instead of open-drain | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: Depending on the carrier board, the CTRL_FORCE_OFF_MOCI# is pulled up to 3.3V or 5V, which violates the absolute maximum voltage of the push-pull type signal on version V1.0 of the module. Description: The signal type of the CTRL_FORCE_OFF_MOCI# has been changed from 1.8V push-pull to a 5V tolerant open-drain. The reason is to simplify the carrier board design and to omit the need for a level shifter on the carrier board. Workaround: On Verdin Development Boards, it is possible to remove the jumper for the CTRL_FORCE_OFF_MOCI# signal (pin A23 an B23 of X6). On the Dahlia carrier board, remove resistor R247. However, both workarounds disable the "kill-feature". Therefore, after a shutdown, the supplies are not turned off. |
| HAR-3240 | Known Issue | Power rails of Wi-Fi module cannot be turned off | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: It is not possible to save power by only temporarily enabling the Wi-Fi and Bluetooth module. Description: It is not possible to turn off the power rails of the Wi-Fi and Bluetooth module after they have been turned on. Workaround: After booting the module, turn on the power rails for the Wi-Fi and Bluetooth module only if the radio is required. Keep the rails turned on or reboot the system if the rails need to be turned off again. |
| HAR-3195 | Feature Request | Change the name from NFF to Verdin | | Verdin iMX8M Mini V1.1A |
Description: The product name printed on the PCB contains NFF instead of Verdin. |
| HAR-3366 | Known Issue | Undefined state of CTLR_PWR_EN_MOCI in power-off-state | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: The peripheral power rails on the carrier boards maybe do not get disabled in power-off-state as expected. Description: Due to back feeding, the CTRL_PWR_EN_MOCI can have a residual voltage. This means the voltage remaining at CTRL_PWR_EN_MOCI can be too high (>0.3V) which can be interpreted as a high state by some input circuits. Workaround: Make sure the input low threshold for the circuits that are connected to the CTRL_PWR_EN_MOCI signals are high enough or use the CTRL_FORCE_OFF_MOCI# for disabling the power rails in power-off-state. |
| HAR-3192 | Known Issue | Keeping CTRL_RESET_MICO# down does not keep module in reset | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: It is not possible to delay the power-up cycle or prolong a reset cycle by keeping the CTRL_RESET_MICO# input signal down. Description: Holding the CTRL_RESET_MICO# down does keep the module in the reset state. The falling edge of the CTRL_RESET_MICO# triggers the reset cycle, which reboots the module independent of whether the CTRL_RESET_MICO# signal is kept low. Similarly, keeping the CTRL_RESET_MICO#
low while powering up the module does not stop the module from booting entirely.
The behavior will be changed in version 1.1 of the module. The holding down of the CTRL_RESET_MICO# signal will prolong the reset cycle. A falling edge on the CTRL_RESET_MICO# input will initiate the reset cycle while the module will wait for the rising edge for releasing the reset of the on-module reset and the external CTRL_RESET_MOCI#. Workaround: Not available. |
| HAR-3191 | Known Issue | Incorrect assertion of CTRL_FORCE_OFF_MOCI# in reset and power down cycle | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: Depending on the carrier board, the power can get killed during the reset cycle, or the powerdown does not switch off the rails in the expected order. Description: The CTRL_FORCE_OFF_MOCI# is on the V1.0 module a simple GPIO with an on-module pull-up resistor. Depending on the carrier board, the power can get killed during reset cycle or the power down does not switch off the rails in the expected order. Workaround: In order to be able to perform a reset cycle without killing the power, on the Verdin Development Board the jumper for the CTRL_FORCE_OFF_MOCI# needs to be removed (pin A23 and B23 of X6). On the Dahlia, the resistor R96 needs to be removed for the same purpose. However, this workaround will disable the kill feature of the carrier board. |
| HAR-3184 | Known Issue | KSZ9031 assembled instead of KSZ9131 Indicated in the product datasheet and schematic | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: The KSZ9131 is an updated version of the KSZ9031. The features are identical. However, the KSZ9131 resolves several errata of the KSZ9031, including issues with passing Ethernet compliance tests.
The KSZ9031 and the KSZ9131 are officially software compatible. However, there are some differences in the settings of the RGMII timing. Make sure that the BSP supports the corresponding Ethernet PHY.
The new KSZ9131 will be assembled in the next product version. Description: The part KSZ9031RNXIC has been assembled instead of KSZ9131RNXI that is indicated in the product datasheet.
Workaround: Not available. |
| HAR-2728 | Known Issue | Verdin iMX8MM: JTAG Boundary Scan not accessible | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: It is not possible to use the Boundary Scan mode. Description: It is not possible to access the JTAG Boundary Scan mode. The JTAG strapping on the module is not correct. An incorrect JTAG ID is read back. Workaround: Not available. |
| HAR-2727 | Known Issue | After power-down the module cannot be turned on by using CTRL_PWR_BTN_MICO# | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: If a power control scheme is used that keeps the main module rail permanently on, the module cannot be turned on after shutting down. For booting the module after a shutdown, the main rail always needs to be power cycled. Description: After powering down the module, the module cannot be turned on by using the CTRL_PWR_BTN_MICO# signal. Workaround: Power cycle the main supply of the module. One option is to kill the main power rails by using the CTRL_FORCE_OFF_MOCI# signal. |
| HAR-2726 | Known Issue | Undefined state of CTLR_PWR_EN_MOCI during reset cycle | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Customer Impact: Depending on the carrier board circuit, the carrier board’s power rails are not disabled during the reset cycle. This means these rails are maybe not cycled during the reset state. If a peripheral device uses a power-on-reset rather than the system reset, the device may not get reset. Description: During a reset cycle the CTRL_PWR_EN_MOCI signal can go to an undefined state. For some time, the signal can be neither high nor low. Workaround: If a defined state of the CTRL_PWR_EN_MOCI is required during the reset cycle, use a comparator circuit. |
| HAR-2333 | Known Issue | MCP2517FDT-H/JHA is assembled instead of MCP2518FDT- E/QBB as indicated in the product datasheet and schematic | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Description: The MCP2517FDT-H/JHA has been assembled instead of MCP2518FDT- E/QBB indicated in the product datasheet. Workaround: Do not use the additional features of the MCP2518. |
| HAR-2332 | Known Issue | Missing pull-up on CAN SPI MISO signals might cause signal flickering | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Description: Missing pullup’s on CAN SPI MISO signals might cause signal flickering. This could result in unecessary higher current consumption.
Workaround: There is no software or hardware workaround available for V1.0 modules. A weak external pullup will be added to V1.1 modules in order to avoid the MISO signal to float. |
| HAR-2331 | Known Issue | Missing SD/SDIO external pull-up resistors may lead to malfunction of SD Cards in default and high speed modes | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Description: The i.MX8M Mini errata number e50080 affects the SDIO interface signals when they are used in Default Speed and High-Speed bus modes without external pull-up resistors because the current capability of these pins could degrade. Workaround: If UHS-I speed modes are used (SDR12, SDR25, DDR50, SDR50, or SDR104), the interface runs in 1.8V. In this case, the 3.3V IO voltage level is only used during the enumeration process. Therefore, UHS-I graded SD cards are recommended to be used. |
| HAR-2326 | Known Issue | No dedicated reset for eMMC | Verdin iMX8M Mini V1.0B | Verdin iMX8M Mini V1.1A |
Description: The dedicated reset input of the boot eMMC on the module is not connected to the SoC. Therefore, the eMMC can only be reset by a power-on reset. Workaround: If the eMMC needs to be reset, a complete system reset needs to be performed which includes a power cycle that triggers the power-on-reset of the eMMC. |
