My ESP32 issues.

[idahowalker]

For me the guru meditation error: core 0 panic'ed occurs once every several hours, after the addition of my last 2 tasks.

Running ESP32 and freeRTOS.

With freeRTOS, I am using the xTaskCreatePinnedToCore function.

So the fisrt thing I did was move one of the two newest functions over to the other core; from 0 to 1. I also made the tasks variables volatile. Whiles a 2nd task accessed the variables it did not modify them but *shrug* gotta try something.

Now I wait. In the mean time if anyone has any ideas, I all 'ears', errr I mean eyes.

[ESP_igrr]

You can try this documentation page, it explains more about various exceptions. Perhaps you can use the backtrace and core dump features to find the place in the code where error happens.

https://docs.espressif.com/projects/esp ... rrors.html

[idahowalker]

You can try this documentation page, it explains more about various exceptions. Perhaps you can use the backtrace and core dump features to find the place in the code where error happens.

https://docs.espressif.com/projects/esp ... rrors.html

I have managed to belay the number of times the error is happening by improving my code through the addition of (freeRTOS) semaphoremutex. Also, at this time the code, with the meditation error doing a reboot recovers as if nothing happened and the number of times the error happens has been reduced.

I have read over and bookmarked the link you posted. I will use the info provided in the link as I work on eliminating the error. Right now the error is only happening over the course of many hours and lots of waiting for it to happen again is on order.

Thanks for the link.

[idahowalker]

What does this mean :" [V] esp32-hal-i2c.c:1387] i2cSetFrequency(): Fifo threshold=9" ?

[idahowalker]

Update.

From the link, as posted above, I was able to determine that a null pointer to a structure was being given as the error message. With 3 queues on core 0, I, changed, one at a time, each queue sending a copy of the queue instead of a pointer. I am now left with one queue pointer on core 0 that has given me, finally, the guru meditation error. Now I am working, on the one queue that is using a pointer to a structure on core 0, on eliminating the error.

As a note: There are 3 structures on core 1 being passed by pointers, core 1 has not shown to have a problem.

[idahowalker]

Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC : 0x400d3ee8 PS : 0x00060830 A0 : 0x800d161c A1 : 0x3ffb7860
A2 : 0x3ffc2574 A3 : 0x3ffc2d61 A4 : 0x3ffc3e04 A5 : 0x00000000
A6 : 0x00000041 A7 : 0x0000000e A8 : 0x800d3ee8 A9 : 0x3ffb7840
A10 : 0x00000000 A11 : 0x0000002c A12 : 0xfffffc01 A13 : 0x000003ff
A14 : 0x7ff00000 A15 : 0x408f4000 SAR : 0x0000001d EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000001 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xffffffff

Backtrace: 0x400d3ee8:0x3ffb7860 0x400d1619:0x3ffb78a0

As per: https://docs.espressif.com/projects/esp ... rrors.html

LoadProhibited, StoreProhibited
This CPU exception happens when application attempts to read from or write to an invalid memory location. The address which was written/read is found in EXCVADDR register in the register dump. If this address is zero, it usually means that application attempted to dereference a NULL pointer. If this address is close to zero, it usually means that application attempted to access member of a structure, but the pointer to the structure was NULL. If this address is something else (garbage value, not in 0x3fxxxxxx - 0x6xxxxxxx range), it likely means that the pointer used to access the data was either not initialized or was corrupted.

When I received the above error, which is the error I have been continuously getting, I did not have any structures on core0. Also, all the structures that ran on core0 were moved to core1 and core1 has not given me such an error message.

I have, at this point, put in a new ESP32.

[idahowalker]

The new ESP32 did not want to upload and I did not feel like messing with it so I kept at it with the original ESP32.

Ends up that the Adafruit Ultimate GP library caused the error.

[idahowalker]

I have run into the issue of the 2 device thingy.

I have been able to run 1 I2C and 1 SPI device on the ESP32. When I connect, either 2 I2C or 2 SPI devices the ESP32 does not work anymore.

I have I can put device A on SPI HSPI or VSPI and that device works. I can put device B on SPI HSPI or VSPI and that device works. If I wires in device A on either HSPI or VSPI the alone device works, if I add in device B to the other SPI port then the ESP32 has issues booting or has issues uploading the library that will run the device B.

Also, I have the same sort of issue with I2C. I2C device A or B works well nut I2C A and B do not work well. Issue being the ESP32 fails to boot, fails to load the software, or fails to do 'anything' after an upload.

Ideas or suggestions are welcome.

[idahowalker]

What are the GPIO pins 6,7,8,9,10,11 good for if they are not to be used?

[ESP_Sprite]

What are the GPIO pins 6,7,8,9,10,11 good for if they are not to be used?

They are used, but they're used by the (external to the ESP32) flash chip that stores your program.