You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have made a logic capture:
you can see the DAT0 is kept low and clock is enabled so the host is waiting for something.
From the spec:
After receiving a block of data and completing the CRC check, the card will begin writing and hold the DAT0 line low if its write buffer is full and unable to accept new data from a new WRITE_BLOCK command.
Hi,
We are using the sd_device for simulation purpose (verilator) to emulate a SDCARD used by a softcore running linux. (SpinalHDL/SaxonSoc#7)
Got a few issue, had to add some "state exit" logic to unblock the situation durring the weird sequance that the linux SDCARD driver does to unlock/unfreeze sdcard on boot (SpinalHDL@414c935#diff-6903b38ec20622e06f2d9b5083d4f347R327)
Also, had to add support for RESP_R1B (used after MULTIPLE_READ)
Now seem there is some issue with WRITE_MULTIPLE ending.
Do you have some ideas about those issues ?
If you want we can setup a easy to use case reproduction for you to get some waves :)
Anyway, thanks for the project ^^
The text was updated successfully, but these errors were encountered: