PicoCore™MX8ULP codec info

Quote from Saturnion

Second question: without using the A35 core to initialize the codec from the m33 core, the documentation talks about I2C_D, did I understand correctly that this will be I3C0 located on the PTA(14,15) pins?

This is correct. I2C_D is the I3C0 interface from the RT domain.

We are currently developing an SRTM program for the Cortex-M that will allow the Linux system to control the i3C0 and all other RT domain peripherals (I2C, GPIO, SAI, TPM, ...). At the current stage of development, I2C, I3C (I2C compatible) and GPIO are available to Linux via SRTM. SAI for LP audio will follow and will also be available in the next release.

Quote from Saturnion

As far as I know, it is impossible to use SAI4 from m33 core (correct me if this is not so), the documentation states that PTCs are also connected to the codec (as I understand it is about SAI1), so can I use SAI1 to transfer audio data to the codec while the A35 core and SAI4 are enabled? (or is it necessary to make sure that SAI4 is disabled?)

The PicoCoreMX8ULP allows SAI4 (APD) or SAI1 (RTD) to be used for the audio codec. Both peripherals are usually not configured at the same time via jumpers. Depending on the hardware configuration, only SAI4 or SAI1 can be configured.

The configuration was tested with SAI4 for the current pre-release (Y2024.04). The necessary settings can be found in the respective devicetree.
If you want to use the Cortex-M for audio, SAI1 must be configured.

With the SAI1 configuration, the Linux system cannot output audio in the current pre-release. However, we are currently working on a solution so that the Linux system can also use the SAI1 via the SRTM framework.

The best way to do this is to contact support@fs-net.de.

Please also provide the serial number of your product so that we can determine your current configuration, as well as a reference to the forum post.

We can assist you with the reconfiguration SAI4 -> SAI1 if necessary.