You need Trinket/rebug I think as you are using the new methods if I remeber correctly.@mattytrog which one of the 2? legacy or method3?
You need Trinket/rebug I think as you are using the new methods if I remeber correctly.@mattytrog which one of the 2? legacy or method3?
Is bootlogo drawing messed up for you on 1.3.2? I get no boot logo after the Sept screen minus this little bar on the left edge of the screen.1.3.2 installed and working well, thank you for all the continued updates and support
There is no built-in bootlogo. You need to add one.Is bootlogo drawing messed up for you on 1.3.2? I get no boot logo after the Sept screen minus this little bar on the left edge of the screen.
Is bootlogo drawing messed up for you on 1.3.2? I get no boot logo after the Sept screen minus this little bar on the left edge of the screen.
Lol nah... Just bits and bobs added. Thank-you anyway!As standard there isn't one, I think you must add one in
It's running extremely well for me, this chip software keeps getting better and better.... everyday is June 15th with Mattytrog at the wheel
Right. I did. Just used the standard Atmosphere boot logo. Worked fine on Switchboot 1.2.2 and Hekate 4.10 and 4.10.1 with the same image and INI file.There is no built-in bootlogo. You need to add one.
Right. I did. Just used the standard Atmosphere boot logo. Worked fine on Switchboot 1.2.2 and Hekate 4.10 and 4.10.1 with the same image and INI file.
Works fine here... Yeah I see the strip on the edge. Will fix that for next release.
No, it doesn't. Try an older Switchboot, or Hekate to see the difference. After the Sept screen, the boot logo should display again and not be immediately erased. From power off, it should go: Boot logo, Sept screen, Boot logo, Nintendo Logo, Switch Logo.
Ummm...OK
I can add a delay if you like to stop the fb clearing so quickly...
The boottime has got faster. Thats why is disappears quickly but I can slow it down if you wish.
There is also a boot delay option.
The FB is cleared as soon as boot begins (hence the "free (bootlogo);")Boot delay is set to 2 or 3 for me. But boot delay is before the Sept screen. Spend 5 minutes trying Hekate or an older Switchboot to see the difference. The framebuffer clearing is not because the boot sped-up, unless by that you mean your modification to the code jumps to clearing the framebuffer while still doing other stuff in the background.
Thank you for the feedback sir!Updated my Trinket from 1.10 to 1.3.2 and so far everything working great including the SXOS License.dat restore feature. Thanks for the continued work on this
I think I hardcoded switchboot in there... I know I have now. Not uploaded it yet.And I forgot the source before...I am using Mode 1 in a few switches and your Fusee-UF2 chain loader seems to be an ideal solution for a more permanent flash. I was trying to find a way to get Fusee-UF2 to chain launch SwitchBoot so it would be easier to update in the future. Having to reflash the trinket every time a new Atmosphère build or new Switch update is released is a bit problematic when helping friends update their hardware.
The idea would be to have Fusee-UF2 launch a start.bin on SD root, actually SwitchBoot.bin, and then have SwitchBoot autolaunch payload.bin as usual. This would allow to update SwitchBoot by simply replacing start.bin with the latest version when it's updated. The problem is that both Fusee-UF2 and SwitchBoot are hardcoded to look for and launch payload.bin which results in an infinite loop if Fusee-UF2 launches Switchboot directly (as payload.bin).
I've looked for the source Fusee payload you have created to simply change the payload filename but I cannot find it on your github. Do you have the source available somewhere or would you be willing to build a "special" UF2 version that looks for a different filename on SD root so we can chain Fusee-UF2 and SwitchBoot?
Appreciate all the work you have been doing - have been a day 1 user of your trinket m0 solution. Cheers!
I think I hardcoded switchboot in there... I know I have now. Not uploaded it yet.And I forgot the source before...
In summary...
I have made a new Fusee-UF2 that works exactly the same as before... Apart from "switchboot.bin" is hardcoded... So if switchboot.bin is found, that will run instead of payload.bin... Of course if you have a payload.bin, that will be launched by "switchboot" as it has hijacked Fusee-UF2. If there is no Switchboot, payload.bin will launch as usual.
Also... Fusee-UF2 will make a new text file on SD root (only 70 ish bytes) that contains strap info. If straps are connected and working, this file will tell you. This can then be viewed or imported into switchboot/hekate or whatever to be displayed.
If you don't need the information, feel free to ignore it.
So, the chain of command will go...
Fusee-UF2 runs... Is switchboot present?
Yes - run switchboot. No - run payload.bin... if neither are present, max77620 reboot state is reset and unit powered off.
If yes, switchboot will launch your payload.bin as it has taken over from Fusee-UF2.
You need Trinket/rebug I think as you are using the new methods if I remeber correctly.
nah it's cool
Nah it' all good thanks. I'll un-solder the strap see how it goes.