Looking for how they Complied for PicoBoot? [question]

[Dracrius]

Describe the problem you're having

A clear and concise description of what the bug is.

I have attempted to build a more recent more stable version of cubeboot from the current Pull Request #40 to run on PicoBoot. I've got the dol created but when you follow the PicoBoot Compile Guide like so (webhdx/PicoBoot#110) it will fail as @webhdx clarified

The DOL file has to use the same entrypoint address as the original IPL (0x81300000). Cubeboot DOL is compiled to use a different address which makes it incompatible with PicoBoot. They have provided precompiled PicoBoot firmware in the past but I don't the details what kind of process they used to compile it. You have to try asking them for help.

As such I've created this issue in hopes that someone that is still around may know how @OffBroadway compiled cubeboot for PicoBoot despite the entry point mismatch.

Thanks in advanced, I'm sure it will help countless people if we can get this documented as cubeboot is really nice to have but has quite clearly fallen out of development so we need to update it ourselves! Especially with M.2 Loader around the corner we won't be able to run on these really old builds for much longer.

…
cubeboot.zip

[Dracrius]

By searching the forks I found that @Creamen made a fork with a docker file Creamen@aa23480 which I used to figure out how it was done! For future reference if you don't feel like digging through and you find this out of the half a dozen dol files this project creates it is the one in the entry folder that works with the PicoBoot build tools.