You can write to encrypted FATFS, but for read/write scenario it is recommended to use FATFS on top of wear_levelling library. I'm still confused. Are you saying that wear leveling and encryption are mutually exclusive? I'm thinking that wear leveling won't be important for sensitive data that is o...

2) For read-only data, you can create a FATFS image, write it encrypted to a partition, and mount it as raw data in read-only mode . So we cannot write data to an encyrpted file system during runtime? I need to provision the ESP32 during runtime and store sensitive in encrypted storage. Is NVS the ...

ECONNABORTED = 113. No really time to start worrying about the cert yet. You don't seem to be finding the server or the server isn't listening on the port.

John A

Pretty sure that GPIO 0 is available after boot. If you are going work on stuff like this it's worth getting a cheap scope to analyze these kinds of problems.

John A

I measuring NTC resistance. But I can measure everything: NTC, carbon resistor, PT100... The problem is that if with ESP32 No.1 I read, for example, 2570, with ESP32 No.2 I read 2640 and with ESP32 No.3 I read 2465..... I read that ESP32 needs calibration, one by one, but for me is impossible to th...

snahmad75 wrote: ↑

Mon Apr 08, 2019 9:37 pm

Thanks for reply. I will investigate who allocated at 0x3ffcfe24 address

The allocated address where the problem is from is probably the one before 0x3ffcfe24. That's the block that's writing past the end and overwriting the next allocation information.

Super simple fix. The PHY was address zero and I was using address 31.

John A

Not sure why I'm having a problem with this board a friend made. I'm running the ethernet_example in the IDF. I've checked and double checked that MDIO and MDC are the correct assigned pins. Not control over PHY power. I've included a scope capture that seems to indicate properly data coming from th...

"Bad head at 0x3ffcfe24" If you search the IDF for "head != NULL" and look at the ones that are an assert in the heap section, you will see the function "verify_allocated_region" is finding the header to the allocated region has been overwritten and the sanity check "(head->head_canary != HEAD_CANAR...

I learned something today. I didn't realize that FreeRTOS ran in the Aurduino environment.

John A