cab92d310d
Add a CDC/ACM (console) + USB fastboot (ADB "fastboot" personality) composite device to the shared rp2040_composite.c board glue, and a new "fastboot_usb" defconfig for waveshare-rp2040-zero and waveshare-rp2040-lcd-1.28. - boards/arm/rp2040/common/src/rp2040_composite.c: add a third composite slot for CONFIG_USBADB (covers both plain ADB and, with CONFIG_USBFASTBOOT, the "fastboot" personality of the same driver) alongside the existing MSC/CDC-ACM slots. While adding this, fixed a latent bug: the CDC/ACM block never advanced ifnobase/ strbase after filling in its own slot, because CDC/ACM used to always be the *last* device in the composite (nothing downstream ever needed the incremented values). Now that a device can follow CDC/ACM, the missing increment caused the fastboot interface to be assigned the same USB interface number as CDC/ACM's control interface (both 0), which the Linux kernel rejects with "Duplicate descriptor for config 1 interface 0 altsetting 0, skipping" and drops the fastboot interface entirely (confirmed via lsusb -v and disassembly of the generated board_composite_connect() code). - boards/arm/rp2040/waveshare-rp2040-zero/configs/fastboot_usb and boards/arm/rp2040/waveshare-rp2040-lcd-1.28/configs/fastboot_usb: new defconfig booting directly into fastbootd (CONFIG_INIT_ENTRYPOINT="fastbootd_main", no nsh) which brings up the CDC/ACM + fastboot composite via CONFIG_SYSTEM_FASTBOOTD_USB_BOARDCTL as soon as fastbootd starts, so the CDC/ACM sub-interface still provides a console for boot/ fastbootd log visibility without requiring a wired UART, while the fastboot vendor interface is what `fastboot devices`/`getvar` talk to. Assisted-by: OpenCode:claude-sonnet-5 Signed-off-by: wangjianyu3 <wangjianyu3@xiaomi.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.