idf.py build esp32c3 “SHA-256 comparison failed” (IDFGH-7203) #8798
Labels
Comments
|
Hi @QGB, Which version of IDF are you using? Can you have a try flashing your board with |
|
As @o-marshmallow mentioned, using |
|
@o-marshmallow |
|
Have you tried |
I compile it in ubuntu virtual machine. no esp32c3 connected. esp32c3 board connect to Win10 laptop. I copy the builded binary file to Win10 and use |
|
I see. In that case you cannot connect the port to the docker image according to the note at the end of the https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-docker-image.html page. At the end of Please pay attention to the arguments after As others pointed out, the following doesn't look correct: You can find the correct arguments above. Usually there are 3 binaries to flash. It looks like you are flashing your application at the offset of the bootloader. I'd like to suggest to build and flash from Windows directly. It is a much easier way in comparison with the one you are following now. |
|
flash success |
|
|
不使用 idf build 出来的 或者 idf.py menuconfig 选择 2MB ，但是 esptool --flash_size 4MB 。 或者 --flash_freq 40m 【默认是 80m】 虽然可以成功运行，但在启动时会出现： |
|
加入 arduino 组件时，必须先 删除 老 build 文件夹。不然 idf.py menuconfig "Arduino Configuration" 找不到 |
espressif-bot
pushed a commit
to espressif/esptool
that referenced
this issue
May 11, 2022
jack0c
pushed a commit
that referenced
this issue
Jun 10, 2022
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Jul 8, 2022
Mark as not for python 2.7.
Summary of upstream release notes, less bugfixes:
* Version 4.1
ESP32-C2: Added flash encryption support
elf2image: Added argument to disable appending SHA256 digests
* Version 4.0
Starting from v4.0.0, esptool adopts the semantic versioning
specification, please read the related "Versions" esptool
documentation page when deciding which version to use.
** Breaking changes
Public API has been defined by limiting access to internals that
have been refactored into multiple source files. Changing or
refactoring these limited internals won't be considered a breaking
change in future releases. Migration is easy and self-explanatory
(you will get an import error if something has moved) and is
required only in projects that import esptool directly.
If active security features are detected, the default behavior
changes to prevent unintentional bricking (#699):
If flash encryption is enabled, erase_flash and erase_region
cannot be executed.
If secure boot is enabled, erase_flash, erase_region and
write_flash operations cannot be performed (write_flash is just
restricted to protect the bootloader region 0x0000->0x8000).
An override flag --force lets the users execute these operations
anyways.
Flash parameters in an image header can now be changed only when no
SHA256 digest is appended (espressif/esp-idf#8798).
Python versions 2.7, 3.4, 3.5, and 3.6 have been deprecated, the
code is now Python 3-only compatible. Releases v4 and later can't be
installed from PyPI on these deprecated Python versions.
The ESP8684 alias has been removed, ESP32-C2 has to be used.
Megabit flash sizes have been deprecated, use megabyte units from
now on.
** New Features
Added stub flasher support for ESP32-C2 ECO1, deprecated ECO0 stub (can still be used with ROM).
espefuse.py: Added a new package - ESP32-D0WDR2-V3
radimkarnis
pushed a commit
to radimkarnis/esptool
that referenced
this issue
Aug 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
serial port 16
The text was updated successfully, but these errors were encountered: