Skip to content

v0.12.0-esp32-20230921
Compare
Choose a tag to compare
@gerekon gerekon released this 22 Sep 08:10
· 333 commits to master since this release
v0.12.0-esp32-20230921
a23a2d4

Features:

  • target/esp32p4: Added ESP32-P4 target support. Basic debugging functionality without flash support is now available.
  • target/esp32{c2,c3,h2,c6}: Exposed custom CSRs for RISC-V targets.
  • target/esp32{h2,c6}: Added memory protection support.
  • target/espressif: Added support to print details for abort(), assert() and pseudo exception reasons.
  • target/espressif: Added GDB File I/O support (https://sourceware.org/gdb/onlinedocs/gdb/File_002dI_002fO-Overview.html).
  • target/espressif: Added support for stack hardware protection in RISC-V chips.
  • helper/log: Added log_non_error_levels_to_stdout command to send non-error logs to stdout. This can be useful for IDEs to detect errors messages.
  • jtag/drivers: Added SWD bitbang support for esp_gpio driver.
  • loaders/esp32{c2,h2,c6}: Added cpu_clock_configure functionality. This allows to improve flash access speed by temporary boosting CPU clock by flasher stub.
  • loaders/esp32{h2,c6}: Added flash encryption support.

Bug fixes:

  • target/xtensa: Fixed GDB watchpoint hit location handling to show previous and new value. Previously watchpoint hit just before memory access and no stepping over store/load instruction was performed, so GDB did not showed old and new variable value.
  • target/esp32s3: Keep APP_CPU clock gating enabled after SW reset. It avoids extra core 1 reset by IDF code which can lead to loosing breakpoints set on that core.
  • target/espressif: Suppressed empty Gcov file read error. During Gcov data dump, target code tries to read existing but empty Gcov data file. So for the first dump it generates error message what actually does not indicate an error.
  • target/esp_common: Fixed handling of spaces in file paths ensuring that command arguments are handled properly.

Other:

Assets 10