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 noticed on logic analyzer traces that at slow clock speeds (e.g. 400kHz), the microSDXC card I am using sometimes starts clocking the data out on the data lines before it has finished clocking the response out on the CMD line. The litesdcard interface only starts looking for the data after the response is complete, so it doesn't see the data, and eventually times out.
As far as I can see in the SD spec, it is legal for the card to start clocking the data out any time after the response has started. I think we need to start the state machine for receiving data at the same time when the state machine for receiving the response is started, not when the response state machine finishes.
The text was updated successfully, but these errors were encountered:
I have noticed on logic analyzer traces that at slow clock speeds (e.g. 400kHz), the microSDXC card I am using sometimes starts clocking the data out on the data lines before it has finished clocking the response out on the CMD line. The litesdcard interface only starts looking for the data after the response is complete, so it doesn't see the data, and eventually times out.
As far as I can see in the SD spec, it is legal for the card to start clocking the data out any time after the response has started. I think we need to start the state machine for receiving data at the same time when the state machine for receiving the response is started, not when the response state machine finishes.
The text was updated successfully, but these errors were encountered: