Hi all -
My app has recently started to show this error. It occurs on a seemingly quiet device, every hour or so. I'm using IDF v4.1 on a WROVER module.
According to the docs, this is caused either by a task ending, or some interference on a flash pin. I've virtually ruled out the possibility of a task ending. Since I'm using a self-contained ESP32 module, I don't see how I can be upsetting the flash pins, unless it has something to do with my configuration settings.
Here's a representation of my SPI settings. Can anyone see something I've configured that might be causing this?
Thanks...I really need to eliminate this ASAP.
(solved) GME: IllegalInstruction
(solved) GME: IllegalInstruction
- Attachments
-
- spi.png (46.51 KiB) Viewed 2713 times
Last edited by mzimmers on Fri Nov 13, 2020 7:42 pm, edited 1 time in total.
-
- Posts: 9050
- Joined: Thu Nov 26, 2015 4:08 am
Re: GME: IllegalInstruction
Note it can also be a power supply issue sometimes. Just an extra thing to perhaps keep an eye out for.
Re: GME: IllegalInstruction
Hi Sprite -
That was one of my first thoughts too, but I have three units, all connected via different power mechanisms, that exhibit this error.
This is a relatively recent problem. I'm not sure, but I think it might have coincided with my move to v4.1. I upgraded to commit c7ba54e on the recommendation of igrr, but that didn't fix the issue.
That was one of my first thoughts too, but I have three units, all connected via different power mechanisms, that exhibit this error.
This is a relatively recent problem. I'm not sure, but I think it might have coincided with my move to v4.1. I upgraded to commit c7ba54e on the recommendation of igrr, but that didn't fix the issue.
-
- Posts: 9050
- Joined: Thu Nov 26, 2015 4:08 am
Re: GME: IllegalInstruction
Strange. What does the crashdump look like on these devices? Any similarity, or just a crash at a random location?
Re: GME: IllegalInstruction
Igrr gave me a patch 10306. Said it was a known problem, but the fix hadn't made it into release/v4.1 yet. Seems to be fixed now.