To get the maximum resolution out of an encoder the example counts all 4 edges that occur for each full step of the encoder. To do this, it sets up two channels. One channel counts the edges of signal A and uses the corresponding level of signal B at every edge of A to determine the direction. The o...

Yes, it is possible. But not via the public (GPIO) API.
You can configure the pin as GPIO, then 'manually' reconnect the peripheral signal to that pin. Like this.

On a 240MHz core, I would have expected that I could easily enter an ISR, toggle a Port Pin and return in 60 cycles, I know. But there's more going on in terms of setting up the context for running an ISR function written in C than one would expect: https://github.com/espressif/esp-idf/blob/46acfdc...

twompark wrote: ↑

Wed Oct 02, 2024 4:10 pm

It seems the KSZ8863 driver uses the older I2C routines that don't have the built-in locking.

The "legacy" I2C driver also handles mutual exclusion for each I2C port: https://github.com/espressif/esp-idf/bl ... 2c.c#L1551

greycon wrote: ↑

Thu Oct 03, 2024 1:20 pm

I would just use one of the ESP32 timers, set to contintually countdown, and reload.
... And calculate the values for 25 uS?

OP needs 4MHz, i.e. 0.25us intervals, not 25us.
0.25us corresponds to 60 CPU clock cycles @ 240 MHz; that's barely enough to even enter an ISR.

To efficiently count edges, you may want to look into the Pulse Counter peripheral.

You're not missing interrupts. Your handler code just doesn't toggle the output pin on one interrupt out of every three.

To capture both edges, use GPIO_INTR_ANYEDGE instead of GPIO_INTR_POSEDGE.

And instead of Try

espNewAddict wrote: ↑

Tue Oct 01, 2024 5:21 pm

Is this chip capable of handling all of this?

Yes, any ESP32 should easily handle this, even the single-cores. (Using PWM or PDM for the (2x3?) 'analog' signals for the LED strips.)

The key to avoiding timing 'disruptions' is to not do things in software which the hardware can do.

See e.g. the example at https://github.com/espressif/esp-idf/tree/v5.3.1/examples/system/esp_event/default_event_loop It uses the provided macros to declare and define event bases. Notice that an "event base" is not a string but actually only a pointer, i.e. a memory address. An event base is identi...