Hello, I am currently working on a project where an ESP32 based board is used in a legged robot as a bridge between a control computer using Ethernet or Wi-Fi and a set of sensors and actuators using SPI. The control loop is working at 1kHz. While working in Wi-Fi, we are sometimes witnessing some s...

Hello all !

Any insight on this ? Is there something I am missing about the ESP32 ethernet API ?

Hi, thank you for your reply. it's something related to the OS scheduler We are already investigating the guilt of the scheduler and RT capabilities of the OS in that matter, but the issues are still present (even though less frequent) with 2 ESP32s (one sending, one receiving) so Linux is not the o...

Hello, I am currently working on a project where an ESP32 based board is used in a legged robot as a bridge between a control computer using Ethernet and a set of sensors and actuators using SPI. The control loop is working at 1kHz. Sometimes, we are clearly seeing that some packets are lost or dela...

Thank you for your answer, that would be great !

ESP_morris wrote: ↑

Wed May 27, 2020 10:15 am

By now, you can hack esp-idf code a little to pin the task to the core you want: https://github.com/espressif/esp-idf/bl ... p32.c#L458

This litlle hack worked perfectly, thanks.

Maxime

Hi ! Thank you for your answer. The board I'm working on is used in a legged robot as a bridge between a control computer using Ethernet and a set of sensors and actuators using SPI. The control loop is working at 1kHz. Then, we need the Ethernet communication, and especially the receiving callback,...

The reaction to a incoming packet needs to be as fast as possible, that's why being able to pin that to one core would be very helpful.

Any insight on this ?

Hello, I am currently working on a project where an ESP32 based board needs to communicate with a computer via Ethernet. Is there any way to pin all Ethernet related tasks to core 1, as for the Wi-Fi task in menuconfig ? I should specify that I am using the driver in standalone mode (without TCP/IP ...