diff options
| author | Patrick Delaunay <[email protected]> | 2022-02-15 16:23:23 +0100 |
|---|---|---|
| committer | Jaehoon Chung <[email protected]> | 2022-06-15 15:34:18 +0900 |
| commit | d72267049b484577294e17140b369dee339b2352 (patch) | |
| tree | f647be6529e9e1692d8377e8b1fef31adc5cf4e1 /doc/develop/python_cq.rst | |
| parent | 212875e707b6bc75780386c2cb28fbac7e2ab8f3 (diff) | |
env: mmc : align erase address and size on erase_grp_size
On eMMC device, the erase_grp_size > 1 so the address and size for the
erase block command in env/mmc.c can be unaligned on erase group size and
some strange trace occurs and the result is not guarantee by MMC devices.
The SD-Card behavior doesn't change as erase_grp_size = 1 for SD-Card.
For example, on eMMC present on STM32MP15C-EV1 and before the patch:
STM32MP> env erase
Erasing Environment on MMC...
Caution! Your devices Erase group is 0x400
The erase range would be change to 0x2000~0x27ff
16 blocks erased: OK
Caution! Your devices Erase group is 0x400
The erase range would be change to 0x2000~0x23ff
16 blocks erased: OK
OK
After this patch:
STM32MP> env erase
Erasing Environment on MMC...
1024 blocks erased at 0x2000: OK
1024 blocks erased at 0x2000: OK
OK
Here the 2 copies of U-Boot environment are in the same devices Erase
group: it is erased twice.
Signed-off-by: Patrick Delaunay <[email protected]>
Reviewed-by: Patrice Chotard <[email protected]>
Diffstat (limited to 'doc/develop/python_cq.rst')
0 files changed, 0 insertions, 0 deletions