v0.10.0-esp32-20211111

2021/11/11 Release, based on OpenOCD v0.10.0

Features:

• flash/esp32s3: Added ESP32-S3 flash support (#178 (comment)). Access to chip's flash is supported including setting breakpoints there.
• esp/riscv: Added coverage data collection support for Espressif RISCV chips. Currently this functionality is verified for ESP32-C3 only.
• esp_usb_jtag: Added ability to filter out USB device by product serial. Now it is possible to specify which USB device should be used by command espusbjtag serial <serial_num>.

Bug fixes:

• esp32s2-c3: Added automatic target reset upon GDB connection if memory protection is enabled (#190, #183, #176 (comment)).
• esp32c3: Avoided missing chip reset due to problems with dmi_scan. This led to the problem when SW breakpoints and syscalls do not work.
• esp32c3: Enables ebreaks in 'FLASH_BOOT' mode only. This led to the problem with flashing esp32c3 over UART with connected OpenOCD.
• flash/esp: Added detection of unexpected target algorithm exit during a flash read/write. Now the error message is printed if flash stub invocation ended up accidentally.
• flash/esp: Fixed cache flush in flasher stub for esp32s2/esp32c3. This problem led to partial data writes to flash.
• esp_usb_jtag: Added USB device re-enumeration in case of data transfer problem (#176, #178). This problem led to built-in USB-JTAG getting stuck after HW reset.
• esp_usb_jtag: Made tx/rx routines a bit more responsive and reliable. Added several attempts to tx/rx data in of failure.
• esp32s2-s3: Added power config register reset to prevent getting stuck in soft reset. This problem led to application getting stuck after resetting the target with reset run.
• esp32c3: Fixed WDT reset issue while waiting for resume after soft reset. This problem led to application getting stuck after resetting the target with reset run.
• esp_remote: Fixed runtest function. This problem was causing error during ESP32-C3 examination.
• gdb_server: Fixed registers access error reporting. Now it is controlled by gdb_report_register_access_error command. This problem led to RISCV GDB register access reporting and when GDB register packet is received when target is running.
• algorithm: Fixed cleaning up algorithm data upon failure.
• algorithm: Fixed '.data' and '.bss' section size alignment to avoid possible data corruption when running algorithms.