lbernstone

Please provide minimal code to reproduce. This looks like you are trying to access the flash in a routine that does not have access (eg, an ISR)

Perhaps you could put a mutex on the disk access if they are blocking each other.

I think you want flash_mode to be dio even when memory_type is qio_opi. This behavior of the flash is a symptom of memory misconfiguration.

> Hi, guys. Although I haven't figured out this problem yet, I fixed my problem by moving all the `preferences` objects out of the class and using them directly in...

If you hold down the gpio0 (boot) button and then press the reset button, do you see the Espressif USB JTAG device in lsusb? You must manually put the device...

Code doesn't run in a void. If there is something else actively using the flash, Preferences must wait to access the device. Provide code that can be compiled that demonstrates...

It certainly looks like it is not able to identify the chip after the bootloader hands off control to the main app. Does this work with a [basic esp-idf app](https://github.com/espressif/esp-idf/tree/release/v5.1/examples/storage/nvs_rw_value)...

What do you get if you run [`esptool chip_id`](https://github.com/espressif/esptool)?

Sure does sound like unsupported hardware. 4MBit is not enough to boot arduino-esp32. As suggested, compile a firmware in [esp-idf](https://docs.espressif.com/projects/esp-idf/en/v5.1.4/esp32s3/get-started/windows-setup.html), and then submit the [issue upstream](https://github.com/espressif/esp-idf/issues).

W25Q80RVS will likely be recognized, but 2MB (16Mbit) is the smallest supported by the framework.