This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[FAQ] AM64x Common design Errors / Recommendations for Custom board hardware design – EVM / SK Schematics Design Update Note

Other Parts Discussed in Thread: SK-AM64B, TMDS64EVM, AM625

I am referring the collaterals for the below EVM / SK. 

SK-AM64B (PROC100A), TMDS64EVM (PROC101C)

Is there any Update to be Done on the collaterals to reuse in my custom design.

  • Hi Board designers, 

    Here are some recommended updates based on the learnings for performance improvements.

    Schematics - Design Value Updates 

    1. VCC_3V3_SYS LOAD SWITCH

    SoC IO supply rails have slew rate requirements specified.

    Refer Power Supply Slew Rate Requirement section of the data sheet.

    Add a cap 220 pF or higher on the Load switch CT (Switch slew rate control) pin.

    2. SD card power reset Load switch 

    Add a cap 220 pF or higher on the Load switch CT (Switch slew rate control) pin.

    3. eMMC supply decap

    Add decaps as required to the eMMC memory supply rails 

    4. USB VBUS divider 

    5. Provision to Bypass CMC

    6. USB power switch 

    Use power switch with OC indication. Connect the OC output of the power switch to SoC input

    7. SoC clock MCU_OSC0_XI. MCU_OSC0_XO - connecting external clock 

    DNI the R and C placed at the output of the clock buffer connected to the MCU OSC0 clock input. Placement of these components reduces the amplitude and could affect the performance

    8. SoC  MCU_OSC0_XO termination - when using external clock 

    Data sheet section reference : MCU_OSC0 LVCMOS Digital Clock Source

    Do not leave XO un connected 

    The oscillator was designed to measure the differential voltage between XI and XO, for creating a internal reference clock.  So there is no guarantee they will get the correct differential input voltage if the XO pin is allowed to float.  The datasheet clearly shows this pin needs to be connected to VSS when using an LVCMOS clock source.

    9. Ethernet PHY updates

    10. Caution with EPHY 1V and VPP 1.8V LDO

    Miniature DQN package used.

    Package Outline

    PCB pads 

    There is a likely chance of assembly error due to the LOD outline, pins orientation and  the land pattern (pads and pitch)

    Take note of the following

    EPHY 1.8V supply pins when not used should not be shorted

    Note the recommended caps for the EPHY supplies

    Note the Rbias R and C values 

    Note the pulldown for the EPHY Reset

    11 EXTINTn RC and pullup 

    EXTINTn is a open drain output type IO buffer. The IO has slew rate limit requirements when pulled to 3.3V/

    Add an RC to limit the slew rate.

    Regards,

    Sreenivasa

  • Hi Board designers, 

    Refer below workarounds when load switch is not used for resetting the SD card power supply and the supply is fixed to 3.3V

    https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/09_02_01_09/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.html?highlight=mmc#steps-for-working-around-sd-card-issues

    https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.html

      

    Given below are the list of various workarounds that can be done in the device tree node to get SD card working. The workarounds are ordered in increasing order of reducing performance.

    All the changes mentioned below, are to be done in the MMCSD device tree node corresponding to the SD instance. This is usually the first (index starting from zero) instance.

    1. Restricting to a given speed mode
      • By default the kernel driver tries to enumerate a SD card in the highest supported speed mode. Given below is the order in which the driver tries to enumerate a SD card
        • SDR104
        • DDR50
        • SDR50
        • SD HS
        • SD legacy
      • These speed capabilites can be masked using device tree property sdhci-caps-mask.
        • Limit to DDR50: sdhci-caps-mask= <0x00000002 0x00000000>
        • Limit to SDR50: sdhci-caps-mask= <0x00000006 0x00000000>
        • Limit to SD HS: sdhci-caps-mask= <0x00000007 0x00000000>
        • Limit to SD legacy: sdhci-caps-mask= <0x00000007 0x00200000>

    ·   &sdhci1 {·       /* SD/MMC */·      vmmc-supply = <&vdd_mmc1>;·      vqmmc-supply = <&vdd_sd_dv>;·      pinctrl-names = "default";·      pinctrl-0 = <&main_mmc1_pins_default>;·      ti,driver-strength-ohm = <50>;·      disable-wp;·      sdhci-caps-mask = <0x00000006 0x00000000>; /* Limiting to SDR50 speed mode */·   };

    • Limiting to SD HS speed mode can also be done by using the property no-1-8-v. This disable switching to 1.8V which is required for UHS speed modes(SDR104, DDR50, SDR50)

    ·   &sdhci1 {·       /* SD/MMC */·       vmmc-supply = <&vdd_mmc1>;·       vqmmc-supply = <&vdd_sd_dv>;·       pinctrl-names = "default";·       pinctrl-0 = <&main_mmc1_pins_default>;·       ti,driver-strength-ohm = <50>;·       disable-wp;·       no-1-8-v; /* disabling all the UHS modes */};

    Regards,

    Sreenivasa

  • Hi Board designers, 

    MMC0 PCB Connectivity Requirements

    we have issues with an eMMC connected to MMC0 of a AM6254 processor on a custom board.

    In the datasheet of the AM625 processors we found layout requirements for the MMC0 interface. 



    Does this "min" specification mean that the traces of the MMC0 interfaces MUST have a minimum length? If yes can you specify this in inches or mm?

    Yes, there is a minimum trace delay requirement for this peripheral. 

    The delay values are defined with the unit of picoseconds (ps). You will need to determine the propagation velocity of each signal trace on your specific PCB design to know how much additional trace needs to be inserted to achieve the appropriate delay.

    Regards,

    Sreenivasa

  • Hi Board designers, 

    To implement UHS-I refer below steps:

    The SD card interface pullups have to be connected to the 3.3V_1.8V VDDSHV_SDIO switched supply output from the PMIC 

    The SD card needs to be powered using a fixed 3.3V supply.

    The 3.3V supply to the SD card needs to be switched through a power switch

    Provision to reset the power switch using SOC IOs is recommended 

    An ANDing logic is recommend to reset the SD cars power switch. 

    The SOC VDDSHV5 supply needs to be connected to the .3V_1.8V VDDSHV_SDIO switched supply output from the PMIC

    Regards,

    Sreenivasa