CI builds with -Werror and the board's build carried thousands of warnings, all rooted in the vendor SDK integration: - The NMSIS riscv_encoding.h redefines 32 CSR macros that NuttX's <arch/csr.h> (pulled in through <nuttx/irq.h>) already defines with its own encodings. No -Wno flag covers macro redefinitions, so the SDK patch now undefines those names right before the NMSIS definitions. Same treatment for COMPILE_TIME_ASSERT in wifi_management.h. - The vendor sources are not NuttX-warning-clean (undefined macros in #if, %d for uint32_t, shadowed locals, K&R prototypes, ...); add the matching -Wno suppressions scoped to this chip's build. - Fix the port's own warnings properly: gd32vw55x_eclic.h redefined CSR_MINTSTATUS with the Nuclei address (0x346) over the standard CLIC one in csr.h (renamed to CSR_NUCLEI_MINTSTATUS), an unused variable in gdwifi_transmit() and a dead function in wrapper_nuttx.c. All seven configurations now build with "-Wno-cpp -Werror" (the CI flags). Smoke-validated on hardware: Wi-Fi WPA2 association and ping, BLE advertising, connect and GATT write. Assisted-by: Claude Opus 4.8 Signed-off-by: Jorge Guzman <jorge.gzm@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.