[ Describe the issue in detail and what you were doing beforehand. ]
I was booting up my switch in emunand cfw mode after updating the emunand firmware from 15.0.1 to 16.0.0 using tegraexplorer to dump the OFW firmware and daybreak to apply the update in Fat32 + ExFat. Atmo is latest stable release
[ Did you make any changes related to Atmosphère itself? ]
None so far from the previous one
How can the issue be reproduced?
N/A
Crash Report
[ Crash reports can be found under /atmosphere/crash_reports. ]
[ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ]
[ If you don't include a crash report in instances of crash related issues, we will ask you one to provide one. ]
atmo fatal error reports.zip
I tried submitting the fatal error bin files to the gist, but it wouldnt take, no matter what, and the crash report folder had outdated reports that did not match up with my current setup at all
System Firmware Version
OFW: 16.0.0 (previously 15.0.1 before updating)
CFW: 16.0.0 (from tegraexplorer firmware dump + daybreak update), was previously 15.0.1 before "updating"
Environment?
What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
Official release or unofficial build:
[ Official, Hekate 6.0.2]
Do you have additional kips or sysmodules you're loading: MissionControl v0.8.0 (sysymodule made for using other bluetooth based controllers like ds4 controllers, xbox controllers, etc...., )
Homebrew software installed: ignore the blurred title on that folder, gotta rename it to something less......let's just say crass, for now
EmuMMC or SysNAND: EmuMMC (I guess partition based? i usually use the fat32 + exfat format when doing the setup with tegra)
Additional context?
I just checked the MissionControl sysmodule to see if anything changed, and there was an update to work with the 16.0.0 firmware, will immediately try using it after removing the older one, see if it makes any difference. otherwise, if necessary, i can remake my atmo setup from scratch (will be a pain to make sure its all done right, but its doable)
Bug Report
What's the issue you encountered?
[ Describe the issue in detail and what you were doing beforehand. ] I was booting up my switch in emunand cfw mode after updating the emunand firmware from 15.0.1 to 16.0.0 using tegraexplorer to dump the OFW firmware and daybreak to apply the update in Fat32 + ExFat. Atmo is latest stable release [ Did you make any changes related to Atmosphère itself? ] None so far from the previous one
How can the issue be reproduced?
N/A
Crash Report
[ Crash reports can be found under
/atmosphere/crash_reports
. ] [ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ] [ If you don't include a crash report in instances of crash related issues, we will ask you one to provide one. ] atmo fatal error reports.zip I tried submitting the fatal error bin files to the gist, but it wouldnt take, no matter what, and the crash report folder had outdated reports that did not match up with my current setup at allSystem Firmware Version
OFW: 16.0.0 (previously 15.0.1 before updating) CFW: 16.0.0 (from tegraexplorer firmware dump + daybreak update), was previously 15.0.1 before "updating"
Environment?
Additional context?
I just checked the MissionControl sysmodule to see if anything changed, and there was an update to work with the 16.0.0 firmware, will immediately try using it after removing the older one, see if it makes any difference. otherwise, if necessary, i can remake my atmo setup from scratch (will be a pain to make sure its all done right, but its doable)