Add the Microchip EV49N51A Ethernet to Wi-Fi Bridge board, built around the WFI32E01PE module (PIC32MZ-W1) with a LAN8720A Ethernet PHY. The nsh configuration runs SYSCLK at 200 MHz with the console on UART1 (dedicated pins RA8/RA9, header J203, 115200 8N1) and drives the red and green user LEDs on RK1/RK3. It selects PGC2/PGD2 as the debug channel. The SST26VF032B serial flash on SPI1 (dedicated pins, CS on RA1) is exported as /dev/mtdblock0. Its SPI frequency is set to 20 MHz: the SST26 driver's 64 MHz default is above PBCLK3/2 (25 MHz), which pic32mz_spi.c does not handle. mips-debug.ld is used with every toolchain. It has no OUTPUT_FORMAT, because XC32 and Pinguino name their little-endian ELF targets differently; the board passes -EL to the linker instead. With XC32 the board builds with -mno-dsp -mno-dspr2: NuttX does not enable or save the DSP ASE state. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Daniel P. Carvalho <danieloak@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 | ||
| .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.