Hey there, looking at the code i didnt immediately found what is causing the issue, but i had a couple of ideas that i think it would also work. Personally i think it would be easier to work with tasks instead of interrupts. ESP32 has freertos embedded Ex task 1 control the wifi connection, this inc...

About the reason the crash was happening: I was processing some commands within the SerialBluetooth callback, this was probably causing an delay or stack issue and causing the weird issue. To fix it i've created an queue, and the only thing the callback does now is copy the rx buffer to this queue. ...

Update: Found an case where the function crashed and exited without returning the semaphore first, this was causing the issue. Thanks for the tips.

Hi, why when this crash happens the esp32 does not reboot as usual? is there some kind of setting which i could change to make sure that i does reboot? or would be best to make a separated hardware watchdog? (already tried to find the crash cause here https://www.esp32.com/viewtopic.php?f=19&t=32432...

I'm receiving error 500 (screenshot attached) when trying to use the search function in this forum. tried using vpn and changing to a secondary network without any luck

This one is taking my sleep, lol :cry: I still believe that the issue happens when more than one "thing" is trying to access the i2c bus, but unfortunately i cant find out who to blame! every function that access i2c are inside its own task, which is protected by the same shared semaphore. and i che...

Hello ESP_Sprite, thanks for the suggestion, i believe it was indeed corruption duo access conflict during void setup() phase, while i was setting the last modules up, the first ones already had they tasks running, causing competition to access the i2c, conflicting with the setup_functions which wer...

Hello!, I have 5 tasks accessing the multiple devices under the same i2c bus, to avoid conflict i have added semaphore on them, but i am still getting these errors (originating from different tasks): ERROR 1: assert failed: xQueueGenericSend queue.c:832 (pxQueue->pcHead != ((void *)0) || pxQueue->u....

There are a couple of possible reasons i can think of: - Does your relay board has an optocoupler? its important to keep the output eletrically isolated from the relay, it draws way too much current for the output, and its a good idea having an diode to protect against switching surges (reference ht...

I'm making a simple program to measure for how long a pin stays on, and i'm getting ~42us delay on interrupt change routine exemplified below, any ideas on how to improve this code? Outside the interrupt i'm running a calculation formula once every second, inside the main loop, which reads instant_c...