According to the Dexter GrovePi docs on GitHub, I can execute the line below in the Linux Terminal to add support for GrovePi to a Pi4 running a non-RaspianForRobots Linux distro:
curl -kL dexterindustries.com/update_gopigo | bash
However, it errors out when I run it on ym Pi4 running Ubuntu 20.04.
Is this not yet functional? If so, will it be eventually?
Thanks!
What specific errors did you see? Ā That is important information that will help us help you track down the specific problem.
Heya!
Hereās the terminal text I got when I tried to execute the upgrade:
ubuntu@ubuntu:~$ curl -kL dexterindustries.com/update_gopigo | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 250 100 250 0 0 1059 0 --:--:-- --:--:-- --:--:-- 1059
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 11096 100 11096 0 0 11357 0 --:--:-- --:--:-- --:--:-- 48243
id: āpiā: no such user
main: line 24: [: 1000: unary operator expected
Welcome to GoPiGo Installer.
Updating GoPiGo for master branch with the following options:
--no-dependencies=false
--no-update-aptget=false
--bypass-rfrtools=false
--bypass-python-rfrtools=false
--bypass-gui-installation=false
--user-local=false
--env-local=false
--system-wide=true
Using "master" branch
Options used for RFR_Tools script: "--system-wide master --use-python3-exe-too --update-aptget --install-deb-deps --install-python-package --install-gui"
main: line 162: /home/pi/.tmp_rfrtools.sh: No such file or directory
Installing RFR_Tools. This might take a while..
bash: /home/pi/.tmp_rfrtools.sh: No such file or directory
rm: cannot remove '/home/pi/.tmp_rfrtools.sh': No such file or directory
RFR_Tools failed installing with exit code 127. Exiting.
ubuntu@ubuntu:~$
You say youāre trying to load software for GrovePi but youāre running the install script for GoPiGo.
Try:
curl -kL dexterindustries.com/update_grovepi | bash
I donāt see where it says this will work with āa non-RaspianForRobots Linux distroā.
more info here: https://github.com/DexterInd/GrovePi
and here: https://github.com/DexterInd/GrovePi/blob/master/Script/README.md
-Kevin
My understanding is that if you have any recent version of plain-vanilla Raspbian, it will (should) work. If not, post here and at-mention cleoqc.
Thanks for the feedback, folks. And duh on me for missing that package name.
Iāll try it on a current Raspian build soon then.
I too am having problems seeing the grovepi on my raspberrypi4 running ubuntu 20.04.
The i2c_bcm2708 kernel module is loaded, an i2c device exists at /dev/i2c-1 and i2cdetect correctly lists my i2c bus which is 1.
The command āsudo i2cdetect 1ā shows no devices connected, I was expecting to see the grovepi at address 0x04.
Note that the scripts in the GrovePi repo donāt work with the same errors as above i.e there is no ā/home/piā directory, āpiā user etc. as this is not raspbian. I could hack these maybe to overcome this but Iām not sure this will help at the mo.
Note using raspbian or any variant of it is not an option for me.
Steve,
Short answer:
You may be hosed.
Longer answer:
Though you may be hosed, you might be able to work around it.
As far as I know, (based on my reading the posts made by those more skilled than I), these libraries weāre specifically designed for a Raspbian / Raspbian for Robots environment and there are important dependencies for Raspbian there.
I have also seen posts that talk about using C# and/or C++ libraries with the 'bots, that they exist, but I donāt remember where. Ā You can try snooping the Dexter GitHub repo or searching these fora for posts about alternative libraries.
I understand that there may be real reasons why Raspbian and/or Raspbian for Robots is not desirable. Ā You may, if possible, want to try a first iteration or two using Raspbian, just to verify that things work the way you expect - and then branch out into uncharted territory.
Go ahead and try, see what you can find, and let us know what happens!
P.S.
I am going to mention @Cleoqc and @cyclicalobsessive, they being my go-to wizards. Ā They might remember something Iāve forgotten.
Hi jimrh,
Thanks for the reply, Iāll do as you suggest in that case, Iāll have a good look round the repo to see what I can find, also it wonāt kill me to just put a raspbian image on an sd card and boot from that just to check the board out. Iāve no reason to believe its not working but it might give me some more pointers.
Iāll post back here with my findings.
hello @steve.hamblett,
Is running Raspbian for setup permissible?
You need to make sure your grovepi runs firmware 1.4, and it can only be updated via Raspbian. Once itās updated, you can use Ubuntu. This may be the cause of the device not showing up on the i2cbus. Please, make sure you do see it on Raspbian first. Then we can eliminate that potential issue.
The file you definitely need from the repo is this one:
but go ahead and clone the repo because there may be some drivers also, depending on which sensors/actuators you use in your project. Running setup.py shouldnāt be raspbian dependant although Iām not 100% certain.
OK thanks, yes, I can use raspbian to set this up and then switch to ubuntu,. Iāll get the board working in its native env first as you suggest.
Ok, getting somewhere, on a fresh raspbian install after executing the install script
curl -kL dexterindustries.com/update_grovepi | bash
and rebooting, if I run i2cdetect -l I get
i2c-1 i2c bcm2835 I2C adapter I2C adapter
so i2c is on bus 1, when I scan it I see no devices.
Running the script /home/pi/Dexter/GrovePi/Troubleshooting/complete_test.sh and selecting option 3, the i2c test, I get
Error: Could not open file /dev/i2c-0' or /dev/i2c/0ā: No such file or directory
so it seems to want i2c bus 0, whereas i2c bus 1 has been created.
Iām guessing this is not right. Note option 1 of this script, the software test seems to be OK, the only errror i get is
wiringPi Not Found (ERR)
OK, ubuntu was creating i2c bus 1, hence they are both doing the same.
Bit more
the command python grovepi.py gives
library supports this fw versions: 1.4.0
the command bash firmware_update.sh gives
avrdude: AVR device not responding
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
ā¦ and more ā¦
OK, think were OK now, I added the line
dtparam=i2c_vc=on
to the boot/config.txt on Raspbian, this gave me i2c bus 0, so I now have 12c 0 and 1.
Scanning the buses now shows that the grovepi is on bus 1 as device 0x04, not bus 0 as I expected, but at least it was present. I plugged in some of my i2c grove devices, these were seen correctly again on bus 1.
Updated the firmware as per the instruction in the README, this seemed to work, verified it with the complete_test script in trobleshooting.
Over to Ubuntu, only one i2c bus, bus 1 but the grovepi and my devices were present as on raspbian.
OK, I access my devices through mraaās i2c api, I need to look at this next.
Steve,
On any later version of the Pi, (where ālater versionā means a version with a 40-pin GPIO), i2c buss zero is now dedicated to the HAT IDENT function and is no longer on pins 2 and 3 as before.
On the old, 26 pin devices, pins 2 and 3 were i2c buss 0, because that was all there was - there was no i2c buss 1 then as the hardware didnāt support it.
When the Raspberry Pi Foundation updated things to the 40-pin GPIO, i2c buss 0 was moved to (physical) pins 27 and 28 to handle the IDENT feature of the new HAT specification, and the newly added i2c buss 1 was wired to pins 2 and 3, replacing the i2c connection that used to be there.
So, anything that uses the older 26 pin standard for the GPIO, (and the older versions of Raspbian that ran on them), will have to have the i2c buss ID changed from zero to one when used on newer versions of the Pi and/or newer versions of Raspbian.
For what itās worth, on this page (https://www.dexterindustries.com/GrovePi/get-started-with-the-grovepi/) under ā2. Setup the Softwareā, it still says that you can install the DexterIndustries GrovePi+ add-on software to any Linux distro, as follows ā¦
Advanced users , can, if they choose to, use their own image. If you already have your own flavor of linux running on the Raspberry Pi, you can use our bash script to setup for the GrovePi. Configuring your own image following the steps below:
In the command line type: sudo curl -kL dexterindustries.com/update_grovepi | bash. Restart the Raspberry Pi. sudo reboot. Your SD card now has what it needs to start using the GrovePi!
Iām thinking maybe the post-acquisition DexterIndustries isnāt too concerned with the GrovePi+?
For anyone interested, there is a solution: https://wiki.seeedstudio.com/Grove_Base_Hat_for_Raspberry_Pi.
I have not tried it yet but I know for sure you need a user named pi for the scripts to work (you can remove the user afterwards).
Do you have a pi user?
This would be for the Seeed Base Hat, which is a different product.
Is this documented anywhere? Sounds like this is either missing or needs to be more obvious.
