Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cubeboot.ini not responding to changes. #10

Open
pvtd0nut opened this issue Oct 11, 2022 · 9 comments
Open

cubeboot.ini not responding to changes. #10

pvtd0nut opened this issue Oct 11, 2022 · 9 comments
Labels
question Further information is requested

Comments

@pvtd0nut
Copy link

Hi,

Love having the animation back. I'm using IPL boot through pico, I get a perfect animation for boot but no matter what I do, I can't get the cubeboot.ini to actually make any changes.

I'd absolutely love to see a guide on how to make changes.

Cheers!

@pvtd0nut pvtd0nut added the question Further information is requested label Oct 11, 2022
@trevor403
Copy link
Member

Hello! At the moment, cubeboot does not iterate all devices looking for a cubeboot.ini file. Once it finds a device, it will mount it and only use that device. So check if you have an SDGecko or GCLoader plugged in.

The order that cubeboot will search for devices now is: GCLoader, SD2SP2, SDGecko Slot B, SDGecko Slot A

@pvtd0nut
Copy link
Author

I have my SD in my SD2SP adapter, plugged into the serial port.

@zekromisblack
Copy link

i also have this issue, although my gc boots fine into swiss and i only use the sd2sp2

@trevor403
Copy link
Member

If you have a GCLoader, cubeboot will only look on that SD card for cubeboot.ini

I can make cubeboot look at every device but that is going to change boot times. Maybe we can add a compat version.

@zekromisblack
Copy link

i dont use a gc loader, i used the sd boot method with picoboot, a compat version would be handy though

@zekromisblack
Copy link

I've tested both the sd boot method and the rp2040 method and both do not respond to ini changes (eg colour and custom text) boot animation works fine though

@pvtd0nut
Copy link
Author

pvtd0nut commented Nov 1, 2022

I've tested both the sd boot method and the rp2040 method and both do not respond to ini changes (eg colour and custom text) boot animation works fine though

Exactly my experience.

@PegasystemsInc
Copy link

@pvtd0nut @zekromisblack Not sure what either of your INI files look like, but when I downloaded the default INI file, each line began with a semi-colon and a space. I took a look through the code and discovered that the semi-colon is an escape character and that any line beginning with one will be disregarded. I deleted both the semi-colon and the space after it, and this fixed my issue.

I'm not sure if this is the issue that you are both facing, but I figured I'd call it out since it sounds similar to what I was dealing with.

@zekromisblack
Copy link

@PegasystemsInc This fixed it perfectly.

@trevor403 side note you may want to edit the included INI file so users don't have to troubleshoot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants