Cannot read flash partition #697

DaneSlattery · 2024-10-25T10:20:00Z

I cannot read flash partitions with espflash on an esp32-s3 devkit over UART.

[2024-10-25T10:47:14Z INFO ] 🚀 A new version of espflash is available: v3.2.0
[2024-10-25T10:47:14Z INFO ] Serial port: '/dev/ttyUSB0'
[2024-10-25T10:47:14Z INFO ] Connecting...
[2024-10-25T10:47:14Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       30:30:f9:55:19:54
Error: espflash::read_flash::corrupt_data

  × Corrupt data, expected 1000 bytes but receved fd1 bytes

I am able to do the same with esptool.py:

esptool.py read_flash 0x9000 0x6000 ./nvs_dump.bin
esptool.py v4.8.1
Found 33 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_3v3)
Crystal is 40MHz
MAC: 30:30:f9:55:19:54
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
24576 (100 %)
24576 (100 %)
Read 24576 bytes at 0x00009000 in 2.2 seconds (90.0 kbit/s)...
Hard resetting via RTS pin...

I don't know what is missing?

The text was updated successfully, but these errors were encountered:

MabezDev · 2024-10-25T10:41:09Z

Can you try again with --no-stub?

DaneSlattery · 2024-10-25T10:46:43Z

Here's the result:

espflash read-flash --no-stub 0x9000 0x6000 ./nvs_dump_devkit   
[2024-10-25T10:45:55Z INFO ] 🚀 A new version of espflash is available: v3.2.0
Error: espflash::stub_required

  × This command requires using the RAM stub
  help: Don't use the `--no-stub` option with the command

zakimoo · 2024-11-21T14:58:48Z

same hier

espflash read-flash 0x0 0x0400000 test_3.bin

[2024-11-21T14:48:38Z INFO ] Serial port: '/dev/ttyUSB0'
[2024-11-21T14:48:38Z INFO ] Connecting...
[2024-11-21T14:48:38Z INFO ] Using flash stub
Chip type:         esp32c3 (revision v0.3)
Crystal frequency: 40 MHz
Flash size:        4MB
Features:          WiFi, BLE
MAC address:       a0:76:4e:5a:41:70
Error: espflash::read_flash::corrupt_data

  × Corrupt data, expected 1000 bytes but receved fcf bytes

but with esptool.py it works

esptool.py -b 460800 read_flash 0 0x0400000 flash_contents.bin
esptool.py v4.8.1
Found 1 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-C3
Chip is ESP32-C3 (QFN32) (revision v0.3)
Features: WiFi, BLE, Embedded Flash 4MB (XMC)
Crystal is 40MHz
MAC: a0:76:4e:5a:41:70
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
4194304 (100 %)
4194304 (100 %)
Read 4194304 bytes at 0x00000000 in 106.9 seconds (314.0 kbit/s)...
Hard resetting via RTS pin...

liclac · 2025-02-02T17:34:37Z

Same here, also trying to dump the default NVS partition of my ESP32-S3 devboard (a Heltec LoRa 32 V3).

$ espflash read-flash 0x9000 24576 config2.img
[2025-02-02T17:15:59Z INFO ] Serial port: '/dev/ttyUSB0'
[2025-02-02T17:15:59Z INFO ] Connecting...
[2025-02-02T17:15:59Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       34:cd:b0:3d:40:24
Error: espflash::read_flash::corrupt_data

  × Corrupt data, expected 1000 bytes but receved ffe bytes

Here's the full log, when running with RUST_LOG=trace: https://gist.github.com/liclac/01ee6b5f5bea1095cf37c86c43fb9f60

Doing the same operation with esptool.py works:

$ esptool.py read_flash 0x9000 24576 config.img
esptool.py v4.8.1
Found 3 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded Flash 8MB (GD)
Crystal is 40MHz
MAC: 34:cd:b0:3d:40:24
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
24576 (100 %)
24576 (100 %)
Read 24576 bytes at 0x00009000 in 2.2 seconds (90.3 kbit/s)...
Hard resetting via RTS pin...

I am able to use espflash write-bin to write this dumped image back to it:

$ espflash write-bin 0x9000 config.img
[2025-02-02T17:24:06Z INFO ] Serial port: '/dev/ttyUSB0'
[2025-02-02T17:24:06Z INFO ] Connecting...
[2025-02-02T17:24:07Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       34:cd:b0:3d:40:24
[00:00:00] [========================================]       1/1       0x9000
[2025-02-02T17:24:09Z INFO ] Binary successfully written to flash!

I'm also able to change the data, write it, and read it back just fine:

$ tr \xFF \xAA < config.img > config2.img

$ espflash write-bin 0x9000 config2.img
[2025-02-02T17:26:27Z INFO ] Serial port: '/dev/ttyUSB0'
[2025-02-02T17:26:27Z INFO ] Connecting...
[2025-02-02T17:26:27Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       34:cd:b0:3d:40:24
[00:00:00] [========================================]       1/1       0x9000
[2025-02-02T17:26:29Z INFO ] Binary successfully written to flash!

$ esptool.py read_flash 0x9000 24576 config2_.img
esptool.py v4.8.1
Found 3 serial ports
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded Flash 8MB (GD)
Crystal is 40MHz
MAC: 34:cd:b0:3d:40:24
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
24576 (100 %)
24576 (100 %)
Read 24576 bytes at 0x00009000 in 2.2 seconds (90.3 kbit/s)...
Hard resetting via RTS pin...

$ diff <(xxd config2.img) <(xxd config2_.img)

$ $ espflash read-flash 0x9000 24576 config.img
[2025-02-02T17:31:33Z INFO ] Serial port: '/dev/ttyUSB0'
[2025-02-02T17:31:33Z INFO ] Connecting...
[2025-02-02T17:31:33Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        8MB
Features:          WiFi, BLE
MAC address:       34:cd:b0:3d:40:24
Error: espflash::read_flash::corrupt_data

  × Corrupt data, expected 1000 bytes but receved ffd bytes

A minor observation is that for some reason, every time I re-write the partition and try reading it again, it changes how many bytes the error message says it received, just by a few bytes back or forth seemingly at random (I've seen ffc, ffd and ffe, in no particular order).

Happy to provide any additional information, help debug things, etc., but I'm a bit lost as to where to even start with this.

liclac · 2025-02-03T17:41:53Z

I discovered something very interesting: it seems to work fine as long as I ask for 0x1000 bytes or less. The moment I go above that, things start failing - 0x1001 through 0x1009 gets a timeout, 0x1010 and I'm back to the corruption error.

SergioGasquez · 2025-02-06T14:18:05Z

but I'm a bit lost as to where to even start with this.

I guess we should compare both implementations:

SergioGasquez · 2025-02-10T15:03:15Z

I think we encountered this issue on our HIL setup:

When using espflash read-flash 0x1000 0x200 flash_content.bin, the CI passes: https://github.com/esp-rs/espflash/actions/runs/13242998308
When using espflash read-flash 0 0x2000 flash_content.bin, the CI fails: https://github.com/esp-rs/espflash/actions/runs/13243719658/job/36965109560

Error: espflash::read_flash::corrupt_data

  × Corrupt data, expected 1000 bytes but receved fc3 bytes

Locally, I can reproduce the issue on some devkits, but in other devkits it works fine:

ESP8684-DevKitC-02 26MHz (clock): works fine
ESP32-C6-DevKitC-1: Fails
ESP32-S3-DevKitC-1: Fails

* ci: Use job.env to avoid duplications * ci: Add erase-region, hold-in-reset, reset and checksum-md5 tests * ci: Use bash scripts * cI: Update workflow * feat: Udpate testing elfs * test: Read 0x2000 bytes of flash * docs: Add TODOs for issue #697 * fix: Typo Co-authored-by: Jesse Braham <[email protected]> * docs: Improve the todo comment --------- Co-authored-by: Jesse Braham <[email protected]>

jessebraham · 2025-02-11T12:53:01Z

Small update, after some investigation this appears to be an issue with the flasher stub. I was able to successfully read sizes larger than 0x1000 by using the old C stub. Will try to hunt down what's going wrong there.

SergioGasquez · 2025-02-12T09:18:24Z

This is a stub issue, we have esp-rs/esp-flasher-stub#75 to track it, and we may go back to using the C stubs (at least for the moment) in espflash. Ill close the issue

jessebraham added this to esp-rs Oct 25, 2024

github-project-automation bot moved this to Todo in esp-rs Oct 25, 2024

jessebraham added the bug Something isn't working label Jan 9, 2025

jessebraham added the status:needs-investigation Issue requires further investigation label Jan 20, 2025

jessebraham self-assigned this Feb 10, 2025

jessebraham added this to the v4 milestone Feb 10, 2025

SergioGasquez added a commit to SergioGasquez/espflash that referenced this issue Feb 10, 2025

docs: Add TODOs for issue esp-rs#697

b822f81

SergioGasquez added a commit to SergioGasquez/espflash that referenced this issue Feb 10, 2025

docs: Add TODOs for issue esp-rs#697

08993c0

SergioGasquez added a commit to SergioGasquez/espflash that referenced this issue Feb 10, 2025

docs: Add TODOs for issue esp-rs#697

6a40571

SergioGasquez mentioned this issue Feb 10, 2025

espflash read-flash should also work with --no-stub #757

Closed

SergioGasquez mentioned this issue Feb 12, 2025

READ_FLASH command is not properly processed esp-rs/esp-flasher-stub#75

Open

SergioGasquez closed this as completed Feb 12, 2025

github-project-automation bot moved this from Todo to Done in esp-rs Feb 12, 2025

SergioGasquez mentioned this issue Feb 17, 2025

Improve HIL tests #773

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot read flash partition #697

Cannot read flash partition #697

DaneSlattery commented Oct 25, 2024 •

edited

Loading

MabezDev commented Oct 25, 2024

DaneSlattery commented Oct 25, 2024

zakimoo commented Nov 21, 2024

liclac commented Feb 2, 2025

liclac commented Feb 3, 2025

SergioGasquez commented Feb 6, 2025

SergioGasquez commented Feb 10, 2025

jessebraham commented Feb 11, 2025

SergioGasquez commented Feb 12, 2025

Cannot read flash partition #697

Cannot read flash partition #697

Comments

DaneSlattery commented Oct 25, 2024 • edited Loading

MabezDev commented Oct 25, 2024

DaneSlattery commented Oct 25, 2024

zakimoo commented Nov 21, 2024

liclac commented Feb 2, 2025

liclac commented Feb 3, 2025

SergioGasquez commented Feb 6, 2025

SergioGasquez commented Feb 10, 2025

jessebraham commented Feb 11, 2025

SergioGasquez commented Feb 12, 2025

DaneSlattery commented Oct 25, 2024 •

edited

Loading