Skip to content

fix DDR52 writes on Centauri 2 MMC8GB eMMC - #479

Draft
0xD34DC0DE wants to merge 1 commit into
OpenCentauri:mainfrom
0xD34DC0DE:fix/c2-mmc8gb-ddr52
Draft

0xD34DC0DE wants to merge 1 commit into
OpenCentauri:mainfrom
0xD34DC0DE:fix/c2-mmc8gb-ddr52

Conversation

@0xD34DC0DE

Copy link
Copy Markdown

Some Centauri 2 boards ship an eMMC (MMC8GB, mfr 0x32/OEM 0x0101) that fails on DDR52 writes with CRC status errors, so COSMOS cannot boot past PREINIT.
Stock firmware runs the same chip at DDR52 50 MHz.

This PR adds a sunxi-mmc patch with opt-in DT properties that reproduce the stock Allwinner BSP setup and enables them for mmc2 on the C2/CC2 DTS:

  • ddr-old-timing: DDR52 in old timing mode, 100 MHz module clock from pll-periph0, no internal divider
  • sample-delay = <36>: centre of the stress-test passing window (12..56)
  • fifo-watermark = <0x300f00f0>: stock FTRGL value
  • write-threshold: stock card write threshold on writes

Various combination of these settings change where tested to narrow it down to only the necessary changes.

Also, max-frequency is set to 50 MHz andmmc-hs200-1_8v is dropped since the chip rejects HS200 and stock never uses it.

Sample delay values where stress tested and the working window appears to start at 12 and instability starts when going over 56.
Dumps from another affected printer's device tree showed 24 as the sample delay chosen by the U-Boot boot time sample delay timing for that particular printer.

For now, this fix assumes 36 as a safe value for the sample delay (aiming for the center of the valid sample delay window).
Further tests are required to confirm that this value can be hardcoded without requiring the same boot time DL tuning that stock fw's U-Boot performs.

Additionaly, this fix needs to be tested on the non-affected eMMC version of the board to confirm its working correctly and that no eMMC version detection logic is necessary.

No prints where attempted yet with a build of this fw (updates to come for that part)

This branch is waiting to be deployed

1 waiting deployment
approval-needed — 6d3499c0 Waiting Nov 15, 2026 by 0xD34DC0DE via approve #870
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant