problem installing moitessier firmware [closed]

[Luckbert]

Ist das eine Himbeere 3?
Rooco-Leute haben mir gerade gesagt, dass es ein Problem mit RPi3 gibt, das sie lösen wollen.

Hallo,
Ja, ich habe einen PI3.

Gut zu wissen, dass ein Problem bekannt ist und bearbeitet wird.
Grüße Jürgen

[Rooco]

Obviously there is a problem with TTY devices with the new kernel. The HAT registers itself as TTY as well. They've changed something at the registration process and this might cause problems on some systems. The problem definitely exists on the Pi 3 and Pi 3+. We didn't face any issues with the Pi 4. However, the theoretically the problem might be on the Pi 4 as well, if the system uses additional TTY devices.

A solution is already in testing stage and we might publish soon if successfull.

[Luckbert]

Obiously there is a problem with TTY devices with the new kernel. The HAT is registers as TTY as well. They've changed something at the registration process and this might cause problems on some systems. The problem definitely exists on the Pi 3 and Pi 3+. We didn't face any issues with the Pi 4. However, the problem might be on the Pi 4 as well, if the system uses additional TTY devices.

A solution is already in testing stage and we might publish soon if successfull.

Hello, Rooco,
Thanks for your message. We'll just have to wait and see. Thanks for your trouble.
Greetings Jürgen

[Max1947]

Okay, everything seems fine ... only additional TTYs are missing, as Rooco says, and we will have to wait for the new kernel in Pi4. Meanwhile, good wind to everyone!

https://i.imgur.com/gEdtKJO.png

https://i.imgur.com/yseoo60.png

https://i.imgur.com/iLEPqsA.png

[Rooco]

There is a package available for testing: https://get.rooco.tech/moitessier/buster...t_only.deb

Would be great if someone could test it and give feedback.
The package does not support all prior kernels, only 5.4.51 (with the latest kernel commit).

Package was tested with Pi 3, Pi 3+ and Pi 4.

[Max1947]

There is a package available for testing: https://get.rooco.tech/moitessier/buster...t_only.deb

Would be great if someone could test it and give feedback.
The package does not support all prior kernels, only 5.4.51 (with the latest kernel commit).

Package was tested with Pi 3, Pi 3+ and Pi 4.

  Ok, installed and it seems to work. The various ttys are always missing from the MCS board and in serial ...
PI4 + hat v.1 + MCS, see: 

https://i.imgur.com/83EwI69.png

https://i.imgur.com/ertFiFy.png  

[Rooco]

There is a package available for testing: https://get.rooco.tech/moitessier/buster...t_only.deb

Would be great if someone could test it and give feedback.
The package does not support all prior kernels, only 5.4.51 (with the latest kernel commit).

Package was tested with Pi 3, Pi 3+ and Pi 4.

  Ok, installed and it seems to work. The various ttys are always missing from the MCS board and in serial ...
PI4 + hat v.1 + MCS, see: 

https://i.imgur.com/83EwI69.png

https://i.imgur.com/ertFiFy.png  

But the HAT work?
Do you get NMEA messages using the following command?
cat /dev/moitessier.spi

[Max1947]

There is a package available for testing: https://get.rooco.tech/moitessier/buster...t_only.deb

Would be great if someone could test it and give feedback.
The package does not support all prior kernels, only 5.4.51 (with the latest kernel commit).

Package was tested with Pi 3, Pi 3+ and Pi 4.

  Ok, installed and it seems to work. The various ttys are always missing from the MCS board and in serial ...
PI4 + hat v.1 + MCS, see: 

https://i.imgur.com/83EwI69.png

https://i.imgur.com/ertFiFy.png  

But the HAT work?
Do you get NMEA messages using the following command?
cat /dev/moitessier.spi

The Hat work...see:

https://i.imgur.com/V3AuE95.png 

[Rooco]

Great that it works!!!

I think the driver for the MCS board is facing the same issue. I'm not sure if this is a bug in the new Raspberry Pi kernel or a feature. The problem is definitely caused by a fixed device numbering for TTY devices.

Regards,
Thomas

[Max1947]

Great that it works!!!

I think the driver for the MCS board is facing the same issue. I'm not sure if this is a bug in the new Raspberry Pi kernel or a feature. The problem is definitely caused by a fixed device numbering for TTY devices.

Regards,
Thomas

  Yes, as anticipated by Thomas of GeDaD, I will have to wait for the release of the new Raspy kernel: https://github.com/raspberrypi/linux/issues/3765