-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CircuitPython core code crashed hard. Whoops! #7925
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
Comments
Please update your UM FeatherS2 to Circuit Python 8.0.5 stable or newer release and try again. Most of the hard fault issues dealing with Wifi & MQTT have been addressed in 8.0.5 as beta tested in issue #7907 If your project still hard faults after upgrading then we will need another round of beta testing with your code. |
Thanks DJDevon. CircuitPython core code crashed hard. Whoops! The UM FeatherS2 had been running for 2.5 hours, at the time of the crash the MQTT topic was static so no changes being made to the GPIOs. Just monitoring in the MQTT loop. |
Could you also try with "Absolute Newest", linked from the board download page on CircuitPython.org? |
I actually have a pan/tilt servo kit. Can help test this on latest beta release sometime this week on the UM Feather S2 with motor featherwing. The UM FeatherS2 has a special featherS2.py that is created upon initial install with many pre-defined functions. I'm not sure if they're required or just helpers but in all of my uses I've always included it in my code.py def enable_LDO2(state):
"""Set the power for the second on-board LDO to allow no current draw when not needed."""
ldo2.value = state
# A small delay to let the IO change state
time.sleep(0.035) import feathers2
# Make sure the 2nd LDO is turned on
feathers2.enable_LDO2(True)
# Turn on the internal blue LED
feathers2.led_set(True) Unlike the Adafruit Feather ESP32-S2 the UM FeatherS2 has a 2nd LDO that should be enabled for some things. I haven't used it specifically yet, I think it's for helping low power consumption by automatically shutting off the 2nd LDO during deep sleep. If there is an issue with sleep commands possible hard faults might occur? Needs investigation. I hammered on MMQTT and I2C on the UM Feather S2 last week with over 25,000 transactions over 72 hours. The code I used is now an example in my Github for the UM FeatherS2. This hard fault has to be coming from something else that I didn't specifically test for last week. Will look into it with you. |
Thanks, I will add the LD02 code and have a look at your example. |
Hi Dan, yes I will try the newest over the weekend as well. Thanks |
Using the latest "Adafruit CircuitPython 8.1.0-beta.2 on 2023-04-26; FeatherS2 with ESP32S2" and the code has the "feathers2.enable_LDO2(True)" the UMFeatherS2 has run for 10 hours without crashing. Using 2 UMFeatherS2 I have sent 140,000 MQTT messages from one to the other via a raspberry pi running mosquito. One way only and neither have crashed. |
@devansau That's great news! If you could test it without the LDO2(True) to intentionally try to get it to fail that would definitely help. |
@DJDevon3 @dhalbert All good with the LDO2(True) removed. @DJDevon3 I have used the adafruit motor featherwings and it works well. I recently upgraded the motors and smoked 2 motor featherwings. I think it was the back EMF so I have reverted to my own board which deals with this. |
Awesome! Good luck with your project. Thank you for the testing. Might want to consider opening an issue for the motor featherwings or were you using them beyond the rated capability? |
CircuitPython version
Code/REPL
Behavior
Auto-reload is off.
Running in safe mode! Not running saved code.
You are in safe mode because:
CircuitPython core code crashed hard. Whoops!
Crash into the HardFault_Handler.
Please file an issue with the contents of your CIRCUITPY drive at
https://github.com/adafruit/circuitpython/issues
Press any key to enter the REPL. Use CTRL-D to reload.
Adafruit CircuitPython 8.0.3 on 2023-02-23; FeatherS2 with ESP32S2
Description
There is not enough info i the crash to say any more.
Pins D12, D9, D19 and D15 are driving a relay board.
The program runs for hours and then a hard fault on circuitython.
Additional information
I have had this running on a MAC serial port and it shows the hard fault.


I have had it running initiallyy on batteries with no console and it stops and I assume it is with the same hard fault.
Any fault finding suggestions would be appreciated.
The text was updated successfully, but these errors were encountered: