This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Moitessier HAT firmware update failed after update to OpenPlotter 1.2
#1
The Moitessier HAT stops working after upgrade to 1.2 and no GPS data can be received from the HAT.

I tried to install the new firmware for the HAT via the OpenPlotter GUI, but it constantly fails.

I wiped the system and re-installed from NOOBS 1.0.0 and flashed the HAT with version Moitessier_4.14.34_armhf.deb and the flash works correctly. 

When on OpenPlotter version 1.0.0, GPS data is seen in SignalK server and can be seen in diagnostics for the serial0 port.

Running the auto-update to OpenPlotter 1.2.0 the HAT goes offline for GPS data. The IMU and temperature sensors can still be access via the Moitessier HAT interface in the OpenPlotter GUI, but no GPS data.

I have run this process 3 times and the same result. Once updated to version 1.2.0, the current kernel version shows 4.14.71-v7+ #1145 SMP Friday September 21.........

The available package list shows 4 versions

4.14.34
4.14.50
4.14.62
4.14.69

None of the versions match the current kernel version and none of the versions will install, all giving the following output in the updater window.

Code:
(Reading database ... 123129 files and directories currently installed.)
Preparing to unpack .../moitessier_4.14.69_armhf.deb ...
Unpacking moitessier (1.20180817-1-697-g27e84c6-4.14.69-1.0.0) over (1.20180417-1-4.14.34-1.0.0) ...
Setting up moitessier (1.20180817-1-697-g27e84c6-4.14.69-1.0.0) ...
Running post install...
Updating HAT firmware...

******************************************************************************************
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 "/home/pi/moitessier/flasher/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!!
******************************************************************************************


**************************************************************************************
The firmware file "application.binary" is used for the update
**************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************


**************************************************************************************
*                                                                                    *
* FIRMWARE UPDATE FAILED!!!                                                          *
*                                                                                    *
**************************************************************************************

Error occured. You might try to install the package again.
If there have been failures, check the log and close this window.


(Reading database ... 123129 files and directories currently installed.)
Preparing to unpack .../moitessier_4.14.69_armhf.deb ...
Unpacking moitessier (1.20180817-1-697-g27e84c6-4.14.69-1.0.0) over (1.20180417-1-4.14.34-1.0.0) ...
Setting up moitessier (1.20180817-1-697-g27e84c6-4.14.69-1.0.0) ...
Running post install...
Updating HAT firmware...

******************************************************************************************
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 "/home/pi/moitessier/flasher/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!!
******************************************************************************************


**************************************************************************************
The firmware file "application.binary" is used for the update
**************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************

INFO: Loading driver "./i2c-gpio-param.ko".
insmod: ERROR: could not insert module ./i2c-gpio-param.ko: Invalid module format

******************************************************************************************
ERROR occured!!

Could not load "./i2c-gpio-param.ko".
******************************************************************************************


******************************************************************************************
ERROR occured!!

An error occured, we will retry.
******************************************************************************************


**************************************************************************************
*                                                                                    *
* FIRMWARE UPDATE FAILED!!!                                                          *
*                                                                                    *
**************************************************************************************

Error occured. You might try to install the package again.
If there have been failures, check the log and close this window.




The OpenPlotter is currently on a completely clean install of OpenPlotter 1.2.0 without any configuration changes or modifications to try to get to the bottom of the issue. The auto-update of the interface on the SERIAL tab of the GUI cannot find the data type of the serial port and does not recognise the data with the error message "we have not found recognizable data on device". If the port is set to serial0 manually, there is no data received from HAT to the GPSD assignment.


/var/log/messages has the following output

