Yuvaraj1867 wrote: ↑Mon Oct 26, 2020 4:09 pm
1). If i run this command I'm getting the following data. - C:\Python27>python.exe C:\esp32-cmake\esp-idf\components\esptool_py\esptool\espefuse.py --baud 115200 --port COM93 summary
Log:
C:\Python27>python.exe C:\esp32-cmake\esp-idf\components\esptool_py\esptool\espefuse.py --baud 115200 --port COM93 summary
espefuse.py v2.7-dev
Connecting.....
....WARNING: Coding scheme has encoding bit error warnings (0xbad)
Hi -
can you please use the actually version of esptools.
i think you use v2.7-dev version
perhabs you can check by using this command:
C:\Python27\python.exe C:\esp32-cmake\esp-idf\components\esptool_py\esptool\esptool.py version
you can download the actually version
from github, example from here
it should give you then the info likewise
esptool.py v3.0-dev
3.0-dev
Yuvaraj1867 wrote: ↑Mon Oct 26, 2020 4:09 pm
2). For the second command I'm the following attached(Pic no:2) data. - C:\Python27>python.exe C:\esp32-cmake\esp-idf\components\esptool_py\esptool\esptool.py --port COM93 erase_flash
now try the same with the actually espool version,
before you can perhabs check fuses with the actually espefuse.py ( is also in this repo and path ) like you did before.
you will get more infos.
you can use the same python path and app and change the argument to your actually downloaded esptool path example.
Yuvaraj1867 wrote: ↑Mon Oct 26, 2020 4:09 pm
May i know the next step...
- check esptool version you use
- update
esp-idf or download actually
esptool
- check the new downloaded esptool by version check ( actually should be V3.0.. )
- use the actually esptool ( with esp32-s2 support ) for espefuse.py and esptool.py
- try to erase_flash with the actually version
FYI:
you can make a
Backup of your Saola with esptool
there are many command args possible, also check the help arg by run esptool with -h
c:\............ .....esptool.py -h
L:\tools\esptool-master>python esptool.py -h
usage: esptool [-h] [--chip {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32c3}]
[--port PORT] [--baud BAUD]
[--before {default_reset,no_reset,no_reset_no_sync}]
[--after {hard_reset,soft_reset,no_reset}] [--no-stub]
[--trace] [--override-vddsdio [{1.8V,1.9V,OFF}]]
[--connect-attempts CONNECT_ATTEMPTS]
{load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,version,get_security_info}
...
esptool.py v3.0-dev - ESP8266 ROM Bootloader Utility
positional arguments:
{load_ram,dump_mem,read_mem,write_mem,write_flash,run,image_info,make_image,elf2image,read_mac,chip_id,flash_id,
read_flash_status,write_flash_status,read_flash,verify_flash,erase_flash,erase_region,version,get_security_info}
Run esptool {command} -h for additional help
load_ram Download an image to RAM and execute
dump_mem Dump arbitrary memory to disk
read_mem Read arbitrary memory location
write_mem Read-modify-write to arbitrary memory location
write_flash Write a binary blob to flash
run Run application code in flash
image_info Dump headers from an application image
make_image Create an application image from binary files
elf2image Create an application image from ELF file
read_mac Read MAC address from OTP ROM
chip_id Read Chip ID from OTP ROM
flash_id Read SPI flash manufacturer and device ID
read_flash_status Read SPI flash status register
write_flash_status Write SPI flash status register
read_flash Read SPI flash content
verify_flash Verify a binary blob against flash
erase_flash Perform Chip Erase on SPI flash
erase_region Erase a region of the flash
version Print esptool version
get_security_info Get some security-related data
optional arguments:
-h, --help show this help message and exit
--chip {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32c3}, -c {auto,esp8266,esp32,esp32s2,esp32s3beta2,esp32c3}
Target chip type
--port PORT, -p PORT Serial port device
--baud BAUD, -b BAUD Serial port baud rate used when flashing/reading
--before {default_reset,no_reset,no_reset_no_sync}
What to do before connecting to the chip
--after {hard_reset,soft_reset,no_reset}, -a {hard_reset,soft_reset,no_reset}
What to do after esptool.py is finished
--no-stub Disable launching the flasher stub, only talk to ROM
bootloader. Some features will not be available.
--trace, -t Enable trace-level output of esptool.py interactions.
--override-vddsdio [{1.8V,1.9V,OFF}]
Override ESP32 VDDSDIO internal voltage regulator (use
with care)
--connect-attempts CONNECT_ATTEMPTS
Number of attempts to connect, negative or 0 for
infinite. Default: 7.
L:\tools\esptool-master>
hope this helps.
best wishes
rudi
