58c07d00d1
Add the autoleds driver for the three on-board user LEDs (LD5 red PG10, LD6 green PG0, LD7 blue PG8; all active-low). Structure mirrors boards/arm/stm32h5/nucleo-h563zi with the polarity and initial-OFF state corrected for the active-low wiring. * boards/Kconfig: ARCH_BOARD_NUCLEO_N657X0_Q selects ARCH_HAVE_LEDS so the ARCH_LEDS prompt becomes available. * arch/arm/src/stm32n6/stm32_idle.c: include <arch/board/board.h> so LED_IDLE is defined and up_idle() actually calls into the autoleds driver around WFI. The existing nsh and ostest defconfigs do not pin CONFIG_ARCH_LEDS and therefore inherit its Kconfig default (y when ARCH_HAVE_LEDS is selected), so after this patch they include the autoleds driver by default. This matches the convention on the comparable H5 and H7 Nucleo defconfigs, which also leave ARCH_LEDS at its default. Tested on Nucleo-N657X0-Q: nsh and ostest still build, flash and run. With CONFIG_ARCH_LEDS=y, green is steady at the NSH idle prompt; red pulses on each IRQ but the on-time is too brief to be clearly visible to the eye. Signed-off-by: ImBonkers <samuelnlinden@pm.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 | ||
| .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.