d0a86138ce
In RS-485 mode the DIR (DE) pin was only released on TX_BRK_IDLE_DONE. That interrupt is part of the UART break feature (UART_TXD_BRK), which this driver never enables, so it does not fire after normal data: DIR stayed asserted after the first transmit and the port never received again. TX_DONE is the right event, but the upper half calls txint(false) as soon as its software buffer is empty, while the last bytes are still in the FIFO (see #15888), so it has to outlive txint(false): * txint(false) keeps TX_DONE enabled on an RS-485 port. * On TX_DONE with the software buffer and TX FIFO empty, the handler waits (bounded) for the transmitter to go idle, releases DIR and disables TX_DONE. * txempty() uses uart_hal_is_tx_idle() (FIFO count and FSM state). The raw TXFIFO_EMPTY bit only means the FIFO is below its empty threshold, so tcdrain() could return with data still in the FIFO. Same approach as the ESP32-S3 fix in #20389. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Erik Englund <erik.englund@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 | ||
| .mcp.json | ||
| .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.