esp-storage

esp-storage copied to clipboard

Hang on write when using esp-wifi in the same crate

8

I attempted to make an OTA flasher for esp32 using esp-wifi and esp-storage. Using only esp-storage, I'm able to read the partition table and I'm able to write the "otadata"...

karlri

Maybe there should be an option in `espflash flash` that disables erasing of the NVS?

ProfFan

Fixes #26 @dimpolo this should fix your issue with code running on the other core

bjoernQ

Does one have to disable interrupts before using `FlashStorage::write`?

10

I'm seeing this backtrace on a ESP32S3 when ISRs are being ran on the same core: Backtrace ``` Exception occured 'IllegalInstruction' Context PC=0x4201219e PS=0x00060030 0x4201219e - core::sync::atomic::atomic_load at C:\Users\d.polonski\.rustup\toolchains\esp\lib\rustlib\src\rust\library\core\src\sync\atomic.rs:3153 0x00060030...

dimpolo

We should have example crates per chip like we do in `esp-wifi`, `esp-medtls` etc. to eliminate the need to edit `Cargo.toml` for some chips

bjoernQ

flash address

2

The demo hard codes `let flash_addr = 0x9000;`. I'm wondering if this address always works or how I can find a valid address. While writing this issue I found https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/partition-tables.html...

oleid

It should be possible to omit a page erase if the bytes to write are all 0xff - we can check that before erasing the page Additionally, we might consider...

bjoernQ