I have a hard time understanding ESPNOW. In principle it would be quite easy: select the same channel on *both* devices, transmit on one device on this channel, and receive on another device on this channel. ESPNOW (apparently) does 2 transmissions behind the scenes, one from the sender (data), one ...

Different platforms aside, the reason why mkspiffs has to be compiled separately for each SPIFFS configuration is that some parts of SPIFFS configuration happen at compile time. Hence, different configuration => different binaries. This is explained here: https://github.com/igrr/mkspiffs#spiffs-con...

Specifically look for mkspiffs-X.Y.Z-esp-idf-win32.zip download on the page linked by fly135. I'm not including an actual link here because newer release may come out, but the link here would point to outdated version. Thank you so much for pointing this out. I wasn't familiar with github having "r...

Here's an ESP32 die shot. https://s.zeptobars.com/esp32-HD.jpg . Just for fun, can anyone spot the two CPU's. Just took a look. Sprite was not joking, holly s! :shock: :o Maybe a higher density lithography process could be used instead of 40 nm (32, 28, 22 nm) to keep the same die size and have mor...

I edited my post to more clearly state I request the mkspiffs binary (for MSYS32 Windows). I ask this question because it is of little use to send someone to github, make them install a Windows (cross?) C-compiler, manage paths, deal with windows-linux/msys32/path/compiler issues, search google and ...

I am trying to create a precompiled spiffs partition. https://esp-idf.readthedocs.io/en/latest/api-reference/storage/spiffs.html says "Host-Side tools for creating SPIFS partition images exist and one such tool is mkspiffs". However the 'mkspiffs' doesn't work out of the box, mkspiffs isn't included...

This [-Werror=pointer-sign] => '-funsigned-char' issue causes an error, so I can no longer flash the project, so I'm stuck. Changing everything to 'char' is not an option (and the concept of possibly negative chars makes no sense to me). Anyone has an idea as to how to solve this (see top post)? ---...

I added the CFLAGS, I now have this component.mk file in the "main" folder: # # "main" pseudo-component makefile. # # (Uses default behaviour of compiling all source files in directory, adding 'include' to include path.) COMPONENT_ADD_INCLUDEDIRS += \ drivers COMPONENT_SRCDIRS += \ drivers CFLAGS +=...

Currently an ESP-IDF install is not portable. As usernames are inserted into the Home folder, every install is different because of this irrelevant detail. So I suggest that you mandate "db_home: /home/user" in "C:\msys32\etc\nsswitch.conf" before running mingw32.exe the first time, so paths no long...

If you use ESP-IDF then Eclipse is building via the ESP-IDF build system (with GNU Make). So you have to make any change like this in the ESP-IDF build system files. Yes I do use Eclipse. Thank you for your kind reply. I wil try this. Note that the installation tutorial is out of date with the new ...