Closed chewhs00 closed 1 year ago
Do you have any particular reason to use --no-stub
? You are right that it is not working but I don't know what we could do about it. The ROM code is invoked and not everything is initialized/implemented there for OPI flash support.
If you don't use --no-stub
then the flasher stub of esptool is used where this is implemented and should work.
@dobairoland , I thought stub only works when accessing within 16MB. Is that no longer the case?
Support was added in v4.5.
Any release schedule this get included in idf 4.4 and idf 5.0?
It is already included with ESP-IDF v5.0+. There is no schedule now if or when will be included with v4.4.x.
Operating System
Ubuntu 20.04.5 LTS
Esptool Version
v4.5.1
Python Version
3.8.10
Chip Description
ESP32-S3 (revision v0.1), 32MB Octal Flash, 80MHz, opi_dtr
Device Description
Module on a custom board.
Hardware Configuration
No response
How is Esptool Run
Terminal, esptool repo
Full Esptool Command Line that Was Run
~/esp/esptool/esptool.py --chip esp32s3 --p /dev/ttyUSB0 --no-stub write_flash --flash_size 32MB -z 0x1C10000 dummy.bin
Esptool Output
More Information
My goal is to flash a 256kB binary image at a location above 16MB boundary, in this case at 0x1C10000. To check if it is successfully written to the proper location, I read it back with/without stub, at both locations 0xC10000 and 0x1C10000. With the above sequence of read/write, I still don't know if I wrote to 0x1C10000 correctly or I have accidentally corrupted 0xC10000. This --no-stub option sometimes fails for unknown reason!
Other Steps to Reproduce
See above Esptool Output
I Have Read the Troubleshooting Guide