a8ac2e74e0
The SAADC internal sample timer only works with a single enabled channel, so hardware-timed multi-channel scan was not possible. Add NRF52_SAADC_TIMER_PPI, a third trigger mode in which a general-purpose TIMER compare event is routed to TASKS_SAMPLE over PPI. All enabled channels are scanned, and the TIMER prescaler allows much lower sample rates than the internal timer, which is limited to 16MHz/CC with CC in 80..2047. NRF52_SAADC_CONTINUOUS is no longer tied to the internal timer and works with either source. Its EasyDMA buffers now hold NRF52_SAADC_CONTINUOUS_BUFLEN whole scans rather than that many single samples, so MAXCNT becomes chan_len * BUFLEN. Samples are interleaved scan by scan, so a channel map is built once at configure() time and passed to the upper half with the batch; the upper half already accepts a per-sample channel array. A single-channel configuration produces the same MAXCNT and the same delivery as before. Because both features want a PPI channel, add a build-time check that NRF52_SAADC_PPI_CHANNEL and NRF52_SAADC_CONTINUOUS_PPI_CH differ, and constrain the latter under the SoftDevice controller like the former. NRF52_SAADC_CHANNELS gains a default and range for the new mode, and documents that the internal timer is restricted to one channel. Assisted-by: Claude Code Signed-off-by: raiden00pl <raiden00@railab.me> |
||
|---|---|---|
| .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 | ||
| .mcp.json | ||
| .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.