Reference
diff --git a/en/device-dev/quick-start/preparing-the-ubuntu-build-environment.md b/en/device-dev/quick-start/preparing-the-ubuntu-build-environment.md
deleted file mode 100644
index e1f0774daadb6d6f807a95c16affac8e8a630b27..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/preparing-the-ubuntu-build-environment.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# Preparing the Ubuntu Build Environment
-
-- [Method 1: Setting up an Ubuntu Build Environment Using a Docker Environment](#section1643363843714)
- - [Obtaining Standard-System Source Code](#section58448331029)
- - [Installing and Using the Docker Environment](#section22916211916)
-
-- [Method 2: Setting up an Ubuntu Build Environment Using an Installation Package](#section25961010189)
- - [Installing Dependent Tools](#section109262032104819)
- - [Obtaining Standard-System Source Code](#section6325556113718)
- - [Obtaining prebuilts](#section16453104219209)
-
-
-You can use either the Docker environment or installation package provided by OpenHarmony to set up an Ubuntu build environment. This section describes the two methods.
-
-## Method 1: Setting up an Ubuntu Build Environment Using a Docker Environment
-
-The standard OpenHarmony system provides a Docker environment which encapsulates build tools. To use the Docker environment, perform the following steps:
-
-1. Obtain the standard-system source code.
-2. Install and use the Docker environment.
-
-### Obtaining Standard-System Source Code
-
-Obtain the [standard-system source code](https://repo.huaweicloud.com/harmonyos/os/2.0/code-2.0-canary.tar.gz). The obtained source code is the static code. If you want to obtain the latest source code from Gitee, use [repo](../get-code/source-code-acquisition.md).
-
-### Installing and Using the Docker Environment
-
-For details, see [Installing and Using Docker](../get-code/tool-acquisition.md).
-
-## Method 2: Setting up an Ubuntu Build Environment Using an Installation Package
-
-The procedure is as follows:
-
-1. Install dependent tools.
-2. Obtain the standard-system source code.
-3. Obtain prebuilts.
-
-### Installing Dependent Tools
-
-The installation command is as follows:
-
-```
-sudo apt-get install binutils git-core git-lfs gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip m4
-```
-
-> **CAUTION:**
->The preceding command is applicable to Ubuntu 18.04. For other Ubuntu versions, use the corresponding installation commands based on the installation package name. If the Ubuntu version is later than 18.04, Python 2.7 and python-minimal must be installed.
-
-### Obtaining Standard-System Source Code
-
-Obtain the [standard-system source code](https://repo.huaweicloud.com/harmonyos/os/2.0/code-2.0-canary.tar.gz). The obtained source code is the static code. If you want to obtain the latest source code from Gitee, use [repo](../get-code/source-code-acquisition.md).
-
-### Obtaining prebuilts
-
-1. Go to the OpenHarmony working directory.
-
- ```
- cd OpenHarmony
- ```
-
-2. Execute the following script:
-
- ```
- build/prebuilts_download.sh
- ```
-
- By default, the downloaded prebuilts binary file is stored in **OpenHarmony\_2.0\_canary\_prebuilts** \(which is in the same directory as **OpenHarmony**\).
-
-
diff --git a/en/device-dev/quick-start/running-a-hello-ohos-program-4.md b/en/device-dev/quick-start/running-a-hello-ohos-program-4.md
deleted file mode 100644
index 62c151696188113379a554af194eae697f0f22b4..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/running-a-hello-ohos-program-4.md
+++ /dev/null
@@ -1,268 +0,0 @@
-# Running a Hello OHOS Program
-
-- [Creating a Program](#section1550972416485)
-- [Building](#section234175193114)
-- [Burning](#section7609155824819)
-- [Running an Image](#section17612105814480)
-- [Follow-up Learning](#section9712145420182)
-
-This section describes how to create, compile, burn, and run the first program, and finally print **Hello OHOS!** on the develop board.
-
-## Creating a Program
-
-1. Create a directory and the program source code.
-
- Create the **applications/sample/camera/apps/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 **OHOS** to **World**. You can use either C or C++ to develop a program.
-
- ```
- #include
-
- int main(int argc, char **argv)
- {
- printf("\n************************************************\n");
- printf("\n\t\tHello OHOS!\n");
- printf("\n************************************************\n\n");
-
- return 0;
- }
- ```
-
-2. Create a build file.
-
- Create the **applications/sample/camera/apps/BUILD.gn** file. The file content is as follows:
-
- ```
- import("//build/lite/config/component/lite_component.gni")
- lite_component("hello-OHOS") {
- features = [ ":helloworld" ]
- }
- executable("helloworld") {
- output_name = "helloworld"
- sources = [ "src/helloworld.c" ]
- include_dirs = []
- defines = []
- cflags_c = []
- ldflags = []
- }
- ```
-
-3. Add a new component.
-
- Add the configuration of the **hello\_world\_app** component to the **build/lite/components/applications.json** file. The sample code below shows some configurations defined in the **applications.json** file, and the code between **\#\#start\#\#** and **\#\#end\#\#** is the new configuration \(Delete the rows where **\#\#start\#\#** and **\#\#end\#\#** are located after the configurations are added.\)
-
- ```
- {
- "components": [
- {
- "component": "camera_sample_communication",
- "description": "Communication related samples.",
- "optional": "true",
- "dirs": [
- "applications/sample/camera/communication"
- ],
- "targets": [
- "//applications/sample/camera/communication:sample"
- ],
- "rom": "",
- "ram": "",
- "output": [],
- "adapted_kernel": [ "liteos_a" ],
- "features": [],
- "deps": {
- "components": [],
- "third_party": []
- }
- },
- ##start##
- {
- "component": "hello_world_app",
- "description": "Communication related samples.",
- "optional": "true",
- "dirs": [
- "applications/sample/camera/apps"
- ],
- "targets": [
- "//applications/sample/camera/apps:hello-OHOS"
- ],
- "rom": "",
- "ram": "",
- "output": [],
- "adapted_kernel": [ "liteos_a" ],
- "features": [],
- "deps": {
- "components": [],
- "third_party": []
- }
- },
- ##end##
- {
- "component": "camera_sample_app",
- "description": "Camera related samples.",
- "optional": "true",
- "dirs": [
- "applications/sample/camera/launcher",
- "applications/sample/camera/cameraApp",
- "applications/sample/camera/setting",
- "applications/sample/camera/gallery",
- "applications/sample/camera/media"
- ],
- ```
-
-4. Modify the board configuration file.
-
- Add the **hello\_world\_app** component to the **vendor/hisilicon/hispark\_aries/config.json** file. The sample code below shows the configurations of the **applications** subsystem, and the code between **\#\#start\#\#** and **\#\#end\#\#** is the new configuration \(Delete the rows where **\#\#start\#\#** and **\#\#end\#\#** are located after the configurations are added.\)
-
- ```
- {
- "subsystem": "applications",
- "components": [
- ##start##
- { "component": "hello_world_app", "features":[] },
- ##end##
- { "component": "camera_sample_app", "features":[] }
-
- ]
- },
- ```
-
-
-## Building
-
-If the Linux environment is installed using Docker, perform the compilation by referring to [Using Docker to Prepare the Build Environment](../get-code/tool-acquisition.md). If the Linux compilation environment is installed using a software package, execute the following commands to compile source code in the root directory of the source code package.
-
-```
-hb set (Set the building path.)
-. (Select the current path.)
-Select ipcamera_hispark_aries@hisilicon and press Enter.
-hb build -f (Start building.)
-```
-
-The result files are generated in the **out/hispark\_aries/ipcamera\_hispark\_aries** directory.
-
-**Figure 1** Settings
-
-
-> **NOTICE:**
->The U-boot file of the Hi3518E V300 development board can be obtained from the following path: device/hisilicon/hispark\_aries/sdk\_liteos/uboot/out/boot/u-boot-hi3518ev300.bin
-
-## Burning
-
-The USB port is the only burning mode supported by the Hi3518 development board.
-
-1. Connect the PC and the target development board through the serial port and USB port. In this section, the Hi3518EV300 is used as an example. For details, please refer to [Introduction to the Hi3518 Development Board](https://device.harmonyos.com/en/docs/start/introduce/oem_camera_start_hi3518-0000001050170473).
-2. Open Device Manager, then check and record the serial port number corresponding to the development board.
-
- > **NOTE:**
- >If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_hi3518-drivers-0000001050743695).
-
- 
-
-3. Open DevEco Device Tool and go to **Projects** \> **Settings**.
-
- 
-
-4. On the **hi3518ev300** tab page, set the programming options.
-
- - **upload\_port**: Select the serial port number obtained in step [2](#en-us_topic_0000001057313128_li46411811196).
- - **upload\_protocol**: Select the programming protocol **hiburn-usb**.
- - **upload\_partitions**: Select the file to be programmed. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are programmed at the same time.
-
- 
-
-5. Switch between the **hi3518ev300\_fastboot**, **hi3518ev300\_kernel**, **hi3518ev300\_rootfs**, and **hi3518ev300\_userfs** tab pages, and modify the settings. In general cases, you can leave the fields at their default settings. To change the default settings, select the target item in the **New Option** field first.
-
- 
-
-6. When you finish modifying, click **Save** in the upper right corner.
-
- 
-
-7. Open the project file, go to  \> **PROJECT TASKS** \> **partition:hi3518ev300\_fastboot** \> **Erase** to erase U-boot.
-
- 
-
-8. When the following message is displayed, power off the development board and then power it on.
-
- 
-
-9. If the following message is displayed, it indicates that U-Boot is erased successfully.
-
- 
-
-10. Go to **env:hi3518ev300** \> **Upload** to start programming.
-
- 
-
-11. If the following message is displayed, it indicates that the programming is successful.
-
- 
-
-
-## Running an Image
-
-1. Connect to a serial port.
-
- > **NOTICE:**
- >If the connection fails, rectify the fault by referring to [FAQs](../quick-start/faqs-2.md).
-
- **Figure 2** Serial port connection
-
-
- 
-
- 1. Click **Monitor** to enable the serial port. The **TERMINAL** window is displayed.
- 2. Press **Enter** repeatedly until **hisilicon** displays.
- 3. Go to [step 2](#li9441185382314) if the board is started for the first time or the startup parameters need to be modified; go to [step 3](#li6442853122312) otherwise.
-
-2. \(Mandatory for the first burning\) Modify the **bootcmd** and **bootargs** parameters of U-boot. This step is a fixed operation and the result can be saved. However, you need to perform the following steps again if U-boot needs to be reburnt.
-
- **Table 1** Parameters of the U-boot
-
-
- Command
- |
- Description
- |
-
|---|
-
- setenv bootcmd "sf probe 0;sf read 0x40000000 0x100000 0x600000;go 0x40000000";
- |
- Run this command to set the content of bootcmd. Select the flash whose number is 0, and read content that has a size of 0x600000 (6 MB) and a start address of 0x100000 to memory address 0x40000000. The size must be the same as that of the OHOS_Image.bin file in the IDE.
- |
-
- setenv bootargs "console=ttyAMA0,115200n8 root=flash fstype=jffs2 rw rootaddr=7 M rootsize=8 M";
- |
- In this command, bootargs is set to the serial port output, the baud rate is 115200, the data bit is 8, and the rootfs is mounted to the flash memory. The file system type is set to jffs2 rw, which provides the read-write attribute for the JFFS2 file system. rootaddr=7 M rootsize=8 M indicates the actual start address and length of the rootfs.img file to be burnt, respectively. The file size must be the same as that of the rootfs.img file in the IDE.
- |
-
- saveenv
- |
- saveenv means to save the current configuration.
- |
-
- reset
- |
- reset means to reset the board.
- |
-
- pri
- |
- pri means to view the displayed parameters.
- |
-
-
-
-
- > **NOTICE:**
- >**go 0x40000000** \(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.
-
-3. If **hisilicon \#** is displayed during the startup, run the **reset** command. After the system automatically starts and **OHOS** is displayed, run the **./bin/helloworld** command and then press **Enter**. The system is started successfully if information shown in the following figure is displayed.
-
- **Figure 3** Successful system startup and program execution
- 
-
-
-## Follow-up Learning
-
-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).
-
diff --git a/en/device-dev/quick-start/running-a-hello-ohos-program-5.md b/en/device-dev/quick-start/running-a-hello-ohos-program-5.md
index 713bd45a6bda1acfa95c9b2061669fd5475ebb1a..e3f5d5e2955b1b44c9999d567a171ca426f5104b 100644
--- a/en/device-dev/quick-start/running-a-hello-ohos-program-5.md
+++ b/en/device-dev/quick-start/running-a-hello-ohos-program-5.md
@@ -1,4 +1,4 @@
-# Running a Hello OHOS Program
+# Running a Hello OHOS Program
- [Creating a Program](#section1550972416485)
- [Building](#section234175193114)
@@ -46,9 +46,9 @@ This section describes how to create, compile, burn, and run the first program,
}
```
-3. Add a new component.
+3. Add a component.
- Add the configuration of the **hello\_world\_app** component to the **build/lite/components/applications.json** file. The sample code below shows some configurations defined in the **applications.json** file, and the code between **\#\#start\#\#** and **\#\#end\#\#** is the new configuration \(Delete the rows where **\#\#start\#\#** and **\#\#end\#\#** are located after the configurations are added.\)
+ Add the configuration of the **hello\_world\_app** component to the **build/lite/components/applications.json** file. The sample code below shows some configurations defined in the **applications.json** file, and the code between **"\#\#start\#\#"** and **"\#\#end\#\#"** is the new configuration \(Delete the rows where **"\#\#start\#\#"** and **"\#\#end\#\#"** are located after the configurations are added.\)
```
{
@@ -128,7 +128,7 @@ This section describes how to create, compile, burn, and run the first program,
## Building
-If the Linux environment is installed using Docker, perform the building by referring to [Using Docker to Prepare the Build Environment](../get-code/tool-acquisition.md). If the Linux environment is installed using a software package, go to the root directory of the source code and run the following commands for source code compilation:
+If the Linux environment is installed using Docker, perform the building by referring to [Using Docker to Prepare the Build Environment](../get-code/docker-environment.md). If the Linux environment is installed using a software package, go to the root directory of the source code and run the following commands for source code compilation:
```
hb set (Set the building path.)
@@ -143,53 +143,53 @@ The result files are generated in the **out/hispark\_aries/ipcamera\_hispark\_a
> **NOTICE:**
->The U-boot file of the Hi3518E V300 development board can be obtained from the following path: device/hisilicon/hispark\_aries/sdk\_liteos/uboot/out/boot/u-boot-hi3518ev300.bin
+>The U-Boot file of the Hi3518E V300 development board can be obtained from the following path: device/hisilicon/hispark\_aries/sdk\_liteos/uboot/out/boot/u-boot-hi3518ev300.bin
## Burning
The USB port is the only burning mode supported by the Hi3518 development board.
-1. Connect the PC and the target development board through the serial port and USB port. In this section, the Hi3518EV300 is used as an example. For details, please refer to [Introduction to the Hi3518 Development Board](https://device.harmonyos.com/en/docs/start/introduce/oem_camera_start_hi3518-0000001050170473).
+1. Connect the PC and the target development board through the serial port and USB port. In this section, the Hi3518EV300 is used as an example. For details, see [Introduction to the Hi3518 Development Board](https://device.harmonyos.com/en/docs/start/introduce/oem_minitinier_des_3518-0000001105201138).
2. Open Device Manager, then check and record the serial port number corresponding to the development board.
> **NOTE:**
>If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_hi3518-drivers-0000001050743695).
- 
+ 
3. Open DevEco Device Tool and go to **Projects** \> **Settings**.
- 
+ 
4. On the **Partition Configuration** tab page, modify the settings. In general cases, you can leave the fields at their default settings.
5. On the **hi3518ev300** tab page, set the programming options.
- - **upload\_port**: Select the serial port number obtained in step [2](#en-us_topic_0000001057313128_li46411811196).
+ - **upload\_port**: Select the serial port number obtained in [2](#en-us_topic_0000001057313128_li46411811196).
- **upload\_protocol**: Select the programming protocol **hiburn-usb**.
- **upload\_partitions**: Select the file to be programmed. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are programmed at the same time.
- 
+ 
6. When you finish modifying, click **Save** in the upper right corner.
-7. Open the project file, go to  \> **PROJECT TASKS** \> **hi3518ev300\_fastboot** \> **Erase** to erase U-boot.
+7. Open the project file and click . In the DevEco Device Tool window, choose **PROJECT TASKS** \> **hi3518ev300\_fastboot** \> **Erase** to erase U-Boot.
- 
+ 
8. When the following message is displayed, power off the development board and then power it on.
- 
+ 
9. If the following message is displayed, it indicates that U-Boot is erased successfully.
- 
+ 
10. Go to **hi3518ev300** \> **Upload** to start programming.
- 
+ 
11. If the following message is displayed, it indicates that the programming is successful.
- 
+ 
## Running an Image
@@ -208,9 +208,9 @@ The USB port is the only burning mode supported by the Hi3518 development board.
2. Press **Enter** repeatedly until **hisilicon** displays.
3. Go to [step 2](#li9441185382314) if the board is started for the first time or the startup parameters need to be modified; go to [step 3](#li6442853122312) otherwise.
-2. \(Mandatory for the first burning\) Modify the **bootcmd** and **bootargs** parameters of U-boot. This step is a fixed operation and the result can be saved. However, you need to perform the following steps again if U-boot needs to be reburnt.
+2. \(Mandatory for first-time burning\) Modify the **bootcmd** and **bootargs** parameters of U-Boot. This step is a fixed operation and the result can be saved. However, you need to perform the following steps again if U-Boot needs to be reburnt.
- **Table 1** Parameters of the U-boot
+ **Table 1** Parameters of the U-Boot
Command
@@ -248,7 +248,7 @@ The USB port is the only burning mode supported by the Hi3518 development board.
|
|---|
> **NOTICE:**
- >**go 0x40000000** \(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 0x40000000** \(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.
3. If **hisilicon \#** is displayed during the startup, run the **reset** command. After the system automatically starts and **OHOS** is displayed, run the **./bin/helloworld** command and then press **Enter**. The system is started successfully if information shown in the following figure is displayed.
diff --git a/en/device-dev/quick-start/running-a-hello-ohos-program.md b/en/device-dev/quick-start/running-a-hello-ohos-program.md
index 5f38a61c19e21dfa897231cf60086708b586ca67..1bc2f5daad267626fea4ccda977975597197e26e 100644
--- a/en/device-dev/quick-start/running-a-hello-ohos-program.md
+++ b/en/device-dev/quick-start/running-a-hello-ohos-program.md
@@ -1,4 +1,4 @@
-# Running a Hello OHOS Program
+# Running a Hello OHOS Program
- [Creating a Program](#section204672145202)
- [Building](#section1077671315253)
@@ -129,7 +129,7 @@ This section describes how to create, compile, burn, and run the first program,
## Building
-If the Linux environment is installed using Docker, perform the building by referring to [Using Docker to Prepare the Build Environment](../get-code/tool-acquisition.md). If the Linux environment is installed using a software package, go to the root directory of the source code and run the following commands for source code compilation:
+If the Linux environment is installed using Docker, perform the building by referring to [Using Docker to Prepare the Build Environment](../get-code/docker-environment.md). If the Linux environment is installed using a software package, go to the root directory of the source code and run the following commands for source code compilation:
```
hb set (Set the building path.)
@@ -144,55 +144,55 @@ hb build -f (Start building.)
The result files are generated in the **out/hispark\_taurus/ipcamera\_hispark\_taurus** directory.
> **NOTICE:**
->The U-boot file of the Hi3516D V300 development board can be obtained from the following path: device/hisilicon/hispark\_taurus/sdk\_liteos/uboot/out/boot/u-boot-hi3516dv300.bin
+>The U-Boot file of the Hi3516D V300 development board can be obtained from the following path: device/hisilicon/hispark\_taurus/sdk\_liteos/uboot/out/boot/u-boot-hi3516dv300.bin
## Burning
The Hi3516 development board allows you to burn flash memory over the USB port, serial port, or network port. The following uses the network port burning as an example.
-1. Connect the PC and the target development board through the power port, serial port, and network port. In this section, the Hi3516DV300 is used as an example. For details, please refer to [Introduction to the Hi3516 Development Board](https://device.harmonyos.com/en/docs/start/introduce/oem_camera_start_3516-0000001052670587).
+1. Connect the PC and the target development board through the power port, serial port, and network port. In this section, the Hi3516DV300 is used as an example. For details, please refer to [Introduction to the Hi3516 Development Board](https://device.harmonyos.com/en/docs/start/introduce/oem_minitinier_des_3516-0000001152041033).
2. Open Device Manager, then check and record the serial port number corresponding to the development board.
> **NOTE:**
>If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_hi3518-drivers-0000001050743695).
- 
+ 
3. Open DevEco Device Tool and go to **Projects** \> **Settings**.
4. On the **Partition Configuration** tab page, modify the settings. In general cases, you can leave the fields at their default settings.
-5. On the **hi3516dv300** tab page, configure the programming options.
+5. On the **hi3516dv300** tab page, set the programming options.
- - **upload\_port**: Select the serial port number obtained in step [2](#en-us_topic_0000001056443961_li142386399535).
+ - **upload\_port**: Select the serial port number obtained in [2](#en-us_topic_0000001056443961_li142386399535).
- **upload\_protocol**: Select the programming protocol **hiburn-net**.
- **upload\_partitions**: Select the file to be programmed. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are programmed at the same time.
- 
+ 
6. Check and set the IP address of the network adapter connected to the development board. For details, see [Setting the IP Address of the Network Port for Programming on Hi3516](https://device.harmonyos.com/en/docs/ide/user-guides/set_ipaddress-0000001141825075).
7. Set the IP address of the network port for programming:
- - **upload\_net\_server\_ip**: Select the IP address set in [6](#en-us_topic_0000001056443961_li1558813168234), such as 192.168.1.2.
- - **upload\_net\_client\_mask**: Set the subnet mask of the development board, such as 255.255.255.0. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated.
- - **upload\_net\_client\_gw**: Set the gateway of the development board, such as 192.168.1.1. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated.
- - **upload\_net\_client\_ip**: Set the IP address of the development board, such as 192.168.1.3. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated.
+ - **upload\_net\_server\_ip**: Select the IP address set in [6](#en-us_topic_0000001056443961_li1558813168234). Example: 192.168.1.2.
+ - **upload\_net\_client\_mask**: Set the subnet mask of the development board, such as 255.255.255.0. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated. Example: 255.255.255.0.
+ - **upload\_net\_client\_gw**: Set the gateway of the development board, such as 192.168.1.1. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated. Example: 192.168.1.1.
+ - **upload\_net\_client\_ip**: Set the IP address of the development board, such as 192.168.1.3. Once the **upload\_net\_server\_ip** field is set, this field will be automatically populated. Example: 192.168.1.3.
- 
+ 
8. When you finish modifying, click **Save** in the upper right corner.
-9. Open the project file and go to  \> **PROJECT TASKS** \> **hi3516dv300** \> **Upload** to start programming.
+9. Open the project file and click . In the DevEco Device Tool window, choose **PROJECT TASKS** \> **hi3516dv300** \> **Upload** to start programming.
- 
+ 
10. When the following message is displayed, power off the development board and then power it on.
- 
+ 
-11. Start programming. When the following message is displayed, it indicates that the programming is successful.
+11. Start burning. When the following message is displayed, the burning is successful.
- 
+ 
## Running an Image
@@ -211,12 +211,12 @@ The Hi3516 development board allows you to burn flash memory over the USB port,
2. Press **Enter** repeatedly until **hisilicon** displays.
3. Go to step [2](#l5b42e79a33ea4d35982b78a22913b0b1) if the board is started for the first time or the startup parameters need to be modified; go to step [3](#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.
> **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
Command
@@ -250,7 +250,7 @@ The Hi3516 development board allows you to burn flash memory over the USB port,
|
|---|
> **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** \(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.
3. Run the **reset** command and press **Enter** to restart the board. After the board is restarted, **OHOS** is displayed when you press **Enter**.
diff --git a/en/device-dev/quick-start/running-a-hello-world-program.md b/en/device-dev/quick-start/running-a-hello-world-program.md
index 8cb794b97c38fb0ae33cc2c32b80370bb9245584..033f919351f898df2b656b5512bedf524a613adb 100644
--- a/en/device-dev/quick-start/running-a-hello-world-program.md
+++ b/en/device-dev/quick-start/running-a-hello-world-program.md
@@ -1,4 +1,4 @@
-# Running a Hello World Program
+# Running a Hello World Program
- [Modifying Source Code](#section79601457101015)
- [Debugging and Verification](#section1621064881419)
@@ -135,7 +135,7 @@ To parse the call stack information, the **Hi3861\_wifiiot\_app.asm** file is
3. Determine that an exception occurs in the **WadRecvCB** function based on the call stack information.
- 
+ 
4. Check and modify the code.
diff --git a/en/device-dev/quick-start/setting-up-the-environment-1.md b/en/device-dev/quick-start/setting-up-the-environment-1.md
deleted file mode 100644
index 49586bc1993e592982cc191d1e38c96a1eaa8b89..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/setting-up-the-environment-1.md
+++ /dev/null
@@ -1,151 +0,0 @@
-# Setting Up the Environment
-
-- [Environment Requirements](#section179175261196)
- - [Hardware](#section5840424125014)
- - [Software](#section965634210501)
-
-- [Installing Linux Build Tools](#section182916865219)
- - [Changing Linux Shell to Bash](#section1715027152617)
- - [Installing Basic Software Used for Compilation and Building \(Required Only for Ubuntu 20+\)](#section45512412251)
- - [Installing a File Packing Tool](#section1969111820270)
- - [Installing the JVM](#section1692618112713)
-
-
-## Environment Requirements
-
-### Hardware
-
-- Hi3516D V300 IoT camera development board
-- USB-to-serial cable and network cable \(The Windows workstation is connected to the Hi3516D V300 development board through the USB-to-serial cable and network cable.\)
-
-The following figure shows the hardware connections.
-
-**Figure 1** Hardware connections
-
-
-
-
-### Software
-
-> **NOTICE:**
->This section describes how to use an installation package to set up the compilation and development environment. If you are going to use Docker to set up the environment, skip this section and [Installing Linux Build Tools](#section182916865219).
-
-The following table describes the tools required for setting up the general environment for a Linux server of the Hi3516 development board and how to obtain these tools.
-
-**Table 1** Development tools and obtaining methods
-
-
-Development Tool
- |
-Description
- |
-How to Obtain
- |
-
|---|
-
-bash
- |
-Processes CLI commands.
- |
-System configuration
- |
-
-Basic software package for compilation and building (required only for Ubuntu 20+)
- |
-Provides a basic software package for compilation and building.
- |
-Internet
- |
-
-dosfstools, mtools, and mtd-utils
- |
-Pack files.
- |
-apt-get install
- |
-
-Java virtual machine (JVM)
- |
-Compiles, debugs, and runs Java programs.
- |
-apt-get install
- |
-
-
-
-
-## Installing Linux Build Tools
-
-> **NOTICE:**
->- If you acquire the source code using an HPM component or HPM CLI tool, you do not need to install compilation tools like **LLVM** and **hc-gen**.
->- \(Recommended\) If you obtain the source code through an image site or a code repository, you should install **hc-gen**. When installing the compilation tool, ensure that its environment variable path is unique.
-
-### Changing Linux Shell to Bash
-
-Check whether bash is used as the shell.
-
-```
-ls -l /bin/sh
-```
-
-If **/bin/sh -\> bash** is not displayed, do as follows to change shell to bash.
-
-**Method 1:** Run the following command on the device and then click **No**.
-
-```
-sudo dpkg-reconfigure dash
-```
-
-**Method 2:** Run the first command to delete **sh** and then run the second command to create a new soft link.
-
-```
-sudo rm -rf /bin/sh
-sudo ln -s /bin/bash /bin/sh
-```
-
-### Installing Basic Software Used for Compilation and Building \(Required Only for Ubuntu 20+\)
-
-Install the software.
-
-```
-sudo apt-get install build-essential && sudo apt-get install gcc && sudo apt-get install g++ && sudo apt-get install make && sudo apt-get install zlib* && sudo apt-get install libffi-dev
-```
-
-### Installing a File Packing Tool
-
-1. Start a Linux server.
-2. Install **dosfstools**.
-
- ```
- sudo apt-get install dosfstools
- ```
-
-3. Install **mtools**.
-
- ```
- sudo apt-get install mtools
- ```
-
-4. Install **mtd-utils**.
-
- ```
- sudo apt-get install mtd-utils
- ```
-
-
-### Installing the JVM
-
-1. Start a Linux server.
-2. Install the Java Runtime Environment \(JRE\).
-
- ```
- sudo apt-get install default-jre
- ```
-
-3. Install the Java Development Kit \(JDK\).
-
- ```
- sudo apt-get install default-jdk
- ```
-
-
diff --git a/en/device-dev/quick-start/setting-up-the-environment-2.md b/en/device-dev/quick-start/setting-up-the-environment-2.md
index 1c3604b02e1ab335b5ae9d4480b59826bccbe253..0e8430d75a7fa0bfe54420a0fcb8638108732710 100644
--- a/en/device-dev/quick-start/setting-up-the-environment-2.md
+++ b/en/device-dev/quick-start/setting-up-the-environment-2.md
@@ -1,4 +1,4 @@
-# Setting Up the Environment
+# Setting Up the Environment
- [Environment Requirements](#section179175261196)
- [Hardware](#section5840424125014)
diff --git a/en/device-dev/quick-start/setting-up-the-environment-3.md b/en/device-dev/quick-start/setting-up-the-environment-3.md
deleted file mode 100644
index 7f27e367398083b4f12aa2f2346b449b73d56109..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/setting-up-the-environment-3.md
+++ /dev/null
@@ -1,156 +0,0 @@
-# Setting Up the Environment
-
-- [Environment Requirements](#section1724111409282)
- - [Hardware](#section487353718276)
- - [Software Requirements](#section17315193935817)
-
-- [Installing Linux Build Tools](#section8831868501)
- - [Changing Linux Shell to Bash](#section1715027152617)
- - [Installing Basic Software Used for Compilation and Building \(Required Only for Ubuntu 20+\)](#section45512412251)
- - [Installing a File Packing Tool](#section1686964015274)
- - [Installing hc-gen](#section18706403274)
-
-
-## Environment Requirements
-
-### Hardware
-
-- Hi3518E V300 IoT camera development board
-- USB-to-serial cable and network cable \(The Windows workstation is connected to the Hi3518E V300 development board through the USB-to-serial cable and network cable.\)
-
- The following figure shows the hardware connections.
-
-
-**Figure 1** Hardware connections
-
-
-### Software Requirements
-
-> **NOTICE:**
->This section describes how to use an installation package to set up the compilation and development environment. If you are going to use Docker to set up the environment, skip this section and [Installing Linux Build Tools](#section8831868501).
-
-The following table describes the tools required for setting up the general environment for a Linux server of the Hi3518 development board and how to obtain these tools.
-
-**Table 1** Development tools and obtaining methods
-
-
-Development Tool
- |
-Description
- |
-How to Obtain
- |
-
|---|
-
-bash
- |
-Processes CLI commands.
- |
-System configuration
- |
-
-Basic software package for compilation and building (required only for Ubuntu 20+)
- |
-Provides a basic software package for compilation and building.
- |
-Internet
- |
-
-dosfstools, mtools, and mtd-utils
- |
-Pack files.
- |
-apt-get install
- |
-
-
-
-
-## Installing Linux Build Tools
-
-> **NOTICE:**
->- If you acquire the source code using an HPM component or HPM CLI tool, you do not need to install **hc-gen**.
->- \(Recommended\) If you obtain the source code through an image site or a code repository, you should install the compilation tool **hc-gen**. When installing the compilation tool, ensure that its environment variable path is unique.
-
-### Changing Linux Shell to Bash
-
-Check whether bash is used as the shell.
-
-```
-ls -l /bin/sh
-```
-
-If **/bin/sh -\> bash** is not displayed, do as follows to change shell to bash.
-
-**Method 1:** Run the following command on the device and then click **No**.
-
-```
-sudo dpkg-reconfigure dash
-```
-
-**Method 2:** Run the first command to delete **sh** and then run the second command to create a new soft link.
-
-```
-sudo rm -rf /bin/sh
-sudo ln -s /bin/bash /bin/sh
-```
-
-### Installing Basic Software Used for Compilation and Building \(Required Only for Ubuntu 20+\)
-
-Install the software.
-
-```
-sudo apt-get install build-essential && sudo apt-get install gcc && sudo apt-get install g++ && sudo apt-get install make && sudo apt-get install zlib* && sudo apt-get install libffi-dev
-```
-
-### Installing a File Packing Tool
-
-1. Start a Linux server.
-2. Install **dosfstools**.
-
- ```
- sudo apt-get install dosfstools
- ```
-
-3. Install **mtools**.
-
- ```
- sudo apt-get install mtools
- ```
-
-4. Install **mtd-utils**.
-
- ```
- sudo apt-get install mtd-utils
- ```
-
-
-### Installing hc-gen
-
-1. Start a Linux server.
-2. Download [hc-gen](https://repo.huaweicloud.com/harmonyos/compiler/hc-gen/0.65/linux/hc-gen-0.65-linux.tar).
-3. Decompress the hc-gen installation package to **\~/hc-gen** on the Linux server.
-
- ```
- tar -xvf hc-gen-0.65-linux.tar -C ~/
- ```
-
-4. Set an environment variable.
-
- ```
- vim ~/.bashrc
- ```
-
- Copy the following command to the last line of the **.bashrc** file, save the file, and exit.
-
- ```
- export PATH=~/hc-gen:$PATH
- ```
-
-5. Validate the environment variable.
-
- ```
- source ~/.bashrc
- ```
-
-
diff --git a/en/device-dev/quick-start/setting-up-the-environment-4.md b/en/device-dev/quick-start/setting-up-the-environment-4.md
index e8938baf915d5fc9fad719a6c46684307c607d56..606871622b0805662544e092fd9c1e64e4f1cb27 100644
--- a/en/device-dev/quick-start/setting-up-the-environment-4.md
+++ b/en/device-dev/quick-start/setting-up-the-environment-4.md
@@ -1,4 +1,4 @@
-# Setting Up the Environment
+# Setting Up the Environment
- [Environment Requirements](#section1724111409282)
- [Hardware](#section487353718276)
diff --git a/en/device-dev/quick-start/setting-up-the-environment.md b/en/device-dev/quick-start/setting-up-the-environment.md
index 382dc5ac66d2cd78bfb6bd1e307b9a362b1aafee..9eb8b040c6320fb44813778e45d0cfe647623a74 100644
--- a/en/device-dev/quick-start/setting-up-the-environment.md
+++ b/en/device-dev/quick-start/setting-up-the-environment.md
@@ -1,4 +1,4 @@
-# Setting Up the Environment
+# Setting Up the Environment
- [Environment Requirements](#section466851916410)
- [Hardware](#section19202111020215)
@@ -362,6 +362,6 @@ Perform the following operations on the Windows station.
2. Install the driver.
3. After the driver is installed, remove and then insert the USB cable. The serial port entry should be displayed as shown in the following figure.
- 
+ 
diff --git a/en/device-dev/quick-start/setting-up-ubuntu-development-environment-in-docker-mode-and-building-source-code.md b/en/device-dev/quick-start/setting-up-ubuntu-development-environment-in-docker-mode-and-building-source-code.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a3ca86c3294e3af31e06cd636d3c886c897ce94
--- /dev/null
+++ b/en/device-dev/quick-start/setting-up-ubuntu-development-environment-in-docker-mode-and-building-source-code.md
@@ -0,0 +1,118 @@
+# Setting Up Ubuntu Development Environment in Docker Mode and Building Source Code
+
+- [Obtaining Standard-System Source Code](#section8761819202511)
+ - [Prerequisites](#section102871547153314)
+ - [Procedure](#section429012478331)
+
+- [Obtaining the Docker Environment](#section181431248132513)
+- [Building Source Code](#section92391739152318)
+
+The standard OpenHarmony system provides a Docker environment which encapsulates build tools.
+
+> **NOTE:**
+>- Before using Docker, install it by following instructions in [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
+>- You can also use the [installation package](setting-up-ubuntu-development-environment-with-installation-package-and-building-source-code.md) to set up the Ubuntu development environment.
+
+## Obtaining Standard-System Source Code
+
+### Prerequisites
+
+1. Register your account with Gitee.
+2. Register an SSH public key for access to Gitee.
+3. Install the [git client](http://git-scm.com/book/en/v2/Getting-Started-Installing-Git) and [git-lfs](https://gitee.com/vcs-all-in-one/git-lfs?_from=gitee_search#downloading)), and configure basic user information.
+
+ ```
+ git config --global user.name "yourname"
+ git config --global user.email "your-email-address"
+ git config --global credential.helper store
+ ```
+
+4. Run the following commands to install the **repo** tool:
+
+ ```
+ 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
+ ```
+
+
+### Procedure
+
+Method 1 \(recommended\): Use the **repo** tool to download the source code over SSH. \(You must have registered an SSH public key for access to Gitee.\)
+
+```
+repo init -u git@gitee.com:openharmony/manifest.git -b master --no-repo-verify
+repo sync -c
+repo forall -c 'git lfs pull'
+```
+
+Method 2: Use the **repo** tool to download the source code over HTTPS.
+
+```
+repo init -u https://gitee.com/openharmony/manifest.git -b master --no-repo-verify
+repo sync -c
+repo forall -c 'git lfs pull'
+```
+
+## Obtaining the Docker Environment
+
+**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 Source Code
+
+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 product supported by the current distribution, for example, **Hi3516DV300**.
+
+ Files generated during the build 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.
+
+3. Burn the image. For details, see [Burning Images](burning-images.md).
+
+> **NOTE:**
+>You can exit Docker by simply running the **exit** command.
+
diff --git a/en/device-dev/quick-start/setting-up-ubuntu-development-environment-with-installation-package-and-building-source-code.md b/en/device-dev/quick-start/setting-up-ubuntu-development-environment-with-installation-package-and-building-source-code.md
new file mode 100644
index 0000000000000000000000000000000000000000..0aaa9188a038d1279efdb270e4ffc2ac04ea2273
--- /dev/null
+++ b/en/device-dev/quick-start/setting-up-ubuntu-development-environment-with-installation-package-and-building-source-code.md
@@ -0,0 +1,98 @@
+# Setting Up Ubuntu Development Environment with Installation Package and Building Source Code
+
+- [Installing Dependent Tools](#section18431165519244)
+- [Obtaining Standard-System Source Code](#section113751052102517)
+ - [Prerequisites](#section102871547153314)
+ - [Procedure](#section429012478331)
+
+- [Running prebuilts](#section0495320152619)
+- [Building Source Code](#section1664835963517)
+
+## Installing Dependent Tools
+
+The installation command is as follows:
+
+```
+sudo apt-get update && sudo apt-get install binutils git git-lfs gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip m4 bc gnutls-bin python3.8 python3-pip
+```
+
+> **NOTE:**
+>The preceding command is applicable to Ubuntu 18.04. For other Ubuntu versions, modify the preceding installation command based on the installation package name.
+
+## Obtaining Standard-System Source Code
+
+### Prerequisites
+
+1. Register your account with Gitee.
+2. Register an SSH public key for access to Gitee.
+3. Install the [git client](http://git-scm.com/book/en/v2/Getting-Started-Installing-Git) and [git-lfs](https://gitee.com/vcs-all-in-one/git-lfs?_from=gitee_search#downloading)), and configure basic user information.
+
+ ```
+ git config --global user.name "yourname"
+ git config --global user.email "your-email-address"
+ git config --global credential.helper store
+ ```
+
+4. Run the following commands to install the **repo** tool:
+
+ ```
+ 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
+ ```
+
+
+### Procedure
+
+Method 1 \(recommended\): Use the **repo** tool to download the source code over SSH. \(You must have registered an SSH public key for access to Gitee.\)
+
+```
+repo init -u git@gitee.com:openharmony/manifest.git -b master --no-repo-verify
+repo sync -c
+repo forall -c 'git lfs pull'
+```
+
+Method 2: Use the **repo** tool to download the source code over HTTPS.
+
+```
+repo init -u https://gitee.com/openharmony/manifest.git -b master --no-repo-verify
+repo sync -c
+repo forall -c 'git lfs pull'
+```
+
+## Running prebuilts
+
+Go to the root directory of the source code and run the following script to install the compiler and binary tool:
+
+```
+bash build/prebuilts_download.sh
+```
+
+By default, the downloaded prebuilts binary file is stored in **OpenHarmony\_2.0\_canary\_prebuilts** \(which is in the same directory as **OpenHarmony**\).
+
+## Building Source Code
+
+Perform the following operations in the Linux environment:
+
+1. Go to the root directory of the source code and run the following command to build the distribution.
+
+ ```
+ ./build.sh --product-name {product_name}
+ ```
+
+ **product\_name** indicates the product supported by the current distribution, for example, **Hi3516DV300**.
+
+2. Check the build result. After the build is complete, the following information is displayed in the log:
+
+ ```
+ build system image successful.
+ =====build Hi3516DV300 successful.
+ ```
+
+ Files generated during the build 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.
+
+ > **NOTE:**
+ >For details about module-specific build operations, see [Compilation and Building Overview](../subsystems/building-guidelines-for-the-standard-system.md).
+
+3. Burn the image. For details, see [Burning Images](burning-images.md).
+
diff --git a/en/device-dev/quick-start/windows-development-environment-10.md b/en/device-dev/quick-start/setting-up-windows-development-environment.md
similarity index 99%
rename from en/device-dev/quick-start/windows-development-environment-10.md
rename to en/device-dev/quick-start/setting-up-windows-development-environment.md
index 91c42c4f088d5f467479bb40cd1819e67277cfe4..4308389e169c415c5a502738359d0eed094fd3fc 100644
--- a/en/device-dev/quick-start/windows-development-environment-10.md
+++ b/en/device-dev/quick-start/setting-up-windows-development-environment.md
@@ -1,4 +1,4 @@
-# Windows Development Environment
+# Setting Up Windows Development Environment
- [Obtaining the Software](#en-us_topic_0000001058091994_section1483143015558)
- [Installing Visual Studio Code](#en-us_topic_0000001058091994_section71401018163318)
diff --git a/en/device-dev/quick-start/standard-system.md b/en/device-dev/quick-start/standard-system.md
index 33f6ed2a876d5ef8f93d7ee22c0546ea37ba9c67..f0aa95fdac24012324baa361c8958305bcfd436f 100644
--- a/en/device-dev/quick-start/standard-system.md
+++ b/en/device-dev/quick-start/standard-system.md
@@ -1,9 +1,15 @@
# Standard System
-- **[Overview](overview-7.md)**
+- **[Introduction](introduction.md)**
-- **[Environment Setup](environment-setup-8.md)**
+- **[Setting Up Windows Development Environment](setting-up-windows-development-environment.md)**
-- **[How to Develop](how-to-develop-12.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)**
diff --git a/en/device-dev/quick-start/ubuntu-build-environment-10.md b/en/device-dev/quick-start/ubuntu-build-environment-10.md
deleted file mode 100644
index 6b44c27dfc7b0a91a0564f60fd486865db8b242b..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/ubuntu-build-environment-10.md
+++ /dev/null
@@ -1,149 +0,0 @@
-# Ubuntu Build Environment
-
-- [Setting up a Ubuntu Build Environment Using a Docker Environment](#section1643363843714)
- - [Obtaining System Source Code](#section58448331029)
- - [Installing and Using the Docker Environment](#section22916211916)
-
-- [Setting up a Ubuntu Build Environment Using an Installation Package](#section25961010189)
- - [Obtaining Standard-System Source Code](#section15424183111912)
- - [Installing Dependent Tools](#section109262032104819)
- - [Obtaining prebuilts](#section16453104219209)
- - [Configuring the Node.js Environment and Obtaining the Node\_modules Dependency Package](#section133741330192119)
- - [Installing the hc-gen Tool](#section149281248182116)
-
-
-You can use either the Docker environment or installation package provided by OpenHarmony to set up a Ubuntu build environment. This section describes the two methods.
-
-## Setting up a Ubuntu Build Environment Using a Docker Environment
-
-The standard OpenHarmony system provides a Docker environment which encapsulates build tools. To use the Docker environment, perform the following steps:
-
-1. Obtain the system source code.
-2. Install and use the Docker environment.
-
-### Obtaining System Source Code
-
-For details, see [Source Code Acquisition](../get-code/source-code-acquisition.md).
-
-### Installing and Using the Docker Environment
-
-For details, see [Installing and Using Docker](../get-code/tool-acquisition.md).
-
-## Setting up a Ubuntu Build Environment Using an Installation Package
-
-The procedure is as follows:
-
-1. Obtain the system source code.
-2. Install dependent tools.
-3. Obtain prebuilts.
-4. Configure the Node.js environment and obtain the Node\_modules dependency package.
-5. Install the hc-gen tool.
-
-### Obtaining Standard-System Source Code
-
-For details, see [Source Code Acquisition](../get-code/source-code-acquisition.md).
-
-### Installing Dependent Tools
-
-The installation command is as follows:
-
-```
-sudo apt-get install binutils git-core git-lfs gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip m4 python2.7 python-minimal
-```
-
-### Obtaining prebuilts
-
-1. Go to the OpenHarmony working directory.
-
- ```
- cd OpenHarmony
- ```
-
-2. Download the script.
-
- ```
- curl https://gitee.com/landwind/script-tools/raw/master/Shell/OpenHarmony/OpenHarmony_2.0_canary_prebuilts_download.sh >./prebuilts_download.sh
- ```
-
-3. Download and decompress the prebuilts package in a specified directory.
-
- ```
- bash ./prebuilts_download.sh
- ```
-
- By default, binary files are stored in the **OpenHarmony\_2.0\_canary\_prebuilts** directory, which is in the same directory as **OpenHarmony**. To change the storage path, change the value of **bin\_dir** in **prebuilts\_download.sh**.
-
-4. Return to the previous directory.
-
- ```
- cd -
- ```
-
-
-### Configuring the Node.js Environment and Obtaining the Node\_modules Dependency Package
-
-To build the JS framework, you need to download and configure Node.js on a Linux server. The procedure is as follows:
-
-1. Download Node.js on a Linux server.
-
- ```
- mkdir -p OpenHarmony/prebuilts/build-tools/common/nodejs # Create the nodejs directory.
- cd OpenHarmony/prebuilts/build-tools/common/nodejs # Go to the nodejs directory.
- wget --no-check-certificate https://nodejs.org/download/release/v12.18.4/node-v12.18.4-linux-x64.tar.gz # Download the Node.js package.
- ```
-
-2. Decompress the Node.js package and configure the Node.js environment.
-
- ```
- tar -zxvf node-v12.18.4-linux-x64.tar.gz # Decompress the Node.js package.
- echo "export PATH=`pwd`/node-v12.18.4-linux-x64/bin:${PATH}" >> ~/.bashrc;source ~/.bashrc # Set a Node.js environment variable.
- cd - # Return to the previous directory.
- ```
-
-3. Go to the **third\_party/jsframework** directory of the OpenHarmony code and download the **node\_modules** package.
-
- ```
- cd OpenHarmony/third_party/jsframework # Go to the jsframework directory.
- npm install # Download the node_modules package.
- cd - # Return to the previous directory.
- ```
-
-4. Store the **node\_modules** package in the **prebuilts/build-tools/common/js-framework** directory of the OpenHarmony code.
-
- ```
- mkdir -p OpenHarmony/prebuilts/build-tools/common/js-framework # Create the js-framework directory.
- cp -rp OpenHarmony/third_party/jsframework/node_modules OpenHarmony/prebuilts/build-tools/common/js-framework/
- ```
-
-
-### Installing the hc-gen Tool
-
-hc-gen is used to compile the driver. To install hc-gen, perform the following steps:
-
-1. Start a Linux server.
-2. Download [hc-gen](https://repo.huaweicloud.com/harmonyos/compiler/hc-gen/0.65/linux/hc-gen-0.65-linux.tar).
-3. Decompress the hc-gen installation package to **\~/hc-gen** on the Linux server.
-
- ```
- tar -xvf hc-gen-0.65-linux.tar -C ~/
- ```
-
-4. Set an environment variable.
-
- ```
- vim ~/.bashrc
- ```
-
- Copy the following command to the last line of the **.bashrc** file, save the file, and exit.
-
- ```
- export PATH=~/hc-gen:$PATH
- ```
-
-5. Validate the environment variable.
-
- ```
- source ~/.bashrc
- ```
-
-
diff --git a/en/device-dev/quick-start/ubuntu-build-environment.md b/en/device-dev/quick-start/ubuntu-build-environment.md
index 918845d214738226770103a3581133f66d557cc1..50c25fe1ea26c3f94dae8ce906c188d01e604850 100644
--- a/en/device-dev/quick-start/ubuntu-build-environment.md
+++ b/en/device-dev/quick-start/ubuntu-build-environment.md
@@ -1,4 +1,4 @@
-# Ubuntu Build Environment
+# Ubuntu Build Environment
- [Obtaining Source Code and Tools](#section1897711811517)
- [Obtaining Source Code](#section1545225464016)
@@ -11,6 +11,9 @@
- [Installation Procedure](#section11518484814)
- [Uninstalling hb](#section3512551574)
+- [Installing Other Tools](#section830511218494)
+ - [Installation Procedure](#section54409586499)
+
Operating system: 64-bit version of Ubuntu 16.04 or later.
@@ -24,9 +27,9 @@ Perform the following steps to set up the build environment:
6. Install hb.
> **NOTICE:**
->- Docker is provided for the Ubuntu build environment, which encapsulates related build tools. If you use Docker to prepare the build environment, you do not need to perform the following steps in this section. Instead, refer to [Using Docker to Prepare the Build Environment](../get-code/tool-acquisition.md).
+>- Docker is provided for the Ubuntu build environment, which encapsulates related build tools. If you use Docker to prepare the build environment, you do not need to perform the following steps in this section. Instead, refer to [Using Docker to Prepare the Build Environment](../get-code/docker-environment.md).
>- By default, basic software, such as Samba and Vim, is installed in the system. Adaptation on the software is required to support file sharing between the Linux server and the Windows workstation.
->- For details about the compilation and building subsystem of OpenHarmony, see the [Compilation and Building Overview](../subsystems/compilation-and-building-overview.md).
+>- For details about the compilation and building subsystem of OpenHarmony, see the [Compilation and Building Overview](../subsystems/building-guidelines-for-mini-and-small-systems.md).
## Obtaining Source Code and Tools
@@ -79,10 +82,11 @@ The following table describes the tools and source code required for setting up
Functions as the compiler toolchain.
|
-For master and OpenHarmony_2.x branch/tag, please use v10.0.1 from the following link: https://repo.huaweicloud.com/harmonyos/compiler/clang/10.0.1-62608/linux/llvm.tar.gz
+ | For the master and OpenHarmony_v2.x branches and tags, use version 10.0.1:
+https://repo.huaweicloud.com/harmonyos/compiler/clang/10.0.1-62608/linux/llvm.tar.gz
|
-