fixes for boot and (single-block, cmd17-only) Linux driver #820
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the current sdcard clocking, when building a rocket-litex system at exactly 50 MHz, when 12.5 or 25 MHz are requested, it is possible to obtain those frequencies by using an exact power-of-two divisor for the sdclock (4 and 2, respectively). However, when driven at the full 25 MHz during
sdcardboot
, data transfer from the sdcard hangs. The first patch adds an additional halving of the sdclock frequency to ensure the sdclock frequency is never too fast forsdcardboot
.The second patch allows the current single-block-at-a-time (cmd17-only) Linux driver to avoid running into command timeouts when e.g.,
dd
-ing a large file to/dev/null
from the mounted sdcard. This doesn't help enable multi-block (cmd18) transfers without timeouts, but I will open a separate issue to keep track of those debugging efforts.