Page 2 of 3
Re: Revpi Core3 DO failure
Posted: 10 Dec 2020, 14:17
by RR4711
Also: is there an official changelog on what has changed in the FW?
And: I noted that there is less FWU files in /lib/firmware/revpi than on my other systems. Were some modules left out in the Debian package?
Markus
Re: Revpi Core3 DO failure
Posted: 10 Dec 2020, 15:27
by dirk
Hi Markus,
Will there also be an updated Kernel?
Yes, we're planing to release the Buster RevPi image in January 2021.
The latest updates between the Images are always available in our
Git Hub repositories Kernelbakery and ImageBakery.
Also: is there an official changelog on what has changed in the FW?
And: I noted that there is less FWU files in /lib/firmware/revpi than on my other systems. Were some modules left out in the Debian package?
Thank you for your notice we will check this and respond you as soon as posible.
Re: Revpi Core3 DO failure
Posted: 10 Dec 2020, 15:32
by RR4711
dirk wrote: ↑10 Dec 2020, 15:27
Yes, we're planing to release the Buster RevPi image in January 2021.
Excellent!
I meant more a changelog for the firmware running on the modules.
Thank you for your notice we will check this and respond you as soon as posible.
Thanks.
Re: Revpi Core3 DO failure
Posted: 11 Dec 2020, 08:49
by LuukvanLoon
c.baumann wrote: ↑10 Dec 2020, 10:19
Hello,
firmware updates for the AIO, DIO, DI and DO are now available.
Update the revpi-firmware package and follow the instructions for
Connect and
Core .
Hello,
Thank you for the quick service!
Could you please tell me what the latest firmware version is? I have followed
this guide, and the RevPi tells me that no new firmware is installed and that V1.4 >= V1.3. Could it be possible that I can not download the latest firmware when i follow the steps in the guide?
I've tested the application agian and with V1.4 the same fault occurs.
With kind regards,
Luuk.
Re: Revpi Core3 DO failure
Posted: 11 Dec 2020, 16:02
by RR4711
Hi,
the DIO version should be V1.5 after updating, and AIO is updating to V1.4:
Code: Select all
pi@hoxaxispi ~/devel/src/bin(feature/KunbusArmAxis)$ piTest -d
Found 4 devices:
Address: 0 module type: 105 (0x69) RevPi Connect V1.0
Module is present
input offset: 291 length: 6
output offset: 297 length: 5
Address: 31 module type: 96 (0x60) RevPi DIO V1.5
Module is present
input offset: 178 length: 70
output offset: 248 length: 18
Address: 30 module type: 103 (0x67) RevPi AIO V1.4
Module is present
input offset: 89 length: 20
output offset: 109 length: 4
Address: 29 module type: 103 (0x67) RevPi AIO V1.4
Module is present
input offset: 0 length: 20
output offset: 20 length: 4
Markus
Re: Revpi Core3 DO failure
Posted: 12 Dec 2020, 15:56
by LuukvanLoon
RR4711 wrote: ↑11 Dec 2020, 16:02
Hi,
the DIO version should be V1.5 after updating, and AIO is updating to V1.4:
Markus
Hello Markus,
When i follow the steps in the guide i get the following result:
Code: Select all
pi@RevPi40427:~ $ sudo apt-get update
Fetched 267 kB in 54s (4,851 B/s)
Reading package lists... Done
pi@RevPi40427:~ $ sudo apt-get install revpi-firmware
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
pi@RevPi40427:~ $ piTest -f
firmware is up to date: 1.4 >= 1.3
pi@RevPi40427:~ $ piTest -d
Found 2 devices:
Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present
input offset: 0 length: 6
output offset: 6 length: 5
Address: 32 module type: 96 (0x60) RevPi DIO V1.4
Module is present
input offset: 11 length: 70
output offset: 81 length: 18
Is there any other way to upgrade the firmware, beacuse it looks like this doesn't work.
Luuk
Re: Revpi Core3 DO failure
Posted: 12 Dec 2020, 17:48
by RR4711
LuukvanLoon wrote: ↑12 Dec 2020, 15:56
When i follow the steps in the guide i get the following result:
Code: Select all
pi@RevPi40427:~ $ sudo apt-get update
Fetched 267 kB in 54s (4,851 B/s)
Reading package lists... Done
pi@RevPi40427:~ $ sudo apt-get install revpi-firmware
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
pi@RevPi40427:~ $ piTest -f
firmware is up to date: 1.4 >= 1.3
pi@RevPi40427:~ $ piTest -d
Found 2 devices:
Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present
input offset: 0 length: 6
output offset: 6 length: 5
Address: 32 module type: 96 (0x60) RevPi DIO V1.4
Module is present
input offset: 11 length: 70
output offset: 81 length: 18
Is there any other way to upgrade the firmware, beacuse it looks like this doesn't work.
Luuk
Are you still on the old distri and not on stretch? I wonder about the "5 not updated"
can you try
Code: Select all
sudo apt-get update
sudo apt-get upgrade
and post the output here?
When I do a
Code: Select all
pi@sulfurpi ~$ sudo dpkg --list rev*
I get:
Code: Select all
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii revpi-firmware 1:1.4 all Revolution Pi firmware
ii revpi-repo 1.0.4stretch all Revolution Pi package repository
ii revpi-tools 1.0.12-1 armhf Revolution Pi tools
ii revpi-wallpape 1.0.0-2 all Revolution Pi Wallpaper
ii revpi-webstatu 1.2.10 all Revolution Pi Web Status
ii revpi7 1.0.3-1 all Adapter between piControl and Sie
You should get similiar results.
Can you post the output of
as well?
Also make sure you attach only one Module at a time to the Pi when updating.
Markus
Re: Revpi Core3 DO failure
Posted: 13 Dec 2020, 13:41
by LuukvanLoon
Hello Markus,
Are you still on the old distri and not on stretch? I wonder about the "5 not updated"
What do you mean with old distri or stretch? I have just purchased a new RevPi Core.
can you try
Code: Select all
sudo apt-get update
sudo apt-get upgrade
and post the output here?
I have tried it and this is the output:
Sudo apt-get update
Code: Select all
pi@RevPi40427:~ $ sudo apt-get update
Hit http://packages.revolutionpi.de jessie InRelease
Get:1 http://mirrordirector.raspbian.org jessie InRelease [15.0 kB]
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://repository.teamviewer.com stable InRelease
Hit http://packages.revolutionpi.de jessie/main armhf Packages
Hit http://packages.revolutionpi.de jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Ign http://packages.revolutionpi.de jessie/contrib Translation-en_GB
Ign http://packages.revolutionpi.de jessie/contrib Translation-en
Ign http://packages.revolutionpi.de jessie/main Translation-en_GB
Ign http://packages.revolutionpi.de jessie/main Translation-en
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Hit http://repository.teamviewer.com stable/tvrevpi armhf Packages
Ign http://repository.teamviewer.com stable/tvrevpi Translation-en_GB
Ign http://repository.teamviewer.com stable/tvrevpi Translation-en
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Fetched 15.0 kB in 48s (308 B/s)
Reading package lists... Done
Sudo apt-get upgrade
Code: Select all
pi@RevPi40427:~ $ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
coinor-libcbc3 coinor-libcgl1 coinor-libclp1 coinor-libcoinmp1 coinor-libcoinutils3 coinor-libipopt1 coinor-libosi1
libaudiofile1 libboost-atomic1.55.0 libboost-date-time1.55.0 libboost-filesystem1.55.0
libboost-program-options1.55.0 libboost-regex1.55.0 libboost-system1.55.0 libboost-thread1.55.0 libclucene-contribs1
libclucene-core1 libcolamd2.8.0 libeot0 libexttextcat-2.0-0 libexttextcat-data libffi5 libglew1.10 libgltf-0.0-0
libgmime-2.6-0 libgpgme11 libhsqldb1.8.0-java libhyphen0 liblangtag-common liblangtag1 liblockfile-bin liblockfile1
libmhash2 libmumps-seq-4.10.0 libmythes-1.2-0 libneon27-gnutls liboauth0 libpisock9 libqt5concurrent5 libqt5core5a
libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5svg5 libqt5widgets5 libraptor2-0
librasqal3 libraw10 librdf0 libruby2.1 libscsynth1 libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0
libxcb-render-util0 libxcb-xkb1 libxkbcommon-x11-0 libyajl2 libyaml-0-2 lp-solve qttranslations5-l10n ruby ruby2.1
rubygems-integration squeak-vm
Use 'apt-get autoremove' to remove them.
Done
The following packages have been kept back:
pix-icons pix-plym-splash python-openssl python3-openssl raspberrypi-ui-mods
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
When I do a
Code: Select all
pi@sulfurpi ~$ sudo dpkg --list rev*
I get:
Code: Select all
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii revpi-firmware 1:1.4 all Revolution Pi firmware
ii revpi-repo 1.0.4stretch all Revolution Pi package repository
ii revpi-tools 1.0.12-1 armhf Revolution Pi tools
ii revpi-wallpape 1.0.0-2 all Revolution Pi Wallpaper
ii revpi-webstatu 1.2.10 all Revolution Pi Web Status
ii revpi7 1.0.3-1 all Adapter between piControl and Sie
You should get similiar results.
When I do this, I get the following result
Code: Select all
pi@RevPi40427:~ $ sudo dpkg --list rev*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-========================-=================-=================-=====================================================
ii revpi-firmware 20170622-1 all Revolution Pi firmware
ii revpi-repo 1.0.2jessie-1 all Revolution Pi package repository
ii revpi-tunnel 1.0.0-1 all Revolution Pi remote access tunnel
ii revpi-wallpaper 1.0.0-1 all Revolution Pi Wallpaper
ii revpi-webstatus 1.2.4-1 all Revolution Pi Web Status
ii revpipyload 0.9.2-1 all PLC Loader für Python-Projekte auf den RevolutionPi
Can you post the output of
as well?
This is the output:
Code: Select all
pi@RevPi40427:~ $ cat /etc/issue
Raspbian GNU/Linux 8 \n \l \4 \6
Also make sure you attach only one Module at a time to the Pi when updating.
Only the DIO module is connected to the right.
Thank you for your help!
Luuk
Re: Revpi Core3 DO failure
Posted: 13 Dec 2020, 19:14
by RR4711
You are still on Debian Jessie, so your dealer may have had it on stock for a very long time. Please upgrade to stretch, as for whatever reason the firmware files are not provided for Debian Jessie even though I don't see a technical reason. An update to buster is also announced for January 2021, so you may as well wait to avoid having to update two times in a short interval (if you want to). Stretch will be also out of support sooner or later.
You can try a dist upgrade, but maybe just flashing the latest image is easier (I don't know how much stuff you need to configure for your application).
Markus
Re: Revpi Core3 DO failure
Posted: 13 Dec 2020, 19:29
by RR4711
LuukvanLoon wrote: ↑11 Dec 2020, 08:49
no new firmware is installed and that V1.4 >= V1.3. Could it be possible that I can not download the latest firmware when i follow the steps in the guide?
That just tells you that the module has already a newer FW than the one shipped with the operating system so it refuses to update. As I said, likely the Computer was stored for a long time so in the meanwhile KUNBUS delivered the DO module already with a newer version than the one provided with your old Linux.
If you update the image and then do another update run as in the instructions you should be able to flash the DO FW to the newer version.
Markus