Is it possible something might have been shorting one of the SPI pins on the ESP32 at the time it was not responding to commands (ie flash model 0xffff, etc)? This is the most common cause of this problem that I see (the chip appears to disappear entirely if it isn't getting a complete set of SPI s...

And no, I have no memory allocations, but I'll disable wifi just to see if that makes a difference. I tried, no difference. Bad idea I guess. To make a real difference I would have to purge the project of anything Wifi. That would mean reducing the project, which also implies getting to a state tha...

What is happening?? I don't know, but my guess would be silent memory corruption somewhere else which is sometimes breaking everything when you call settimeofday(). You probably implied this, but I have no evidence of settimeofday() actually being called, it is only linked in. And no, I have no mem...

Thanks for the reply. As a reminder, the first thing user code does is print something. > Are you able to post a full project that (at least sometimes) exhibits this problem, somewhere? Hopefully that won't be needed. Below all output on verbose (should have remembered that): Wrote 3072 bytes (160 c...

I think a better ESP32 would be just that, a better, leaner device with perfected ADC and RTC, as price is still a major consideration. Two radios would also interest us (for ESPNOW). But most of all, instead of cramming everything in a single device, why not have cheap I/O extenders which implement...

I haven't played audio yet, but it is certainly possible to output the audio via I2S. You might get started with the I2S example under Peripherals (https://github.com/espressif/esp-idf/tree/master/examples/peripherals/i2s). I looked at the quality of the sound generated, http://webbot.org.uk/iPoint/...

The situation is different now, as the code links. But the weird behaviour again involves settimeofday(). The program, including the code below, links: void esp32_rtc_init(struct tm *rtc_time) { struct timeval t; t.tv_sec = mktime(rtc_time); t.tv_usec = 0; printf("SETTIMEOFDAY"); settimeofday(&t, 0)...

I think auto-detect implies accessing the flash memory to see where it ends. As WiFive mentioned, esptool.py detects flash size by reading flash chip ID, which itself is not stored in flash. If it reads 0xffffff from that register, it means that SPI communication between ESP32 and the flash chip is...

"Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB" Isn't the size obtained by reading nonvolatile chip registers? Did you do a test of your other parts to see how many bytes/sectors were failing? Hello WiFive, thanks for responding. I think auto-detect im...

That's a bit odd! There are some situations where changing the source code input to the compiler can move things around in the linker output, and trigger bugs like memory corruption which were harmless before. Can you please post some more info: - What IDF version? - If you turn up the default log ...