For some reason in Raspbian (Jessie) /dev/ttyAMA0 always boots with the following permissions:
ls -l /dev/ttyAMA0
crw--w---- 1 root tty 204, 64 Jun 1 21:10 /dev/ttyAMA0
I need group tty to have read access, so emulating this solution I tried adding a root crontab job:
@reboot chmod 660 /dev/ttyAMA0
Which appears to either have no effect or is reverted immediately. Grateful for any tips.
The following will ensure read access, but changes group from tty to dialout.
sudo systemctl mask [email protected]
And on reboot we have:
# ls -l /dev/ttyAMA0
crw-rw---- 1 root dialout 204, 64 Jun 2 11:29 /dev/ttyAMA0
I've been advised that to do this you should also consider stopping any kernel console logging going out the serial port, which can be achieved by removing console=serial0,115200 from file /boot/cmdline.txt.
Any comment on any unintended implications of this method would be appreciated.
systemctl mask command. This would make sense as there's a need to protect kernel logs. The kernel console logging can also be disabled via raspi-config - namely in the interfacing options (this does exactly the same as removing the console=... section from /boot/cmdline.txt
Commented
Mar 15, 2022 at 2:36
You could always add:
chmod 660 /dev/ttyAMA0
to the /etc/rc.local file. As rc.local is executed with root privileges it should work.
I don't know why the permissions are wrong.
Until they are corrected use the following in the root crontab.
@reboot (sleep 30; chmod 660 /dev/ttyAMA0)&
For my RPi 3 Model B, I used geotheory's solution (sudo systemctl mask [email protected]) for /dev/ttyS0 and it was the cure to my problem of flaky serial communication. Characters were dropping and the connection was timing out frequently. Now it's solid.
