(2020-10-12, 10:44 PM)seandepagnier Wrote: [ -> ]Does the older tinypilot image work on the same hardware?
It should support pi 0, 1, 2, 3
What errors? Can you md5sum the extracted image?
MD5 sum : 69d4c8706c920e15e476c8499005a875
Errors shown in attached picture.
This is on an Raspberry Pi 2, without WiFi adapter.
I have tried a 32GB and a 16GB card, same errors on both.
I have also tried to write the image with 3 different programs, BalenaEtcher, Win32DiskImager, and RaspberryPi imager.
Also tried the same on a RPi3+, but hangs on boot.
I tried some of the older images - same problem.
And tried to write the image using another computer.
I also tested piCore 9.0.3 - this works on Rpi2, but hangs on Rpi3+.
I am not sure what to try next - i do not want to buy a Pi Zero.
Maybe use a Pi4 with Raspbian, and install pypilot..
I do want to have the autopilot on a dedicated Pi.
New image boots on Zero, but no web service.
Boots as an AP.
Can be pinged on 192.168.14.1 and responds.
Looking at disk images that were intalled via linux disk manager: restore img command;
I have always used this method to install images with no problem.
But here is what I see for what it is worth, intentional or not;
[
attachment=1091]
Yeah, the partitions are there but, looks pretty scrambled vs below where just the necessary partition suffice.
[
attachment=1092]
Seems to be missing or misplaced file and a folder
These were from your 2019 dec release
[
attachment=1094]
[
attachment=1093]
And last but not least, thanks Sean!
(2020-10-14, 03:11 PM)jmj Wrote: [ -> ] (2020-10-12, 10:44 PM)seandepagnier Wrote: [ -> ]Does the older tinypilot image work on the same hardware?
It should support pi 0, 1, 2, 3
What errors? Can you md5sum the extracted image?
MD5 sum : 69d4c8706c920e15e476c8499005a875
Errors shown in attached picture.
I have
md5sum tinypilot_2020_10_05.img
c31e7247f0e297adbf37f483e07ef558 tinypilot_2020_10_05.img
so this is a different file have. Maybe it corrupted on upload or download??
Also compressed md5:
$ md5sum tinypilot_2020_10_05.img.xz
33dbc00fe41020b628f14ab22fedbcc3 tinypilot_2020_10_05.img.xz
Please verify the checksum.
There are 2 more partitions that are "missing" I used them for working space and swap to build gcc and scipy on a 16gb card, but there are only the 2 partitions you need that fit in the first 1gb
The "errors" in the screenshots should be taken as warnings, they are not fatal.
(2020-10-13, 01:46 PM)Onno Wrote: [ -> ]Hi Sean thanks for al your efforts!
I see some improvements but have some issues:
When i hit my starboard 1 button connected to gpio22 the engage led wil turn on but nothing else happens!
When i hit the starboard 1 button in the browser the actuator does move!
In LCD setup it shows key: gpio22 and action: starboard1 when I hit the button
I see that the engange led will turn on as long it is set in servo.period but this has no influence on the starboard1 button in the browser?
Same with port 1 button.
On older images it worked fine.
I tried this a bunch and I think the buttons do work. Are you sure? There should at least be voltage output.
The new version does something different with manual control. Before it moved in bursts, now it moves when the button is down and stops when you release to give better manual control. It runs the motor at lower speeds so maybe it's not enough to move your motor at all, and this is why. The starboard10 button should give you full speed at least.
(2020-10-14, 10:22 PM)I have Wrote: [ -> ]md5sum tinypilot_2020_10_05.img
c31e7247f0e297adbf37f483e07ef558 tinypilot_2020_10_05.img
My checksum was for the tinypilot_2020_10_11.img file.
When i check the tinypilot_2020_10_05.img file i get the same MD5 as you.
I tested a new download of the 10_05 file - still the same problem.
I use Windows, maybe i should try this on a Linux machine ?
(2020-10-14, 03:11 PM)jmj Wrote: [ -> ]Also tried the same on a RPi3+, but hangs on boot.
I tried some of the older images - same problem.
And tried to write the image using another computer.
I also tested piCore 9.0.3 - this works on Rpi2, but hangs on Rpi3+.
tinypilot is based on picore so if it doesn't boot it won't work. I think the rpi3 works but not the rpi3+
Quote:I am not sure what to try next - i do not want to buy a Pi Zero.
Maybe use a Pi4 with Raspbian, and install pypilot..
I do want to have the autopilot on a dedicated Pi.
Really? The zero is much cheaper and also by far the lowest power consumption.
(2020-10-14, 03:46 PM)wdee Wrote: [ -> ]New image boots on Zero, but no web service.
The web service takes 3-4 minutes to start working after boot. This is longer than before, but this version does a lot more and it gets running in 30 seconds instead of a minute. I'm sure the web startup could be optimized more too.
It is my intention to support pi3+ and pi4 for tinypilot, but this requires tinycore 11 I'm not sure I'm ready to switch until I can do long-term tests for reliability and I also have to recompile everything again which takes a while.
(2020-10-15, 09:15 PM)seandepagnier Wrote: [ -> ]It is my intention to support pi3+ and pi4 for tinypilot, but this requires tinycore 11 I'm not sure I'm ready to switch until I can do long-term tests for reliability and I also have to recompile everything again which takes a while.
That is good news - i will put tinypilot on hold until pi4 is supported.
Will i loose any functonality by running Raspbian and pypilot - is it the same code base ?
I want to build and test the hardware, and can install tinypilot later.
My boat is on land for the winter, so i am in no hurry.
Thanks for taking time to give good answers.
(2020-10-14, 03:11 PM)jmj Wrote: [ -> ] (2020-10-12, 10:44 PM)seandepagnier Wrote: [ -> ]Does the older tinypilot image work on the same hardware?
It should support pi 0, 1, 2, 3
What errors? Can you md5sum the extracted image?
MD5 sum : 69d4c8706c920e15e476c8499005a875
Errors shown in attached picture.
I didn't see an answer in this thread, so for the benefit of anyone coming along later, those errors can be ignored:
https://forum.openmarine.net/showthread....7#pid11777