> > For SD a CMD13 after CMD38 is required, too. > > I guess I can add that. > > Just realized that sending CMD13 is not sufficient as the kernel will poll > because of R1B and clear the error flag. > Anyway I have this kernel patch for a write flag bit that aggregates errors > during polling until card is in TRAN again. > I will send it then, since I don't think there is a good way of solving this for SD in > mmc-utils, please consider this patch on its own. Leaving SD aside for now - I Still wasn't able to get an expert opinion - holiday season etc. While waiting however, looking in Table 70 - Device Status field/command - cross reference, I can see that : - ERASE_RESET - is not reported for any of cmd35, cmd36, and cmd38 - ERASE_PARAM - is 'X' for cmd35 only - ERASE_SEQ_ ERROR - is 'R' for cmd35 and cmd36 So potentially only ERASE_SEQ_ ERROR may reside in those commands responses. But mmc-utils uses multi-ioctl for that, so there couldn't be any mis-ordering? Which error bits you see in which command responses? Thanks, Avri > > Regards, > Christian > > Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz Managing Director: > Dr. Jan Peter Berns. > Commercial register of local courts: Freiburg HRB381782
