68f4dff099
Adds a section covering CONFIG_SENSORS_LSM6DS3TRC_FIFO: what it changes (one interrupt/I2C read per watermark instead of per sample) and its three limitations while it's on -- both sub-sensors forced to the same ODR, temperature no longer per-sample (one read per drain applied to the whole batch), and both sub-sensors must stay physically enabled regardless of subscription, since the chip's FIFO write trigger needs both running -- plus the watermark/ORB-buffer-size relationship callers need to respect. Also documents a related chip quirk found during bench testing: diff_words reads 0 at the exact moment a real FIFO overrun occurs, even though the FIFO is still completely full of valid, retained data (a forced read past that point recovers real samples, not garbage). This isn't a bug in this driver: ST's own engineers confirm the same behavior for this chip family on their community forum (thread "LSM6DS3 FIFO status clarification", td-p/184022), and the mainline Linux st_lsm6dsx driver doesn't attempt to recover from it either -- it only special-cases an empty FIFO, not an overrun one. Documenting this in a comment rather than adding recovery logic: with the small watermark this driver uses, reaching a real overrun at all means the drain has already fallen many seconds behind, and ST's own guidance for this condition is to avoid it via watermark sizing rather than recover from it. Signed-off-by: Felipe Moura <moura.fmo@gmail.com> |
||
|---|---|---|
| .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.