[EXT_EP-13303] Kernel: MMCSD HS200 Write Failures Created: 07/Apr/26  Updated: 07/Apr/26  Resolved: 07/Apr/26

Status: Fixed
Project: Embedded Software & Tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: TI User Assignee: TI User
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Product: Linux Core SDK
Internal ID: LCPD-46897
Forum URL: NA
Found In Release: 12.00.00
Fix In Release: 12.00.00
Affected Platform/Device: am62axx_sk-fs
am62dxx_evm-fs
am62lxx_evm-fs
am62pxx_sk-fs
am62xx_lp_sk-fs
am62xx_sk-fs
am62xxsip_sk-fs
Workaround: Implement a software recovery mechanism which re-issues the failed multiple block write with minimum 5us delay between blocks to reduce noise. One way to achieve this delay is using single block writes for the failed multiple block write

 Description   

The MMC0 interface has the potential for write failures when issuing multiple block writes operating in HS200 mode with excessive IO supply noise.

To minimize IO supply noise follow below best practices and refer to the linked app note:

  • Use wide power planes/pours adjacent to ground layers with a thin dielectric between them.
  • Place power planes/pours and adjacent ground planes as close to the surface of the powered components as possible.
  • Use a wide variety of decoupling capacitor values and place low ESL capacitors as close to the decoupled device as possible.
  • Use one decoupling capacitor per power pin.
  • Use short and wide traces to decoupling capacitors and power/ground vias.
  • Sitaraâ„¢ Processor Power Distribution Networks: Implementation and Analysis

    Workaround to Implement:
    software recovery mechanism which re-issues the failed multiple block write with minimum 5us delay between blocks to reduce noise. One way to achieve this delay is using single block writes for the failed multiple block write

Fixed: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.18.y&id=8830e3e74d20e91d65dc7d303256a51a16d80cfd


Generated at Fri May 01 09:56:58 CDT 2026 using Jira 10.3.7#10030007-sha1:a563685562f94d165eb4e158cfb2a142338d8c54.