diff options
| author | Mateusz Kijowski <mateusz@kijowski.info> | 2018-06-29 01:32:02 +0200 |
|---|---|---|
| committer | Damien George <damien.p.george@gmail.com> | 2018-07-05 19:39:06 +1000 |
| commit | 1751f5ac7bd48f5673791801b052487ae73d064d (patch) | |
| tree | 5d49f220c40773eab619c67e4f907cf09ecb0cb5 /py/modcmath.c | |
| parent | 14ab81e87accedfb9ed231b206dd21f3a0143404 (diff) | |
| download | micropython-1751f5ac7bd48f5673791801b052487ae73d064d.tar.gz micropython-1751f5ac7bd48f5673791801b052487ae73d064d.zip | |
drivers/sdcard: Do not release CS during the middle of read operations.
It seems that some cards do not tolerate releasing the card (by setting CS
high) after issuing CMD17 (and 18) and raising it again before reading
data. Somehow this causes the 0xfe data start marker not being read and
SDCard.readinto() is spinning forever (or until this byte is in the data).
This seems to fix weird behviour of SDCard.readblocks() returning different
data, also solved hanging os.mount() for my case with a 16GB Infineon card.
This stackexchange answer gives more context:
https://electronics.stackexchange.com/questions/307214/sd-card-spi-interface-issue-read-operation-returns-0x3f-0xff-instead-of-0x7f-0#307268
Diffstat (limited to 'py/modcmath.c')
0 files changed, 0 insertions, 0 deletions