-
Notifications
You must be signed in to change notification settings - Fork 95
Allow xell-gggggg to boot from XellLaunch on an RGH #28
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
Allow xell-gggggg to boot from XellLaunch on an RGH #28
Conversation
|
Nvm, going to close this one. Doesn't appear to work on my RGH3 corona... will need to come back to this eventually. |
|
From startup threads code: You're checking: Could be a typo and just luck that it worked on another system..? |
Good catch, it's pretty late for me and I didn't notice the typo when I copied the code out of my own XeLL fork. I'll fix it and retry in the morning. Fingers crossed that's it. |
|
Corrected the typo, can confirm it now works on my corona 4gb and 16mb winch |
|
Do you have a JTAG console to verify that it's working correctly there aswell still? |
I do have a JTAG falcon as well, I will test it there this evening and report back. |
8673700 to
f3f2d27
Compare
|
@Swizzy just tested on my falcon JTAG, everything works as expected. I'm able to boot from eject at system startup, from the dashboard with XellLaunch, and i can return to XeLL from another libxenon app. I did force push back to commit f3f2d27, even though wakeup_cpus isn't really used anymore it is referenced by |
I think we'll adress that at a later time. |
The reason xell-gggggg hangs on a black screen when you try to start it from a running system with something like XeLLLaunch is because it's programmed to always go down the SoC init codepath, which is only appropriate when we're jumping to XeLL early on in the boot process. When starting from the dashboard (or on a JTAG) we should be going down the thread catch codepath.
To determine whether or not to go down the thread catch codepath, this PR checks to see if thread 0 has been started. Otherwise, we go down the SoC init path. I've tested this on my RGH falcon, 0f Xenon, rgh corona, and winch and it seems to work OK, but wider testing would be useful
This is based on my code pasted in the discord channel:
https://discord.com/channels/1415992251707818046/1415993110734962719/1432909307602534522