ESP32 Forum

Hello.

Consider having a task pinned to core 1, running with no interrupts.

Inside of it, a routine is called, basically as the example below:
After the loop, the count returned, divided by the timeout passed, gives me a performance of the loop of about ~1.35 counts per micro second.

Question: the ESP32 is running at 240 MHz, the sole uninterrupted task in core 1 should be running at 240 MHz; Why am I getting a loop performance near to 1 MHz ? does esp_timer_get_time() takes many tenths to hundredths of cycles to execute?
I was expecting the count variable to be incremented many many times faster than that.

Am I missing something here? I was hoping to have, say, 20 counts per microsecond. Or something far from "1.35"...

In time:
I tested a modification of the above loop, where I did: And it gives me ~1.267 counts per uS. So I think there is a HUGE overhead in the esp_timer_get_time() function.
Can this be improved? Is the esp_timer_get_time code being run from flash or something like it?

Thanks

Sorry, it's no simple return of a variable, as that would mean having an interrupt increasing that variable once per microsecond, which would impact performance lots more... what esp_timer_get_time does instead is read some hardware timer (it actually has multiple implementations, depending which hw you want to use) and then 1. do some deeper magic to read a 64-bit variable on a 32-bit processor without the timer incrementing between the two reads, and 2. doing some math to convert it to microseconds. I can imagine this takes a few cycles.

Hello.
I searched and found this function that returns the value of a clock counter register; it's just 32 bits so it overflows each ~17.9 seconds, however is fast to give a more precise delay.
Tested making a call and saving values before and after 100 asm(" nop"); statements. It returned a difference in count of 112 since before and after the nop's. So it can be usable for a finer grain count.
"xthal_get_ccount()";
- And also served to confirm that a 'nop' asm operation takes 1/240M seconds to execute - a 4.16667 ns delay

Do note that aside from only being 32-bit, the xthal_get_ccount function counts clock ticks and as such is dependent on the CPU clock frequency. If you enable dynamic clock scaling, the CPU frequency (and as such the speed of that counter) may change.