I do not refer to the event handlers (type esp_event_handler_t), but to the event handler instances (type esp_event_handler_instance_t). I do not see different behaviour for the above code and a code where I set the handler instances to NULL:


ESP_ERROR_CHECK(esp_event_handler_instance_register ...

In esp-idf/examples/wifi/getting_started/station/main/station_example_main.c there are 2 event handler instances defined and used.
Wouldn't it suffice to use only 1 or even none and setting the last argument in the register function to NULL?


esp_event_handler_instance_t instance_any_id;
esp ...

I compiled your code for my ESP32C3 and flashed it: it runs w/o any problems when the TX/RX GPIOs are connected to a CAN transceiver, e.g. SN65230.


I (257) main_task: Started on CPU0
I (257) main_task: Calling app_main()
===================TWAI Sender Example Starting...===================
W (267 ...

Hello forum,
I am using options that I set up in my project's Kconfig.projbuild. As all configuration of a project (ESP hardware, IDF, user) ends up in a flat file ("sdkconfig", all prefixed with CONFIG_), how can I avoid a name clash with existing system entries? Are there any naming rules ...

To answer myself: SPIFFS cannot do this. Should have looked up this before posting.

From the SPIFFS wiki:

Seeking in a file

As opposed to posix, spiffs cannot create gaps in files. Sorry. You can seek around, but seeking beyond file end will promptly put the offset at the file end.


Sorry for ...

I tried to enlarge an existing file by positioning the file pointer beyond the end of the file and writing a character there, expecting to have filled the characters in between w/ zeros. The code below works okay under Linux, but fseek fails with errno 5 (EIO) when tried on SPIFFS. Is this a known ...

Hi all,
somehow I cannot find this "announcement for ESP32 rev 2". As I noticed these days that I can communicate with 20kbaud CAN bus only from rev 2 upwards I am really interested to get my hands on rev 2.

BTW: I cannot find any trace of a CAN register description in the technical reference ...

To follow up myself: the mentioned change went in with the commit by "projectgus" on 16 Sep. See the diff for esp_image_format.c, lines 217-222 (OLD) / 227-231 (NEW) and 224-232 (OLD) / 233-244 (NEW): "if (data->image.hash_appended) {...}" has been moved into the else branch by this.

I compared the code of the current esp_image_format.c with an older version (pulled from git on October, 7th). And the older version has the copying of the hash to the image_digest (the block "if (data->image.hash_appended)" ) AFTER the "if (verify_sha) { ... } else { ...}" block, while the current ...

To continue my test: "Last thing I checked is an error-free return from a call to err = verify_simple_hash(sha_handle, data);" --> this function even debug-prints a non-null hash:
D (1794) boot: Calculated hash: 3954b6030aa3f19e7aeb7acbd93ed974e4ef5e8d5865f366e101047a079649fa
But it does not make ...