!19873 翻译完成 18549：根据IDE版本修改截图和步骤

Merge pull request !19873 from ester.zhou/TR-18549

en/device-dev/quick-start/quickstart-appendix-hi3516-ide.md

@@ -4,12 +4,12 @@
 >
 > Since OpenHarmony 3.2, the standard system does not perform adaptation verification for the Hi3516D V300 development board. You are advised to use RK3568 to develop standard-system devices.
 >
-> If you still need to use Hi3516DV300 to develop standard-system devices, adaptation may fail. In this case, contact the chip supplier to obtain the adaptation guide or complete adaptation by yourself.
+> If you still use Hi3516D V300 to develop standard-system devices, adaptation may fail. Contact the chip supplier to obtain the adaptation guide and complete adaptation by yourself.
 
-In addition to the small system, the Hi3516DV300 development board also supports the standard system. This topic describes how to develop the standard system on Hi3516DV300 by using DevEco Device Tool.
+In addition to the small system, the Hi3516D V300 development board also supports the standard system. This topic describes how to develop the standard system on Hi3516DV300 with DevEco Device Tool, by walking you through a simple example.
 
 
-The following exemplifies how to run the first program on the development board. This program displays the message "Hello World!" .
+The following exemplifies how to run the first program on the development board. This program displays the message "Hello World!"
 
 
 Before development, complete the following preparations:
@@ -49,44 +49,44 @@ Perform the steps below in the source code directory:
 1. Create a directory and write the service code.
    
    Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program.
-
-
-   ```
-   #include <stdio.h>
-   #include "helloworld.h"
-   int main(int argc, char **argv)
-   {
-       HelloPrint();
-       return 0;
-   }
-   void HelloPrint()
-   {
-       printf("\n\n");
-       printf("\n\t\tHello World!\n");
-       printf("\n\n");
-   }
-   ```
-
+   
+   
+      ```
+      #include <stdio.h>
+      #include "helloworld.h"
+      int main(int argc, char **argv)
+      {
+          HelloPrint();
+          return 0;
+      }
+      void HelloPrint()
+      {
+          printf("\n\n");
+          printf("\n\t\tHello World!\n");
+          printf("\n\n");
+      }
+      ```
+   
    Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows:
-
-
-   ```
-   #ifndef HELLOWORLD_H
-   #define HELLOWORLD_H
-   #ifdef __cplusplus
-   #if __cplusplus
-   extern "C" {
-   #endif
-   #endif
-   void HelloPrint();
-   #ifdef __cplusplus
-   #if __cplusplus
-   }
-   #endif
-   #endif
-   #endif // HELLOWORLD_H
-   ```
-
+   
+   
+      ```
+      #ifndef HELLOWORLD_H
+      #define HELLOWORLD_H
+      #ifdef __cplusplus
+      #if __cplusplus
+      extern "C" {
+      #endif
+      #endif
+      void HelloPrint();
+      #ifdef __cplusplus
+      #if __cplusplus
+      }
+      #endif
+      #endif
+      #endif // HELLOWORLD_H
+      ```
+   
 2. Create a build file.
    1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows:
       
@@ -106,7 +106,8 @@ Perform the steps below in the source code directory:
          configs = []
          deps =[]    # Internal dependencies of the component.
          part_name = "hello"    # Component name. This parameter is mandatory.
-         install_enable = true # Whether to install the software by default. This parameter is optional. By default, the software is not installed.
+         install_enable = true # Whether to install the software by default. This parameter is optional.
+                                 By default, the software is not installed.
        }
        ```
    2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows:
@@ -145,11 +146,11 @@ Perform the steps below in the source code directory:
            }
        }
        ```
-
-       The **bundle.json** file consists of two parts. The first part describes the information about the subsystem to which the component belongs, and the second part defines the build configuration for the component. When adding a component, you must specify the **sub_component** of the component. If there are APIs provided for other components, add them in **inner_kits**. If there are test cases, add them in **test**.
-
+   
+    The **bundle.json** file consists of two parts. The first part describes the information about the subsystem to which the component belongs, and the second part defines the build configuration for the component. When adding a component, you must specify the **sub_component** of the component. Add the APIs provided for other components, if any, in **inner_kits**. Add the test cases, if any, in **test**.
+   
 3. Modify the subsystem configuration file.
