mirror of
https://github.com/espressif/esp-idf.git
synced 2025-09-22 17:02:25 +00:00
docs: provide CN translation for 18484
This commit is contained in:
Shang Zhou
@@ -52,12 +52,12 @@ Some development boards have the USB-to-UART bridge installed. If a board does n
|
||||
|
||||
}
|
||||
|
||||
Some development boards also includes the USB-to-UART bridge, besides the USB peripheral.
|
||||
Apart from the USB peripheral, some development boards also include the USB-to-UART bridge.
|
||||
|
||||
USB-to-UART Bridge on Development Board
|
||||
---------------------------------------
|
||||
|
||||
For boards with an installed USB-to-UART bridge the connection between the personal computer and the bridge is USB and between the bridge and {IDF_TARGET_NAME} is UART.
|
||||
For boards with an installed USB-to-UART bridge, the connection between the personal computer and the bridge is USB and between the bridge and {IDF_TARGET_NAME} is UART.
|
||||
|
||||
.. blockdiag::
|
||||
:caption: Development Board with USB-to-UART Bridge
|
||||
@@ -150,7 +150,7 @@ Sometimes the USB-to-UART bridge is external. This is often used in small develo
|
||||
|
||||
.. note:: The {IDF_TARGET_NAME} supports only *USB CDC and JTAG*.
|
||||
|
||||
If you are flashing for the first time, you need to get the {IDF_TARGET_NAME} into the download mode manually. To do so, press and hold the **BOOT** button and then press the **RESET** button once. After that release the **BOOT** button.
|
||||
If you are flashing for the first time, you need to get the {IDF_TARGET_NAME} into the download mode manually. To do so, press and hold the ``BOOT`` button and then press the ``RESET`` button once. After that release the ``BOOT`` button.
|
||||
|
||||
.. only:: esp32s2
|
||||
|
||||
@@ -164,7 +164,7 @@ This section provides guidance on how to establish a serial connection between {
|
||||
Connect {IDF_TARGET_NAME} to PC
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
Connect the {IDF_TARGET_NAME} board to the PC using the USB cable. If device driver does not install automatically, identify USB to serial converter chip on your {IDF_TARGET_NAME} board (or external converter dongle), search for drivers in internet and install them.
|
||||
Connect the {IDF_TARGET_NAME} board to the PC using the USB cable. If device driver does not install automatically, identify USB-to-UART bridge on your {IDF_TARGET_NAME} board (or external converter dongle), search for drivers in internet and install them.
|
||||
|
||||
Below is the list of USB to serial converter chips installed on most of the {IDF_TARGET_NAME} boards produced by Espressif together with links to the drivers:
|
||||
|
||||
@@ -173,7 +173,6 @@ Below is the list of USB to serial converter chips installed on most of the {IDF
|
||||
|
||||
Please check the board user guide for specific USB-to-UART bridge chip used. The drivers above are primarily for reference. Under normal circumstances, the drivers should be bundled with an operating system and automatically installed upon connecting the board to the PC.
|
||||
|
||||
|
||||
For devices downloaded using a USB-to-UART bridge, you can run the following command including the optional argument to define the baud rate.
|
||||
|
||||
.. code-block:: bash
|
||||
@@ -184,8 +183,7 @@ You can change the flasher baud rate by replacing ``BAUD`` with the baud rate yo
|
||||
|
||||
.. note::
|
||||
|
||||
If the device does not support the auto download mode, you need to get into the download mode manually.
|
||||
To do so, press and hold the BOOT button and then press the RESET button once. After that release the BOOT button.
|
||||
If the device does not support the auto download mode, you need to get into the download mode manually. To do so, press and hold the ``BOOT`` button and then press the ``RESET`` button once. After that release the ``BOOT`` button.
|
||||
|
||||
Check port on Windows
|
||||
---------------------
|
||||
|
||||
@@ -3,22 +3,22 @@ Flashing Troubleshooting
|
||||
|
||||
:link_to_translation:`zh_CN:[中文]`
|
||||
|
||||
Failed to connect
|
||||
Failed to Connect
|
||||
-----------------
|
||||
|
||||
{IDF_TARGET_STRAP_GPIO:default="[NEEDS TO BE UPDATED]", esp32="GPIO0", esp32s2="GPIO0", esp32s3="GPIO0", esp32c2="GPIO9", esp32c3="GPIO9"}
|
||||
|
||||
If you run the given command and see errors such as "Failed to connect", there might be several reasons for this. One of the reasons might be issues encountered by ``esptool.py``, the utility that is called by the build system to reset the chip, interact with the ROM bootloader, and flash firmware. One simple solution to try is manual reset described below, and if it does not help you can find more details about possible issues in the `esptool troubleshooting <https://docs.espressif.com/projects/esptool/en/latest/esp32/troubleshooting.html>`_ page.
|
||||
If you run the given command and see errors such as "Failed to connect", there might be several reasons for this. One of the reasons might be issues encountered by ``esptool.py``, the utility that is called by the build system to reset the chip, interact with the ROM bootloader, and flash firmware. One simple solution to try is to manually reset as described below. If it does not help, you can find more details about possible issues in the `esptool troubleshooting <https://docs.espressif.com/projects/esptool/en/latest/esp32/troubleshooting.html>`_ page.
|
||||
|
||||
``esptool.py`` resets {IDF_TARGET_NAME} automatically by asserting DTR and RTS control lines of the USB to serial converter chip, i.e., FTDI or CP210x (for more information, see :doc:`establish-serial-connection`). The DTR and RTS control lines are in turn connected to ``{IDF_TARGET_STRAP_GPIO}`` and ``CHIP_PU`` (EN) pins of {IDF_TARGET_NAME}, thus changes in the voltage levels of DTR and RTS will boot {IDF_TARGET_NAME} into Firmware Download mode. As an example, check the `schematic <https://dl.espressif.com/dl/schematics/esp32_devkitc_v4-sch-20180607a.pdf>`_ for the ESP32 DevKitC development board.
|
||||
``esptool.py`` resets {IDF_TARGET_NAME} automatically by asserting DTR and RTS control lines of the USB-to-UART bridge, i.e., FTDI or CP210x (for more information, see :doc:`establish-serial-connection`). The DTR and RTS control lines are in turn connected to ``{IDF_TARGET_STRAP_GPIO}`` and ``CHIP_PU`` (EN) pins of {IDF_TARGET_NAME}, thus changes in the voltage levels of DTR and RTS will boot {IDF_TARGET_NAME} into Firmware Download mode. As an example, check the `schematic <https://dl.espressif.com/dl/schematics/esp32_devkitc_v4-sch-20180607a.pdf>`_ for the ESP32 DevKitC development board.
|
||||
|
||||
In general, you should have no problems with the `official esp-idf development boards <https://www.espressif.com/en/products/devkits>`_. However, ``esptool.py`` is not able to reset your hardware automatically in the following cases:
|
||||
|
||||
- Your hardware does not have the DTR and RTS lines connected to ``{IDF_TARGET_STRAP_GPIO}`` and ``CHIP_PU``
|
||||
- The DTR and RTS lines are configured differently
|
||||
- There are no such serial control lines at all
|
||||
- Your hardware does not have the DTR and RTS lines connected to ``{IDF_TARGET_STRAP_GPIO}`` and ``CHIP_PU``.
|
||||
- The DTR and RTS lines are configured differently.
|
||||
- There are no such serial control lines at all.
|
||||
|
||||
Depending on the kind of hardware you have, it may also be possible to manually put your {IDF_TARGET_NAME} board into Firmware Download mode (reset).
|
||||
|
||||
- For development boards produced by Espressif, this information can be found in the respective getting started guides or user guides. For example, to manually reset an ESP-IDF development board, hold down the **Boot** button (``{IDF_TARGET_STRAP_GPIO}``) and press the **EN** button (``CHIP_PU``).
|
||||
- For development boards produced by Espressif, this information can be found in the respective getting started guides or user guides. For example, to manually reset an ESP-IDF development board, hold down the ``Boot`` button (``{IDF_TARGET_STRAP_GPIO}``) and press the ``EN`` button (``CHIP_PU``).
|
||||
- For other types of hardware, try pulling ``{IDF_TARGET_STRAP_GPIO}`` down.
|
||||
|
||||
@@ -84,9 +84,9 @@ You are using this menu to set up project specific variables, e.g., Wi-Fi networ
|
||||
|
||||
If you are using the USB for flashing the {IDF_TARGET_NAME}, you need to change the channel for the console output from UART (default) to USB.
|
||||
|
||||
1. Navigate to the option ``Channel for console output``
|
||||
1. Navigate to the option ``Channel for console output``.
|
||||
|
||||
``Component config ---> ESP System Settings ---> Channel for console output``
|
||||
``Component config`` > ``ESP System Settings`` > ``Channel for console output``
|
||||
|
||||
2. Change to the option (the default will be always UART):
|
||||
|
||||
|
||||
@@ -81,7 +81,7 @@ You are using this menu to set up project specific variables, e.g., Wi-Fi networ
|
||||
|
||||
To use the USB for flashing the {IDF_TARGET_NAME}, you need to change the channel for the console output to USB. For the {IDF_TARGET_NAME}, the default console output channel is the UART.
|
||||
|
||||
1. Navigate to the option ``Channel for console output``
|
||||
1. Navigate to the option ``Channel for console output``.
|
||||
|
||||
``Component config ---> ESP System Settings ---> Channel for console output``
|
||||
|
||||
|
||||
Reference in New Issue
Block a user