EMMCFirmwareBugs » History » Version 4
Denis 'GNUtoo' Carikli, 11/22/2020 03:47 PM
| 1 | 1 | Denis 'GNUtoo' Carikli | h1. EMMCFirmwareBugs |
|---|---|---|---|
| 2 | |||
| 3 | 4 | Denis 'GNUtoo' Carikli | {{toc}} |
| 4 | |||
| 5 | 1 | Denis 'GNUtoo' Carikli | h2. Data corruption |
| 6 | |||
| 7 | Several devices have fixes or workarounds in vendor kernels for data corruptions in the eMMC. This can lead to non-working devices as it could potentially corrupt the bootloaders for instance. |
||
| 8 | |||
| 9 | The bug #2104 has more details for the Galaxy SIII. |
||
| 10 | |||
| 11 | h3. Affected devices |
||
| 12 | |||
| 13 | 3 | Denis 'GNUtoo' Carikli | h4. VTU00M |
| 14 | |||
| 15 | *Affected devices*: Some Galaxy SIII (GT-I9300) |
||
| 16 | *Vendor kernel patch*: "mmc: Soft-patch MoviNAND VTU00M (16GB) eMMC failure":https://git.replicant.us/replicant/kernel_samsung_smdk4412/commit/?id=da8461692362317a8ffce4d4646953985fcf4e1d |
||
| 17 | *Upstream status*: not upstream |
||
| 18 | *Replicant >=9 status*: not yet ported |
||
| 19 | |||
| 20 | h5. How to check |
||
| 21 | |||
| 22 | As this patch shows: |
||
| 23 | <pre> |
||
| 24 | + if (!strncmp(host->card->cid.prod_name, "VTU00M", 6) && |
||
| 25 | + (host->card->cid.prod_rev == 0xf1) && |
||
| 26 | + (mmc_start_movi_smart(host->card) == 0x2)) |
||
| 27 | + host->card->movi_ops = 0x2; |
||
| 28 | </pre> |
||
| 29 | |||
| 30 | * The name of the eMMC is VTU00M |
||
| 31 | * Only certain revisions are affected (revision 0xf1) |
||
| 32 | * The revision is probably in the prv field |
||
| 33 | |||
| 34 | h5. Vendor kernel workaround analysis |
||
| 35 | |||
| 36 | The "mmc: Soft-patch MoviNAND VTU00M (16GB) eMMC failure":https://git.replicant.us/replicant/kernel_samsung_smdk4412/commit/?id=da8461692362317a8ffce4d4646953985fcf4e1d patch patches the eMMC firmware at runtime (it patches the firmware in RAM). |
||
| 37 | |||
| 38 | The eMMC firmware patch makes the eMMC hang when a corruption is about to happen. |