It seems acceptable within reason: - even though the TCP connection is not TLS protected you still have encryption of the physical layer provided by WPA2 - enabling TLS will be confusing to most users because you can't provide valid server certificates to each ESP32 device. Arguably this detracts fr...

If you have 4MB partition maps and 8MB flash, you can manually manage the free flash space beyond the 4MB, i.e. create your own partition table for that space. It would be easier to flash two variants with native idf partition tables, though.

Because of: EXCVADDR: 0x00000000 it looks like you are referencing a NULL pointer. Maybe tell us what's at: line main.c:55 (from the stack trace) or possibly post the whole main function. It would be less unwieldy if you shorten the log to only contain a single reboot cycle. Also, it's hard for us t...

Two things: - there is no reason to checkout the vs code extension via git. Try installing via the extension manager in vs code - One of the errors is "Host key verification failed." Github had to change in SSH key recently. Perhaps this error is a result of that. If this is the problem you need to ...

In case you can't just trivially extract the firmware using the `esp_tools.py` command, it may be easier to just sniff the i2c traffic between the two devices? That should be a whole lot easier to understand than a machine language copy of the firmware...

If it is well architectured C code with a clearly demarcated bsp/hal layer, you just need to implement the necessary funtionaly in the hal layer. Otherwise you need to go through the existing code, identify PIC dependant bits and change those to their corresponding IDF functions. It will probably be...

There is currently an open issue around this. The workaround is to launch code from a directory that contains a file named `CMakeLists.txt` the issue is here : https://github.com/espressif/vscode-esp ... 8920587182 and seems to be resolved in 1.6.1

Have you had a look at the documentation? https://docs.espressif.com/projects/esp ... -v-program

Espressif chips are not "hardened" to the extent that you could use them, e.g. in a bank, medical or defense environment (to my knowledge anyway). As a consequence, a dedicated adversary would likely always be able to extract your firmware, possibly by means of an electron microscope, laser attacks ...

However, because I have no CS line, it seems that the : err = spi_slave_transmit(SPI2_HOST, &Transaction, portMAX_DELAY); never exits. That api seems to expect transactions delineated by C's changes. Two options that come to mind: - toggle the CS state on a fake pin by setting their pull-up and pul...