Code:
Oct 20 11:46:50 openplotter kernel: [ 1067.811213] w1_master_driver w1_bus_master1: Attaching one wire slave 00.280000000000 crc e1
Oct 20 11:46:50 openplotter kernel: [ 1067.813900] w1_master_driver w1_bus_master1: Family 0 for 00.280000000000.e1 is not registered.
Oct 20 11:47:53 openplotter kernel: [ 1131.322996] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a80000000000 crc 6d
Oct 20 11:47:53 openplotter kernel: [ 1131.328121] w1_master_driver w1_bus_master1: Family 0 for 00.a80000000000.6d is not registered.
Oct 20 11:48:57 openplotter kernel: [ 1194.844414] w1_master_driver w1_bus_master1: Attaching one wire slave 00.680000000000 crc a7
Oct 20 11:48:57 openplotter kernel: [ 1194.851224] w1_master_driver w1_bus_master1: Family 0 for 00.680000000000.a7 is not registered.
Oct 20 11:49:32 openplotter kernel: [ 1230.363719] i2c_gpio_param: disagrees about version of symbol module_layout
Oct 20 11:49:32 openplotter kernel: [ 1230.385987] i2c_gpio_param: disagrees about version of symbol module_layout
Oct 20 11:49:32 openplotter kernel: [ 1230.415556] i2c_gpio_param: disagrees about version of symbol module_layout
Oct 20 11:49:32 openplotter kernel: [ 1230.437497] i2c_gpio_param: disagrees about version of symbol module_layout
Oct 20 11:49:32 openplotter kernel: [ 1230.463119] i2c_gpio_param: disagrees about version of symbol module_layout
Oct 20 11:49:37 openplotter kernel: [ 1235.254259] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b
Oct 20 11:49:37 openplotter kernel: [ 1235.256932] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered.
Oct 20 11:50:40 openplotter kernel: [ 1298.405195] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f
Oct 20 11:50:40 openplotter kernel: [ 1298.410492] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered.
Oct 20 11:51:20 openplotter kernel: [ 1337.605463] w1_master_driver w1_bus_master1: Attaching one wire slave 00.980000000000 crc d3
Oct 20 11:51:20 openplotter kernel: [ 1337.610501] w1_master_driver w1_bus_master1: Family 0 for 00.980000000000.d3 is not registered.
Oct 20 11:52:09 openplotter kernel: [ 1386.926026] w1_master_driver w1_bus_master1: Attaching one wire slave 00.580000000000 crc 19
Oct 20 11:52:09 openplotter kernel: [ 1386.931642] w1_master_driver w1_bus_master1: Family 0 for 00.580000000000.19 is not registered.
Oct 20 11:53:01 openplotter kernel: [ 1438.966329] w1_master_driver w1_bus_master1: Attaching one wire slave 00.d80000000000 crc 95
Oct 20 11:53:01 openplotter kernel: [ 1438.971993] w1_master_driver w1_bus_master1: Family 0 for 00.d80000000000.95 is not registered.
Oct 20 11:53:27 openplotter kernel: [ 1465.496624] w1_master_driver w1_bus_master1: Attaching one wire slave 00.380000000000 crc 7c
Oct 20 11:53:27 openplotter kernel: [ 1465.503272] w1_master_driver w1_bus_master1: Family 0 for 00.380000000000.7c is not registered.
Oct 20 11:54:12 openplotter kernel: [ 1510.250224] pps pps0: removed
Oct 20 11:54:17 openplotter kernel: [ 1514.966403] w1_master_driver w1_bus_master1: Attaching one wire slave 00.b80000000000 crc f0
Oct 20 11:54:17 openplotter kernel: [ 1514.969309] w1_master_driver w1_bus_master1: Family 0 for 00.b80000000000.f0 is not registered.
Oct 20 11:55:22 openplotter kernel: [ 1579.689198] w1_master_driver w1_bus_master1: Attaching one wire slave 00.780000000000 crc 3a
Oct 20 11:55:22 openplotter kernel: [ 1579.694697] w1_master_driver w1_bus_master1: Family 0 for 00.780000000000.3a is not registered.
Oct 20 11:56:14 openplotter kernel: [ 1631.727784] w1_master_driver w1_bus_master1: Attaching one wire slave 00.f80000000000 crc b6
Oct 20 11:56:14 openplotter kernel: [ 1631.733223] w1_master_driver w1_bus_master1: Family 0 for 00.f80000000000.b6 is not registered.

var/log/syslog has the following output

