-
Notifications
You must be signed in to change notification settings - Fork 150
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
Serial done better #187
base: master
Are you sure you want to change the base?
Serial done better #187
Conversation
…imary serial device (miniUART)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look straightforward, I'll sign off on them
Sharing my learnings from diving into getting bluetooth to work on the RPi 4. In fact I had to disable bluetooth altogether in the
which looks like how it was before, but this time we're doing it 'the right way'. I'm giving up on bluetooth in the short term, might try again with the RPi5 since that doesn't have the miniUART anymore. It would be good for someone to give this PR a test just to make sure this works fine. I need to add instructions for adding the disable bluetooth overlay. |
@@ -24,7 +24,7 @@ | |||
print(roboclaw0.ReadVersion(address)) | |||
print(roboclaw0.ReadEncM1(address)) | |||
elif connected1: | |||
print("Connected to /dev/serial1.") | |||
print("Connected to /dev/serial1. Only proceed if you know what you're doing, otherwise ask for help on Slack.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whats this slack?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simplified instructions for serial comms setup and switch to using primary serial device (miniUART).
Before this PR, the setup caused the serial device chain to look like this:
which is not the recommended approach. After, it will look like:
When set up correctly using
raspi-config
, there should be no need for udev rules or/boot/firmware/config.txt
hacking.