cc77be145a
rp2040_epread() armed the DPSRAM buffer-control register with the full usbdev request length. That length is only correct for requests no larger than the buffer-control LEN field, which is 10 bits wide (max 1023 bytes). Class drivers that post larger read requests -- e.g. cdcncm allocates a 16 KiB NTB read buffer -- overflow LEN: 16384 & 0x3ff is 0, and the high bits corrupt the neighbouring control flags. The controller then sees a zero-length available buffer and completes the transfer immediately with zero bytes, over and over, so no OUT data is ever received (cdcncm floods "Wrong NTH SIGN, skblen 0"). The receive path already accumulates a request across multiple packets: rp2040_rxcomplete() copies each packet, advances xfrd and re-arms via rp2040_rdrequest() until the request is satisfied or a short packet arrives. So the buffer only ever needs to be armed for a single maximum-size packet. Clamp nbytes accordingly. This matches the transmit path, which already chunks to ep.maxpacket in rp2040_wrrequest. Bulk classes with small reads (cdcacm, usbmsc) were unaffected because their request lengths already fit in LEN, which is why the defect only showed up on cdcncm. Validated on raspberrypi-pico (RP2040): a CONFIG_NET_CDCNCM device that previously received nothing now passes traffic in both directions with 0% packet loss. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AHJRvWeBMTHwzpwjaUg4HW Signed-off-by: Ricard Rosson <ricard@groundbits.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.