-
+   
    Add the configuration of the new subsystem to the **build/subsystem_config.json** file.
 
 
@@ -161,9 +162,9 @@ Perform the steps below in the source code directory:
    ```
 
 4. Modify the product configuration file.
-
+   
    In the **productdefine/common/products/Hi3516DV300.json** file, add the **hello** part after the existing part.
-
+   
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    >
    > In this example, the OpenHarmony-v3.1-Release version is used, where the Hi3516 configuration file is **productdefine/common/products/Hi3516DV300.json**. In OpenHarmony-v3.2-Beta2 and later versions, the Hi3516 configuration file is **vendor/hisilicon/Hi3516DV300/config.json**.
@@ -189,22 +190,25 @@ With DevEco Device Tool, you can easily build source code of the Hi3516DV300 dev
    
    ![en-us_image_0000001274745038](figures/en-us_image_0000001274745038.png)
 
-2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete. If a message is displayed indicating that some tools are missing, click **Install** to automatically install the required tools.
+2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete.
+
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If some tool types are missing, click **Add Utility** to add them.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+   - If the status of **OpenHarmony Environment Dependency** is abnormal (![status_uninstall](figures/status_uninstall.png), click **Install**.
    
-   ![en-us_image_0000001292531862](figures/en-us_image_0000001292531862.png)
+   ![3516_standard_false](figures/3516_standard_false.png)
 
-3. Install the toolchain related to Hi3516DV300. Certain tools may require the root access to install. In this case, enter the user password in the **TERMINAL** window.
+   Certain tools may require the root access to install. For these tools, enter the user password in the **TERMINAL** window as prompted.
 
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    >
    > - If pip fails to be installed, [change the Python source](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) and try again.
-   > - If APT fails to be installed, [change the APT source](https://device.harmonyos.com/en/docs/documentation/guide/faq-toolchain-install-0000001301623822) and try again.
+   > - If apt fails to be installed, [change the apt source](https://device.harmonyos.com/en/docs/documentation/guide/faq-toolchain-install-0000001301623822) and try again.
 
    ![en-us_image_0000001274748606](figures/en-us_image_0000001274748606.png)
 
-   After the toolchain is automatically installed, the figure below is displayed.
-
-   ![en-us_image_0000001296270098](figures/en-us_image_0000001296270098.png)
+   After the installation is complete, the status of the tools and environment dependencies is displayed as ![status_install](figures/status_install.png).
 
 4. On the **hispark_taurus_standard** tab page, set **build_type**, whose default value is **debug**.
    
@@ -251,9 +255,12 @@ Hi3516DV300 supports burning for the standard system through the USB port and ne
    
    ![en-us_image_0000001275752808](figures/en-us_image_0000001275752808.png)
 
-4. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
-   
-   ![Phoenix-upload](figures/Phoenix-upload.png)
+4. On the **Tool Chain** tab page, DevEco Device Tool automatically checks for the uploader tool.
+
+   - If the tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+
+   ![3516_standard_false](figures/3516_standard_false.png)
 
 5. On the **hispark_taurus_standard** tab page, set the burning options. The settings are automatically saved.
 

en/device-dev/quick-start/quickstart-ide-3516-build.md

@@ -13,32 +13,35 @@ With DevEco Device Tool, you can easily build source code of the Hi3516DV300 dev
 
    ![en-us_image_0000001274745038](figures/en-us_image_0000001274745038.png)
 
-2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete. If a message is displayed indicating that some tools are missing, click **Install** to automatically install the required tools.
+2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete.
+
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If some tool types are missing, click **Add Utility** to add them.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+   - If the status of **OpenHarmony Environment Dependency** is abnormal (![status_uninstall](figures/status_uninstall.png), click **Install**.
 
    ![en-us_image_0000001307480750](figures/en-us_image_0000001307480750.png)
 
-3. Install the toolchain related to Hi3516DV300. Certain tools may require the root access to install. In this case, enter the user password in the **TERMINAL** window.
+   Certain tools may require the root access to install. For these tools, enter the user password in the **TERMINAL** window as prompted.
 
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    >
    > - If pip fails to be installed, [change the Python source](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) and try again.
-   > - If APT fails to be installed, [change the APT source](https://device.harmonyos.com/en/docs/documentation/guide/faq-toolchain-install-0000001301623822) and try again.
+   > - If apt fails to be installed, [change the apt source](https://device.harmonyos.com/en/docs/documentation/guide/faq-toolchain-install-0000001301623822) and try again.
 
    ![en-us_image_0000001360080305](figures/en-us_image_0000001360080305.png)
 
-   After the toolchain is automatically installed, the figure below is displayed.
-
-   ![en-us_image_0000001307320918](figures/en-us_image_0000001307320918.png)
-
-4. On the **ipcamera_hispark_taurus** tab page, set **build_type**, whose default value is **debug**.
+   After the installation is complete, the status of the tools and environment dependencies is displayed as ![status_install](figures/status_install.png).
+   
+3. On the **ipcamera_hispark_taurus** tab page, set **build_type**, whose default value is **debug**.
 
    ![en-us_image_0000001307160958](figures/en-us_image_0000001307160958.png)
 
-5. Choose **PROJECT TASKS** > **ipcamera_hispark_taurus** > **Build** to start building.
+4. Choose **PROJECT TASKS** > **ipcamera_hispark_taurus** > **Build** to start building.
 
    ![en-us_image_0000001360439881](figures/en-us_image_0000001360439881.png)
 
-6. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the build is complete.
+5. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the build is complete.
 
    ![en-us_image_0000001307480754](figures/en-us_image_0000001307480754.png)
 

en/device-dev/quick-start/quickstart-ide-3516-burn.md

@@ -7,7 +7,7 @@ Burning is the process of downloading compiled program files to a development bo
 The images of Hi3516DV300 are burnt in the Windows environment. After burning is initiated, DevEco Device Tool copies the target program files generated in the Ubuntu environment to the specified Windows directory in remote mode, and then burns the program files to Hi3516DV300 using the Windows burning tool.
 
 
-Hi3516DV300 supports burning for the small system through the USB port, network port, and serial port. This topic describes how to burn source code through the USB port.
+Hi3516D V300 supports burning for the small system through the USB port, network port, and serial port. This topic describes how to burn source code through the USB port.
 
 
 ## Prerequisites
@@ -33,24 +33,29 @@ Hi3516DV300 supports burning for the small system through the USB port, network
 
    ![en-us_image_0000001275752808](figures/en-us_image_0000001275752808.png)
 
-4. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
+4. On the **Tool Chain** tab page, DevEco Device Tool automatically checks for the uploader tool.
 
-   ![Phoenix-upload](figures/Phoenix-upload.png)
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
 
-5. On the **hi3516dv300** tab page, set the burning options. The settings are automatically saved.
+   ![3516_false](figures/3516_false.png)
+
+5. On the **ipcamea_hispark_taurus** tab page, set the burning options. The settings are automatically saved.
    - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time. Check the preset information of the files to be burnt and modify them when necessary. To modify the burning settings for a specific file, click ![en-us_image_0000001275592884](figures/en-us_image_0000001275592884.png) next to the file.
       > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
       >
-      > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
-
+      > Set the start address and length of the partition based on the size of the files to be burnt.
+      >
+      > Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+      
       ![3516-small-partitions](figures/3516-small-partitions.png)
-
+   
    - **upload_protocol**: Select the burning protocol **hiburn-usb**.
    - **upload_port**: Select the serial port number obtained.
-  
-   ![3516-small-usb](figures/3516-small-usb.png)
    
-6. Choose **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows.
+      ![3516-small-usb](figures/3516-small-usb.png)
+   
+6. Choose **ipcamera_hispark_taurus** > **Upload** to transfer the files to be burnt from Ubuntu to Windows.
 
    ![en-us_image_0000001326234609](figures/en-us_image_0000001326234609.png)
 
@@ -58,7 +63,9 @@ Hi3516DV300 supports burning for the small system through the USB port, network
 
    ![en-us_image_0000001275835836](figures/en-us_image_0000001275835836.png)
 
-7. When the following information is displayed in the **TERMINAL** window, press and hold the **Update** key within 15 seconds, remove and insert the USB cable, and then release the **Update** key to start burning.
+7. When the following information is displayed in the **TERMINAL** window, press and hold the **Update** key (shown below) within 15 seconds, remove and insert the USB cable, and then release the **Update** key to start burning.
+
+   ![3516_button](figures/3516_button.png)
 
    ![en-us_image_0000001326412233](figures/en-us_image_0000001326412233.png)
 

en/device-dev/quick-start/quickstart-ide-3568-build.md

@@ -13,22 +13,25 @@ With DevEco Device Tool, you can easily build source code of the Rockchip RK3568
 
    ![en-us_image_0000001327669509](figures/en-us_image_0000001327669509.png)
 
-2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete. If a message is displayed indicating that some tools are missing, click **Install** to automatically install the required tools.
+2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete.
+
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If some tool types are missing, click **Add Utility** to add them.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+   - If the status of **OpenHarmony Environment Dependency** is abnormal (![status_uninstall](figures/status_uninstall.png), click **Install**.
+
+   ![rk3568_false](figures/rk3568_false.png)
+
+   Certain tools may require the root access to install. For these tools, enter the user password in the **TERMINAL** window as prompted.
 
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    >
    > - If pip fails to be installed, [change the Python source](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) and try again.
    > - If APT fails to be installed, [change the APT source](https://device.harmonyos.com/en/docs/documentation/guide/faq-toolchain-install-0000001301623822) and try again.
-
-   ![en-us_image_0000001292531806](figures/en-us_image_0000001292531806.png)
-
-   Install the toolchain related to RK3568. Certain tools may require the root access to install. In this case, enter the user password in the **TERMINAL** window.
-
+   
    ![en-us_image_0000001327429541](figures/en-us_image_0000001327429541.png)
 
-   After the toolchain is automatically installed, the figure below is displayed.
-
-   ![en-us_image_0000001349388493](figures/en-us_image_0000001349388493.png)
+   After the installation is complete, the status of the tools and environment dependencies is displayed as ![status_install](figures/status_install.png).
 
 3. On the **rk3568** tab page, set **build_type**, whose default value is **debug**.
 

en/device-dev/quick-start/quickstart-ide-3568-burn.md

@@ -7,9 +7,9 @@ Burning is the process of downloading compiled program files to a development bo
 The images of RK3568 are burnt in the Windows environment. After burning is initiated, DevEco Device Tool copies the target program files generated in the Ubuntu environment to the specified Windows directory in remote mode, and then burns the program files to RK3568 using the Windows burning tool.
 
 
-## Prerequisites
+## Preparations
 
-[Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) and install **DriverInstall.exe**.
+[Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) and install **DriverInstall.exe**. If a message is displayed to indicate that the driver has been installed, you can proceed to the burning steps.
 
 > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
 >
@@ -31,9 +31,12 @@ The images of RK3568 are burnt in the Windows environment. After burning is init
 
    ![en-us_image_0000001330777737](figures/en-us_image_0000001330777737.png)
 
-4. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
+4. On the **Tool Chain** tab page, DevEco Device Tool automatically checks for the uploader tool.
 
-   ![3865-uploader](figures/3865-uploader.png)
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+
+   ![rk3568_false](figures/rk3568_false.png)
 
 5. On the **rk3568** tab page, set the burning options. The settings are automatically saved.
 
@@ -53,10 +56,8 @@ The images of RK3568 are burnt in the Windows environment. After burning is init
 
 7. If the message "Operation paused, Please press Enter key to continue" is displayed, press **Enter**.
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   >
    > If the message "The board is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
-   
 
-Wait until the burning is complete. If the following message is displayed, the burning is successful.
+   Wait until the burning is complete. If the following message is displayed, the burning is successful.
 
    ![en-us_image_0000001327549705](figures/en-us_image_0000001327549705.png)

en/device-dev/quick-start/quickstart-ide-3861-build.md

@@ -13,11 +13,17 @@ With DevEco Device Tool, you can easily build source code of the Hi3861V100 deve
 
    ![en-us_image_0000001275483042](figures/en-us_image_0000001275483042.png)
 
-2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete. If a message is displayed indicating that some tools are missing, click **Install** to automatically install the required tools.
+2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compiler toolchain is complete.
+
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If some tool types are missing, click **Add Utility** to add them.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
+   - If the status of **OpenHarmony Environment Dependency** is abnormal (![status_uninstall](figures/status_uninstall.png), click **Install**.
 
    ![en-us_image_0000001333256741](figures/en-us_image_0000001333256741.png)
 
-3. Install the toolchain related to Hi3861V100. Certain tools may require the root access to install. In this case, enter the user password in the **TERMINAL** window.
+   Certain tools may require the root access to install. For these tools, enter the user password in the **TERMINAL** window as prompted.
+
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    >
    > - If pip fails to be installed, [change the Python source](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) and try again.
@@ -25,19 +31,17 @@ With DevEco Device Tool, you can easily build source code of the Hi3861V100 deve
 
    ![en-us_image_0000001280938208](figures/en-us_image_0000001280938208.png)
 
-   After the toolchain is automatically installed, the figure below is displayed.
-
-   ![en-us_image_0000001281378224](figures/en-us_image_0000001281378224.png)
+   After the installation is complete, the status of the tools and environment dependencies is displayed as ![status_install](figures/status_install.png).
 
-4. On the **wifiiot_hispark_pegasus** tab page, set **build_type**, whose default value is **debug**.
+3. On the **wifiiot_hispark_pegasus** tab page, set **build_type**, whose default value is **debug**.
 
    ![en-us_image_0000001333581089](figures/en-us_image_0000001333581089.png)
 
-5. Choose **PROJECT TASKS** > **wifiiot_hispark_pegasus** > **Build** to start building.
+4. Choose **PROJECT TASKS** > **wifiiot_hispark_pegasus** > **Build** to start building.
 
    ![en-us_image_0000001281221352](figures/en-us_image_0000001281221352.png)
 
-6. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the build is complete.
+5. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the build is complete.
 
    ![en-us_image_0000001405938781](figures/en-us_image_0000001405938781.png)
 

en/device-dev/quick-start/quickstart-ide-3861-burn.md

@@ -28,15 +28,14 @@ The images of Hi3861V100 are burnt in the Windows environment. After burning is
 
    ![en-us_image_0000001333802045](figures/en-us_image_0000001333802045.png)
 
-4. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
+4. On the **Tool Chain** tab page, DevEco Device Tool automatically checks for the uploader tool.
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   >
-   > If a later version of Uploader is available or another burning tool is required, select it in **Uploader** > **Use Custom Burn Tool**.
+   - If any tool is indicated as **uninstalled** (![status_uninstall](figures/status_uninstall.png)), click **Download Uninstalled Tools** to install all the required tools, or click **Download** next to a tool to install the specific tool.
+   - If **Download** is not available for a missing tool, it is not cataloged in DevEco Device Tool. In this case, you need to download the tool to the local host and click **Import** to import it.
 
-   ![Phoenix-upload](figures/Phoenix-upload.png)
+   ![3861_false](figures/3861_false.png)
 
-5. On the **hi3861** tab page, set the burning options. The settings are automatically saved.
+5. On the **wifiiot_hispark_pegasus** tab page, set the burning options. The settings are automatically saved.
    - **upload_port**: Select the serial port number obtained.
    - **upload_protocol**: Select the burning protocol **hiburn-serial**.
    - **upload_partitions**: Select the file for burning. To modify the burning settings for a specific file, click ![en-us_image_0000001333642545](figures/en-us_image_0000001333642545.png) next to the file.

en/device-dev/quick-start/quickstart-ide-env-ubuntu.md

@@ -19,6 +19,10 @@ The following describes how to set up the Ubuntu environment.
 
 - DevEco Device Tool: latest and same version installed on both Ubuntu and Windows
 
+  > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+  >
+  > The following uses DevEco Device Tool of the 3.1 Release version as an example. The supported features and operations vary according to the DevEco Device Tool version. For details, see the [User Guide](https://device.harmonyos.com/en/docs/documentation/guide/service_introduction-0000001050166905).
+
 
 ## Procedure
 

en/device-dev/quick-start/quickstart-ide-env-win.md

@@ -10,7 +10,11 @@ The following describes how to set up the Windows environment.
 
 - Windows 10 (64-bit): 8 GB or larger memory and a 100 GB or larger hard disk recommended
 
-- DevEco Device Tool: latest and same version installed on both Windows and Ubuntu
+- DevEco Device Tool: latest and same version installed on both Ubuntu and Windows
+
+  > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+  >
+  > The following uses DevEco Device Tool of the 3.1 Release version as an example. The supported features and operations vary according to the DevEco Device Tool version. For details, see the [User Guide](https://device.harmonyos.com/en/docs/documentation/guide/service_introduction-0000001050166905).
 
 
 ## Procedure
@@ -23,6 +27,7 @@ The following describes how to set up the Windows environment.
 
 4. Set the installation path for DevEco Device Tool and click **Next**. Make sure the path does not contain Chinese characters and is **in a drive other than the C drive**.
 
+   ![en-us_image_0000001326386753](figures/en-us_image_0000001326386753.png)
 
 5. Install the dependent tools by following the onscreen instructions.
 

en/device-dev/quick-start/quickstart-ide-import-project.md

 # Creating a Project and Obtaining Source Code
 
 
-When creating an OpenHarmony project, DevEco Device Tool automatically downloads the source code in one of the following types, depending on the use case: **OpenHarmony Stable Version**, **OpenHarmony Sample**, and **HarmonyOS Connect Solution**.
-
-
-**OpenHarmony Stable Version** provides source code of an OpenHarmony stable version, which is acquired from a mirror site. The OpenHarmony-v1.1.4-LTS, OpenHarmony-v3.0.3-LTS, and OpenHarmony-v3.1-Release versions are supported.
+When creating an OpenHarmony project, DevEco Device Tool automatically downloads the source code in one of the supported types.
 
+Source code of an OpenHarmony stable version is downloaded from a mirror site. The following versions are available: OpenHarmony-v3.0.3-LTS, OpenHarmony-v3.1-Release, OpenHarmony-v3.2-Beta3, OpenHarmony-v3.2-Beta4, OpenHarmony-v3.2-Beta5, and OpenHarmony-v3.2-Release.
 
 The source code from a mirror site is generally what's available when the stable version is released. Therefore, it may be out of date. To acquire the latest source code of a version, follow the instructions in [Acquiring Source Code from the Gitee Code Repository](../get-code/sourcecode-acquire.md). After acquiring the source code, import it to DevEco Device Tool by following the instructions in [Importing OpenHarmony Source Code](https://device.harmonyos.com/en/docs/documentation/guide/open_project-0000001071680043).
 
-
-The following describes how to download source code of the **OpenHarmony Stable Version** type. For details about how to download source code of the **OpenHarmony Sample** and **HarmonyOS Connect Solution** types, see [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/documentation/guide/service_introduction-0000001050166905).
+The following describes how to download source code of the **OpenHarmony Stable Version** type. For details about how to download source code of other types, see [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/documentation/guide/service_introduction-0000001050166905).
 
 
 ## Prerequisites
@@ -29,7 +26,7 @@ A remote connection from the Windows environment to the Ubuntu environment has b
    ![en-us_image_0000001272258726](figures/en-us_image_0000001272258726.png)
 
 2. On the project configuration wizard page, configure the project settings.
-   - **OpenHarmony Source Code**: OpenHarmony version of the source code to download. The available versions are OpenHarmony-v1.1.4-LTS, OpenHarmony-v3.0.3-LTS, or OpenHarmony-v3.1-Release. Select **OpenHarmony Stable Version** here.
+   - **OpenHarmony Source Code**: OpenHarmony version of the source code to download. Select a version under **OpenHarmony Stable Version**, such as OpenHarmony-v3.0.3-LTS, OpenHarmony-v3.1-Release, OpenHarmony-v3.2-Beta3, OpenHarmony-v3.2-Beta4, OpenHarmony-v3.2-Beta5, and OpenHarmony-v3.2-Release.
    - **Project Name**: project name.
    - **Project Path**: path for storing the project files.
    - **SOC**: supported SoC.