The problem with "leaving it so as it is" is, that the struct's default vals are already not the defaults the ESP32 starts with. As you can see from quoted headers, `force` and `enable` are set to `1` which is clearly not how the ESP32 behaves (as it reads MTDO by default). Hence, I'm concerned abou...

Thank you! I'm still unsure about the meanings and values for `drefh`, `drefm` and `drefl`, though.

I'm using a Wrover-module on a custom PCB and made a mistake by not being able to guarantee that the strapping pin MTDI is alwa ys pulled low during power-up in order to operate the (wrover-)internal flash with 3.3V instead of 1.8V, as the latter results in failing write ops (reads are fine, at leas...

Thank you! Could you shed some light on why IO12 is actually used as a strapping pin on the wrover module? Why isn't the eFuse burned by default, as one of the main purposes of the wrover-module is to have additional *internal* flash? (internal as in: part of the module; I know from the bare-metal S...

I'm using the ESP32 Wrover-E with additional flash (16MiB) and overlooked GPIO12 being a strapping pin configuring whether the internally SPI connected flash is powered by 1.8V or 3.3V. GPIO12 is used as MISO on our board, whereas the ESP32 is the master and the partner is slave. Hence, the slave is...