Answer: turns out that the event queue full situation has always been there, it is just that when debugging the PPP stuff we switched on CONFIG_LOG_DEFAULT_LEVEL_VERBOSE and it became visible: seems to be TX DONE or some such pouring out when we send stuff over the UART, which we don't care about an...

We've been using ESP-IDF of various versions (currently 5.0.3) with cellular and other modules via UART, using the built-in ESP-IDF uart driver (i.e. with uart_driver_install() , and an event queue size of 20) for years now, never had a problem with it ever, rock solid. However, we've just started u...

We have some library code of our own which attaches a PPP interface at the esp-netif level in ESP-IDF at run-time. The code #includes "sdkconfig.h" and switches on CONFIG_LWIP_PPP_SUPPORT so that it doesn't try to do anything unless the user has built with it. However, this code will go "bang" somew...

I would like to have an ESP-IDF component set a compilation flag that is effective on EVERYTHING in any build that component is included in: the main application, any other components, including components in the test subdirectory, absolutely everything, like appending a value to C_FLAGS might have ...

Hi, and thanks for that. Checking, in that case it was something to do with "how many HID devices should show up", a setting in menuconfig, which unfortunately doesn't apply in my case; my code is pure C/C++, no HW involved.

I have a native [ .cpp ] CMake library, which is already successfully built and used under native CMake for Linux and Windows in the usual way (i.e. add_library() , target_include_directories() and then a call to target_link_libraries() following add_executable() ) which I would like to use within t...

For me the issue was just that the value one passes to the i2c_set_timeout() function needs to be calculated differently for the ESP32x3 chips: it is no longer a simple millisecond value, it is 2^SCLK_period. For example, if the 40 MHz crystal is chosen as SCLK then you have 2^(x * 25) ns, where x c...

@andreko worth you checking if this is an issue for you as the C3 is the same.

For the benefit of anyone who gets here, after a few days of conversation with an _extremely_ helpful and knowledgeable Espressif engineer, we figured out my misunderstanding, details here: https://github.com/espressif/esp-idf/issues/11397 but in summary the timeout value value passed ESP32 is a mul...

For the benefit of anyone who gets here, after a few days of conversation with an _extremely_ helpful and knowledgeable Espressif engineer, we figured out what was going on, details here: https://github.com/espressif/esp-idf/issues/11397 but in summary the value passed to `i2c_set_timeout()` in ESP3...