Orangepizero3 support

[meganukebmp]

Since @meteyou already added the device and it built fine in armbian-builds, this should probably get us support for this board.

Unfortunately I am unable to build the workflows and see if it actually works correctly.

[KwadFan]

Well, I already see a design flaw in this PR. Images without a boot partition will not work, because you need it to configure the network. There is no way to connect before hand.
Also moving partition layout out of the default file will also lead to issues if we build more than those 2 Images.

The orangepi_net module is used to provide network setup funtkionality which uses the fat partition.
I cant test the base Image from the PR mainsail-crew/armbian-builds#37, because I thought the Image would be correct as I aproved it. As said cant test, so I heavily relie on your feedback.

Is there no fat partition on that particular Image?

[KwadFan]

Verified it already, this Image has no FAT32 boot partition, therefore it wont work with that build chain.

We need to address this in armbian-builds.

On the base images you can setup everything on first boot. This "mechanic" doesnt exist in MainsailOS!
So, we need to fix the base image first.

[meteyou]

i will doublecheck the orangepi settings. maybe i overview something there...

[meganukebmp]

It appears your armbian builds do have a boot partition! And it works too, which is because the armbian build system overrides the boot scripts. However, the boot partition is not accessible under windows because it gets created of type Linux extended boot rather than Win95 FAT. I'm not sure why.

If I modify the disk partitions after building it it and change type from Linux extended boot to Win95 FAT it ends up working on windows just fine.

Do any other boards exhibit this behavior?

[meganukebmp]

This last patch would allow for the builds to succeed. However the boot partition is labeled in such a way that windows cannot see it. Windows is fully capable of reading these partitions normally, it's just labeled as Linux extended boot rather than Win95 FAT Which prevents windows from assigning it a drive letter.

[meteyou]

hmm... its funny, because it should be the same as the zero2 image, but it is different...

[meganukebmp]

Actually the zero2 image ends up identical... It's partition type 0xEA, aka linux extended boot. And fails to mount on windows. To test this I even flashed the zero2 image to an sdcard.

234 = 0xEA

[meteyou]

ok. then it looks like kwad tested it wrong the last time. i have to doublecheck the complete workflow of orangepi again. looks like a generic issue in this workflow and the filesystem.

Thx for all your work!

[KwadFan]

So, I did some test with images resulting from this PR:
mainsail-crew/armbian-builds#37

Images can be found here:
https://github.com/mainsail-crew/armbian-builds/actions/runs/6631552667

The resulting images show the correct FAT partition.

But...
I cant test it on real hardware, due missing the Zero3, Zero2 is working as expected.
Also I cant test how the resulting SDCard looks under Windows because I use Linux as daily driver 🤷‍♂️

[VectorForce3D]

So, I did some test with images resulting from this PR: mainsail-crew/armbian-builds#37

Images can be found here: https://github.com/mainsail-crew/armbian-builds/actions/runs/6631552667

The resulting images show the correct FAT partition.

But... I cant test it on real hardware, due missing the Zero3, Zero2 is working as expected. Also I cant test how the resulting SDCard looks under Windows because I use Linux as daily driver 🤷‍♂️

I own all of the hardware necessary to test this. If I can be of service, I would be more than happy to test this build.

[SkAntRu]

Hi, i can test it on OPi Zero3 1.5Gb and I very interested in adding support for it!
Actions with images https://github.com/mainsail-crew/armbian-builds/actions/runs/6631552667 expired, can you rerun it?