62b41ad9b4
Some checks are pending
MemBrowse Memory Report / changes-filter (push) Waiting to run
MemBrowse Memory Report / load-targets (push) Waiting to run
MemBrowse Memory Report / identical (push) Blocked by required conditions
MemBrowse Memory Report / analyze (push) Blocked by required conditions
stm32_waitresponse() polls SDIO_STA bounded only by an iteration counter, set to 0x7fffffff for all R1/R1B/R2/R4/R5/R6 commands. The hardware CTIMEOUT flag is the intended exit for a missing response, but it is only generated while the card clock is running and the CPSM has reached its Wait state. If the card clock stops or the peripheral fails, SDIO_STA never updates and the loop spins for INT32_MAX iterations while holding the FAT filesystem lock, at the caller's priority-inheritance boosted priority if higher priority tasks block on the filesystem. Since the mmcsd layer retries failed commands, the driver's recovery paths are never reached and the system never recovers. Bound the wait by time instead: 250 ms for response-bearing commands (the largest timeout the SD specification allows for any operation) and 10 ms for the no-response/R3/R7 cases. CTIMEOUT remains the normal error exit within microseconds; the software bound only fires when the peripheral itself is dead, converting an unbounded spin into -ETIMEDOUT so the existing mmcsd retry logic can run. Signed-off-by: Luka Filipović <filipovicluka3@gmail.com> Assisted-by: Claude Code:claude-fable-5 |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.