Fallbackmode for SD card init failed
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Referring to the following issues and the following error using fsbl code with sd cards:
- https://support.xilinx.com/s/question/0D52E00006hpiTJSAY/high-speed-sd-card-cant-finish-initialization-during-fbsl-and-uboot?language=en_US
- https://support.xilinx.com/s/question/0D52E00006hpTekSAE/zynq-fsbl-cannot-read-bootbin-from-sd-card?language=en_US
Boot mode is SD
SD: rc= 0
SD: Unable to open file BOOT.BIN: 3
SD_INIT_FAIL
FSBL Status = 0xA009
Due to the prompt and looking at the code an issue could arise in trying to switch to another sd card speed in call XSdPS_Change_BusSpeed(). If there might be an error communicating with the card it might be an idea to implement a fallback mode which would not change the busspeed and stays with 25 MHz after it detected the error in switching speeds.
Would this be an idea to make this fsbl code more robust?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the FSBL SD initialization path around XSdPS_Change_BusSpeed() and the reported SD_INIT_FAIL sequence. Reproduce or trace the failure when switching bus speed, then assess a fallback that keeps the card at 25 MHz. Done means the fallback behavior is defined and the FSBL can continue reading BOOT.BIN after a speed-switch error.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100