Testing Component | SC598-SOM-EZKIT | SC594-SOM-EZKIT | SC589-EZKIT | SC589-MINI | SC584-EZKIT | SC573-EZKIT |
---|---|---|---|---|---|---|
SRU DAI routing configuration | ✅ | ✅ | ✅ | ✅ | ||
SPORT sending I2S data to CODECs | ✅ | ✅ | ✅ | ✅ | ||
ADAU1761 Audio In Driver | N/A | N/A | N/A | ✅ | N/A | N/A |
ADAU1962 Audio Out Driver | ✅ | ✅ | ✅ | N/A | ✅ | ✅ |
ADAU1979 Audio In Driver | ✅ | ✅ | ✅ | N/A | ✅ | ✅ |
ICAP | ✅ | N/A | N/A | N/A | N/A | N/A |
SHARC ALSA | ✅ | N/A | N/A | N/A | N/A | N/A |
remoteproc | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
virtio rpmsg | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Common Clock Framework | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
CRC Check Using Crypto Framework | ✅ | N/A | N/A | N/A | N/A | N/A |
DMA Peripheral Implicitly tested as it's used by SPI, OSPI, and UART drivers | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
MDMA Implicitly tested as it's used only by remoteproc to load data to SHARC shared memory | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
EMAC0 (eth0) | ✅ (950 Mbit/s) | ✅ (450 Mbit/s) | ✅ (190 Mbit/s) | ✅ (180 Mbit/s) | ✅ (190 Mbit/s) | ✅ (180 Mbit/s) |
EMAC0 (AVB) | ❔ | ❔ | ❔ | ❔ | ❔ | ❔ |
EMAC11 | ❗ | ❗ | ❔ | ❔ | ❔ | ❔ |
GPIO Control | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
GPTimers | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
I2C | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
SRAM/L2 alloc | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Pin Control Driver | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
RCU driver/system reset | ✅ | ✅ | ✅ | ❌2 | ✅ | ✅ |
SPI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
QSPI Boot | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
eMMC dev/mmcblk0 | ✅ | ✅ | N/A | N/A | N/A | N/A |
eMMC Boot3 | ❗ | ❔ | N/A | N/A | N/A | N/A |
SD dev/mmcblk0 | ✅ | N/A | ✅ | ✅ | N/A | ❔ |
SD Boot | ✅ | N/A | ✅ | ✅ | N/A | ✅ |
OSPI4 | ❗ | ❗ | N/A | N/A | N/A | N/A |
uart0 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
USB: Host | ✅ | ✅ | ✅ | ✅ | ✅ | ❔ |
USB: Device | ❔ | ❔ | ❔ | ❔ | ❔ | ❔ |
Watchdog | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
✅ PASS
❗ PASS with warning(s), see note
N/A Not Applicable
❌ Not Tested
1Currently, the driver can enumerate the IP and identify what is present, but the PHY is not configured/reset yet and so ethernet communications do not work.
2There is a known issue on the SC589-MINI's watchdog which prevents the RCU driver/system from resetting properly
3Currently, booting with the kernel and RFS on SD/eMMC is the only supported configuration, primarily due to hardware limitations on the SOM-CRR-EZKIT (so U-Boot must still be stored on the SPI flash). See more in the relevant example
4OSPI is not currently working for MX66 chip under 5.15 kernel. OSPI (1S-8S-8S mode) does work for SC594 & IS25LX256