alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2025-08-08 04:02:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

esp8684: rename target to esp32c2

Browse Source
This commit is contained in:
laokaiyao
2022-01-18 10:32:56 +08:00
parent 6e00f10fd4
commit cf049e15ed
354 changed files with 894 additions and 897 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/api-guides/index.rst
View File

@@ -31,7 +31,7 @@ API Guides
OpenThread <openthread>
Partition Tables <partition-tables>
Performance <performance/index>
:not esp8684: RF Calibration <RF_calibration>
:not esp32c2: RF Calibration <RF_calibration>
:esp32: Secure Boot <../security/secure-boot-v1>
Secure Boot V2 <../security/secure-boot-v2>
Thread Local Storage <thread-local-storage>

28
docs/en/api-guides/jtag-debugging/esp8684.inc → docs/en/api-guides/jtag-debugging/esp32c2.inc
View File

@@ -11,9 +11,9 @@
::
openocd -f board/esp8684-BOARD_NAME.cfg
openocd -f board/esp32c2-BOARD_NAME.cfg
.. |run-openocd-device-name| replace:: ESP8684
.. |run-openocd-device-name| replace:: ESP32C2
---
@@ -23,7 +23,7 @@
CHIP SPECIFIC LOG OUTPUT
.. |run-openocd-cfg-file-err| replace:: ``Can't find board/esp8684-BOARD_NAME.cfg``
.. |run-openocd-cfg-file-err| replace:: ``Can't find board/esp32c2-BOARD_NAME.cfg``
---
@@ -31,7 +31,7 @@
::
openocd -f board/esp8684-BOARD_NAME.cfg -c "program_esp filename.bin 0x10000 verify exit"
openocd -f board/esp32c2-BOARD_NAME.cfg -c "program_esp filename.bin 0x10000 verify exit"
---
@@ -39,7 +39,7 @@
.. code-block:: bash
src/openocd -f board/esp8684-BOARD_NAME.cfg
src/openocd -f board/esp32c2-BOARD_NAME.cfg
---
@@ -47,13 +47,13 @@
.. code-block:: batch
src\openocd -f board/esp8684-BOARD_NAME.cfg
src\openocd -f board/esp32c2-BOARD_NAME.cfg
---
.. idf-py-openocd-default-cfg
.. |idf-py-def-cfg| replace:: ``-f board/esp8684-BOARD_NAME.cfg``
.. |idf-py-def-cfg| replace:: ``-f board/esp32c2-BOARD_NAME.cfg``
---
@@ -61,13 +61,13 @@
::
openocd -f board/esp8684-BOARD_NAME.cfg -c "init; halt; esp appimage_offset 0x210000"
openocd -f board/esp32c2-BOARD_NAME.cfg -c "init; halt; esp appimage_offset 0x210000"
---
.. openocd-cfg-files
.. list-table:: OpenOCD configuration files for ESP8684
.. list-table:: OpenOCD configuration files for ESP32C2
:widths: 25 75
:header-rows: 1
@@ -86,11 +86,11 @@
.. jtag-pins
.. list-table:: ESP8684 pins and JTAG signals
.. list-table:: ESP32C2 pins and JTAG signals
:widths: 25 75
:header-rows: 1
* - ESP8684 Pin
* - ESP32C2 Pin
- JTAG Signal
* - MTDO / GPIOX
- TDO
@@ -110,7 +110,7 @@
::
openocd -l openocd_log.txt -d3 -f board/esp8684-BOARD_NAME.cfg
openocd -l openocd_log.txt -d3 -f board/esp32c2-BOARD_NAME.cfg
---
@@ -118,7 +118,7 @@
::
openocd -d3 -f board/esp8684-BOARD_NAME.cfg 2>&1 | tee openocd.log
openocd -d3 -f board/esp32c2-BOARD_NAME.cfg 2>&1 | tee openocd.log
---
@@ -132,7 +132,7 @@
.. devkit-defs
.. |devkit-name| replace:: ESP8684
.. |devkit-name| replace:: ESP32C2
.. |devkit-name-with-link| replace:: LINK TO DEVKIT
---

2
docs/en/api-guides/memory-types.rst
View File

@@ -134,7 +134,7 @@ The same region of RTC FAST memory can be accessed as both instruction and data
In single core mode, remaining RTC FAST memory is added to the heap unless the option :ref:`CONFIG_ESP_SYSTEM_ALLOW_RTC_FAST_MEM_AS_HEAP` is disabled. This memory can be used interchangeably with :ref:`DRAM`, but is slightly slower to access and not DMA capable.
.. only:: not esp32 and not esp8684
.. only:: not esp32 and not esp32c2
Remaining RTC FAST memory is added to the heap unless the option :ref:`CONFIG_ESP_SYSTEM_ALLOW_RTC_FAST_MEM_AS_HEAP` is disabled. This memory can be used interchangeably with :ref:`DRAM`, but is slightly slower to access.

2
docs/en/api-guides/partition-tables.rst
View File

@@ -88,7 +88,7 @@ The ESP-IDF bootloader ignores any partition types other than ``app`` (0x00) and
SubType
~~~~~~~
{IDF_TARGET_ESP_PHY_REF:default = ":ref:`CONFIG_ESP_PHY_INIT_DATA_IN_PARTITION`", esp8684 = "(not updated yet)"}
{IDF_TARGET_ESP_PHY_REF:default = ":ref:`CONFIG_ESP_PHY_INIT_DATA_IN_PARTITION`", esp32c2 = "(not updated yet)"}
The 8-bit subtype field is specific to a given partition type. ESP-IDF currently only specifies the meaning of the subtype field for ``app`` and ``data`` partition types.

4
docs/en/api-guides/unit-tests.rst
View File

@@ -300,7 +300,7 @@ Refer to :component_file:`cmock/CMock/docs/CMock_Summary.md` for more details on
Requirements
^^^^^^^^^^^^
The following requirements are necessary to generate the mocks:
The following requirements are necessary to generate the mocks:
.. list::
- Installed ESP-IDF with all its requirements
@@ -316,7 +316,7 @@ In the component mock, the following parts are specified:
.. list::
- The headers providing the functions to generate mocks for
- Include paths of the aforementioned headers
- Include paths of the aforementioned headers
- Dependencies of the mock component (this is necessary e.g. if the headers include files from other components)
All these parts have to be specified using the IDF build system function ``idf_component_mock``. You can use the IDF build system function ``idf_component_get_property`` with the tag ``COMPONENT_OVERRIDEN_DIR`` to access the component directory of the original component and then register the mock component parts using ``idf_component_mock``: