-
Notifications
You must be signed in to change notification settings - Fork 85
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
Run GoPiGo3 w/ RHEL/CentOS/Fedora IoT? #320
Comments
Hello there and welcome back! Of the top of my head, you need to make sure SPI and I2C are active. Lately the GoPiGo3 uses pigpiod which may not be available on other distros so you would need some changes in gopigo3.py The import : https://github.com/DexterInd/GoPiGo3/blob/master/Software/Python/gopigo3.py#L30 And these setup lines And this install script: Lines 47 to 51 in 7652f5b
You won't need any of the tools that are tailored to beginners and that saves a lot of hassle. Instead of running the install script, you can go ahead and run
I think it will work... |
@slowrunner has been able to install it on Ubuntu, he may have some words of wisdom. |
Slowrunner, (also known as "cyclicalobsessive" on the forum), has done a considerable body of work on this exact subject - getting Dexter Industries GoPiGo software to work on other platforms. Please check his work on the Dexter forums at https://forum.dexterindustries.com One possible kicker: Please go to the forums, post your question there too, and if you try this with any non-Debian based release, let us know what worked and what didn't. One other thing: Thanks! |
@goetzrieger These are my steps to install the basic GoPiGo3 API and supporting configuration on Ubuntu 20.0.4:
|
One thing that is implicit in all of this is that there is a hard dependency on the "pi" user as the primary, (default), user. This is a known "issue" based on the fact that the GoPiGo libraries were originally designed to be installed over a stock Raspbian install where the default username was "pi". This is known and there are plans to fix this - I don't know if or when. The "pi" user should also be in the sudoers file and in the wheel group to make sure it can do whatever you need it to do. References to raspi-config do not apply to non Raspbian based systems, AFAIK. One other note: =============== Question: I know of Pidora, (and some RISC based stuff and maybe Arch), but things like Red Hat, Slackware, CentOS, etc - I don't know. Which specific distributions are you talking about? (links please!) It might be interesting to try installs on a GoPiGo-3 and see what happens. |
Wow, good to see there is a really active community around! Even after this Covid-induced time of very little in-person events. But I‘m really eager going back running Robot Hackathons now. And @CleoQc, I very well remember how you helped out with faulty boards on short notice to rescue one of our event in 2019. Okay. From what I understand there is an „old-style“ sysfs interface to GPIO that is deprecated since Kernel 4.8 or so and the new /dev/gpiochip* interface. Most modern distros are starting to use the new interface, notably Fedora-based ones. https://embeddedbits.org/new-linux-kernel-gpio-user-space-interface/ So on Fedora the old sysfs-style interface is not enabled in the kernel and pigpiod is not available. Nicole mentioned above Gopigo3 Python libs are using pigpiod now which I understand is using the sysfs interface. Does that mean there is a lot of work in porting the gopigo3 libs/API to the new interface? The library is called libgpiod and has Python bindings, too. I’m being a bit verbose because I‘m pretty new to this stuff and this would put a stop on my experiment already. |
@jharris1993 Fedora is kind of the upstream community project to our Red Hat Enterprise Linux. We are moving fast into the „Edge“ use cases so Fedora and in the newest version RHEL are able to run on ARM as found in lots of IoT devices. https://docs.fedoraproject.org/en-US/quick-docs/raspberry-pi/ My main target for our GopiGo’s is Fedora IoT which is running on Raspi quite well and is a great foundation for deploying containerized applications. https://getfedora.org/en/iot/ This would e.g. allow us to run the Gopigo libs in a container and maybe something like a Tensorflow-lite based image recognition application in another one on the robot. But first I‘ve got to get the robot running with Fedora. |
Hi there:
Is it feasible or does anybody has experience running the GoPiGo3 with a non-Debian Linux distro like in $SUBJECT?
Background: We have a small fleet of GoPiGo3's (around 15) we used to run event workshops for our (Red Hat, that is) developer line of products. Until, well, Covid came along. So it's been 2.5 years and we would like to revive this, but would like to brush up our game:
All of this requires one of the above distros running and probably a raspi 4 and something like a Google Coral TPU stick.
Before I start digging into the setup scripts and hitting roadblocks any help would be appreciated!
The text was updated successfully, but these errors were encountered: