Rasberry 4 – Moitessier HAT 1 – Aggiornamento kernel 5.4.51

 

To comment on questions or provide answers, please login first.
Register | Login

 

Questions and AnswersCategory: Moitessier HATRasberry 4 – Moitessier HAT 1 – Aggiornamento kernel 5.4.51
Gino Fumagalli asked 3 months ago

Hi, I can’t update to the latest version. The serials in OP2 are lost. See: https: //imgur.com/1JJoeFu
See also here: https://forum.openmarine.net/showthread.php?tid=2795&pid=15140#pid15140

3 Answers
Thomas Staff answered 3 months ago

Have you installed the latest Moitessier package?

Proceed as follows on your Pi using a terminal:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
wget https://get.rooco.tech/moitessier/buster/release/5.4.51/2.1.0/moitessier_1.20200723-1_5.4.51_2.1.0_armhf.deb
sudo dpkg -i moitessier_1.20200723-1_5.4.51_2.1.0_armhf.deb

geronius answered 2 months ago

Hi Thomas,
I can’t get the hat working on my Pi 3b with the new kernel version
(freshly installed and updated from 2020-03-24-OpenPlotter-v2-Moitessier-HAT.img)
Any update (tried multiple times / either via OP2 installer as well as via dpkg) fails after successful flash.
See messages below
What’s wrong?
Regards,
Michael


(Lese Datenbank … 101526 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von …/moitessier_5.4.51_2.1.0_armhf.deb …
Entpacken von moitessier (2.1.0) über (2.1.0) …
[1;93m
******************************************************************************************
Running post remove… (upgrade)
******************************************************************************************
[0m
[1;93m
******************************************************************************************
Nothing to do
******************************************************************************************
[0m
moitessier (2.1.0) wird eingerichtet …
[1;93m
******************************************************************************************
Running post install…
******************************************************************************************
[0m
/etc/systemd/system/moitessier.shutdown.service
[1;93m
******************************************************************************************
File /etc/systemd/system/moitessier.shutdown.service deleted.
******************************************************************************************
[0m
[Unit]
Description=Moitessier Shutdown
[Service]
ExecStart=/home/pi/moitessier/scripts/system_shutdown
Restart=always
[Install]
WantedBy=multi-user.target
[1;93m
******************************************************************************************
Setting up interfaces…
******************************************************************************************
[0m
moitessier: setting up /etc/modules
i2c-dev
[1;93m
******************************************************************************************
Updating HAT firmware…
******************************************************************************************
[0m
******************************************************************************************
This script is used to flash the STM32 microcontroller on the Moitessier HAT.
One of the following options can be applied:
-r : Will load the latest firmware release from the remote repository https://github.com/mr-rooney/moitessier-firmware.git.
The firmware will be located in “./fw/application.binary”.
-s : Specifies the firmware that should be used.
This option requires the path + filename as parameter
-f : Forces the Raspberry Pi to shutdown after firmware update. A shutdown + power cycle
is required only for virgin Moitessier HATs without any firmware.
Note: Options -s and -r must not be applied at the same time!!
******************************************************************************************
[1;93m
******************************************************************************************
Determining I2C GPIO device
******************************************************************************************
[0m
[1;93m
******************************************************************************************
I2C GPIO device: 3
******************************************************************************************
[0m
******************************************************************************************
The firmware file “application.binary” is used for the update
******************************************************************************************

******************************************************************************************
Terminating running processes…
******************************************************************************************

******************************************************************************************
“kplex” not running
******************************************************************************************

******************************************************************************************
“gpsd” not running
******************************************************************************************

******************************************************************************************
“opencpn” not running
******************************************************************************************

******************************************************************************************
“node” not running
******************************************************************************************
…………………………….
******************************************************************************************
Flashing firmware.
******************************************************************************************
Error probing interface “serial_posix”
stm32flash 0.5
http://stm32flash.sourceforge.net/
Using Parser : Raw BINARY
Interface i2c: addr 0x41
GPIO sequence start
setting gpio 18 to 1… OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 17 to 1… OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 0… OK
delay 100000 us
delay 100000 us
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1… OK
delay 100000 us
delay 100000 us
GPIO sequence end
size = 131072
Version : 0x10
Device ID : 0x0442 (STM32F030xC/F09xxx)
– RAM : Up to 32KiB (6144b reserved by bootloader)
– Flash : Up to 128KiB (size first sector: 2×2048)
– Option RAM : 16b
– System RAM : 8KiB
Write to memory
Erasing memory
Wrote and verified address 0x08000100 (0.20%)

Wrote and verified address 0x08020000 (100.00%) Done.
Starting execution at address 0x08000000… done.
GPIO sequence start
delay 100000 us
delay 100000 us
setting gpio 17 to 0… OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1… OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 0… OK
delay 100000 us
delay 100000 us
delay 100000 us
setting gpio 18 to 1… OK
GPIO sequence end
******************************************************************************************
FIRMWARE UPDATE SUCCESSFULL!!!
******************************************************************************************
insmod: ERROR: could not insert module ./moitessier_5.4.51-v7+.ko: Input/output error
******************************************************************************************
[1;31mERROR occured!![0m
[1;31mCould not load “./moitessier_5.4.51-v7+.ko”.[0m
******************************************************************************************
[1;31m
******************************************************************************************
ERROR occured!!
You might try to install the package again.
******************************************************************************************
[0m
dpkg: Fehler beim Bearbeiten des Paketes moitessier (–install):
»installiertes moitessier-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
moitessier

Thomas Staff answered 2 months ago

Hello Michael,
this error occurs if you use an incompatible package/kernel combination. Are you sure you are using the correct package?
Have you seen, that we have two different 5.4.51 driver packages on our web page? Raspberry Pi has released two different commits but with the same kernel version.

You should proceed as follows:
# sudo apt-get update
# sudo apt-get upgrade
# sudo apt-get dist-upgrade –> these commands will install kernel version 5.4.51 on your system
# Download the latest Moitessier package (moitessier_1.20200723-1_5.4.51_2.1.0_armhf.deb) from our web page: https://www.rooco.eu/2018/06/13/firmware-and-drivers-for-raspberry-pi-moitessier-hat/
# Install the package: sudo dpkg -i moitessier_1.20200723-1_5.4.51_2.1.0_armhf.deb
# Check if HAT is accessible (after reboot): cat /dev/moitessier.spi

Setup:
Raspberry Pi 4 with HAT 1 and HAT 2
Used OpenPlotter image: 2020-03-24-OpenPlotter-v2-Moitessier-HAT-img

geronius replied 2 months ago

Hello Thomas,

that’s exactly how I did it, first using my previously working OP2 installation, later using a fresh IMG as downloaded from OP2 website.
Same result every time. Note that I am using a Pi 3B.

If this helps, I uploaded logs from terminal session and dmesg output here:
https://www.jottacloud.com/s/150716ce767c68e46079b90f9e2e17a3e32
https://www.jottacloud.com/s/1504b276549c4b34896acc3a209dc8ddd8a

Thomas Staff replied 2 months ago

Hello Michael,

please try the following package:
https://get.rooco.tech/moitessier/buster/pi3testing/moitessier_2.1.0_armhf_pi3_test_only.deb

Be aware that this package version does not include prior kernel versions and can only be used for the latest kernel 5.4.51. This is a testing package only!!!

geronius replied 2 months ago

Hi Thomas, thanks for your quick response.
I haven’t tried he experimental build yet as I am presently on my boat. I will check it out in my test environment on the weekend and tell you the outcome
Greetings,
Michael

geronius replied 2 months ago

Hi Thomas,
the testing package installed flawlessly and the hat produces sensible numbers. Unless you tell me not to do so, I will go ahead using the testing version.

Let me know if you need further info or testing to fix the problem

thanks and regards, Michael

Thomas Staff replied 2 months ago

Hello Michael,
we’ve published the latest Moitessier package yesterday. However, it is equal to the testing package but with higher version number.
No need to reinstall the latest package if you don’t want to.

Regards
Thomas

geronius replied 2 months ago

Hi Thomas,
thanks for keeping me informed. The checksumfile is still missing.
Regards,
Michael

Thomas Staff replied 2 months ago

Sorry, link should work now.

 

To comment on questions or provide answers, please login first.
Register | Login