-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
[Bug Report]: 4 in 1 retro arcade controller (USB) crashing switch when trying to connect #792
Comments
Mission Control doesn't currently support USB controllers, but that is indeed Mission Control crashing. Have you perhaps installed an experimental USB build from my discord server? In any case, if you can share the error report I'll take a look at it. I've never heard of a report not showing up in the path displayed on the fatal screen. Make sure you're actually looking in the correct directory. Atmosphere creates several directories for different types of error reports/logs (I often get confused between them) |
I've installed the Mission Control from HB-Store which is 0.10.0. Yea the report wasn't shown from the ftp server but i could find it via file-browser. |
Error reports aren't encrypted, just binary data. You can read them with https://github.com/cathery/AFE_Parser if you want to peek inside yourself |
ahaha, yea encryption wouldn't have make sense at all. Thanks for the parser link. It got me this report. `Fatal report (AFE2): Registers: pstate: 0x80000000 Stack trace: Stack Dump: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 TLS Dump: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f000000 04 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 But to be honest Im not deep enough into the Atmosphere structure to interpret this :/ nor where this Stack trace return Addresses gonna lead me. Can you enlight me? |
FYI, I actively maintain a fork of sys-con -> https://github.com/o0Zz/sys-con |
Switch Firmware Version
17.0.0 (Latest)
Atmosphère Version
1.6.0 (Latest)
Mission Control Version
0.10.0 (Latest)
Boot Method
Hekate
Issue Description
In an Atmosphere 15, the controller worked well. But now it isn't recognized and sometimes crashes the whole switch, requiring a reboot.
I'm guessing that this controller is mimicking a Switch Pro controller because it worked earlier, but I can't find the crash report mentioned in the panic log. There is no log or bin in /atmosphere/fatal_errors/report_#####.bin.
I've already installed sys-con but the Error log leads to MissionControl didn't it?
How can I get the logs for this bug?
Error Report
Additional Context
No response
The text was updated successfully, but these errors were encountered: