SPRADA9C August 2024 – October 2025 AM62P , AM62P-Q1
The processor family supports x3 (three) Multi-Media Card/Secure Digital (MMC/SD/SDIO) (8b (4b) + 4b + 4b) instances.
MMC0 supports 8-bit eMMC (MMC0 interface is compliant with the JEDEC eMMC electrical standard v5.1 (JESD84-B51)) interface. eMMC interface implemented internal to the processor is a dedicated hard macro PHY. The MUX MODE, DSIS, and MUX MODE AFTER RESET columns in the Pin Attributes (AMH Package) table of the device-specific data sheet is blank since the pins (interface) are implemented with a hard macro PHY (does not support pin multiplexing). For supported speeds, see the MMC0 - eMMC Interface section of device-specific data sheet. The required pulls for the eMMC interface as per the JEDEC standard is implemented internal to the processor eMMC hard macro PHY.
Review eMMC related silicon errata AM62Px Sitara™ Processors Silicon Errata, Silicon Revision 1.0, 1.1. The recommendation is to connect VDDA_0P85_DLL_MMC0 (1J1, VDDR_CORE), VDD_MMC0 (1K3, VDDR_CORE) and VDDR_CORE to the same supply source to support future enhancements (including support for HS400 eMMC application) for silicon revision 1.2 and above. For SR1 and SR1.1, when eMMC interface is used and VDD_CORE is 0.85V, the recommendation is to connect VDDA_0P85_DLL_MMC0 (1J1, VDDR_CORE), VDD_MMC0 (1K3, VDDR_CORE) and VDDR_CORE to same source powering VDD_CORE. For SR1 and SR1.1, when eMMC interface is used and VDD_CORE is 0.75V, the recommendation is to connect VDDA_0P85_DLL_MMC0 (1J1, VDDR_CORE), VDD_MMC0 (1K3, VDDR_CORE) and VDDR_CORE to 0.85V supply source. For SR1 and SR1.1, when eMMC is not used the recommendation is to connect VDDA_0P85_DLL_MMC0 (1J1, VDDR_CORE), VDD_MMC0 (1K3, VDDR_CORE) to VDD_CORE.
For more information on eMMC memory interface HS400 support, see the following FAQ:
For more information on eMMC memory interface, see the following FAQ:
For information on the supported speeds, see the following FAQ:
[FAQ] AM623: Can eMMC0 support DDR50 mode
For information on supported interface on the MMC0 port, see the following FAQ:
[FAQ] AM62A3: Any way to get 2 eMMC interfaces?
For information related to eMMC capability to pause the clock when there are no transfers, see the following FAQ:
The FAQ is generic and can also be used for AM62P, AM62P-Q1 processor family.
For connecting the MMC0 interface signals when not used, see the Pin Connectivity Requirements section of device-specific data sheet.
Refer to the silicon errata for eMMC related erratas.
MMC1/MMC2 supports 4-bit SD card interface including support for UHS-I SD card. MMC1 is recommended for implementing SD card interface since MMC1 supports SD card boot mode, MMC1 CLK, CMD, and DAT[3:0] signal functions have been implemented with SDIO buffers and are powered by (referenced to) VDDSHV5. VDDSHV5 can be operated at 1.8V or 3.3V (dynamically switched). MMC1 SDCD and SDWP signal functions are implemented with LVCMOS buffers and are powered by (referenced to) VDDSHV0, which can be operated at fixed 3.3V or 1.8V. The logic state of the MMC1_SDCD and MMC1_SDWP inputs to the host is not recommended to be changed when IO operating voltage for SD card changes to support UHS-I SD card. The required pulls for the SD card interface as per the SD card specifications is required to be implemented external to the processor. An external pulldown for the clock input near to the memory clock input pin is recommended.
MMC1/MMC2 supports 4-bit embedded SDIO interface. MMC2 is recommended for implementing embedded SDIO interface. MMC2 CLK, CMD, and DAT[3:0] signal functions have been implemented with SDIO buffers and are powered by (referenced to) VDDSHV6. VDDSHV6 can be operated at 1.8V or 3.3V (dynamically switched). MMC2 SDCD and SDWP signal functions are implemented with LVCMOS buffers and are powered by (referenced to) VDDSHV6 (VDDSHV0), which can be operated at fixed 3.3V or 1.8V. Refer Signal Description section of the device-specific data sheet for supported pin assignments. The MMC2 pin assignments are different compared to MMC1 because MMC2 is expected to be used with on-board fixed operating voltage SDIO devices similar to Wi-Fi or Bluetooth transceivers. For supported speeds, see the MMC1/MMC2 -SD/SDIO Interface section of device-specific data sheet, refer SK for implementation. Pullups (as required, verify the attached device recommendations including supported pulls) for the SDIO interface is required to be implemented external to the processor. An external pulldown (as required, verify the attached device recommendations including supported pulls) for the clock input near to the memory clock input pin is recommended.
For more information, see the following FAQs:
[FAQ] AM62A7-Q1: how to connect the pin net VDDSHV4, VDDSHV5, and VDDSHV6 if SD card is not used
The FAQs are generic and can also be used for AM62P, AM62P-Q1 processor family.
For MMC1/MMC2, UHS-I SDR50, UHS-I SDR104 receive modes require data training to center the data capture to the center of the data valid window. The timing requirements are not fixed to specific values. The required DLL software configuration settings for MMC1/2 timing modes is provided in the below table:
MMC1/MMC2 DLL Delay Mapping for all Timing Modes of device-specific data sheet.
For more information, see the following FAQ:
[FAQ] AM625 / AM623 / AM620-Q1 / AM625-Q1 / AM625SIP: UHS-I SDR104 Receive mode timing
The FAQ is generic and can also be used for AM62P, AM62P-Q1 processor family.
The processor family supports x1 Octal Serial Peripheral Interface (OSPI0) instance that can be configured for OSPI0 or QSPI0 interface. The recommendation is to follow the SK schematic implementation to interface the OSPI0 interface to a memory device (OSPI or QSPI), addition of series resistor for OSPI0_CLK (for control of possible reflection), pulldown for OSPI0_CLK, pullup for data and CS signals, and implementation of attached memory device reset logic. OSPI0 supports connecting to a x1 (single) attached device.
Refer to the device-specific TRM to connect the supported CS (chip select) to the attached memory device when boot functionality is required to be supported.
OSPI0 supports two data capture modes, PHY mode and Tap mode. To better understand the supported modes, refer to the OSPI, OSPI0 sub-section in the Timing and Switching Characteristics section in the Specifications chapter of the device-specific data sheet.
For more information on OSPI or QSPI memory interface, see the following FAQs:
[FAQ] OSPI FAQ for Sitara/Jacinto devices
The processor family supports x1 General-Purpose Memory Controller (GPMC) interface instance that can be interfaced to NAND flash using 8-bit or 16-bit NAND flash interface signals or NOR flash using supported parallel memory interface (Synchronous or Asynchronous) options listed in the device-specific data sheet and Device Comparison table.
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs (Memory interface signals) that can float (to prevent the attached device inputs from floating until driven by the host).
For more information, see the Memory Interfaces section in the Peripherals chapter of the device-specific TRM.