ESP_Sprite wrote: ↑

Tue Aug 29, 2023 12:31 am

I'm thinking that this may be some weird behaviour in the log_i function rather than the event groups, but I don't have a theory for how that could work.

Yes, I'd be hard pressed to explain that. Especially when it works as expected if I use a Task Notification rather than an Event Group bit.

Interestingly, it works as expected when using a Task Notification . So perhaps unblocking tasks using Event Groups doesn't happen immediately (regardless of the task's priority), but on the FreeRTOS tick boundaries??? #include "Arduino.h" void producerFunction(void *pvParameters); void consumerFunc...

Hello. In the MRE below, the Consumer Task has a higher priority than the Producer Task. So, when the Producer sets the Event Group bit, I would expect the Consumer Task to preempt it, do its printing, and then block itself again BEFORE the (lower priority) Producer Task resumes executing. Therefore...

Hi gfvalvo, ... See taskYIELD_OTHER_CORE in tasks.c. @esp_programmer, thanks for the reply. Where did you find task.c? It's not in my installation, only task.h. Also there is no mention of 'taskYIELD_OTHER_CORE' in any file of my ESP32 installation. However, I did find the following in portmacro.h....

Hello, Suppose a task running on Core 0 posts some data to a FreeRTOS queue. Suppose further that a very high-priority task, that's pinned to Core 1, is currently blocked, pending on information to enter that queue. Ideally, the high-priority task should very quickly become unblocked and preempt wha...

Thanks for the reply. I guess Espressif came to that epiphany sometime between creating the ESP8266 core and creating the the ESP32 core.

So, the ESP8266 Arduino core has a very handy file called 'TZ.h" located in: …/esp8266\hardware\esp8266\3.1.1\cores\esp8266 It contains the Unix time zone codes ('TZ' environment variable) for hundreds of locations around the world. They're defined with human-readable macros. For example: #define TZ...

I did get it to "work" using URL https://raw.githubusercontent.com/espre ... index.json and v1.0.4. But, haven't played with it any since.

Ahhhh … got it. So, it acts kind of the same as a Critical Section would on a single-core, "Vanilla FreeRTOS" implementation for the local core but also makes the "other" core spin if and only if it also tries to acquire the lock.
Thanks.

I realize that this is a really old thread. But, it seems the proper place to post my question. My understanding of a Task or ISR "spinning" is that it's in a loop constantly trying to get ownership of the "lock". There are no context switches so nothing else runs on that core. So, my question ... w...