Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump esptool from 2.8 to 3.0 #4

Closed
wants to merge 1 commit into from
Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 14, 2021

Bumps esptool from 2.8 to 3.0.

Release notes

Sourced from esptool's releases.

Version 3.0

Breaking changes

  • The default esptool.py write_flash --flash_size argument has changed from detect to keep. This means that if no --flash_size argument is passed when flashing a bootloader, the value in the bootloader .bin file header is kept instead of detecting the actual flash size and updating the header. To keep the old behaviour, add the argument esptool.py [...] write_flash [...] -fs detect
  • espefuse.py command line arguments for ESP32 have changed:
    • BLK1, BLK2, BLK3 is now BLOCK1, BLOCK2, BLOCK3`
    • The key usage secure_boot has been replaced with secure_boot_v1, secure_boot_v2. Secure Boot V2 is the new RSA-based Secure Boot mechanism supported on ESP32 V3.

New Features

  • Support for ESP32-S2 SoC has been added
  • Support for detecting ESP32-PICO-V3-02 and ESP32-U4WDH have been added
  • New --connect-attempts argument (espressif/esptool#464)
  • Fixed scrolling problems when output is redirected (for example in Arduino IDE, see discussion at espressif/esptool#482)
  • Produce a meaningful error if the SoC we connect to doesn't match the --chip argument
  • Support different capitalization and spelling for --chip argument (ie -c ESP32, -c esp32-s2, etc.
  • Added dedicated program esp_rfc_2217_server.py for flashing via RFC2217 (i.e. flashing over the network, espressif/esptool#383)

espsecure.py

  • Added support for Secure Boot V2 (ESP32 V3, ESP32-S2)
  • Secure Boot V1: PKCS8 formatted ECDSA keys are now supported via ecdsa library (not including password protected keys)

espefuse.py

  • Added ESP32 ECO3 efuse UART_DOWNLOAD_DIS
  • Added new batch burn mode, support burning more than one eFuse on a single command line
  • espefuse.py internals have been refactored to support multiple chips, produce more information about which eFuses are being written to which values.
  • "Virtual" mode added for host-based testing, allows updating eFuse values on a "virtual" chip inside the host.

Internal features

These features are intended for use inside Espressif:

  • Support for ESP32-S3beta2 & ESP32-C3 have been added. These SoCs are not currently available outside Espressif, so these SoCs are unsupported in this release. Official support will be added in a later esptool release.
  • esptool.py --no-stub read_flash is now supported on ESP32 and later. This option is slower than using the default stub option to read flash, so it's generally not useful for production SoCs.

Bug Fixes

  • Added temporary workaround for a pyserial failure on macOS Big Sur Preview (espressif/esptool#540)
  • Fixed gcc9 warning in the stub (espressif/esptool#501)
  • Fixed some memory types printed in the memory map output
  • Fixed the check for zero bytes before applying an ELF SHA-256 with elf2image --elf-sha256-offset option (espressif/esptool#560)
  • Fixed displaying some single core ESP32 features incorrectly, i.e. ESP32-S0WD
  • Fixed exception on Python 3 if the same flash address was repeated twice (espressif/esptool#558)

Miscellanous Changes

... (truncated)

Commits
  • 4fa0bd7 v3.0 release version
  • 15f791b esptool: Change the default write_flash --flash-size to 'keep'
  • 7d3bd78 espsecure.py sign_data -v 1: Add test for PKCS8 key format
  • e3ab7c2 ecdsa: Replace vendored version with latest upstream via install_requires
  • 2db5fd9 esptool.py: Fix exception on Python 3 if same address is repeated
  • 365a0ba Check the right part of the segment where SHA-256 will be written
  • 456384c espefuse: Add support ESP32-S3BETA2
  • 4094d98 espefuse: Fix size of an efuse filed for esp32-s2
  • bb84464 espefuse: Add support ESP32-C3
  • 05a1ebe Fix Python 2/3 compatibility with xmlrunner from unittest_xml_reporting
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 14, 2021
Bumps [esptool](https://github.com/espressif/esptool) from 2.8 to 3.0.
- [Release notes](https://github.com/espressif/esptool/releases)
- [Commits](espressif/esptool@v2.8...v3.0)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/pip/esptool-3.0 branch from 5185ede to 7553a70 Compare May 9, 2021 11:22
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github May 28, 2021

Superseded by #17.

@dependabot dependabot bot closed this May 28, 2021
@dependabot dependabot bot deleted the dependabot/pip/esptool-3.0 branch May 28, 2021 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
0 participants