89b8c5fc7f
esp_pmstandby() fed up_step_idletime() the sleep duration it *asked* for (time_in_us) rather than the one it actually got (rtc_diff_us), and did so unconditionally. Both halves are wrong. esp_pm_light_sleep_start() already stalls and restores the systimer itself, but only where SOC_SLEEP_SYSTIMER_STALL_WORKAROUND is defined -- esp32c3 and esp32p4. On every other SoC, esp32s3 included, the systimer keeps counting straight through light sleep, so the time is already in the clock and stepping it again adds it twice. Measured on an esp32s3-xiao: over 54 min with 1919 light sleeps totalling 454.7 s, the monotonic clock ran 443.2 s fast -- 0.97 of the time slept, i.e. counted exactly twice, leaving the clock 13.8% fast. Anything that reconstructs wall time from CLOCK_MONOTONIC inherits that error; for this collar it corrupted every IMU sample timestamp. Invisible until light sleep started happening for real, because a board that never sleeps never steps the clock. Note for upstream: the risc-v copy here only switches to the measured duration and does not gate on SOC_SLEEP_SYSTIMER_STALL_WORKAROUND. The two should be reconciled before this is proposed -- it is kept as-is so the asymmetry is visible rather than silently decided. Signed-off-by: Felipe Moura <moura.fmo@gmail.com> Assisted-by: Claude:claude-opus-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.