Skip to content
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

Open
masterpwarz opened this issue Mar 25, 2024 · 4 comments

Comments

@masterpwarz
Copy link

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.

Unbenannt

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

20240325_015450

Additional Context

No response

@ndeadly
Copy link
Owner

ndeadly commented Mar 26, 2024

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)

@masterpwarz
Copy link
Author

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.
It seems encrypted. How do you read that bin file?

report_2db7af6b4.zip

@ndeadly
Copy link
Owner

ndeadly commented Mar 26, 2024

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

@masterpwarz
Copy link
Author

ahaha, yea encryption wouldn't have make sense at all. Thanks for the parser link. It got me this report.

`Fatal report (AFE2):
Magic: AFE2 (0x32454641)
Error description: 0xFFE
Title ID: 10000000000BD00

Registers:
X[00]: 0x2ef271
X[01]: 0x2ef271
X[02]: 0xffffffffffffffcc
X[03]: 0x45aa36cf40
X[04]: 0x45aa36cf8c
X[05]: 0x4
X[06]: 0x0
X[07]: 0x0
X[08]: 0x0
X[09]: 0x0
X[10]: 0x0
X[11]: 0x0
X[12]: 0x1df0
X[13]: 0x0
X[14]: 0x0
X[15]: 0x0
X[16]: 0x0
X[17]: 0x0
X[18]: 0x5d75c042d02fa245
X[19]: 0x45aa36edb0
X[20]: 0x2401c9b450 (MOD_BASE + 0x9b450)
X[21]: 0x2401c9b508 (MOD_BASE + 0x9b508)
X[22]: 0x0
X[23]: 0x0
X[24]: 0x0
X[25]: 0x0
X[26]: 0x0
X[27]: 0x8
X[28]: 0xa55af00ddeadcafe
FP: 0x45aa36ed80
LR: 0x2401c1f5bc (MOD_BASE + 0x1f5bc)
SP: 0x45aa36ed70
PC: 0x2401c342a8 (MOD_BASE + 0x342a8)

pstate: 0x80000000
afsr0: 0x10600
afsr1: 0x11000000
esr: 0x0
far: 0x8
Report identifier: 0x2db7af6b4

Stack trace:
ReturnAddress[00]: 0x2401c2c8b0 (MOD_BASE + 0x2c8b0)
ReturnAddress[01]: 0x2401c348fc (MOD_BASE + 0x348fc)
ReturnAddress[02]: 0x0

Stack Dump: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f

000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000010 e0 ed 36 aa 45 00 00 00 b0 c8 c2 01 24 00 00 00
000020 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000030 58 80 15 00 00 00 00 00 01 00 00 00 00 00 00 00
000040 b0 ed 36 aa 45 00 00 00 b0 ed 36 aa 45 00 00 00
000050 01 01 00 00 58 80 15 00 00 00 00 00 24 00 00 00
000060 60 ee 36 aa 45 00 00 00 02 b4 c9 01 24 00 00 00
000070 30 ee 36 aa 45 00 00 00 fc 48 c3 01 24 00 00 00
000080 60 ee 36 aa 45 00 00 00 08 f5 8a 52 34 00 00 00
000090 00 80 ca 01 24 00 00 00 00 00 00 00 00 00 00 00
0000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000b0 60 ee 36 aa 45 00 00 00 20 01 00 00 00 00 00 00
0000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000f0 20 b5 c9 01 24 00 00 00 60 c7 c2 01 24 00 00 00

TLS Dump: 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f

000000 04 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00
000010 02 00 00 00 07 00 00 00 00 00 00 00 00 00 00 00
000020 00 00 00 00 00 00 00 00 00 00 00 00 7e 8c 12 81
000030 00 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00
000040 00 00 03 50 68 02 00 00 00 00 00 00 00 03 00 00
000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0000f0 00 00 00 00 00 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants