I don't get spikes on the analog-pins, it is a simple voltage divider with 3.3V supply voltage. And the relais are driven with 5V. If the supply voltage would drop the chip would restart immediatly. I think the soldering maybe the problem, i put a DOWD-SoC on an adapter with a soldering Iron. Thank ...

Regarding "erased flash too often", are we talking >100,000 erase cycles here? Yes, i did save the temperature-curves every minute erasing flash-sectors. The chip did still work, only the curves were gone after about half a year, that means about 100.000 write-cycles like in the specs. This was my ...

No, the first chip doesn't work anymore. I reduced frequency on the second chip. Your chip was designed to work many years, but is anyone out there who has chips working that long?

How exactly does it fail when it fails? Do you have a schematic? Especially with a relais or external analog inputs, high-voltage spikes could play a role here. The first chip hung up and restarted after few seconds, so i reduced the frequency. The second chip was my fault, i erased flash too often...

I'm using a voltage divider with the 3.3V supply-voltage, the relais are driven with 5V by an ULN2003. I just wanted to know if this a known problem of the ESP32. I'm going to try the DevkitC, maybe the chip got too hot when i was soldering it on the adapter.

What am i doing wrong? I have 5 analog Inputs and a driver for the relais, some RGB-Leds and a display. The voltage is regulated by an LD33V. The controller is inside of the house, there are always about 20°C. Everything works fine for months.

My ESP32-chips only last half a year. I did reduce frequency form 240 MHz to 160 MHz already. I'm using it for a thermal solar control and this is my fourth chip already.

Hello Mr. and Mrs., i have written a new heap component based on my sorting algorithm http://www.github.com/svenbieg/clusters . Free space is mapped by size and by offset, so the smallest block top most of the heap is returned. Allocating and freeing 30.000 times takes about 496ms, compared to 746ms...

I'd like to see a new memory manager based on my Clusters-algorithm.

http://www.github.com/svenbieg/Clusters

Best regards,

Sven Bieg

The sample does work on pin 4 but not my application, maybe because i have WiFi enabled.
Following pins do work: 5, 17, 18, 19, 21, 22, 25, 26.