This is an automated email from the ASF dual-hosted git repository.

xiaoxiang781216 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git

commit 2e0abe6973d9be2894c0af517b5c9fc1b4315914
Author: Matteo Golin <[email protected]>
AuthorDate: Mon Jul 20 21:01:13 2026 -0400

    docs/applications/txmorse: Document the txmorse application
    
    Documents how to use the txmorse application and how it can be extended
    to support other output devices besides the console and GPIO.
    
    Signed-off-by: Matteo Golin <[email protected]>
---
 .../applications/examples/txmorse/index.rst        | 44 ++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/Documentation/applications/examples/txmorse/index.rst 
b/Documentation/applications/examples/txmorse/index.rst
new file mode 100644
index 00000000000..bc655473e7f
--- /dev/null
+++ b/Documentation/applications/examples/txmorse/index.rst
@@ -0,0 +1,44 @@
+==================================
+``txmorse`` Morse code transmitter
+==================================
+
+This application is an example which transmits Morse code messages using the
+:doc:`Morsey library </applications/audioutils/morsey/index>`.
+
+You can run ``txmorse -h`` to display help information.
+
+Supported Devices
+-----------------
+
+.. note::
+
+   This application does not currently support all possible Morse code
+   transmission devices available on NuttX NuttX. Currently, only GPIO devices
+   are supported.
+
+In order to add support for a new output device, you must submit a patch
+modifying the program to define the interface for the Morsey library for each
+type of output device. Take a look at the current application code to see
+examples for console devices and GPIO devices.
+
+The ``txfunc`` function is used by the ``morsey`` library to transmit a mark.
+You can implement the appropriate driver operations (i.e. ``ioctl`` calls) in
+this function. See the GPIO implementation for an example.
+
+The ``cleanupfunc`` function is used to cleanup the implementation. For most
+NuttX devices, this involves closing the file descriptor.
+
+In the ``main`` function, the path to the output device is used to identify the
+implementation to use. For instance, GPIO devices are under ``/dev/gpio<n>``, 
so
+device paths containing "gpio" cause the GPIO driver to be selected. If no
+player can be associated with the device, the default player is selected which
+just prints the Morse code to the console.
+
+Usage
+-----
+
+The following will output "SOS" over a GPIO device (i.e. buzzer or LED):
+
+.. code:: console
+
+   nsh> txmorse "sos" /dev/gpio0

Reply via email to