8c94a72657
The rp2350 executes in place from external QSPI flash, and a NuttX image normally leaves most of that flash unused. This exposes the unused region as an MTD device so it can carry a filesystem, mirroring what the rp2040 port already provides with rp2040_flash_mtd.c. The region is given by RP23XX_FLASH_MTD_OFFSET and RP23XX_FLASH_MTD_SIZE, both multiples of the 4096 byte erase sector. Initialization fails rather than corrupting the running image if the region would overlap the NuttX binary, checked against __flash_binary_end. Erase and program use the bootrom flash routines. Those stall instruction fetch from the same flash, so they run from SRAM with interrupts disabled and, on SMP builds, the other core parked; afterwards the QSPI interface is returned to execute-in-place mode. By default that restores the fast read mode the bootrom configured at boot; RP23XX_FLASH_MTD_SAFE_XIP instead always uses the bootrom flash_enter_cmd_xip routine, which is slower to execute from but depends only on the documented bootrom entry point. The driver answers BIOC_XIPBASE with the memory-mapped address of the region, so a filesystem supporting execute in place can hand out real flash pointers rather than copying into RAM. The common board bringup registers the device as /dev/rpflash. Assisted-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Marco Casaroli <marco.casaroli@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.