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
Incorrect fusee version! (program=0x4aa02b53, mtc=0x00000000) #2283
Comments
Invalid fusee/atmosphere combo. Either you are launching atmos with a old fusee or you are launching fusee with a old atmos. Make sure that you update the payload in the correct places, it sounds like you are accidentally still using the old fusee. |
You would think. I’ve triple checked. I don’t understand how. Used the latest Atmos and the corresponding fusee :/ |
Well, afaik, that's the only codepath that would cause that error. Not sure what else to tell you really, somehow, you are causing a mismatch |
Download the latest releases from Atmospehre and the fusee.bin and unpack them on your SD card. If he asks you if you want to overwrite it, just say yes, done. Then simply start atmospehre with fusee.bin. |
I've done this time after time still being met with the same screen. Is ther anything I could be overlooking to cause the misalignment? I've overwritten everything and using the most current version of fusee. |
put fusee.bin in /bootloader/payloads/fusee.bin if it launches successfully then you're definitively not injecting the correct payload. |
You have to replace the fusee.bin that you are using as your payload in tegra, my guess is you didn't do that and still sending an old fusee with tegrarcm, that is separate from the copy on the sd card. |
Bug Report
Injecting fusee to launch atmosphere and consistently run into this failure.
What's the issue you encountered?
After replacing the fusee, atmosphere version, and hekate making sure everything was correct, I still run into the message in the title. I'm using TegraRCM mostly but i did try through hekate too.
System Firmware Version
17.0.1
Environment?
Official builds, using Fusee, file based EmuMMC
Additional context?
This is the 3rd switch I've homebrewed and haven't encountered this issue before.
The text was updated successfully, but these errors were encountered: