Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with TTY with RPI 3 / Debian Jessie DV-Mega #85

Closed
majorgearhead opened this issue Mar 21, 2016 · 3 comments
Closed

Issues with TTY with RPI 3 / Debian Jessie DV-Mega #85

majorgearhead opened this issue Mar 21, 2016 · 3 comments

Comments

@majorgearhead
Copy link

I have successfully compiled the DStarRepeater and ircDDBGateway code on my RPI 3 with fresh Raspbian (Debian Jessie) installed. I am running into a bit of a TTY issue. I understand that with the NEW HW ttyAMA0 is being utilized by the Bluetooth modules. Seems like GPIO is assigned ttyS0, which has a getty setup on it. Here is what I did to be able to communicate with my DV-Mega (Disable this getty unit):
sudo systemctl stop serial-getty@ttyS0.service
sudo systemctl disable serial-getty@ttyS0.service
sudo systemctl mask serial-getty@ttyS0.service

This was enough to get it communicating with the board. My issue is this. ircDDBGateway connects to DstarRepeater and also out to the various services. I can issue remote commands and it links, however it will not send RF. I know this is more a dev thread and not a support thread, but has anyone been able to compile this on an RPI Under Debian Jessie and have it work with the DV-MEGA?

@majorgearhead
Copy link
Author

Looks like things work when I disable all of bluetooth and use the ttyAMA0 as normal. Testing clean right now to make sure of this.

@johnhays
Copy link
Collaborator

That is correct ... bluetooth must be disabled to use the GPIO serial port.

On Thu, Mar 24, 2016 at 9:17 AM, majorgearhead notifications@github.com
wrote:

Looks like things work when I disable all of bluetooth and use the ttyAMA0
as normal. Testing clean right now to make sure of this.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#85 (comment)


John D. Hays
K7VE

PO Box 1223, Edmonds, WA 98020-1223
http://k7ve.org/blog http://twitter.com/#!/john_hays
http://www.facebook.com/john.d.hays

@majorgearhead
Copy link
Author

Thanks for the confirmation. In case anyone else is interested, here is how I disabled it:

sudo systemctl stop bluetooth
sudo systemctl stop hciuart
sudo systemctl disable bluetooth
sudo systemctl disable hciuart

Then I added the following to /boot/config.txt

dtoverlay=pi3-disable-bt

Then I removed the console=serial0,115000 line from /boot/cmdline.txt

Everything works great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants