-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Moving PS5 controller away from ESP32 cause unhandled Exception #43
Comments
mmm.... Interesting |
It is a bit odd, I suppose the disConnected event should be triggered, but actually unhandled Exception been thrown. |
Any chance that you can symbolize the stacktrace (e.g: convert the addresses to names) ? I've just tried to reproduce it on a Sparkfun ESP32 Thing + Controller.ino and it disconnected without any problem. |
Hello sir, thanks for your reply, sorry I'm new to esp32, not too sure how can I symbolize the stacktrace, this issue doesn't happen every time but it happens pretty often, I can replicate this issue after a few attempts. I do turn the ESP32 power off and on again everytime I tried. Also while I was walking out of range, I was pressing down X button, pressing down L1,L2,R1,R1, rolling around left joysticks none stop. Please see below log output is I replicated this issue this evening. You may notcie before the 21:11:28.197 -> scan_evt timeout happened the controller already stuck with same input for about 10 seconds even I was moving the left joystick none stop the whole time. And FEX 0 0 starts to show after scan_evt timeout. 21:11:00.494 -> CALLBACK: Controller is connected, index=0 |
yep. not sure what could be causing it... unfortunately I cannot reproduce it. The backtrace could be useful if you somewhat can get the symbols of it. I cannot do that for you compiled the sketch. |
try with this site: https://maximeborges.github.io/esp-stacktrace-decoder/ |
Thanks a lot, I tried again, got stack trace, I commented out BP32.forgetBluetoothKeys() in setup() not sure if that actually make any difference, the exception happens with/without BP32.forgetBluetoothKeys() Log: |
Hello sir @ricardoquesada , I figured out a workaround. I notcied this issue happen after scan_evt timeout, so I added BP32.enableNewBluetoothConnections(false); inside onConnectedController. I belive enableNewBluetoothConnections(false) makes scan_evt stop. |
mmm... very interesting. I wonder if BLE is causing that. |
Hello sir, I'm not sure where should I post this issue, I also posted this issue at :
https://github.com/ricardoquesada/bluepad32-arduino/issues
If it creates a duplicate, I will delete that post.
I connected a PS5 controller to ESP32, it is working fine unless I walk away with the PS5 controller from the ESP32. The issue starts to happen when the PS5 controller 6 meters away from the ESP32.
What happened:
I'm using 'Controller' from example. Upload Controller to ESP32.
Pair PS5 controller with ESP32
Take PS5 controller about 6 memters away from ESP32, turn myself around make sure my body is between the PS5 controller and the ESP32's direction. Keep walking untill abount 10 meters away from ESP32, the PS5 controller turned off itself.
Below error happened in ESP32
FEX 0 0
FEX 0 0
FEX 7 0
ASSERT_PARAM(0 7), in ld_acl.c at line 1772
Guru Meditation Error: Core 0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x4008fed4: 00f01d00 00004136 f01d0000
Core 0 register dump:
PC : 0x4008fedb PS : 0x00060f34 A0 : 0x8008573e A1 : 0x3ffc1f50
A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000007 A5 : 0x3ff9cd42
A6 : 0x000006ec A7 : 0xfffffffb A8 : 0x8000814b A9 : 0x3ffc1ec0
A10 : 0x00000000 A11 : 0x3ffc1ee4 A12 : 0x3ffc1e8f A13 : 0x00000032
A14 : 0x00000000 A15 : 0x3ffc1e95 SAR : 0x00000004 EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000 LBEG : 0x40090f09 LEND : 0x40090f19 LCOUNT : 0xfffffffe
Backtrace: 0x4008fed8:0x3ffc1f50 0x4008573b:0x3ffc1f70 0x400327cb:0x3ffc1f90 0x40087bb5:0x3ffc1fd0 0x40087e89:0x3ffc1ff0 0x4008bde6:0x3ffc2020 0x4008c8af:0x3ffc2040 0x400850be:0x3ffc2060 0x400853dd:0x3ffc2080 0x400853bf:0x00000000 |<-CORRUPTED
ELF file SHA256: 60dedc08e98be6b0
Rebooting...
The text was updated successfully, but these errors were encountered: