update 导入OpenHarmony工程

Signed-off-by: Nduangavin123 <duanxichao@huawei.com>

en/device-dev/get-code/Readme-EN.md

@@ -2,4 +2,6 @@
 
 -   [Source Code Acquisition](source-code-acquisition.md)
 -   [Tool Acquisition](tool-acquisition.md)
+    -   [Docker Environment](docker-environment.md)
+    -   [IDE](ide.md)
 

en/device-dev/get-code/docker-environment.md

+# Docker Environment<a name="EN-US_TOPIC_0000001055701144"></a>
+
+-   [Introduction](#section107932281315)
+-   [Preparations](#section7337134183512)
+-   [Standalone Docker Environment](#section2858536103611)
+    -   [Setting Up the Docker Environment for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)](#section319412277287)
+    -   [Building for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)](#section631485163615)
+    -   [Setting Up the Docker Environment for Standard-System Devices \(reference memory ≥ 128 MB\)](#section13585262391)
+    -   [Building for Standard-System Devices \(reference memory ≥ 128 MB\)](#section193711513406)
+
+-   [HPM-based Docker Environment](#section485713518337)
+    -   [Setting Up the Docker Environment](#section3295842510)
+    -   [Obtaining and Building Source Code](#section69141039143518)
+
+
+## Introduction<a name="section107932281315"></a>
+
+OpenHarmony provides the following two types of Docker environments for you to quickly get the development environment ready:
+
+-   Standalone Docker environment: applicable when using Ubuntu or Windows to build a distribution
+-   HPM-based Docker environment: applicable when using the HarmonyOS Package Manager \(HPM\) to build a distribution
+
+**Table  1**  Docker image
+
+<a name="table11986917191214"></a>
+<table><thead align="left"><tr id="row149861417121215"><th class="cellrowborder" valign="top" width="15.831583158315832%" id="mcps1.2.6.1.1"><p id="p798611714124"><a name="p798611714124"></a><a name="p798611714124"></a>Docker Environment</p>
+</th>
+<th class="cellrowborder" valign="top" width="13.97139713971397%" id="mcps1.2.6.1.2"><p id="p1698661751219"><a name="p1698661751219"></a><a name="p1698661751219"></a>System Type</p>
+</th>
+<th class="cellrowborder" valign="top" width="18.61186118611861%" id="mcps1.2.6.1.3"><p id="p1798671761217"><a name="p1798671761217"></a><a name="p1798671761217"></a>Operating Platform</p>
+</th>
+<th class="cellrowborder" valign="top" width="35.8935893589359%" id="mcps1.2.6.1.4"><p id="p20526205414295"><a name="p20526205414295"></a><a name="p20526205414295"></a>Docker Image Repository</p>
+</th>
+<th class="cellrowborder" valign="top" width="15.69156915691569%" id="mcps1.2.6.1.5"><p id="p1833001309"><a name="p1833001309"></a><a name="p1833001309"></a>Tag</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="row1798661751216"><td class="cellrowborder" rowspan="2" align="center" valign="top" width="15.831583158315832%" headers="mcps1.2.6.1.1 "><p id="p1898631791213"><a name="p1898631791213"></a><a name="p1898631791213"></a>Standalone Docker environment</p>
+</td>
+<td class="cellrowborder" valign="top" width="13.97139713971397%" headers="mcps1.2.6.1.2 "><p id="p1598617177128"><a name="p1598617177128"></a><a name="p1598617177128"></a>Mini and small systems</p>
+</td>
+<td class="cellrowborder" valign="top" width="18.61186118611861%" headers="mcps1.2.6.1.3 "><p id="p898614178122"><a name="p898614178122"></a><a name="p898614178122"></a>Ubuntu or Windows</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.8935893589359%" headers="mcps1.2.6.1.4 "><p id="p12667431305"><a name="p12667431305"></a><a name="p12667431305"></a>swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker</p>
+</td>
+<td class="cellrowborder" valign="top" width="15.69156915691569%" headers="mcps1.2.6.1.5 "><p id="p143320173017"><a name="p143320173017"></a><a name="p143320173017"></a>0.0.5</p>
+</td>
+</tr>
+<tr id="row998612174129"><td class="cellrowborder" valign="top" headers="mcps1.2.6.1.1 "><p id="p1998617172126"><a name="p1998617172126"></a><a name="p1998617172126"></a>Standard system</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.6.1.2 "><p id="p1598641741215"><a name="p1598641741215"></a><a name="p1598641741215"></a>Ubuntu</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.6.1.3 "><p id="p552616549297"><a name="p552616549297"></a><a name="p552616549297"></a>swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.6.1.4 "><p id="p1633303300"><a name="p1633303300"></a><a name="p1633303300"></a>0.0.1</p>
+</td>
+</tr>
+<tr id="row5986201731214"><td class="cellrowborder" align="center" valign="top" width="15.831583158315832%" headers="mcps1.2.6.1.1 "><p id="p136981216143"><a name="p136981216143"></a><a name="p136981216143"></a>HPM-based Docker environment</p>
+</td>
+<td class="cellrowborder" valign="top" width="13.97139713971397%" headers="mcps1.2.6.1.2 "><p id="p969831161416"><a name="p969831161416"></a><a name="p969831161416"></a>Mini and small systems</p>
+</td>
+<td class="cellrowborder" valign="top" width="18.61186118611861%" headers="mcps1.2.6.1.3 "><p id="p18821161052214"><a name="p18821161052214"></a><a name="p18821161052214"></a>Ubuntu or Windows</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.8935893589359%" headers="mcps1.2.6.1.4 "><p id="p1652616548294"><a name="p1652616548294"></a><a name="p1652616548294"></a>swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker</p>
+</td>
+<td class="cellrowborder" valign="top" width="15.69156915691569%" headers="mcps1.2.6.1.5 "><p id="p1433130173010"><a name="p1433130173010"></a><a name="p1433130173010"></a>0.0.3</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+## Preparations<a name="section7337134183512"></a>
+
+Before using the Docker environment, perform the following operations:
+
+1.  Install Docker. For details, see  [Install Docker Engine](https://docs.docker.com/engine/install/).
+2.  Obtain the OpenHarmony source code. For details, see  [Source Code Acquisition](source-code-acquisition.md).
+
+    >![](public_sys-resources/icon-note.gif) **NOTE:** 
+    >You do not need to obtain the source code for the HPM-based Docker environment.
+
+
+## Standalone Docker Environment<a name="section2858536103611"></a>
+
+The Docker image of OpenHarmony is hosted on  [HUAWEI CLOUD SWR](https://console.huaweicloud.com/swr/?region=cn-south-1&locale=en-us#/app/warehouse/warehouseMangeDetail/goldensir/openharmony-docker/openharmony-docker?type=ownImage). Using the Docker image will help simplify environment configurations needed for the building. The following describes the detailed procedure.
+
+### Setting Up the Docker Environment for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)<a name="section319412277287"></a>
+
+**Method 1: Obtaining the Docker image from HUAWEI CLOUD SWR**
+
+1.  Obtain the Docker image.
+
+    ```
+    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
+    ```
+
+2.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
+
+    Run the following command in Ubuntu:
+
+    ```
+    docker run -it -v $(pwd):/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
+    ```
+
+    Run the following command in Windows \(assuming that the source code directory is  **D:\\OpenHarmony**\):
+
+    ```
+    docker run -it -v D:\OpenHarmony:/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
+    ```
+
+
+**Method 2: Using the Dockerfile to Build a Local Docker Image**
+
+1.  Obtain the Dockerfile script for a local Docker image.
+
+    ```
+    git clone https://gitee.com/openharmony/docs.git
+    ```
+
+2.  Go to the directory of the Dockerfile code and run the following command to build the Docker image:
+
+    ```
+    cd docs/docker
+    ./build.sh
+    ```
+
+3.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
+
+    Run the following command in Ubuntu:
+
+    ```
+    docker run -it -v $(pwd):/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
+    ```
+
+    Run the following command in Windows \(assuming that the source code directory is  **D:\\OpenHarmony**\):
+
+    ```
+    docker run -it -v D:\OpenHarmony:/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
+    ```
+
+
+### Building for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)<a name="section631485163615"></a>
+
+The following uses the Hi3516 platform as an example to describe the build procedure.
+
+Set the build path to the current path.
+
+```
+hb set
+ .
+```
+
+**Figure  1**  Setting page<a name="fig18712183616135"></a>  
+
+
+![](figures/en-us_image_0000001101413884.png)
+
+>![](public_sys-resources/icon-note.gif) **NOTE:** 
+>The mapping between the development board and the building GUI:
+>-   Hi3861: wifiiot\_hispark\_pegasus@hisilicon
+>-   Hi3516: ipcamera\_hispark\_taurus@hisilicon
+>-   Hi3518: ipcamera\_hispark\_aries@hisilicon
+
+1.  Select  **ipcamera\_hispark\_taurus@hisilicon**  and press  **Enter**.
+2.  Start building.
+
+    ```
+    hb build -f
+    ```
+
+3.  View the build result.
+
+    The files will be generated in the  **out/hispark\_taurus/ipcamera\_hispark\_taurus**  directory.
+
+
+### Setting Up the Docker Environment for Standard-System Devices \(reference memory ≥ 128 MB\)<a name="section13585262391"></a>
+
+**Method 1: Obtaining the Docker image from HUAWEI CLOUD SWR**
+
+1.  Obtain the Docker image.
+
+    ```
+    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard:0.0.1
+    ```
+
+2.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
+
+    ```
+    docker run -it -v $(pwd):/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard:0.0.1
+    ```
+
+
+**Method 2: Using the Dockerfile to Build a Local Docker Image**
+
+1.  Obtain the Dockerfile script for a local Docker image.
+
+    ```
+    git clone https://gitee.com/openharmony/docs.git
+    ```
+
+2.  Go to the directory of the Dockerfile code and run the following command to build the Docker image:
+
+    ```
+    cd docs/docker/standard
+    ./build.sh
+    ```
+
+3.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
+
+    ```
+    docker run -it -v $(pwd):/home/openharmony openharmony-docker-standard:0.0.1
+    ```
+
+
+### Building for Standard-System Devices \(reference memory ≥ 128 MB\)<a name="section193711513406"></a>
+
+1.  Run the preprocessing script in the root directory of the source code.
+
+    ```
+    ../scripts/prepare.sh
+    ```
+
+2.  Run the following script to start building for standard-system devices \(reference memory ≥ 128 MB\).
+
+    ```
+    ./build.sh --product-name {product_name}
+    ```
+
+    **product\_name**  indicates the platform supported by the current distribution, for example, Hi3516D V300.
+
+    Files generated during building are stored in the  **out/ohos-arm-release/**  directory, and the generated image is stored in the  **out/ohos-arm-release/packages/phone/images/**  directory.
+
+
+>![](public_sys-resources/icon-note.gif) **NOTE:** 
+>You can exit Docker by simply running the  **exit**  command.
+
+## HPM-based Docker Environment<a name="section485713518337"></a>
+
+**docker\_dist**  is a template component in the  [HPM](https://hpm.harmonyos.com/#/en/home)  system. It helps to quickly initialize an HPM project and use the Docker image to quickly build a distribution of OpenHarmony, greatly simplifying environment configurations needed for building. After configuring the Ubuntu and  [hpm-cli](https://device.harmonyos.com/en/docs/develop/bundles/oem_bundle_guide_prepare-0000001050129846)  development environments, perform the following steps to access the Docker environment:
+
+### Setting Up the Docker Environment<a name="section3295842510"></a>
+
+1.  Initialize the installation template by running the following command in any of the working directories:
+
+    ```
+    hpm init -t @ohos/docker_dist
+    ```
+
+2.  Modify the  **publishAs**  field.
+
+    The obtained bundle is of the template type. Open the  **bundle.json**  file in the current directory and change the value of  **publishAs**  from  **template**  to  **distribution**  as needed.
+
+
+### Obtaining and Building Source Code<a name="section69141039143518"></a>
+
+Start building. Docker can be automatically installed only in Ubuntu. If you are using any other operating system, manually install Docker before pulling the image.
+
+-   **Automatically Installing Docker \(Ubuntu\)**
+
+    Running the following command will automatically install Docker, pull the Docker image, and start the pulling and building of the corresponding solution in the container.
+
+    **Method 1:**
+
+    Add a parameter to specify the solution. For example:
+
+    ```
+    hpm run docker solution={product}
+    ```
+
+    **\{product\}**  indicates the solution, for example,  **@ohos/hispark\_taurus**,  **@ohos/hispark\_aries**, and  **@ohos/hispark\_pegasus**.
+
+    **Method 2:**
+
+    Set an environment variable to specify the solution, and then run the build command.
+
+    1.  Select the desired solution.
+
+        ```
+        export solution={product}
+        ```
+
+        **\{product\}**  indicates the solution, for example,  **@ohos/hispark\_taurus**,  **@ohos/hispark\_aries**, and  **@ohos/hispark\_pegasus**.
+
+    2.  Obtain and build the source code.
+
+        ```
+        hpm run docker
+        ```
+
+
+    This example uses the  **@ohos/hispark\_taurus**  solution for illustration. If the execution is successful, the output is as follows:
+
+    ```
+    ...
+    ohos ipcamera_hispark_taurus build success!
+    @ohos/hispark_taurus: distribution building completed.
+    ```
+
+
+-   **Manually Installing Docker \(Non-Ubuntu\)**
+
+    Perform the following operations to install Docker:
+
+    ```
+    # Pull the image.
+    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.3# Compile the Docker image in the Linux environment.
+    hpm run distWithDocker solution={product}
+    # When using Windows, make sure to configure the Git Bash.
+    hpm config set shellPath "Git Bash path"
+    hpm run distWithDocker solution={product}
+    ```
+
+

en/device-dev/get-code/ide.md

+# IDE<a name="EN-US_TOPIC_0000001128361880"></a>
+
+-   [Acquiring the Device Development Tool \(HUAWEI DevEco Device Tool\)](#section2452141120244)
+-   [Acquiring the Application Development Tool \(HUAWEI DevEco Studio\)](#section0904101019258)
+
+## Acquiring the Device Development Tool \(HUAWEI DevEco Device Tool\)<a name="section2452141120244"></a>
+
+HUAWEI DevEco Device Tool is a one-stop integrated development environment \(IDE\) provided to develop applications for OpenHarmony devices. It allows on-demand customization of OpenHarmony components, code editing, building, burning, and debugging, and supports C and C++ languages. This tool is installed in Visual Studio Code as a plug-in. For details, see  [HUAWEI DevEco Device Tool](https://device.harmonyos.com/en/ide)  and  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905).
+
+The roadmap of Huawei DevEco Device Tool for supporting OpenHarmony device development is shown in the figure below.
+
+![](figures/3.png)
+
+## Acquiring the Application Development Tool \(HUAWEI DevEco Studio\)<a name="section0904101019258"></a>
+
+HUAWEI DevEco Studio \(DevEco Studio for short\) is a one-stop IDE oriented to Huawei devices in all scenarios. It provides E2E OpenHarmony application development services, ranging from project template creation to development, building, debugging, and release. With DevEco Studio, you will be able to efficiently develop OpenHarmony applications with distributed capabilities while speeding up innovation. For details, see  [HUAWEI DevEco Studio](https://developer.harmonyos.com/en/develop/deveco-studio)  and  [HUAWEI DevEco Studio User Guide](https://developer.harmonyos.com/en/docs/documentation/doc-guides/tools_overview-0000001053582387).
+

en/device-dev/get-code/source-code-acquisition.md

@@ -62,7 +62,7 @@ This document describes how to acquire OpenHarmony source code and provides its
 4.  Run the following commands to install the  **repo**  tool:
 
     ```
-    curl https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 > /usr/local/bin/repo  # If you do not have the access permission to this directory, download the tool to any other accessible directory and configure the directory to the environment variable.
+    curl -s https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 > /usr/local/bin/repo  # If you do not have the access permission to this directory, download the tool to any other accessible directory and configure the directory to the environment variable.
     chmod a+x /usr/local/bin/repo
     pip3 install -i https://repo.huaweicloud.com/repository/pypi/simple requests
     ```

en/device-dev/get-code/tool-acquisition.md

-# Tool Acquisition<a name="EN-US_TOPIC_0000001055701144"></a>
+# Tool Acquisition<a name="EN-US_TOPIC_0000001111199422"></a>
 
--   [How to Obtain the Docker Environment](#section107932281315)
--   [HPM-based Docker](#section485713518337)
-    -   [Setting Up the Docker Environment](#section18957202218355)
-    -   [Building](#section69141039143518)
+-   **[Docker Environment](docker-environment.md)**  
 
--   [Standalone Docker Environment](#section2858536103611)
-    -   [Setting Up the Docker Environment for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)](#section319412277287)
-    -   [Building for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)](#section631485163615)
-    -   [Setting Up the Docker Environment for Standard-System Devices \(reference memory ≥ 128 MB\)](#section13585262391)
-    -   [Building for Standard-System Devices \(reference memory ≥ 128 MB\)](#section193711513406)
+-   **[IDE](ide.md)**  
 
--   [Acquiring the Device Development Tool \(HUAWEI DevEco Device Tool\)](#section2452141120244)
--   [Acquiring the Application Development Tool \(HUAWEI DevEco Studio\)](#section0904101019258)
-
-## How to Obtain the Docker Environment<a name="section107932281315"></a>
-
-OpenHarmony provides the following two types of Docker environments for you to quickly get the development environment ready:
-
--   HPM-based Docker environment: applicable when using the HarmonyOS Package Manager \(HPM\) to build a distribution.
--   Standalone Docker environment: applicable when using Ubuntu or Windows to build a distribution.
-
-    The following table lists container-based options needed for building in the standalone Docker environment.
-
-    **Table  1**  Docker image
-
-    <a name="table2790164495315"></a>
-    <table><thead align="left"><tr id="row3790644155317"><th class="cellrowborder" valign="top" width="35.5064493550645%" id="mcps1.2.4.1.1"><p id="p8789114445316"><a name="p8789114445316"></a><a name="p8789114445316"></a>Docker Image Repository</p>
-    </th>
-    <th class="cellrowborder" valign="top" width="10.258974102589741%" id="mcps1.2.4.1.2"><p id="p17896448533"><a name="p17896448533"></a><a name="p17896448533"></a>Tag</p>
-    </th>
-    <th class="cellrowborder" valign="top" width="54.23457654234577%" id="mcps1.2.4.1.3"><p id="p1278917444539"><a name="p1278917444539"></a><a name="p1278917444539"></a>Description</p>
-    </th>
-    </tr>
-    </thead>
-    <tbody><tr id="row167901244115315"><td class="cellrowborder" valign="top" width="35.5064493550645%" headers="mcps1.2.4.1.1 "><p id="p87901744185316"><a name="p87901744185316"></a><a name="p87901744185316"></a>swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker</p>
-    </td>
-    <td class="cellrowborder" valign="top" width="10.258974102589741%" headers="mcps1.2.4.1.2 "><p id="p15790184410536"><a name="p15790184410536"></a><a name="p15790184410536"></a>0.0.5</p>
-    </td>
-    <td class="cellrowborder" valign="top" width="54.23457654234577%" headers="mcps1.2.4.1.3 "><p id="p15790124416531"><a name="p15790124416531"></a><a name="p15790124416531"></a>The <span id="text929334781813"><a name="text929334781813"></a><a name="text929334781813"></a>OpenHarmony</span> build environment has been pre-installed. This repository applies to <span id="text167042559153"><a name="text167042559153"></a><a name="text167042559153"></a>Mini-System Devices (reference memory ≥ 128 KB)</span> and <span id="text358943111611"><a name="text358943111611"></a><a name="text358943111611"></a>Small-System Devices (reference memory ≥ 1 MB)</span>.</p>
-    </td>
-    </tr>
-    <tr id="row757355774214"><td class="cellrowborder" valign="top" width="35.5064493550645%" headers="mcps1.2.4.1.1 "><p id="p156285811425"><a name="p156285811425"></a><a name="p156285811425"></a>swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard</p>
-    </td>
-    <td class="cellrowborder" valign="top" width="10.258974102589741%" headers="mcps1.2.4.1.2 "><p id="p15562155818429"><a name="p15562155818429"></a><a name="p15562155818429"></a>0.0.1</p>
-    </td>
-    <td class="cellrowborder" valign="top" width="54.23457654234577%" headers="mcps1.2.4.1.3 "><p id="p17562758184213"><a name="p17562758184213"></a><a name="p17562758184213"></a>The <span id="text956295819420"><a name="text956295819420"></a><a name="text956295819420"></a>OpenHarmony</span> build environment has been pre-installed. This repository applies to <span id="text17573710444"><a name="text17573710444"></a><a name="text17573710444"></a>Standard-System Devices (reference memory ≥ 128 MB)</span>.</p>
-    </td>
-    </tr>
-    </tbody>
-    </table>
-
-    >![](public_sys-resources/icon-note.gif) **NOTE:** 
-    >For details about how to install Docker, see  [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
-
-
-## HPM-based Docker<a name="section485713518337"></a>
-
-**docker\_dist**  is a template component in the  [HPM](https://hpm.harmonyos.com/#/en/home)  system. It helps to quickly initialize an HPM project and use the Docker image to quickly build a distribution of OpenHarmony, greatly simplifying environment configurations needed for building. After configuring the Ubuntu and  [hpm-cli](https://device.harmonyos.com/en/docs/develop/bundles/oem_bundle_guide_prepare-0000001050129846)  development environments, perform the following steps to access the Docker environment:
-
-### Setting Up the Docker Environment<a name="section18957202218355"></a>
-
-1.  Initialize the installation template by running the following command in any of the working directories:
-
-    ```
-    hpm init -t @ohos/docker_dist
-    ```
-
-2.  Modify the  **publishAs**  field.
-
-    The obtained bundle is of the template type. Open the  **bundle.json**  file in the current directory and change the value of  **publishAs**  from  **template**  to  **distribution**  as needed.
-
-
-### Building<a name="section69141039143518"></a>
-
-Start building. Docker can be automatically installed only on Ubuntu. If you are using any other operating system, manually install Docker before pulling the image.
-
--   **Automatically Installing Docker \(Ubuntu\)**
-
-    Running the following command will automatically install Docker, pull the Docker image, and start the pulling and building of the corresponding solution in the container.
-
-    Method 1:
-
-    Add a parameter to specify the solution. For example:
-
-    ```
-    hpm run docker solution={product}
-    ```
-
-    **\{product\}**  indicates the solution, for example,  **@ohos/hispark\_taurus**,  **@ohos/hispark\_aries**, and  **@ohos/hispark\_pegasus**.
-
-    Method 2:
-
-    Set an environment variable to specify the solution, and then run the build command.
-
-    1. Select the desired solution.
-
-    ```
-    export solution={product}
-    ```
-
-    **\{product\}**  indicates the solution, for example,  **@ohos/hispark\_taurus**,  **@ohos/hispark\_aries**, and  **@ohos/hispark\_pegasus**.
-
-    2. Start building.
-
-    ```
-    hpm run docker
-    ```
-
-    This example uses the  **@ohos/hispark\_taurus**  solution for illustration. If the execution is successful, the output is as follows:
-
-    ```
-    ...
-    ohos ipcamera_hispark_taurus build success!
-    @ohos/hispark_taurus: distribution building completed.
-    ```
-
-
--   **Manually Installing Docker \(Non-Ubuntu\)**
-
-    Perform the following operations to install Docker:
-
-    ```
-    # Pull the image.
-    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.3# Compile the Docker image in the Linux environment.
-    hpm run distWithDocker solution={product}
-    # When using Windows, make sure to configure the Git Bash.
-    hpm config set shellPath "Git Bash path"
-    hpm run distWithDocker solution={product}
-    ```
-
-
-## Standalone Docker Environment<a name="section2858536103611"></a>
-
-The Docker image of OpenHarmony is hosted on  [HUAWEI CLOUD SWR](https://console.huaweicloud.com/swr/?region=cn-south-1&locale=en-us#/app/warehouse/warehouseMangeDetail/goldensir/openharmony-docker/openharmony-docker?type=ownImage). Using the Docker image will help simplify environment configurations needed for the building. After configuring the development environments, perform the procedures below to access the Docker environment. Both Ubuntu and Windows are supported. The following procedures use Ubuntu as an example.
-
-### Setting Up the Docker Environment for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)<a name="section319412277287"></a>
-
-**Method 1: Obtaining the Docker image from HUAWEI CLOUD SWR**
-
-1.  Obtain the Docker image.
-
-    ```
-    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
-    ```
-
-2.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
-
-    ```
-    docker run -it -v $(pwd):/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker:0.0.5
-    ```
-
-
-**Method 2: Using the Dockerfile to Build a Local Docker Image**
-
-1.  Obtain the Dockerfile script for a local Docker image.
-
-    ```
-    git clone https://gitee.com/openharmony/docs.git
-    ```
-
-2.  Go to the directory of the Dockerfile code and run the following command to build the Docker image:
-
-    ```
-    cd docs/docker
-    ./build.sh
-    ```
-
-3.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
-
-    ```
-    docker run -it -v $(pwd):/home/openharmony openharmony-docker:0.0.5
-    ```
-
-
-### Building for Mini-System Devices \(reference memory ≥ 128 KB\) and Small-System Devices \(reference memory ≥ 1 MB\)<a name="section631485163615"></a>
-
-The following uses the Hi3516 platform as an example to describe the build procedure. Run the following build scripts to start building:
-
-Set the build path to the current path.
-
-```
-hb set
- .
-```
-
-**Figure  1**  Setting page<a name="fig18712183616135"></a>  
-
-
-![](figures/en-us_image_0000001101413884.png)
-
->![](public_sys-resources/icon-note.gif) **NOTE:** 
->The mapping between the development board and the building GUI:
->-   Hi3861: wifiiot\_hispark\_pegasus@hisilicon
->-   Hi3516: ipcamera\_hispark\_taurus@hisilicon
->-   Hi3518: ipcamera\_hispark\_aries@hisilicon
-
-1.  Select  **ipcamera\_hispark\_taurus@hisilicon**  and press  **Enter**.
-2.  Start building.
-
-    ```
-    hb build -f
-    ```
-
-3.  View the build result.
-
-    The files will be generated in the  **out/hispark\_taurus/ipcamera\_hispark\_taurus**  directory.
-
-
-### Setting Up the Docker Environment for Standard-System Devices \(reference memory ≥ 128 MB\)<a name="section13585262391"></a>
-
-**Method 1: Obtaining the Docker image from HUAWEI CLOUD SWR**
-
-1.  Obtain the Docker image.
-
-    ```
-    docker pull swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard:0.0.1
-    ```
-
-2.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
-
-    ```
-    docker run -it -v $(pwd):/home/openharmony swr.cn-south-1.myhuaweicloud.com/openharmony-docker/openharmony-docker-standard:0.0.1
-    ```
-
-
-**Method 2: Using the Dockerfile to Build a Local Docker Image**
-
-1.  Obtain the Dockerfile script for a local Docker image.
-
-    ```
-    git clone https://gitee.com/openharmony/docs.git
-    ```
-
-2.  Go to the directory of the Dockerfile code and run the following command to build the Docker image:
-
-    ```
-    cd docs/docker/standard
-    ./build.sh
-    ```
-
-3.  Go to the root directory of OpenHarmony code and run the following command to access the Docker build environment:
-
-    ```
-    docker run -it -v $(pwd):/home/openharmony openharmony-docker-standard:0.0.1
-    ```
-
-
-### Building for Standard-System Devices \(reference memory ≥ 128 MB\)<a name="section193711513406"></a>
-
-1.  Run the preprocessing script in the root directory of the source code.
-
-    ```
-    ../scripts/prepare.sh
-    ```
-
-2.  Run the following script to start building for Standard-System Devices \(reference memory ≥ 128 MB\).
-
-    ```
-    ./build.sh --product-name {product_name}
-    ```
-
-    **product\_name**  indicates the platform supported by the current distribution, for example, Hi3516D V300.
-
-    Files generated during compilation are stored in the  **out/ohos-arm-release/**  directory, and the generated image is stored in the  **out/ohos-arm-release/packages/phone/images/**  directory.
-
-
->![](public_sys-resources/icon-note.gif) **NOTE:** 
->You can exit Docker by simply running the  **exit**  command.
-
-## Acquiring the Device Development Tool \(HUAWEI DevEco Device Tool\)<a name="section2452141120244"></a>
-
-HUAWEI DevEco Device Tool is a one-stop integrated development environment \(IDE\) provided to develop applications for OpenHarmony-based smart devices. It allows on-demand customization of OpenHarmony components, code editing, compilation, burning, and debugging, and supports C and C++ languages. This tool is installed in Visual Studio Code as a plug-in. For details, see  [Tool Acquisition](https://device.harmonyos.com/en/ide)  and  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905).
-
-The roadmap of Huawei DevEco Device Tool for supporting OpenHarmony device development is shown in the figure below.
-
-![](figures/3.png)
-
-## Acquiring the Application Development Tool \(HUAWEI DevEco Studio\)<a name="section0904101019258"></a>
-
-HUAWEI DevEco Studio \(DevEco Studio for short\) is a one-stop IDE oriented to Huawei devices in all scenarios. It provides E2E OpenHarmony application development services, ranging from project template creation to development, compilation, debugging, and release. With DevEco Studio, you will be able to efficiently develop OpenHarmony applications with distributed capabilities while speeding up innovation. For details, see  [Tool Acquisition](https://developer.harmonyos.com/en/develop/deveco-studio)  and  [HUAWEI DevEco Studio User Guide](https://developer.harmonyos.com/en/docs/documentation/doc-guides/tools_overview-0000001053582387).
 

en/device-dev/guide/running-on-the-device-9.md

 # Running on the Device<a name="EN-US_TOPIC_0000001115258034"></a>
 
-Before you install the app and run it on the development board, install the DevEco Device Tool by following operations provided in  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905). Burn OpenHarmony into the development board, and run it on the board. For details about how to build, burn, and run an image, see  [Getting Started with Hi3516](../quick-start/how-to-develop-12.md). After the image is running normally and the system is started properly, perform the following steps to install or uninstall the app:
+Before you install the app and run it on the development board, install the DevEco Device Tool by following operations provided in  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905). Burn OpenHarmony into the development board, and run it on the board. For details about how to build, burn, and run an image, see  [Getting Started with Hi3516](../quick-start/standard-system.md). After the image is running normally and the system is started properly, perform the following steps to install or uninstall the app:
 
 1.  Obtain the HDC client from the following path:
 

en/device-dev/overview.md

+# Overview<a name="EN-US_TOPIC_0000001152533331"></a>
+
+-   [System Types](#section767218232110)
+-   [Document Outline](#section19810171681218)
+
+This topic provides a panorama of all documents for you to obtain helpful information quickly. These documents are classified based on your learning progress and development scenarios of OpenHarmony.
+
+## System Types<a name="section767218232110"></a>
+
+It is good practice to understand the system types for you to find useful documents that can guide your development.
+
+OpenHarmony is an open-source distributed operating system for all scenarios. It uses a component-based design to tailor its features to better suit devices with 128 KiB to GiB-level of RAM. You can integrate a flexible combination of system components based on the hardware capabilities of the device.
+
+To make the integration simple and easy on different hardware, OpenHarmony defines three basic system types. You only need to select a suitable system type and configure the mandatory component set, thereby developing a system for your device at the minimum workload. The definitions of the basic system types are provided as follows for your reference:
+
+-   Mini system
+
+    A mini system runs on the devices whose memory is greater than or equal to 128 KiB and that are equipped with MCU processors such as Arm Cortex-M and 32-bit RISC-V. This system provides multiple lightweight network protocols and graphics frameworks, and a wide range of read/write components for the IoT bus. Typical products include connection modules, sensors, and wearables for smart home.
+
+-   Small system
+
+    A small system runs on the devices whose memory is greater than or equal to 1 MiB and that are equipped with application processors such as Arm Cortex-A. This system provides higher security capabilities, standard graphics frameworks, and video encoding and decoding capabilities. Typical products include smart home IP cameras, electronic cat eyes, and routers, and event data recorders \(EDRs\) for smart travel.
+
+-   Standard system
+
+    A standard system runs on the devices whose memory is greater than or equal to 128 MiB and that are equipped with application processors such as Arm Cortex-A. This system provides a complete application framework supporting the enhanced interaction, 3D GPU, hardware composer, diverse components, and rich animations. This system applies to high-end refrigerator displays.
+
+
+In addition, OpenHarmony provides a series of optional system components that can be configured as required to support feature extension and customization. These system components are combined to form a series of system capabilities that, for better understanding, are described as features or functions for you to choose.
+
+## Document Outline<a name="section19810171681218"></a>
+
+-   [Mini and Small System Development Guidelines](#table3762949121211)
+-   [Standard System Development Guidelines](#table17667535516)
+
+**Table  1**  Mini and small system development guidelines \(reference memory < 128 MB\)
+
+<a name="table3762949121211"></a>
+<table><thead align="left"><tr id="row18762649161218"><th class="cellrowborder" valign="top" width="28.472847284728473%" id="mcps1.2.4.1.1"><p id="p1750131161313"><a name="p1750131161313"></a><a name="p1750131161313"></a>Topic</p>
+</th>
+<th class="cellrowborder" valign="top" width="35.61356135613561%" id="mcps1.2.4.1.2"><p id="p8501411141319"><a name="p8501411141319"></a><a name="p8501411141319"></a>Development Scenario</p>
+</th>
+<th class="cellrowborder" valign="top" width="35.91359135913591%" id="mcps1.2.4.1.3"><p id="p050181111314"><a name="p050181111314"></a><a name="p050181111314"></a>Documents</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="row317979135310"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p119871717125320"><a name="p119871717125320"></a><a name="p119871717125320"></a>About <span id="text64714522207"><a name="text64714522207"></a><a name="text64714522207"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p14987151715312"><a name="p14987151715312"></a><a name="p14987151715312"></a>Getting familiar with <span id="text9808161615252"><a name="text9808161615252"></a><a name="text9808161615252"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul59871171533"></a><a name="ul59871171533"></a><ul id="ul59871171533"><li><a href="https://gitee.com/openharmony" target="_blank" rel="noopener noreferrer">About OpenHarmony</a></li><li><a href="glossary/glossary.md">Glossary</a></li></ul>
+</td>
+</tr>
+<tr id="row69521557115217"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p69873174536"><a name="p69873174536"></a><a name="p69873174536"></a>Development resources</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p39871917185313"><a name="p39871917185313"></a><a name="p39871917185313"></a>Preparing for your development</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul59871117135314"></a><a name="ul59871117135314"></a><ul id="ul59871117135314"><li><a href="get-code/source-code-acquisition.md">Source Code Acquisition</a></li><li><a href="get-code/tool-acquisition.md">Acquiring Tools</a></li></ul>
+</td>
+</tr>
+<tr id="row11602937131510"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p457713717150"><a name="p457713717150"></a><a name="p457713717150"></a>Quick start</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p55771237111517"><a name="p55771237111517"></a><a name="p55771237111517"></a>Getting started with setup, build, burning, debugging, and running of <span id="text203751321355"><a name="text203751321355"></a><a name="text203751321355"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><p id="p10832159115410"><a name="p10832159115410"></a><a name="p10832159115410"></a><a href="quick-start/mini-and-small-systems.md">Getting Started for Mini and Small Systems</a></p>
+</td>
+</tr>
+<tr id="row11602103701514"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p16577163716159"><a name="p16577163716159"></a><a name="p16577163716159"></a>Basic capabilities</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p857711379158"><a name="p857711379158"></a><a name="p857711379158"></a>Using basic capabilities of <span id="text8928941123820"><a name="text8928941123820"></a><a name="text8928941123820"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul1577103716159"></a><a name="ul1577103716159"></a><ul id="ul1577103716159"><li><a href="kernel/Readme-EN.md">Kernel</a></li><li><a href="driver/Readme-EN.md">HDF</a></li><li><a href="subsystems/Readme-EN.md">Subsystems</a></li><li><a href="security/security-guidelines.md">Security Guidelines</a></li><li><a href="security/privacy-protection.md">Privacy Protection</a></li></ul>
+</td>
+</tr>
+<tr id="row10602193719152"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p857873713152"><a name="p857873713152"></a><a name="p857873713152"></a>Advanced development</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p155782037201518"><a name="p155782037201518"></a><a name="p155782037201518"></a>Developing smart devices based on system capabilities</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul257883731519"></a><a name="ul257883731519"></a><ul id="ul257883731519"><li><a href="guide/led-peripheral-control.md">LED Peripheral Control</a></li><li><a href="guide/screen-and-camera-control.md">Screen and Camera Control</a></li><li><a href="guide/visual-application-development.md">Development Example for Visual Apps (AirQuality)</a></li></ul>
+</td>
+</tr>
+<tr id="row360273716155"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p12579163711513"><a name="p12579163711513"></a><a name="p12579163711513"></a>Porting and adaptation</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><a name="ul12579137121512"></a><a name="ul12579137121512"></a><ul id="ul12579137121512"><li>Porting and adapting the <span id="text1415622205014"><a name="text1415622205014"></a><a name="text1415622205014"></a>OpenHarmony</span> to an SoC</li><li>Porting and adapting the <span id="text82061719165013"><a name="text82061719165013"></a><a name="text82061719165013"></a>OpenHarmony</span> to a third-party library</li></ul>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul157903731520"></a><a name="ul157903731520"></a><ul id="ul157903731520"><li><a href="porting/third-party-soc-porting-guide.md" target="_blank" rel="noopener noreferrer">Third-Party SoC Porting Guide</a></li><li><a href="porting/third-party-library-porting-guide.md">Third-Party Library Porting Guide</a></li></ul>
+</td>
+</tr>
+<tr id="row9601737181517"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p25791037131519"><a name="p25791037131519"></a><a name="p25791037131519"></a>Contributing components</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p45798376158"><a name="p45798376158"></a><a name="p45798376158"></a>Contributing components to <span id="text207913212498"><a name="text207913212498"></a><a name="text207913212498"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul957919379156"></a><a name="ul957919379156"></a><ul id="ul957919379156"><li><a href="bundles/development-specifications.md">Component Development Specifications</a></li><li><a href="bundles/development-guidelines.md">Component Development Guidelines</a></li><li><a href="bundles/hpm-user-guide.md">HPM User Guide</a></li></ul>
+</td>
+</tr>
+<tr id="row260193701512"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p95794372155"><a name="p95794372155"></a><a name="p95794372155"></a>Reference</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p458073721519"><a name="p458073721519"></a><a name="p458073721519"></a>Referring to development specifications</p>
+</td>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul175808372155"></a><a name="ul175808372155"></a><ul id="ul175808372155"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li></ul>
+</td>
+</tr>
+</tbody>
+</table>
+
+**Table  2**  Standard system development guidelines \(reference memory ≥ 128 MB\)
+
+<a name="table17667535516"></a>
+<table><thead align="left"><tr id="row206665375119"><th class="cellrowborder" valign="top" width="27.872787278727873%" id="mcps1.2.4.1.1"><p id="p4661053145115"><a name="p4661053145115"></a><a name="p4661053145115"></a>Topic</p>
+</th>
+<th class="cellrowborder" valign="top" width="36.053605360536054%" id="mcps1.2.4.1.2"><p id="p126685315112"><a name="p126685315112"></a><a name="p126685315112"></a>Development Scenario</p>
+</th>
+<th class="cellrowborder" valign="top" width="36.07360736073608%" id="mcps1.2.4.1.3"><p id="p26695395112"><a name="p26695395112"></a><a name="p26695395112"></a>Documents</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="row9662532514"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p066105317513"><a name="p066105317513"></a><a name="p066105317513"></a>About <span id="text194583786"><a name="text194583786"></a><a name="text194583786"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p16673531512"><a name="p16673531512"></a><a name="p16673531512"></a>Getting familiar with <span id="text1829856151"><a name="text1829856151"></a><a name="text1829856151"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul10673531517"></a><a name="ul10673531517"></a><ul id="ul10673531517"><li><a href="https://gitee.com/openharmony" target="_blank" rel="noopener noreferrer">About OpenHarmony</a></li><li><a href="glossary/glossary.md">Glossary</a></li></ul>
+</td>
+</tr>
+<tr id="row267155313513"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p13671853205113"><a name="p13671853205113"></a><a name="p13671853205113"></a>Development resources</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p0671053115115"><a name="p0671053115115"></a><a name="p0671053115115"></a>Preparing for your development</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul1867185314519"></a><a name="ul1867185314519"></a><ul id="ul1867185314519"><li><a href="get-code/source-code-acquisition.md">Source Code Acquisition</a></li><li><a href="get-code/tool-acquisition.md">Acquiring Tools</a></li></ul>
+</td>
+</tr>
+<tr id="row13671253165120"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p166795345112"><a name="p166795345112"></a><a name="p166795345112"></a>Quick start</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p1167135345112"><a name="p1167135345112"></a><a name="p1167135345112"></a>Getting started with setup, build, burning, debugging, and running of <span id="text687119202170"><a name="text687119202170"></a><a name="text687119202170"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><p id="p1114162510521"><a name="p1114162510521"></a><a name="p1114162510521"></a><a href="quick-start/standard-system.md">Getting Started for Standard System</a></p>
+</td>
+</tr>
+<tr id="row1168155365119"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p96810536514"><a name="p96810536514"></a><a name="p96810536514"></a>Basic capabilities</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p136812535511"><a name="p136812535511"></a><a name="p136812535511"></a>Using basic capabilities of <span id="text837699804"><a name="text837699804"></a><a name="text837699804"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul116805318517"></a><a name="ul116805318517"></a><ul id="ul116805318517"><li><a href="kernel/Readme-EN.md">Kernel</a></li><li><a href="driver/Readme-EN.md">HDF</a></li><li><a href="subsystems/Readme-EN.md">Subsystems</a></li><li><a href="security/security-guidelines.md">Security Guidelines</a></li><li><a href="security/privacy-protection.md">Privacy Protection</a></li></ul>
+</td>
+</tr>
+<tr id="row1368195345111"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p16681853145115"><a name="p16681853145115"></a><a name="p16681853145115"></a>Advanced development</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p1568753135116"><a name="p1568753135116"></a><a name="p1568753135116"></a>Developing smart devices based on system capabilities</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul136895314518"></a><a name="ul136895314518"></a><ul id="ul136895314518"><li><a href="guide/development-example-for-clock-apps.md">Development Example for Clock Apps</a></li><li><a href="guide/development-example-for-platform-drivers.md">Development Example for Platform Drivers</a></li><li><a href="guide/development-example-for-peripheral-drivers.md ">Development Example for Peripheral Drivers</a></li></ul>
+</td>
+</tr>
+<tr id="row66915375119"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p4696535512"><a name="p4696535512"></a><a name="p4696535512"></a>Porting and adaptation</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p185185615284"><a name="p185185615284"></a><a name="p185185615284"></a>Porting and adapting the <span id="text1434016533511"><a name="text1434016533511"></a><a name="text1434016533511"></a>OpenHarmony</span> to a third-party library</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><p id="p10262183114555"><a name="p10262183114555"></a><a name="p10262183114555"></a><a href="porting/third-party-library-porting-guide.md">Third-Party Library Porting Guide</a></p>
+</td>
+</tr>
+<tr id="row869853125119"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p3691530511"><a name="p3691530511"></a><a name="p3691530511"></a>Contributing components</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p1469115335113"><a name="p1469115335113"></a><a name="p1469115335113"></a>Contributing components to <span id="text1045656075"><a name="text1045656075"></a><a name="text1045656075"></a>OpenHarmony</span></p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul87045395116"></a><a name="ul87045395116"></a><ul id="ul87045395116"><li><a href="bundles/development-specifications.md">Component Development Specifications</a></li><li><a href="bundles/development-guidelines.md">Component Development Guidelines</a></li><li><a href="bundles/hpm-user-guide.md">HPM User Guide</a></li></ul>
+</td>
+</tr>
+<tr id="row1170153125110"><td class="cellrowborder" valign="top" width="27.872787278727873%" headers="mcps1.2.4.1.1 "><p id="p16701253195118"><a name="p16701253195118"></a><a name="p16701253195118"></a>Reference</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p670135335116"><a name="p670135335116"></a><a name="p670135335116"></a>Referring to development specifications</p>
+</td>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul177016538519"></a><a name="ul177016538519"></a><ul id="ul177016538519"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li></ul>
+</td>
+</tr>
+</tbody>
+</table>
+

en/device-dev/quick-start/Readme-EN.md

@@ -33,12 +33,10 @@
             -   [FAQs](faqs-6.md)
 
 -   [Standard System](standard-system.md)
-    -   [Overview](overview-7.md)
-    -   [Environment Setup](environment-setup-8.md)
-        -   [Overview](overview-9.md)
-        -   [Windows Development Environment](windows-development-environment-10.md)
-        -   [Preparing the Ubuntu Build Environment](preparing-the-ubuntu-build-environment.md)
-        -   [FAQs](faqs-11.md)
-
-    -   [How to Develop](how-to-develop-12.md)
+    -   [Introduction](introduction.md)
+    -   [Setting Up Windows Development Environment](setting-up-windows-development-environment.md)
+    -   [Setting Up Ubuntu Development Environment in Docker Mode and Building Source Code](setting-up-ubuntu-development-environment-in-docker-mode-and-building-source-code.md)
+    -   [Setting Up Ubuntu Development Environment with Installation Package and Building Source Code](setting-up-ubuntu-development-environment-with-installation-package-and-building-source-code.md)
+    -   [Burning Images](burning-images.md)
+    -   [FAQs](faqs-7.md)
 

en/device-dev/quick-start/developing-a-driver.md

-# Developing a Driver<a name="EN-US_TOPIC_0000001151968527"></a>
+# Developing a Driver<a name="EN-US_TOPIC_0000001174350613"></a>
 
 -   [Introduction to Driver](#s8efc1952ebfe4d1ea717182e108c29bb)
 -   [Compiling and Burning](#section660016185110)
@@ -423,7 +423,7 @@ The following operations take a HDF-based UART driver as an example to show how
 
 ## Compiling and Burning<a name="section660016185110"></a>
 
-Compile and burn images by referring to  [Building](../quick-start/running-a-hello-ohos-program.md)and  [Burning](../quick-start/running-a-hello-ohos-program.md).
+Compile and burn images by referring to  [Building](../guide/development-example-for-platform-drivers.md)and  [Burning](../guide/development-example-for-platform-drivers.md).
 
 ## Running an Image<a name="section333215226219"></a>
 
@@ -439,14 +439,14 @@ Compile and burn images by referring to  [Building](../quick-start/running-a-hel
 
     1.  Click  **Monitor**  to enable the serial port.
     2.  Press  **Enter**  repeatedly until  **hisilicon**  displays.
-    3.  Go to step  [2](running-a-hello-ohos-program.md#l5b42e79a33ea4d35982b78a22913b0b1)  if the board is started for the first time or the startup parameters need to be modified; go to step  [3](running-a-hello-ohos-program.md#ld26f18828aa44c36bfa36be150e60e49)  otherwise.
+    3.  Go to  [2](running-a-hello-ohos-program.md#l5b42e79a33ea4d35982b78a22913b0b1)  if the board is started for the first time or the startup parameters need to be modified; go to  [3](running-a-hello-ohos-program.md#ld26f18828aa44c36bfa36be150e60e49)  otherwise.
 
-2.  \(Mandatory when the board is started for the first time\) Modify the bootcmd and bootargs parameters of U-boot. You need to perform this step only once if the parameters need not to be modified during the operation. The board automatically starts after it is reset.
+2.  \(Mandatory when the board is started for the first time\) Modify the  **bootcmd**  and  **bootargs**  parameters of U-Boot. You need to perform this step only once if the parameters need not to be modified during the operation. The board automatically starts after it is reset.
 
     >![](public_sys-resources/icon-notice.gif) **NOTICE:** 
-    >The default waiting time in the U-boot is 2s. You can press  **Enter**  to interrupt the waiting and run the  **reset**  command to restart the system after "hisilicon" is displayed.
+    >The default waiting time in the U-Boot is 2s. You can press  **Enter**  to interrupt the waiting and run the  **reset**  command to restart the system after "hisilicon" is displayed.
 
-    **Table  1**  Parameters of the U-boot
+    **Table  1**  Parameters of the U-Boot
 
     <a name="en-us_topic_0000001151888681_table1323441103813"></a>
     <table><thead align="left"><tr id="en-us_topic_0000001151888681_row1423410183818"><th class="cellrowborder" valign="top" width="50%" id="mcps1.2.3.1.1"><p id="en-us_topic_0000001151888681_p623461163818"><a name="en-us_topic_0000001151888681_p623461163818"></a><a name="en-us_topic_0000001151888681_p623461163818"></a>Command</p>
@@ -457,30 +457,30 @@ Compile and burn images by referring to  [Building](../quick-start/running-a-hel
     </thead>
     <tbody><tr id="en-us_topic_0000001151888681_row1623471113817"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001151888681_p102341719385"><a name="en-us_topic_0000001151888681_p102341719385"></a><a name="en-us_topic_0000001151888681_p102341719385"></a>setenv bootcmd "mmc read 0x0 0x80000000 0x800 0x4800; go 0x80000000";</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p92347120389"><a name="en-us_topic_0000001151888681_p92347120389"></a><a name="en-us_topic_0000001151888681_p92347120389"></a>Run this command to read content that has a size of 0x4800 (9 MB) and a start address of 0x800 (1 MB) to the memory address 0x80000000. The file size must be the same as that of the <strong id="en-us_topic_0000001151888681_b9140538191313"><a name="en-us_topic_0000001151888681_b9140538191313"></a><a name="en-us_topic_0000001151888681_b9140538191313"></a>OHOS_Image.bin</strong> file in the IDE.</p>
+    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p92347120389"><a name="en-us_topic_0000001151888681_p92347120389"></a><a name="en-us_topic_0000001151888681_p92347120389"></a>Run this command to read content that has a size of 0x4800 (9 MB) and a start address of 0x800 (1 MB) to the memory address 0x80000000. The file size must be the same as that of the <strong id="b881982511127"><a name="b881982511127"></a><a name="b881982511127"></a>OHOS_Image.bin</strong> file in the IDE.</p>
     </td>
     </tr>
     <tr id="en-us_topic_0000001151888681_row12234912381"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001151888681_p172306219392"><a name="en-us_topic_0000001151888681_p172306219392"></a><a name="en-us_topic_0000001151888681_p172306219392"></a>setenv bootargs "console=ttyAMA0,115200n8 root=emmc fstype=vfat rootaddr=10M rootsize=20M rw";</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p13489329396"><a name="en-us_topic_0000001151888681_p13489329396"></a><a name="en-us_topic_0000001151888681_p13489329396"></a>Run this command to set the output mode to serial port output, baud rate to <strong id="en-us_topic_0000001151888681_b1378372812210"><a name="en-us_topic_0000001151888681_b1378372812210"></a><a name="en-us_topic_0000001151888681_b1378372812210"></a>115200</strong>, data bit to <strong id="en-us_topic_0000001151888681_b27871628822"><a name="en-us_topic_0000001151888681_b27871628822"></a><a name="en-us_topic_0000001151888681_b27871628822"></a>8</strong>, <strong id="en-us_topic_0000001151888681_b678811281528"><a name="en-us_topic_0000001151888681_b678811281528"></a><a name="en-us_topic_0000001151888681_b678811281528"></a>rootfs</strong> to be mounted to the <strong id="en-us_topic_0000001151888681_b978813281220"><a name="en-us_topic_0000001151888681_b978813281220"></a><a name="en-us_topic_0000001151888681_b978813281220"></a>emmc</strong> component, and file system type to <strong id="en-us_topic_0000001151888681_b12788132814217"><a name="en-us_topic_0000001151888681_b12788132814217"></a><a name="en-us_topic_0000001151888681_b12788132814217"></a>vfat</strong>.</p>
-    <p id="en-us_topic_0000001151888681_p12481832163913"><a name="en-us_topic_0000001151888681_p12481832163913"></a><a name="en-us_topic_0000001151888681_p12481832163913"></a><strong id="en-us_topic_0000001151888681_b965011165313"><a name="en-us_topic_0000001151888681_b965011165313"></a><a name="en-us_topic_0000001151888681_b965011165313"></a>rootaddr=10M rootsize=20M rw</strong> indicates the start address and size of the <strong id="en-us_topic_0000001151888681_b1538675832018"><a name="en-us_topic_0000001151888681_b1538675832018"></a><a name="en-us_topic_0000001151888681_b1538675832018"></a>rootfs.img</strong> file to be burnt, respectively. The file size <strong id="en-us_topic_0000001151888681_b0633135515546"><a name="en-us_topic_0000001151888681_b0633135515546"></a><a name="en-us_topic_0000001151888681_b0633135515546"></a>must be the same</strong> as that of the <strong id="en-us_topic_0000001151888681_b69061726113015"><a name="en-us_topic_0000001151888681_b69061726113015"></a><a name="en-us_topic_0000001151888681_b69061726113015"></a>rootfs.img</strong> file in the IDE.</p>
+    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p13489329396"><a name="en-us_topic_0000001151888681_p13489329396"></a><a name="en-us_topic_0000001151888681_p13489329396"></a>Run this command to set the output mode to serial port output, baud rate to <strong id="b433815011512"><a name="b433815011512"></a><a name="b433815011512"></a>115200</strong>, data bit to <strong id="b1933919018155"><a name="b1933919018155"></a><a name="b1933919018155"></a>8</strong>, <strong id="b433912010151"><a name="b433912010151"></a><a name="b433912010151"></a>rootfs</strong> to be mounted to the <strong id="b83409014151"><a name="b83409014151"></a><a name="b83409014151"></a>emmc</strong> component, and file system type to <strong id="b133418081511"><a name="b133418081511"></a><a name="b133418081511"></a>vfat</strong>.</p>
+    <p id="en-us_topic_0000001151888681_p12481832163913"><a name="en-us_topic_0000001151888681_p12481832163913"></a><a name="en-us_topic_0000001151888681_p12481832163913"></a><strong id="b1641214193158"><a name="b1641214193158"></a><a name="b1641214193158"></a>rootaddr=10M rootsize=20M rw</strong> indicates the start address and size of the <strong id="b1441320198151"><a name="b1441320198151"></a><a name="b1441320198151"></a>rootfs.img</strong> file to be burnt, respectively. The file size must be the same as that of the <strong id="b15414219161513"><a name="b15414219161513"></a><a name="b15414219161513"></a>rootfs.img</strong> file in the IDE.</p>
     </td>
     </tr>
     <tr id="en-us_topic_0000001151888681_row18234161153820"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001151888681_p823417118386"><a name="en-us_topic_0000001151888681_p823417118386"></a><a name="en-us_topic_0000001151888681_p823417118386"></a>saveenv</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p32341616389"><a name="en-us_topic_0000001151888681_p32341616389"></a><a name="en-us_topic_0000001151888681_p32341616389"></a><strong id="en-us_topic_0000001151888681_b16238195319315"><a name="en-us_topic_0000001151888681_b16238195319315"></a><a name="en-us_topic_0000001151888681_b16238195319315"></a>saveenv</strong> means to save the current configuration.</p>
+    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p32341616389"><a name="en-us_topic_0000001151888681_p32341616389"></a><a name="en-us_topic_0000001151888681_p32341616389"></a><strong id="b8139162216169"><a name="b8139162216169"></a><a name="b8139162216169"></a>saveenv</strong> means to save the current configuration.</p>
     </td>
     </tr>
     <tr id="en-us_topic_0000001151888681_row192345113811"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001151888681_p7235111183819"><a name="en-us_topic_0000001151888681_p7235111183819"></a><a name="en-us_topic_0000001151888681_p7235111183819"></a>reset</p>
     </td>
-    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p123781411114016"><a name="en-us_topic_0000001151888681_p123781411114016"></a><a name="en-us_topic_0000001151888681_p123781411114016"></a><strong id="en-us_topic_0000001151888681_b32719232420"><a name="en-us_topic_0000001151888681_b32719232420"></a><a name="en-us_topic_0000001151888681_b32719232420"></a>reset</strong> means to reset the board.</p>
+    <td class="cellrowborder" valign="top" width="50%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001151888681_p123781411114016"><a name="en-us_topic_0000001151888681_p123781411114016"></a><a name="en-us_topic_0000001151888681_p123781411114016"></a><strong id="b760219545018"><a name="b760219545018"></a><a name="b760219545018"></a>reset</strong> means to reset the board.</p>
     </td>
     </tr>
     </tbody>
     </table>
 
     >![](public_sys-resources/icon-notice.gif) **NOTICE:** 
-    >**go 0x80000000**  \(optional\) indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press  **Enter**  in the countdown phase of the U-boot startup to interrupt the automatic startup.
+    >**go 0x80000000**  is optional. It indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press  **Enter**  in the countdown phase of the U-Boot startup to interrupt the automatic startup.
 
 3.  Run the  **reset**  command and press  **Enter**  to restart the board. After the board is restarted,  **OHOS**  is displayed when you press  **Enter**.
 
@@ -499,5 +499,5 @@ Compile and burn images by referring to  [Building](../quick-start/running-a-hel
 
 ## Follow-up Learning<a name="section9712145420182"></a>
 
-Congratulations! You have finished all steps! You are advised to go on learning how to develop  [Cameras with a Screen](../guide/cameras-with-a-screen.md).
+Congratulations! You have finished all steps! You are advised to go on learning how to develop  [Cameras with a Screen](../guide/cameras-without-a-screen.md).
 

en/device-dev/quick-start/environment-setup-7.md

-# Environment Setup<a name="EN-US_TOPIC_0000001157501675"></a>
-
--   **[Overview](overview-8.md)**  
-
--   **[Windows Development Environment](windows-development-environment-9.md)**  
-
--   **[Ubuntu Build Environment](ubuntu-build-environment-10.md)**  
-
--   **[FAQs](faqs-11.md)**  
-
-

en/device-dev/quick-start/environment-setup-8.md

-# Environment Setup<a name="EN-US_TOPIC_0000001157501675"></a>
-
--   **[Overview](overview-9.md)**  
-
--   **[Windows Development Environment](windows-development-environment-10.md)**  
-
--   **[Preparing the Ubuntu Build Environment](preparing-the-ubuntu-build-environment.md)**  
-
--   **[FAQs](faqs-11.md)**  
-
-

en/device-dev/quick-start/environment-setup.md

-# Environment Setup<a name="EN-US_TOPIC_0000001151881067"></a>
+# Environment Setup<a name="EN-US_TOPIC_0000001128311058"></a>
 
 -   **[Overview](overview-1.md)**  
 

en/device-dev/quick-start/faq.md

-# FAQ<a name="EN-US_TOPIC_0000001152496467"></a>
+# FAQ<a name="EN-US_TOPIC_0000001128470858"></a>
 
 -   [What should I do if garbled characters and segmentation faults occur during hb installation?](#section411894616119)
 -   [What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation?](#section629417571626)

en/device-dev/quick-start/faqs-2.md

-# FAQs<a name="EN-US_TOPIC_0000001105368702"></a>
-
--   [What should I do when the images failed to be burnt over the selected serial port?](#section627268185113)
--   [What should I do when Windows-based PC failed to be connected to the board?](#section195391036568)
--   [What should I do when the image failed to be burnt?](#section571164016565)
--   [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](#section1039835245619)
--   [What should I do when no command output is displayed?](#section14871149155911)
-
-## What should I do when the images failed to be burnt over the selected serial port?<a name="section627268185113"></a>
-
--   **Symptom**
-
-    **Error: Opening COMxx: Access denied**  is displayed after clicking  **Burn**  and selecting a serial port.
-
-    **Figure  1**  Failed to open the serial port<a name="fig066333283916"></a>  
-    ![](figures/failed-to-open-the-serial-port.png "failed-to-open-the-serial-port")
-
--   **Possible Causes**
-
-    The serial port has been used.
-
--   **Solutions**
-
-1.  Search for the terminal using serial-xx from the drop-down list in the  **TERMINAL**  panel.
-
-    **Figure  2**  Checking whether the serial port is used<a name="fig165994164420"></a>  
-    ![](figures/checking-whether-the-serial-port-is-used.png "checking-whether-the-serial-port-is-used")
-
-2.  Click the dustbin icon as shown in the following figure to disable the terminal using the serial port.
-
-    **Figure  3**  Disabling the terminal using the serial port<a name="fig7911282453"></a>  
-    ![](figures/disabling-the-terminal-using-the-serial-port.png "disabling-the-terminal-using-the-serial-port")
-
-3.  Click  **Burn**, select the serial port, and start burning images again.
-
-    **Figure  4**  Restarting burning<a name="fig1138624316485"></a>  
-    
-
-    ![](figures/changjian1.png)
-
-
-## What should I do when Windows-based PC failed to be connected to the board?<a name="section195391036568"></a>
-
--   **Symptom**
-
-    The file image cannot be obtained after clicking  **Burn**  and selecting a serial port.
-
-    **Figure  5**  Failed to obtain the image file due to unavailable connection<a name="fig5218920223"></a>  
-    ![](figures/failed-to-obtain-the-image-file-due-to-unavailable-connection.png "failed-to-obtain-the-image-file-due-to-unavailable-connection")
-
--   **Possible Causes**
-
-    The board is disconnected from the Windows-based PC.
-
-    Windows Firewall does not allow Visual Studio Code to access the network.
-
--   **Solutions**
-
-1.  Check whether the network cable is properly connected.
-2.  Click  **Windows Firewall**.
-
-    **Figure  6**  Network and firewall setting<a name="fig62141417794"></a>  
-    ![](figures/network-and-firewall-setting.png "network-and-firewall-setting")
-
-3.  Click  **Firewall & network protection**, and on the displayed page, click  **Allow applications to communicate through Windows Firewall**.
-
-    **Figure  7**  Firewall and network protection<a name="fig20703151111116"></a>  
-    ![](figures/firewall-and-network-protection.png "firewall-and-network-protection")
-
-4.  Select the Visual Studio Code application
-
-    **Figure  8**  Selecting the Visual Studio Code application<a name="fig462316612165"></a>  
-    ![](figures/selecting-the-visual-studio-code-application.png "selecting-the-visual-studio-code-application")
-
-5.  Select the  **Private**  and  **Public**  network access rights for the Visual Studio Code application.
-
-    **Figure  9**  Allowing the Visual Studio Code application to access the network<a name="fig132725269184"></a>  
-    ![](figures/allowing-the-visual-studio-code-application-to-access-the-network.png "allowing-the-visual-studio-code-application-to-access-the-network")
-
-
-## What should I do when the image failed to be burnt?<a name="section571164016565"></a>
-
--   **Symptom**
-
-    The burning status is not displayed after clicking  **Burn**  and selecting a serial port.
-
--   **Possible Causes**
-
-    The IDE is not restarted after the DevEco plug-in is installed.
-
--   **Solutions**
-
-    Restart the IDE.
-
-
-## What should I do when the message indicating Python cannot be found is displayed during compilation and building?<a name="section1039835245619"></a>
-
--   **Symptom**
-
-    ![](figures/en-us_image_0000001105056492.png)
-
-
--   **Possible Cause 1**: Python is not installed.
--   **Solutions**
-
-    Install Python by referring to   [Installing and Configuring Python](../quick-start/ubuntu-build-environment.md).
-
--   **Possible Cause 2**: The soft link that points to the Python does not exist in the usr/bin directory.
-
-    ![](figures/en-us_image_0000001151976069.png)
-
--   **Solutions**
-
-    Run the following commands:
-
-    ```
-    # cd /usr/bin/
-    # which python3
-    # ln -s /usr/local/bin/python3 python
-    # python --version
-    ```
-
-    Example:
-
-    ![](figures/en-us_image_0000001152176139.png)
-
-
-## What should I do when no command output is displayed?<a name="section14871149155911"></a>
-
--   **Symptom**
-
-    The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when you press  **Enter**.
-
--   **Possible Cause 1**
-
-    The serial port is connected incorrectly.
-
--   **Solutions**
-
-    Change the serial port number.
-
-    Start  **Device Manager**  to check whether the serial port connected to the board is the same as that connected to the terminal device. If the serial ports are different, perform step  [1](../quick-start/running-a-hello-ohos-program.md)  in the  **Running an Image**  section to change the serial port number.
-
-
--   **Possible Cause 2**
-
-    The U-boot of the board is damaged.
-
--   **Solutions**
-
-    Burn the U-boot.
-
-    If the fault persists after you perform the preceding operations, the U-boot of the board may be damaged. You can burn the U-boot by performing the following steps:
-
-
-1.  Obtain the U-boot file.
-
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:** 
-    >The U-boot file of the two boards can be obtained from the following paths, respectively.
-    >Hi3516D V300:  **device\\hisilicon\\hispark\_taurus\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3516dv300.bin**
-    >Hi3518E V300:  **device\\hisilicon\\hispark\_aries\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3518ev300.bin**
-
-2.  Burn the U-boot file by following the procedures for burning a U-boot file over USB.
-
-    Select the U-boot files of corresponding development boards for burning by referring to  [Programming Flash Memory on the Hi3516](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_upload-0000001052148681)/[Programming Flash Memory on the Hi3518](https://device.harmonyos.com/en/docs/ide/user-guides/hi3518_upload-0000001057313128)
-
-3.  Log in to the serial port after the burning is complete.
-
-    **Figure  10**  Serial port displayed after the U-boot is burnt<a name="en-us_topic_0000001053466255_fig155914681910"></a>  
-    ![](figures/serial-port-displayed-after-the-u-boot-is-burnt.png "serial-port-displayed-after-the-u-boot-is-burnt")
-
-

en/device-dev/quick-start/faqs-3.md

-# FAQs<a name="EN-US_TOPIC_0000001105368702"></a>
+# FAQs<a name="EN-US_TOPIC_0000001128470856"></a>
 
 -   [What should I do when the images failed to be burnt over the selected serial port?](#section627268185113)
 -   [What should I do when Windows-based PC failed to be connected to the board?](#section195391036568)
@@ -97,7 +97,7 @@
 
 -   **Symptom**
 
-    ![](figures/en-us_image_0000001105056492.png)
+    ![](figures/en-us_image_0000001174270715.png)
 
 
 -   **Possible Cause 1**: Python is not installed.
@@ -107,7 +107,7 @@
 
 -   **Possible Cause 2**: The soft link that points to the Python does not exist in the usr/bin directory.
 
-    ![](figures/en-us_image_0000001151976069.png)
+    ![](figures/en-us_image_0000001128470880.png)
 
 -   **Solutions**
 
@@ -122,7 +122,7 @@
 
     Example:
 
-    ![](figures/en-us_image_0000001152176139.png)
+    ![](figures/en-us_image_0000001174270713.png)
 
 
 ## What should I do when no command output is displayed?<a name="section14871149155911"></a>

en/device-dev/quick-start/faqs-5.md

-# FAQs<a name="EN-US_TOPIC_0000001152168589"></a>
-
--   [What should I do when the images failed to be burnt over the selected serial port?](#section1498892119619)
--   [What should I do when Windows-based PC failed to be connected to the board?](#section8512971816)
--   [What should I do when the image failed to be burnt?](#section1767804111198)
--   [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](#en-us_topic_0000001053466255_section1039835245619)
--   [What should I do when no command output is displayed?](#en-us_topic_0000001053466255_section14871149155911)
-
-## What should I do when the images failed to be burnt over the selected serial port?<a name="section1498892119619"></a>
-
--   **Symptom**
-
-    **Error: Opening COMxx: Access denied**  is displayed after clicking  **Burn**  and selecting a serial port.
-
-    **Figure  1**  Failed to open the serial port<a name="en-us_topic_0000001053466255_fig066333283916"></a>  
-    ![](figures/failed-to-open-the-serial-port-9.png "failed-to-open-the-serial-port-9")
-
--   **Possible Causes**
-
-    The serial port has been used.
-
--   **Solutions**
-
-1.  Search for the terminal using serial-xx from the drop-down list in the  **TERMINAL**  panel.
-
-    **Figure  2**  Checking whether the serial port is used<a name="en-us_topic_0000001053466255_fig165994164420"></a>  
-    ![](figures/checking-whether-the-serial-port-is-used-10.png "checking-whether-the-serial-port-is-used-10")
-
-2.  Click the dustbin icon as shown in the following figure to disable the terminal using the serial port.
-
-    **Figure  3**  Disabling the terminal using the serial port<a name="en-us_topic_0000001053466255_fig7911282453"></a>  
-    ![](figures/disabling-the-terminal-using-the-serial-port-11.png "disabling-the-terminal-using-the-serial-port-11")
-
-3.  Click  **Burn**, select the serial port, and start burning images again.
-
-    **Figure  4**  Restarting burning<a name="en-us_topic_0000001053466255_fig1138624316485"></a>  
-    
-
-    ![](figures/changjian1-12.png)
-
-
-## What should I do when Windows-based PC failed to be connected to the board?<a name="section8512971816"></a>
-
--   **Symptom**
-
-    The file image cannot be obtained after clicking  **Burn**  and selecting a serial port.
-
-    **Figure  5**  Failed to obtain the image file due to unavailable connection<a name="en-us_topic_0000001053466255_fig5218920223"></a>  
-    ![](figures/failed-to-obtain-the-image-file-due-to-unavailable-connection-13.png "failed-to-obtain-the-image-file-due-to-unavailable-connection-13")
-
--   **Possible Causes**
-
-    The board is disconnected from the Windows-based PC.
-
-    Windows Firewall does not allow Visual Studio Code to access the network.
-
--   **Solutions**
-
-1.  Check whether the network cable is properly connected.
-2.  Click  **Windows Firewall**.
-
-    **Figure  6**  Network and firewall setting<a name="en-us_topic_0000001053466255_fig62141417794"></a>  
-    ![](figures/network-and-firewall-setting-14.png "network-and-firewall-setting-14")
-
-3.  Click  **Firewall & network protection**, and on the displayed page, click  **Allow applications to communicate through Windows Firewall**.
-
-    **Figure  7**  Firewall and network protection<a name="en-us_topic_0000001053466255_fig20703151111116"></a>  
-    ![](figures/firewall-and-network-protection-15.png "firewall-and-network-protection-15")
-
-4.  Select the Visual Studio Code application
-
-    **Figure  8**  Selecting the Visual Studio Code application<a name="en-us_topic_0000001053466255_fig462316612165"></a>  
-    ![](figures/selecting-the-visual-studio-code-application-16.png "selecting-the-visual-studio-code-application-16")
-
-5.  Select the  **Private**  and  **Public**  network access rights for the Visual Studio Code application.
-
-    **Figure  9**  Allowing the Visual Studio Code application to access the network<a name="en-us_topic_0000001053466255_fig132725269184"></a>  
-    ![](figures/allowing-the-visual-studio-code-application-to-access-the-network-17.png "allowing-the-visual-studio-code-application-to-access-the-network-17")
-
-
-## What should I do when the image failed to be burnt?<a name="section1767804111198"></a>
-
--   **Symptom**
-
-    The burning status is not displayed after clicking  **Burn**  and selecting a serial port.
-
--   **Possible Causes**
-
-    The IDE is not restarted after the DevEco plug-in is installed.
-
--   **Solutions**
-
-    Restart the IDE.
-
-
-## What should I do when the message indicating Python cannot be found is displayed during compilation and building?<a name="en-us_topic_0000001053466255_section1039835245619"></a>
-
--   **Symptom**
-
-    ![](figures/en-us_image_0000001105376260.png)
-
-
--   **Possible Cause 1**
-
-    Python is not installed.
-
--   **Solutions**
-
-    Install Python by referring to  [Installing and Configuring Python](../quick-start/ubuntu-build-environment.md).
-
--   **Possible Cause 2**: The soft link that points to the Python does not exist in the usr/bin directory.
-
-    ![](figures/en-us_image_0000001105216304.png)
-
--   **Solutions**
-
-    Run the following commands:
-
-    ```
-    # cd /usr/bin/
-    # which python3
-    # ln -s /usr/local/bin/python3 python
-    # python --version
-    ```
-
-    Example:
-
-    ![](figures/en-us_image_0000001152256235.png)
-
-
-## What should I do when no command output is displayed?<a name="en-us_topic_0000001053466255_section14871149155911"></a>
-
--   **Symptom**
-
-    The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when you press  **Enter**.
-
--   **Possible Cause 1**
-
-    The serial port is connected incorrectly.
-
--   **Solutions**
-
-    Change the serial port number.
-
-    Start  **Device Manager**  to check whether the serial port connected to the board is the same as that connected to the terminal device. If the serial ports are different, perform step  [1](../quick-start/running-a-hello-ohos-program.md)  in the  **Running an Image**  section to change the serial port number.
-
-
--   **Possible Cause 2**
-
-    The U-boot of the board is damaged.
-
--   **Solutions**
-
-    Burn the U-boot.
-
-    If the fault persists after you perform the preceding operations, the U-boot of the board may be damaged. You can burn the U-boot by performing the following steps:
-
-
-1.  Obtain the U-boot file.
-
-    >![](public_sys-resources/icon-notice.gif) **NOTICE:** 
-    >The U-boot file of the two boards can be obtained from the following paths, respectively.
-    >Hi3516D V300:  **device\\hisilicon\\hispark\_taurus\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3516dv300.bin**
-    >Hi3518E V300:  **device\\hisilicon\\hispark\_aries\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3518ev300.bin**
-
-2.  Burn the U-boot file by following the procedures for burning a U-boot file over USB.
-
-    Select the U-boot files of corresponding development boards for burning by referring to  [Programming Flash Memory on the Hi3516](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_upload-0000001052148681)/[Programming Flash Memory on the Hi3518](https://device.harmonyos.com/en/docs/ide/user-guides/hi3518_upload-0000001057313128)
-
-3.  Log in to the serial port after the burning is complete.
-
-    ![](figures/en-us_image_0000001105536118.png)
-
-

en/device-dev/quick-start/faqs-6.md

-# FAQs<a name="EN-US_TOPIC_0000001152168589"></a>
+# FAQs<a name="EN-US_TOPIC_0000001128311064"></a>
 
 -   [What should I do when the images failed to be burnt over the selected serial port?](#section1498892119619)
 -   [What should I do when Windows-based PC failed to be connected to the board?](#section8512971816)
@@ -97,7 +97,7 @@
 
 -   **Symptom**
 
-    ![](figures/en-us_image_0000001105376260.png)
+    ![](figures/en-us_image_0000001174270743.png)
 
 
 -   **Possible Cause 1**
@@ -110,7 +110,7 @@
 
 -   **Possible Cause 2**: The soft link that points to the Python does not exist in the usr/bin directory.
 
-    ![](figures/en-us_image_0000001105216304.png)
+    ![](figures/en-us_image_0000001174270739.png)
 
 -   **Solutions**
 
@@ -125,7 +125,7 @@
 
     Example:
 
-    ![](figures/en-us_image_0000001152256235.png)
+    ![](figures/en-us_image_0000001174350661.png)
 
 
 ## What should I do when no command output is displayed?<a name="en-us_topic_0000001053466255_section14871149155911"></a>
@@ -169,6 +169,6 @@
 
 3.  Log in to the serial port after the burning is complete.
 
-    ![](figures/en-us_image_0000001105536118.png)
+    ![](figures/en-us_image_0000001174350659.png)
 
 

en/device-dev/quick-start/faqs-11.md → en/device-dev/quick-start/faqs-7.md

-# FAQs<a name="EN-US_TOPIC_0000001114978406"></a>
+# FAQs<a name="EN-US_TOPIC_0000001166804465"></a>
 
 -   **Symptom**
 

en/device-dev/quick-start/faqs.md

-# FAQs<a name="EN-US_TOPIC_0000001105208752"></a>
+# FAQs<a name="EN-US_TOPIC_0000001128311054"></a>
 
 -   [What should I do when the message configure: error: no acceptable C compiler found in $PATH is displayed during Python 3 installation?](#section1221016541119)
 -   [What should I do when the message -bash: make: command not found is displayed during Python 3 installation?](#section1913477181213)
@@ -134,7 +134,7 @@
 
     -   Download the source code from  [https://pypi.org/project/pycrypto/\#files](https://pypi.org/project/pycrypto/#files).
 
-    ![](figures/en-us_image_0000001151976061.png)
+    ![](figures/en-us_image_0000001128470864.png)
 
     -   Save the source code package to the Linux server, decompress the package, and run the  **python3 setup.py install**  command to install  **Crypto**.
     -   Rebuild an environment.
@@ -164,7 +164,7 @@
 
     -   Download the installation package from  [https://pypi.org/project/ecdsa/\#files](https://pypi.org/project/ecdsa/#files).
 
-    ![](figures/en-us_image_0000001152176131.png)
+    ![](figures/en-us_image_0000001128311072.png)
 
     -   Save the installation package to the Linux server and run the  **pip3 install ecdsa-0.15-py2.py3-none-any.whl**  command to install  **ecdsa**.
     -   Rebuild an environment.
@@ -194,7 +194,7 @@
 
     -   Download the installation package from  [https://pypi.org/project/six/\#files](https://pypi.org/project/six/#files).
 
-    ![](figures/en-us_image_0000001152056191.png)
+    ![](figures/en-us_image_0000001174270699.png)
 
     -   Save the source code to the Linux server and run the  **pip3 install six-1.14.0-py2.py3-none-any.whl**  command to install  **six**.
     -   Rebuild an environment.
@@ -247,7 +247,7 @@
 
 -   **Possible Cause 2:**  The soft link that points to the Python does not exist in the  **usr/bin**  directory.
 
-    ![](figures/en-us_image_0000001105376252.png)
+    ![](figures/en-us_image_0000001128311070.png)
 
 -   **Solutions**
 
@@ -262,7 +262,7 @@
 
     Example:
 
-    ![](figures/en-us_image_0000001105216296.png)
+    ![](figures/en-us_image_0000001174350623.png)
 
 
 ## What should I do when an error with  **lsb\_release**  occurs during  **kconfiglib**  installation?<a name="section691681635814"></a>

en/device-dev/quick-start/hi3516-development-board.md

-# Hi3516 Development Board<a name="EN-US_TOPIC_0000001152041033"></a>
+# Hi3516 Development Board<a name="EN-US_TOPIC_0000001174350603"></a>
 
 -   [Introduction](#section26131214194212)
 -   [Development Board Specifications](#section15192203316533)

en/device-dev/quick-start/hi3516.md

-# Hi3516<a name="EN-US_TOPIC_0000001105041328"></a>
+# Hi3516<a name="EN-US_TOPIC_0000001128470852"></a>
 
 -   **[Setting Up the Environment](setting-up-the-environment-2.md)**  
 

en/device-dev/quick-start/hi3518-development-board.md

-# Hi3518 Development Board<a name="EN-US_TOPIC_0000001105201138"></a>
+# Hi3518 Development Board<a name="EN-US_TOPIC_0000001174270693"></a>
 
 -   [Introduction](#section14815247616)
 -   [Development Board Specifications](#section765112478446)