Likely the module was subjected to something not good (overvoltage, power spike, static electricity, ...) that fried the flash chip inside the package. The ESP32 is trying to boot from that but fails. Normally the ESP32 itself doesn't get hot in that state; it's more likely that the flash broke in s...

Sorry, you're right, it's been a while since I dived into RSA/ASN.1 etc. Seems the issue you have is described here . Note that this is about SSH keys but SSL keys have the same format (you can check that with `openssl rsa -in prvtkey.pem -text` if you want.) Could be that the AWS key leaves off the...

Since IDF is in control of the stack it should not happen. No, it is not. ESP-IDF will create the main task with the amount of stack you configure, and it's your job to reconfigure it if it's too small. Enter menuconfig and then Component config → ESP System Settings → Main task stack size to chang...

You don't need to reference the component files in your main CMakeLists.txt, the component itself needs a CMakeLists.txt that makes esp-idf compile them. Also, your 'component' directory should be in the root of your project, not in the 'main' folder.

Proper syntax would be 'idf.py -p /dev/ttyACM0 flash', can you try that?

I don't see the debug log, it would be helpful to see where the stack overflow happens and to have a backtrace of that. Also: what stack did you increase? In your sdkconfig, the main stack (which calls into the bootloader stuff) only is allocated 3584 bytes. I'd suggest using menuconfig to increase ...

Think it's just an unused subdomain.

I seem to remember some RISC-V (C series) does support SPI-RAM or am I mistaken? Both the ESP32P4 and the ESP32C61 can, but these chips aren't (widely) available yet. If so, I guess I will choose the S series for the foreseeable future and I hope Espressif will keep making/supporting them for some ...

...Okay, thanks for sharing, but did you have a question? In general, yes, if you declare variables inside your functions, it'll use up stack space, and if you didn't allocate enough of that to your task, it'll overflow your stack. Making variables global is one way around that, although normally pe...

That's kinda to be expected. A PEM file is a base64 encoding, in this case likely encoding PKCS information. This encodes way more than simply the private key; there's also identifying information like the serial, common name, maybe name and address of issuer etc. Those things are not necessary for ...