cspwcspw wrote:No underlying silicon, or what gives?

2) What is the correct way to disconnect / undo my GPIOs 14 and 22, if I want to return them to "normal use".

Probably

Just select a different signal or different mux function

Adf uses a lot of binary codecs and libs that someone not using audio features has no interest in and are also compiled to a specific commit of idf. There are already too many components in idf that may not be used at all in a project.

If it is a variable it will be placed in dram but if it is a constant:

https://dl.espressif.com/doc/esp-idf/la ... m-data-ram

IRAM_ATTR places the code into internal (nonpaged physical) IRAM as opposed to where code is placed by default which is into flash and then executed "in place" from the (paged virtual) cache which is controlled by the MMU.

Either the interrupt is iram/dram safe meaning it can run when flash/spiram caches are disabled or it isn't. If it isn't then it can use cache memory but will be disabled when cache is unavailable. When you register the interrupt you tell the system what kind it is by specifying flags.

Station, softap, espnow, espmesh?

"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?

I'm talking about esp-idf. Version is misleading, I consider 3.1 more like 0.3.1. 3.2 final may be stable enough to be considered more like a 1.0.

Distributors also have these modules now you don't have to buy direct.