Use rpmsg_send_offchannel_raw to fix stuck issue avoid getting stuck when remote destroy ept. When send messages from ap to android in Rptun thread, Android may have sent NS_DESTROY through rpmsg_port and changed ept->dst to RPMSG_ADDR_ANY in rpmsg_port_ns_callback; So rptun thread may be stuck at this time because rpmsg_send detected dst_ept's dst_addr is RPMSG_ADDR_ANY. rpmsg_virtio_thread(rptun audio): rpmsg_virtio_rx_callback -> rpmsg_router_cb -> rpmsg_send(dst_ept) send to android rpmsg_port_thread (android send NS_DESTROY): rpmsg_port_ns_callback -> dst_ept->dest_addr = RPMSG_ADDR_ANY Signed-off-by: yintao <yintao@xiaomi.com>
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.
