IMX8MP Verdin on Mallow carrier board

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hi Tom,

From the information provided, it seems like you are experiencing issues with the I2S interface (SAI1) on the IMX8M Plus when using the Mallow Carrier Board. The non-uniform BCLK and SYNC signals, along with random activity on the lines, could indeed be indicative of a pin-muxing conflict or misconfiguration.

Here are a few suggestions to troubleshoot and potentially resolve the issue:

1. Pin Configuration: Double-check the pin configuration in your device tree. Ensure that the pins you are using for BCLK, SYNC, and DOUT are correctly configured and do not conflict with other peripherals. The pinctrl settings should match the physical connections on the Mallow board.

2. Clock Configuration: Verify the clock settings in your DTS configuration. Ensure that the assigned clocks and clock rates are correct for your application. The assigned-clock-rates value should match the expected frequency for your I2S interface.

3. Check for Conflicts: Look for any other device tree nodes that might be using the same pins or clocks. Conflicts can arise if multiple peripherals are trying to use the same resources.

4. Driver Support: Ensure that the SAI1 driver is properly enabled and configured in your kernel. Check the kernel documentation for any specific requirements or configurations needed for the SAI1 interface.

5. Debugging: Use tools like devmem2 or memtool to inspect the register values for the IOMUX and clock settings. This can help identify if the hardware is configured as expected.

6. Consult Documentation: Refer to the Verdin iMX8M Plus and Mallow Carrier Board documentation for any specific notes or errata related to the I2S interface.

If the issue persists, consider reaching out to Toradex technical support for further assistance. They may have additional insights or updates that could help resolve the problem.

Regards,
[Your Name]

Please, also check if these links can help you solve your problem:

Digital Audio I2S Slave - SAI3_RX_BCLK - Pin Allocations

Hi, I am finishing up work on a Carrier Board for the iMX8M Plus. We require the use of SAI3_RX for I2S slave audio. My concern is that SAI3_RX_BCLK is on pin 256, which is the same pin as CTRL_SLEEP_MOCI#. I was not planning on using the CTRL_SLEEP_MOCI# function, but am worried it may be tricky to use this pin for anything than its default function. Could reassigning pin 256 cause any software headaches? Is there an alternative pin I could use for SAI3_RX_BCLK if so? Thanks! Tom

Pin Multiplexing - Changing Pin Functionalities in the Linux Device Tree | Toradex Developer Center.