The issue with interrupts in Xtensa CPUs at least is that you don't have a list of vectors, one per interrupt; instead you have a vector per interrupt *level* and there are only a fairly limited amount of them (5 or so iirc). For the C interrupts, we have a bit of code that multiplexes them but for ...

Not sure what you're talking about, as the peripherals themselves don't have sleep options; that stuff is controlled centrally. For instance, the ESP32-C3 has a 'Low power management' chapter that discusses most if not all of them. I agree that there's no 'howto' in the TRM for this, but if needed y...

If there is a "wifi driver program" for the C2 to act like a P4 Wifi-card, and the only worry is programming the P4, it takes many worries away. The plan is to have esp-hosted to make the C2/C3/C6 act as a 'standard WiFi chip'. We should also be able to program that chip via the P4; the C-series ch...

99% sure a measurement error. Make sure you have a good ground connection, and make your measurement loop as small as possible (=no long wire between ground and the probe, or the signal and the probe)

If anything, you shouldn't call any potentially 'long' / blocking things during the ESPNow callback. Normally, you'd quickly filter the package (as in discard it if it's uninteresting) and dump its relevant info in a freertos queue or something if you want to keep it, for another thread to process.

You can. I attached an example on how to do that here. Note that this code is ancient, it e.g. still uses the old make build system, so you may need to tweak it a bit, but the details should be there. In general, this is not implemented in esp-idf because 1. that clock stops in any sleep mode (and m...

0xcf is the first byte of the *encrypted* image format, but it looks like it's written via function calls that expect the *decrypted* image.

I think that code would crash: you're calling a blocking function in a critical section. In general: That sleep mode is not intended to manually call, to be honest; it's ideal for a RTOS idle scenario as the way it sleeps makes it trivial to implement, with the downside being that the savings are no...

If the JSON is a single key/value store, you'd probably best off using the NVS (or specifically for Arduino, the 'preferences' library) rather than a spiffs. Just take the keys that you would put into the JSON file and feed them into the Preferences lib instead.

Glad to hear it works. No need to mark the answer as accepted, the forum doesn't have functionality for that.