From 1737366af77ab59cdd469b67b5a031e44af62c6c Mon Sep 17 00:00:00 2001 From: Xabi Crespo Date: Mon, 26 Jun 2023 09:48:45 +0200 Subject: [PATCH] docs(jtag): Update chip revisions to follow ESP32-C3 errata (GitHub PR) --- docs/en/api-guides/jtag-debugging/index.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/api-guides/jtag-debugging/index.rst b/docs/en/api-guides/jtag-debugging/index.rst index f81b886821..812a51dbcf 100644 --- a/docs/en/api-guides/jtag-debugging/index.rst +++ b/docs/en/api-guides/jtag-debugging/index.rst @@ -78,7 +78,7 @@ Likewise, the "Application Loading and Monitoring" label indicates the key softw .. note:: - Debugging through the USB interface implemented in {IDF_TARGET_NAME} requires to have a chip with revision 3 or newer. Please use other debugging options (e.g. with ESP-Prog) for chip revision 1 and 2. The easiest way to determine the chip revision is to look for the ``Chip is ESP32-C3 (revision 3)`` message near the end of a successful chip flashing done by ``idf.py flash``. + Debugging through the USB interface implemented in {IDF_TARGET_NAME} requires to have a chip with revision 0.3 or newer. Please use other debugging options (e.g. with ESP-Prog) for chip revisions 0.1 and 0.2. The easiest way to determine the chip revision is to look for the ``boot: chip revision: v0.3`` message at the beginning of the boot log. See `SoC errata `_ for more details. .. _jtag-debugging-selecting-jtag-adapter: