I use esp_timer_get_time() function.

That's the reason.

You're right.
I found a simple intermediate solution:
using cpu_hal_get_cycle_count() function (paired with _set_) instead of esp_timer_get_time()

Thanks everyone!

UPD: hardware timer also works well

Do you need to match only the frequency or also the phase?

Phase (the exact time beetwen local and remote periodic events) is a fundamentally important and is the main goal of measurements

What kind of timer for microseconds checking you use?
If it's the hardware timer, then it could be interrupts priorities: systick timer may have the highest interrupt priority.
What's the original purpose to account microseconds?
For flow counter I used PCNT



I use esp_timer_get_time() function ...

At 240MHz, the 32 bit CPU cycle counter overflows every 17.89 seconds. Coincidence?

This is obvious. Common place

My program measures the exact time between two events (interrupts) with microsecond accuracy. Every 17.8 seconds the measurements are distorted by several hundred microseconds. Has anyone encountered such behavior of FreeRTOS?

Did you find a solution for this?
I am having the same problem.

It seems like there should be a solution, since ESP32 apparently allows you to use any GPIO pin for I2S.

You have to create custom board with your pins etc. configuration and select it in Configuration

Is it already known when to expect the ADF version (v.2.7) compatible with IDF v.5.3?

I'm wondering if the expected dual-band chip (ESP32-C5) will support the ESP-NOW protocol?
Maybe some new features or restrictions?