¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. SHARI
  2. Topics

Intermittent serial port connectivity to SA818 on a Pi 5 #Allstar_Setup #SA818-prog

 

I am getting snagged up with some intermittent serial port connectivity to the SA818 module on a Pi 5 with:
?
"Linux allstar 6.6.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux"
"Model ? ? ? : Raspberry Pi 5 Model B Rev 1."
?
using the basic sa818 program (), which is used by sa818-menu.
I see this (below) when issuing a simple command to query the firmware version of the device. The program flops back an forth from successful to an error. I have "console=ttyAMA0,115200" at the end of /boot/firmware/cmdline.txt, and dtparam=uart0 dtoverlay=disable-bt set in /boot/firmware/config.txt. Could the problem be that my soldering on the TP68 or TP69 "pins" is less than ideal, or could this be from something else? An aside, ttyAMA0 is never symlinked to /dev/serial0, but ttyAMA10 is, i.e., /dev/serial0 -> ttyAMA10.
?
Any pro tips would be appreciated.
?
?
Examples:
?
root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff5267b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818:?
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff9bb2b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: WARNING: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff7b65b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
+DMOERRORBUG: Port /dev/ttyAMA0 not SA818: D
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7ffed2b3b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff5568b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: INFO: Firmware SA818, version: V5.5_MM
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff2458b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff7bdfb940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: INFO: Firmware SA818, version: V5.5_MM
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff8810b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff7e84b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: INFO: Firmware SA818, version: V5.5_MM
?
?
?
?
 

Please refer to this document in the Files section of this group.
?
?
When programming the SA818 on a SHARI PiHat or PiZero, the UART on the Pi is used.? It connects to the SA818 via pins 8 and 10 of the Pi GPIO connector.? Normally, the UART on the Pi is not connected to pins 8 and 10.? This can be changed by modifying config.txt.? ASL3 gets the required changes right for everything but the Pi5 (but be sure to do updates and then reboot).
?
The Pi5 must be configured differently for ASL3. For a Pi5, the file config.txt located in /boot/firmware/ must be modified by deleting dtoverlay=disable-bt
and adding dtparam=uart0?
?
For all Pi's, with the proper setting in config.txt, the serial port becomes /dev/ttyAMA0 (not ttyAMA10).? The connection to the Pi UART using the JST connector (red/black cable) goes to the CM108B and is used for Allstar.? It is not used to program the SA818.
?
Steve - N8AR
 

Thanks for the info. I have ensured that dtparam=uart0 is indeed set, and dtoverlay=disable-bt is no longer present in /boot/firmware/config.txt, rebooted the unit, but doing a simple query between for the firmware version of the SA818 still alternates between a success and an error state. This is not a huge deal, it is just annoying as it can cause snags elsewhere.
?
Example after updating config.txt and rebooting:
root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff1b4ab940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fffbb4eb940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: DEBUG: version reply +VERSION:SA818_V5.5_MM
SA818: INFO: Firmware SA818, version: V5.5_MM
?
?
These commands were run several seconds apart.
?
Any other ideas?
?
 

¿ªÔÆÌåÓý

Cold solder joint on the serial pins on the device or could be a defective SA818.

?

-Michael

?

From: [email protected] [mailto:[email protected]] On Behalf Of chroot via groups.io
Sent: Wednesday, December 18, 2024 1:26 AM
To: [email protected]
Subject: Re: [SHARI] Intermittent serial port connectivity to SA818 on a Pi 5 #Allstar_Setup #SA818-prog

?

Thanks for the info. I have ensured that dtparam=uart0 is indeed set, and dtoverlay=disable-bt is no longer present in /boot/firmware/config.txt, rebooted the unit, but doing a simple query between for the firmware version of the SA818 still alternates between a success and an error state. This is not a huge deal, it is just annoying as it can cause snags elsewhere.

?

Example after updating config.txt and rebooting:

root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff1b4ab940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error

?


root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fffbb4eb940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: DEBUG: version reply +VERSION:SA818_V5.5_MM
SA818: INFO: Firmware SA818, version: V5.5_MM

?

?

These commands were run several seconds apart.

?

Any other ideas?

?
 

I had intermittent issues with my serial interface to the SHARI on a PI 4. Some writes would work but other read/write failed to verify/ indicate success.?

Discovered my power supply to the PI was sub par. Could not deliver enough power. Replaced with a larger supply and all worked consistently thereafter.?

Brooks

On Thu, Dec 19, 2024 at 14:04 chroot via <chroott=[email protected]> wrote:
Thanks for the info. I have ensured that dtparam=uart0 is indeed set, and dtoverlay=disable-bt is no longer present in /boot/firmware/config.txt, rebooted the unit, but doing a simple query between for the firmware version of the SA818 still alternates between a success and an error state. This is not a huge deal, it is just annoying as it can cause snags elsewhere.
?
Example after updating config.txt and rebooting:
root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fff1b4ab940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR
Connection error
?

root@allstar:# sa818 --debug --port /dev/ttyAMA0 ?version
SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version')
SA818: DEBUG: Serial<id=0x7fffbb4eb940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False)
SA818: DEBUG: Sending: AT+DMOCONNECT
SA818: DEBUG: Sending: AT+VERSION
SA818: DEBUG: version reply +VERSION:SA818_V5.5_MM
SA818: INFO: Firmware SA818, version: V5.5_MM
?
?
These commands were run several seconds apart.
?
Any other ideas?
?
 

Everything is working well now, and my node is being used. I am uncertain how the intermittent issue resolved itself. Note that dtparam=uart0 is definitely needed, but I still had issues even after I set this parameter and rebooted. Perhaps having the node on for a while and allowing the? electronics heat up a bit (?expansion?) helped. I'm not sure. I am very happy with my setup but I may buy another hat and SA181 chip and try again in the future. Also note that I had to always ignore the serial0 tty and use ttyAMA0 directly as serial0 will always point to ttyAMA10...?
 

Hi,
?
I found two different pieces of information about the correct setup serial port for SA818 on RPI 5 for ASL3 when we use PiHat board
?
?
Step 4. SHARI PiHat 52Pi/Pi5 Setup
You must use the Allstar Link ASL3 image for the Pi5.
We recommend you follow the setup procedure shown in the following YouTube video.
https://www.youtube.com/watch?v=aeuj-yI8qrU
There is one change required for the Pi5. In order for the Pi5 to program the SA818S using the
Pi5 UART, the file /boot/firmware/cmdline.txt must be modified by adding
console=serial0,115200 to the end of the current line in the file.
So the file contents become the single line (Note-number after PARTUUID will differ):
console=tty1 root=PARTUUID=2f611b54-02 rootfstype=ext4 fsck.repair=yes rootwait console=serial0,115200
After modifying the file, reboot the Pi and ttyAMA0 will be available.?
?
?
Also, for a Pi5, the file config.txt located in /boot//firmware must be modified by deleting dtoverlay=disable-bt
and adding dtparam=uart0 (located at the end of the file)
?
My question is whether to make both changes, i.e. in cmdline.txt and config.txt or one of them to have access on PI 5 via /dev/ttyAMA0 to SA818 on GPIO14/15
?
73 Waldek
?
 

The second document is correct for ASL3.
?
?
Steve - N8AR
 

Steve

Thanks for the answer and I understand that I don't have to enter the console=serial0,115200 line for Pi5 in cmdline.txt,
just modify config.txt by deleting dtoverlay=disable-bt and adding dtparam=uart0 (located at the end of the file)
?
Waldek

1 - 9 of 9