Open davesmeghead opened 1 year ago
Moved to long term because it wasn't reproducible by the original filer. Leaving it open in case someone else sees it.
Hi, apologies and I should have updated this issue here but I do get this regularly: CircuitPython core code crashed hard. Crikey! Hard fault: memory access or instruction error
Although I'm only developing the software for the ESP32-S3 at the moment and not using it properly so I assumed that this is a regular occurance and was a known problem being worked on. I also have a lot of python code in at the moment and it's difficult to upload it all but I have no problem with doing that if you want me to. Is it possible that I have a faulty board? If it isn't then I'll try and get something that is repeatable and upload the code here. Is there more information about the problem that I can do with CircuitPython to get it to output more details? Thanks
Is it possible that I have a faulty board?
I doubt it. These errors are usually a software problem.
If it isn't then I'll try and get something that is repeatable and upload the code here.
A small, reproducible code snippet is always best for debugging.
Is there more information about the problem that I can do with CircuitPython to get it to output more details?
You can build a version of CircuitPython that will output the ESP-IDF logging over UART and it'll include a backtrace. See the build instructions and add DEBUG=1
. The #circuitpython-dev channel on the Adafruit Discord is the best place for help getting the build going.
CircuitPython version
Code/REPL
Behavior
CircuitPython core code crashed hard. Crikey! Hard fault: memory access or instruction error
Description
I'm just starting to mess about with it so the program is a mishmash of me trying things but I copied it verbatim
EDIT: After powering the board off and on I can't repeat the problem. I was using it for a long time before though. Also, I realise that I've missed out some imports for the HTTP but I wanted to copy the code as I tried it verbatim.
Additional information
No response