a271b641a5
The packet memory area (PMA) accessors in the M0 USB device driver were carried over from the STM32F1 implementation, where the PMA is seen by the CPU as 16-bit values placed on 32-bit boundaries. On the STM32F0, STM32L0 and other M0 parts the PMA is a linear 16-bit memory, so the F1 scaling is wrong: - STM32_USB_BTABLE_RADDR() shifted the computed buffer descriptor offset left by one, addressing every second descriptor entry. - The buffer descriptor accessors declared the descriptor entries as uint32_t and accessed them 32 bits at a time, so each write clobbered the adjacent entry. - stm32_copytopma() and stm32_copyfrompma() scaled the PMA offset by two when computing the packet buffer address. The result is that endpoint buffer descriptors and packet data are written to the wrong offsets in packet memory, and no transfer completes correctly. Drop the F1 scaling and use 16-bit accesses throughout. Note that the sibling stm32_usbfs.h defines STM32_USB_BTABLE_RADDR() without the shift already, so this brings the M0 header in line with it. Assisted-by: GitHub Copilot:claude-opus-5 Signed-off-by: jsanchez-2g <jsanchez@2g-eng.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.