[NXBOOT] Failed to run TSEC firmware -6

myeuropeanPAL commented 3 years ago

Bug Report

[ If any section does not apply, replace its contents with "N/A". ]
[ Lines between [ ] (square brackets) should be removed before posting. ]

[ * ]
[ Note: If the bug or crash you encountered is related to; ]
[ - software used to make "backups", ]
[ - software explicitly distributed for piracy, etc ]
[ then contributors will not provide support for your issue and your issue will be closed. ]

What's the issue you encountered?

When booting into emuMMC with atmoshphere 0.20.1 I receive the following error message: [NXBOOT] Failed to run TSEC firmware -6 d0d0d0d0 d0d0d0d0!

How can the issue be reproduced?

Booting into emuMMC with hekate v5.6.0 & Nyx v1.0.6

Crash Report

/atmosphere/crash_reports folder does not exist

System Firmware Version

11.0.1

Environment?

What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
Official release or unofficial build: hekate v5.6.0 & Nyx v1.0.6
- [ Official release version x.x.x (or) unofficial build ]
- [ If using an unofficial build, include details on where/how you acquired the build. ]
  - [ Ex: Self-compilation ]
  - [ Ex: Kosmos' distribution of Atmosphère ]
Do you have additional kips or sysmodules you're loading:
Homebrew software installed: [ * ]
EmuMMC or SysNAND: EmuMMC, file-based

Additional context?

Additional info about your environment: EmuMMC firmware 12.1.0
[ Any other information relevant to your issue. ]

SciresM commented 3 years ago

Are you on a patched erista, by chance?

myeuropeanPAL commented 3 years ago

I don't think so, atmosphere-0.19.5 and is booting just fine with hekate v5.6.0 & Nyx v1.0.6

SciresM commented 3 years ago

"0.19.5" upgrade to latest 0.20.1? Does boot succeed using fusee primary directly instead of hekate, or booting directly via hekate instead of fusee primary?

could you post a screenshot of the console info -> fuses page in hekate if the issue persists?

ghost commented 3 years ago

Just to clarify, what they're saying is that the error happens when booting with 0.20.1, but doesn't happen when booting with 0.19.5

SciresM commented 3 years ago

There've been a few reports of this...all reporters have been using gateway's payload loader, which results in an unexpected boot environment.

If you're using that, switch to spacecraft-nx or whatever.

If you're not, we can re-open the issue/etc.

Atmosphere-NX / Atmosphere