4aca170070
This patch introduces CONFIG_CC1101_SPIFREQ_BURST and CONFIG_CC1101_SPIFREQ_SINGLE to Kconfig, allowing users to override the default SPI frequencies for the CC1101 wireless driver. Previously, these values were hardcoded to 6.5 MHz and 9.0 MHz respectively. While these are safe defaults for many setups, specific hardware designs, high routing capacitance, or platforms utilizing internal GPIO switching matrices (such as the ESP32) can suffer from signal integrity degradation at these speeds. By exposing these to Kconfig, users can easily adjust the clock speeds to match their hardware capabilities without modifying the core driver source. Impact: - Build: Adds two new Kconfig options under WL_CC1101. - Runtime: Retains 6.5 MHz / 9.0 MHz defaults. Behavior only changes if overridden via menuconfig. Testing: - Built with default values and custom Kconfig overrides. - Hardware Testing: Tested on a sub-optimal platform utilizing an internal GPIO matrix (ESP32). The CC1101 failed to load at the default 6.5/9.0 MHz due to signal integrity issues. Downclocking the frequencies to 4.0 MHz via Kconfig successfully restored signal integrity and allowed the driver to initialize and operate normally. Signed-off-by: Chip L. <chplee@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.