Hacking Question Atmosphere crashes loading CFW (emuNAND), Hekate crashes loading CFW (sysNAND) & Stock

[DWK]

Okay, tl;dr at the top, my guess is this is happening because the OFW has been updated to 12.0.0. BUT, this means there is something fundamental I don't understand: Why would Atmosphere crash when booting up through emuNAND when emuNAND is still on 11.0.1? Why would Hekate crash loading Stock when that doesn't involve CFW?

When Atmosphere crashes, it's when the Switch logo appears, and it's the screen with the Atmosphere logo and the registers dumped, etc. Hekate crashes when loading sysNAND or Stock saying that the pkg1 version is invalid, which makes sense to me for sysNAND since it's trying to apply CFW, but why is it crashing with the same error when loading Stock?

So, even if the problem is understood (updated to 12.0.0), can anyone help me understand WHY I'm encountering the errors loading 11.0.1 emuNAND or OFW Stock through Hekate?

 

[Adran_Marit]

Okay, tl;dr at the top, my guess is this is happening because the OFW has been updated to 12.0.0. BUT, this means there is something fundamental I don't understand: Why would Atmosphere crash when booting up through emuNAND when emuNAND is still on 11.0.1? Why would Hekate crash loading Stock when that doesn't involve CFW?

When Atmosphere crashes, it's when the Switch logo appears, and it's the screen with the Atmosphere logo and the registers dumped, etc. Hekate crashes when loading sysNAND or Stock saying that the pkg1 version is invalid, which makes sense to me for sysNAND since it's trying to apply CFW, but why is it crashing with the same error when loading Stock?

So, even if the problem is understood (updated to 12.0.0), can anyone help me understand WHY I'm encountering the errors loading 11.0.1 emuNAND or OFW Stock through Hekate?

Okay the second part is because stock still uses the secmon from atmosphere iirc, however, that isn't updated for 12.0.0

as for the emunand crash that's what I don't know and am looking for an answer myself

 

[petspeed]

Do you have a cartridge in the slot? If yes try without it.

 

[DWK]

Do you have a cartridge in the slot? If yes try without it.

Wow, okay, yeah – I had my Xenoblade Chronicles DE cart inserted. After removing it, booting into emuNAND land works fine. But, inserting the cartridge again at any point after this causes it to immediately crash again in the same way. Any idea why this is? Does it have to do with OFW being on 12.0.0, or is that just a coincidence? I've been able to use the cartridge before on 11.0.1/Atmosphere 0.18.1, and I can't imagine why that no longer works.

 

[Chocola]

The lotus firmware (Game cart reader firmware) are updated in 12.0.0, if you like to boot with older version you need to set no_gc option and wait for 12.0.0 support to use cartiges on CFW

 

[DWK]

The lotus firmware (Game cart reader firmware) are updated in 12.0.0, if you like to boot with older version you need to set no_gc option and wait for 12.0.0 support to use cartiges on CFW

Okay, I hadn't thought about the cartridge reader having its own firmware.

So, what does it mean that no_gc is enabled by default and I haven't changed it? That is, how does no_gc work to prevent cartridge firmware upgrades if it's unwise to be running CFW while connected to Nintendo's servers, e.g. for a system update? If I boot Hekate then launch full stock, will no_gc persist (or even apply)? Or are there offline copies of the firmware somewhere that I ought to consider instead for upgrades?

However that might work, I think it's obvious now that I ought never to upgrade unless it's vitally important to do so, i.e. for a critical bug or more importantly because a game requires it.

 

[Chocola]

Okay, I hadn't thought about the cartridge reader having its own firmware.

So, what does it mean that no_gc is enabled by default and I haven't changed it? That is, how does no_gc work to prevent cartridge firmware upgrades if it's unwise to be running CFW while connected to Nintendo's servers, e.g. for a system update? If I boot Hekate then launch full stock, will no_gc persist (or even apply)? Or are there offline copies of the firmware somewhere that I ought to consider instead for upgrades?

However that might work, I think it's obvious now that I ought never to upgrade unless it's vitally important to do so, i.e. for a critical bug or more importantly because a game requires it.

Yup, it have a dedicated ASIC with his proper firmware and sometimes N update it, I imagine that they want the control on reader to prevent cartiges like old R4 for example.

OFW always gona update the lotus firmware, the no_gc option it's to prevent update through CFW, for example if you have your Sysnand on v 10.0.0 and you update your emunand to v 11.0.0 the no_gc option disable reader and prevent the lotus firmware update of your v 11,0.0, in this case if game reader got updated by CFW you lose the reader on OFW, then atmosphere handle it automatically to prevent it.

On your case, the OFW update the game cart reader firmware (and this is inevitable with OFW, because didn't have any prompt or option to disable it), then atmosphere crash because version mismatch.

The lotus firmware it's inside Switch firmware updates, not in all, only specific, but we don't have so much information about it for now, and as I know, the game cart reader have downgrade protection, so we can't reflash a older version.

I always wait to update, usually games and online didn't require the update instantly, you can play in older version anyways meanwhile the CFW support the new version again, the only anoying thing it's the constantly update dialog prompt.

 

[Chocola]

Update to last atmos, 12.0 supported: https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.19.0 and reenable gc if you like use carts on atmosphere ^^