From: Ugo Poddine <ugop@libero.it>
To: linux-hams@vger.kernel.org
Subject: Re: RaspberryPI and soundmodem PTT
Date: Fri, 5 Dec 2014 14:44:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20141205T151705-771@post.gmane.org> (raw)
In-Reply-To: CAGZkoWSzzbMK5nd0ySzL2frcoOt6FAHP9X5SNZO9KsF=yGe44w@mail.gmail.com
Hi everybody,
There is also a different cheaper solution.
a) detach the serial console output from the UART pins of the gPIO board, as
described in several RasperryPI documentation (google can find) : basically
editing the /boot/cmdline.txt startup file...
b) modify, using a text editor (not the soundmodemconfig utility !), the
soundmodem.conf file, setting /dev/ttyAMAO as PTT interface
c) run soundmodem as usual : it will direct the PTT signal on the CTS0 pin
of the UART.
d) the CTS0 pin can be actually (RaspberryPI B+) associated to the GPIO pin
17 (BCM mode)when the pin mapping it's set in ALT3 MODE. The "ALT mode"
(alternative pin mapping matrix in the RaspberryPI) switch can be easily
made by different utilities (for example small "to be compiled" functions
like gpio_alt.c, or alternative Python libraries like "pigpio library" or
other, at the moment it's not managed by standard Python RPi.GPIO libraries
). It's then required to create a small script (Python or bash, able to
switch off SAMBA, sets the GPIO17 in ALT3 mode and finally executes
soundmodem : doing this the GPIO17 can easily drive one of the classic PTT
interfaces without need of heavy and expensive RS232-to-USB HW interfaces.
Enjoy
Ugo Poddine
prev parent reply other threads:[~2014-12-05 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 7:23 RaspberryPI and soundmodem PTT Waldek
2013-09-25 7:27 ` marius
2013-09-26 2:48 ` David Ranch
2013-09-26 5:22 ` Marius Petrescu
2013-09-26 5:34 ` Ray Wells
2013-09-26 6:15 ` Andrew Errington
2014-12-05 14:44 ` Ugo Poddine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20141205T151705-771@post.gmane.org \
--to=ugop@libero.it \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox