597fc8c93b
The shared CMake build hardcoded a single ROM symbol linker script (ameba_rom_symbol_acut_s.ld), so a CMake build of rtl8721f failed to link: __rom_bss_start_ns__ / __rom_bss_end_ns__ and the rtw_* WiFi ROM symbols were left undefined. The make build already appends rtl8721f's four ROM symbol scripts (secure + wifi + os + NS) in arch/arm/src/rtl8721f/ameba_board.mk; the CMake path did not. Make the ROM symbol script set per-IC: - ameba_gen_ldscript.sh now takes one or more ROM ld files as trailing arguments and cat's them in order (was a single fixed argument). - ameba_board.cmake keeps the previous single-script default and lets an arch CMakeLists override it via AMEBA_ROM_LDS; the list is resolved to full paths and passed to the generator. - rtl8721f/CMakeLists.txt sets AMEBA_ROM_LDS to its four ROM symbol scripts, matching its ameba_board.mk cat order. rtl8721dx and rtl8720f are unchanged (still the single default script). Verified on rtl8721f: the nsh CMake build now links the nuttx ELF cleanly with no undefined NS-BSS or rtw_* symbols. Signed-off-by: dechao_gong <dechao_gong@realsil.com.cn> Assisted-by: Claude <noreply@anthropic.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.