Oct 20 11:49:37 openplotter kernel: [ 1235.254259] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b
Oct 20 11:49:37 openplotter kernel: [ 1235.256932] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered.
Oct 20 11:50:40 openplotter kernel: [ 1298.405195] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f
Oct 20 11:50:40 openplotter kernel: [ 1298.410492] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered.
Oct 20 11:51:20 openplotter kernel: [ 1337.605463] w1_master_driver w1_bus_master1: Attaching one wire slave 00.980000000000 crc d3
Oct 20 11:51:20 openplotter kernel: [ 1337.610501] w1_master_driver w1_bus_master1: Family 0 for 00.980000000000.d3 is not registered.
Oct 20 11:52:09 openplotter kernel: [ 1386.926026] w1_master_driver w1_bus_master1: Attaching one wire slave 00.580000000000 crc 19
Oct 20 11:52:09 openplotter kernel: [ 1386.931642] w1_master_driver w1_bus_master1: Family 0 for 00.580000000000.19 is not registered.
Oct 20 11:53:01 openplotter kernel: [ 1438.966329] w1_master_driver w1_bus_master1: Attaching one wire slave 00.d80000000000 crc 95
Oct 20 11:53:01 openplotter kernel: [ 1438.971993] w1_master_driver w1_bus_master1: Family 0 for 00.d80000000000.95 is not registered.
Oct 20 11:53:27 openplotter kernel: [ 1465.496624] w1_master_driver w1_bus_master1: Attaching one wire slave 00.380000000000 crc 7c
Oct 20 11:53:27 openplotter kernel: [ 1465.503272] w1_master_driver w1_bus_master1: Family 0 for 00.380000000000.7c is not registered.
Oct 20 11:54:12 openplotter systemd[1]: Stopping GPS (Global Positioning System) Daemon...
Oct 20 11:54:12 openplotter kernel: [ 1510.250224] pps pps0: removed
Oct 20 11:54:12 openplotter systemd[1]: Stopped GPS (Global Positioning System) Daemon.
Oct 20 11:54:12 openplotter systemd[1]: Started GPS (Global Positioning System) Daemon.
Oct 20 11:54:12 openplotter signalk-server[1758]: TcpProvider:connect ECONNREFUSED 127.0.0.1:30330
Oct 20 11:54:12 openplotter signalk-server[1758]: TcpProvider:connect ECONNREFUSED 127.0.0.1:30330
Oct 20 11:54:13 openplotter systemd[1]: Stopping signalk.service...
Oct 20 11:54:13 openplotter systemd[1]: Stopped signalk.service.
Oct 20 11:54:13 openplotter systemd[1]: Closed signalk.socket.
Oct 20 11:54:13 openplotter systemd[1]: Listening on signalk.socket.
Oct 20 11:54:13 openplotter systemd[1]: Started signalk.service.
Oct 20 11:54:16 openplotter systemd[1]: Configuration file /etc/systemd/system/signalk.socket is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 20 11:54:16 openplotter systemd[1]: Configuration file /etc/systemd/system/signalk.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 20 11:54:16 openplotter systemd[1]: Stopping GPS (Global Positioning System) Daemon...
Oct 20 11:54:16 openplotter systemd[1]: Stopped GPS (Global Positioning System) Daemon.
Oct 20 11:54:16 openplotter systemd[1]: Closed GPS (Global Positioning System) Daemon Sockets.
Oct 20 11:54:16 openplotter systemd[1]: Configuration file /etc/systemd/system/signalk.socket is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 20 11:54:17 openplotter systemd[1]: Stopping signalk.service...
Oct 20 11:54:17 openplotter systemd[1]: Stopped signalk.service.
Oct 20 11:54:17 openplotter systemd[1]: Closed signalk.socket.
Oct 20 11:54:17 openplotter kernel: [ 1514.966403] w1_master_driver w1_bus_master1: Attaching one wire slave 00.b80000000000 crc f0
Oct 20 11:54:17 openplotter kernel: [ 1514.969309] w1_master_driver w1_bus_master1: Family 0 for 00.b80000000000.f0 is not registered.
Oct 20 11:54:37 openplotter systemd[1]: Configuration file /etc/systemd/system/signalk.socket is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 20 11:54:37 openplotter systemd[1]: Configuration file /etc/systemd/system/signalk.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct 20 11:54:38 openplotter systemd[1]: Listening on GPS (Global Positioning System) Daemon Sockets.
Oct 20 11:54:38 openplotter systemd[1]: Started GPS (Global Positioning System) Daemon.
Oct 20 11:54:38 openplotter systemd[1]: Listening on signalk.socket.
Oct 20 11:54:38 openplotter systemd[1]: Started signalk.service.
Oct 20 11:54:43 openplotter signalk-server[2369]: signalk-server running at 0.0.0.0:[object Object]
Oct 20 11:55:22 openplotter kernel: [ 1579.689198] w1_master_driver w1_bus_master1: Attaching one wire slave 00.780000000000 crc 3a
Oct 20 11:55:22 openplotter kernel: [ 1579.694697] w1_master_driver w1_bus_master1: Family 0 for 00.780000000000.3a is not registered.
Oct 20 11:56:14 openplotter kernel: [ 1631.727784] w1_master_driver w1_bus_master1: Attaching one wire slave 00.f80000000000 crc b6
Oct 20 11:56:14 openplotter kernel: [ 1631.733223] w1_master_driver w1_bus_master1: Family 0 for 00.f80000000000.b6 is not registered.
Oct 20 11:57:16 openplotter kernel: [ 1694.377712] w1_master_driver w1_bus_master1: Attaching one wire slave 00.040000000000 crc 61
Oct 20 11:57:16 openplotter kernel: [ 1694.382902] w1_master_driver w1_bus_master1: Family 0 for 00.040000000000.61 is not registered.
Oct 20 11:58:01 openplotter vncserver-x11[481]: Connections: disconnected: 192.168.255.240::51462 ([System] read: Connection timed out (110))
Oct 20 11:58:10 openplotter kernel: [ 1747.707389] w1_master_driver w1_bus_master1: Attaching one wire slave 00.840000000000 crc ed
Oct 20 11:58:10 openplotter kernel: [ 1747.710088] w1_master_driver w1_bus_master1: Family 0 for 00.840000000000.ed is not registered.

