Closed lubosz closed 3 years ago
So after rebasing your git repository to gcwnow's and tonyjih's buildroot 2014.08 branches I noticed that you added an imager
directory, which contains GCW Zero Image Generation Tools port to RG350
.
In a8550f3aa7a5dbb476798f176987ac89d4a7834b you moved that into the Updaters
directory (which you later luckily renamed to lower case), where you keep one copy of the tool for every device. With very little changes between the directories.
So I apparently have 4 forks of the tool available:
No suffix, m
, pg
and v2
. I assume v2
is pocketgo2v2?
https://github.com/Ninoh-FOX/toolchain/tree/master/updaters/imager_v2
It would be really nice to have some documentation and less redundancy here.
yes, v2 is pg2v2
I am go to add a document soom
In your buildroot fork you have an apparently unused make_initial_image.sh for the PocketGo 2v2 with it accompanying genimage.cfg.
I was able to manually copy a
mininit-syspart
, generate amininit-syspart.sha1
and execute the script more or less successfully, after updatinggenimage
to a less ancient version.Although the resulting
sd_image.bin
differs significantly from thesd_image_pg2.bin
you provide in your release section.The image is able to display the splash screen, but ends up in a resize / swap file creation boot loop and results in a corrupted app partition. It also creates an extra hibernate partition which you don't provide in your
sd_image_pg2.bin
and also differs in size of the app partition.Could you please publish your full build scripts, so others are able to reproduce an bootable image like
sd_image_pg2.bin
from source?Also pointing out any documentation how to create such an image would be very appreciated. In your readme you just provide the vanilla buildroot doc with some screenshots. The best documentation I was able to find on the topic is this Spanish blog post: https://apuntes.eduardofilo.es/2020-05-25-rg350_docker_buildroot.html