I am not sure what to do to get the HAT updated and back online sending GPS data. I am in the middle of moving the boat and really need to have the main nav back up and running.

Any help really appreciated.
Reply
#2
Could someone help?
Reply
#3
there is some info in the spanish topic
http://forum.openmarine.net/showthread.p...02#pid7202
i think sailoog is sailing, the store is closed so maybe someone else with the hat will chime in..
install packages 4.14.69
Reply
#4
When sailoog did the commit for 1.2.0 the kernel version was 4.14.69. But now it is at 4.14.71. You need a driver for the new kernel.
To solve this open a terminal and type in:

Code:
cd .config/openplotter/tools/moitessier_hat/packages/
wget https://get.rooco.tech/moitessier/release/4.14.71/latest/moitessier_4.14.71_armhf.deb


Now you can install the driver in openplotter
(Tools->Moitessier Hat Start Install Install)
Reply
#5
That worked perfectly.

Would it be a good idea to have the drivers automatically link to the repo for new versions?
Reply
#6
(2018-10-23, 04:59 PM)e-sailing Wrote: When sailoog did the commit for 1.2.0 the kernel version was 4.14.69. But now it is at 4.14.71. You need a driver for the new kernel.
To solve this open a terminal and type in:

Code:
cd .config/openplotter/tools/moitessier_hat/packages/
wget https://get.rooco.tech/moitessier/release/4.14.71/latest/moitessier_4.14.71_armhf.deb


Now you can install the driver in openplotter
(Tools->Moitessier Hat Start Install Install)
Hello gentlemen

I had the same issue and applied the code as recommended. My kernel is 4.14.79 so I have dowloaded and installed the .79 package. When I go to moitessier hat settings, the only available package I can see is the .34. I have already reboot open plotter and rebooted RPI, with no results! Does anybody have an idea how to solve it? My open plotter version is the 1.0.0.
Reply
#7
try updating to 1.2.0 i see "Update moitessier hat packages" in the changelog
https://github.com/sailoog/openplotter/b...ANGELOG.md
Reply
#8
I have updated to v1.2 but I just cannot get the Moitessier HAT stuff to work. I even downloaded the kernel suggested by e-sailing, but I had the same issue as pgorab, except my raspbian kernel is 4.14.98-v7+, so the update failed. I then tried downloading different kernels, but these don't seem to be available:
- wget https://get.rooco.tech/moitessier/releas..._armhf.deb
- wget https://get.rooco.tech/moitessier/releas..._armhf.deb

Any suggestions?
regards
Trevor
skype: trevor_miles
Reply
#9
download for moitessier_4.14.98_armhf.deb
https://get.rooco.tech/moitessier/releas..._armhf.deb
Code:
sudo dpkg -i moitessier_4.14.98_armhf.deb

i don't have a hat but that should work.

other kernel versions
https://www.rooco.eu/2018/06/13/firmware...ssier-hat/
https://get.rooco.tech/moitessier/release/
 source code
https://github.com/mr-rooney/moitessier/
?
https://www.rooco.eu/question/new-compil...an-kernel/
Reply
#10
(2019-03-13, 10:07 PM)jim321 Wrote: download for moitessier_4.14.98_armhf.deb
https://get.rooco.tech/moitessier/releas..._armhf.deb
Code:
sudo dpkg -i moitessier_4.14.98_armhf.deb

i don't have a hat but that should work.

other kernel versions
https://www.rooco.eu/2018/06/13/firmware...ssier-hat/
https://get.rooco.tech/moitessier/release/
 source code
https://github.com/mr-rooney/moitessier/
?
https://www.rooco.eu/question/new-compil...an-kernel/


Thx Jim, this worked like a charm. Us newbies need a few pointers.

While the package installed correctly, I'm still not getting any GPS signal. 

I've attached a bunch of screenshots from the OpenPlotter UI and also OpenCPN. Have I set something incorrectly?

Any help much appreciated.
regards
Trevor
skype: trevor_miles
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)