diff --git a/en/device-dev/quick-start/Readme-EN.md b/en/device-dev/quick-start/Readme-EN.md
index 2afa83a8d1a6e0ea5e79f97018044f86e1be3a1f..faa682a677c3ad1523a3705b312f371755523fb0 100644
--- a/en/device-dev/quick-start/Readme-EN.md
+++ b/en/device-dev/quick-start/Readme-EN.md
@@ -7,14 +7,14 @@
- [Creating a Source Code Project](quickstart-ide-lite-create-project.md)
- Running a Hello World Program
- Hi3861 Development Board
- - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-application-framework.md)
+ - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-helloworld.md)
- [Building](quickstart-ide-lite-steps-hi3861-building.md)
- [Burning](quickstart-ide-lite-steps-hi3861-burn.md)
- [Networking](quickstart-ide-lite-steps-hi3861-netconfig.md)
- [Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md)
- [Running](quickstart-ide-lite-steps-hi3861-running.md)
- Hi3516 Development Board
- - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-application-framework.md)
+ - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-helloworld.md)
- [Building](quickstart-ide-lite-steps-hi3516-building.md)
- [Burning](quickstart-ide-lite-steps-hi3516-burn.md)
- [Running](quickstart-ide-lite-steps-hi3516-running.md)
@@ -28,7 +28,7 @@
- Running a Hello World Program
- Hi3861 Development Board
- [Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)
- - [Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md)
+ - [Writing a Hello World Program](quickstart-lite-steps-hi3861-helloworld.md)
- [Building](quickstart-lite-steps-hi3861-building.md)
- [Burning](quickstart-lite-steps-hi3861-burn.md)
- [Networking](quickstart-lite-steps-hi3861-netconfig.md)
@@ -36,7 +36,7 @@
- [Running](quickstart-lite-steps-hi3861-running.md)
- Hi3516 Development Board
- [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)
- - [Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)
+ - [Writing a Hello World Program](quickstart-lite-steps-hi3516-helloworld.md)
- [Building](quickstart-lite-steps-hi3516-building.md)
- [Burning](quickstart-lite-steps-hi3516-burn.md)
- [Running](quickstart-lite-steps-hi3516-running.md)
@@ -75,7 +75,7 @@
- [Setting Up Environments for Standard System](quickstart-standard-env-setup.md)
- Running a Hello World Program
- Hi3516 Development Board
- - [Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)
+ - [Writing a Hello World Program](quickstart-std-3516-create.md)
- [Building](quickstart-standard-running-hi3516-build.md)
- [Burning](quickstart-standard-running-hi3516-burning.md)
- [Running](quickstart-standard-running-hi3516-running.md)
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001226634716.png b/en/device-dev/quick-start/figures/en-us_image_0000001226634716.png
index 43d57194d46618a323c5a1505268d4e24c90aecb..9e53432ce41e67ee3e93e96d78262a6ace41d383 100644
Binary files a/en/device-dev/quick-start/figures/en-us_image_0000001226634716.png and b/en/device-dev/quick-start/figures/en-us_image_0000001226634716.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001226922302.png b/en/device-dev/quick-start/figures/en-us_image_0000001226922302.png
index 38083b2db3bf8a5c4bea42ab999f9d9047874650..7e136511b44f7b758ed4830ab20e58905a7cf241 100644
Binary files a/en/device-dev/quick-start/figures/en-us_image_0000001226922302.png and b/en/device-dev/quick-start/figures/en-us_image_0000001226922302.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001266887264.png b/en/device-dev/quick-start/figures/en-us_image_0000001266887264.png
new file mode 100644
index 0000000000000000000000000000000000000000..f931e2cfba06791a3891248c5d8e6a9f0e86bf0e
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001266887264.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001271354693.png b/en/device-dev/quick-start/figures/en-us_image_0000001271354693.png
index 02f74a108d5223682d57dc2e18aaefc3d31e6518..3e4d31eb90fc63376f511d0fb5320a69ee7af150 100644
Binary files a/en/device-dev/quick-start/figures/en-us_image_0000001271354693.png and b/en/device-dev/quick-start/figures/en-us_image_0000001271354693.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001271562433.png b/en/device-dev/quick-start/figures/en-us_image_0000001271562433.png
index a53ea2caebc1a5b7a630d312b60f79dc4ec845c7..e828c808f0fae09773a8408647a9e5386e4d6c21 100644
Binary files a/en/device-dev/quick-start/figures/en-us_image_0000001271562433.png and b/en/device-dev/quick-start/figures/en-us_image_0000001271562433.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001271594749.png b/en/device-dev/quick-start/figures/en-us_image_0000001271594749.png
index c323f6b9751b72f87eecdfe13c67da22395c3b43..edb1711f3c1fa906940d8cbb8d8fcdeb2badd2b6 100644
Binary files a/en/device-dev/quick-start/figures/en-us_image_0000001271594749.png and b/en/device-dev/quick-start/figures/en-us_image_0000001271594749.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001307019009.png b/en/device-dev/quick-start/figures/en-us_image_0000001307019009.png
new file mode 100644
index 0000000000000000000000000000000000000000..cee1d83517ee1fced5373f51cefb12e91346e947
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001307019009.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001312778829.png b/en/device-dev/quick-start/figures/en-us_image_0000001312778829.png
new file mode 100644
index 0000000000000000000000000000000000000000..15791ccc963502062bd54537567db8876d9d7b63
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001312778829.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001312780249.png b/en/device-dev/quick-start/figures/en-us_image_0000001312780249.png
new file mode 100644
index 0000000000000000000000000000000000000000..33827bef0cfc3dd949fd165883b05b7ca47dafb7
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001312780249.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001312898911.png b/en/device-dev/quick-start/figures/en-us_image_0000001312898911.png
new file mode 100644
index 0000000000000000000000000000000000000000..b048f3fda0aa3d64edffdd26948ef732bad31b17
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001312898911.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001312912501.png b/en/device-dev/quick-start/figures/en-us_image_0000001312912501.png
new file mode 100644
index 0000000000000000000000000000000000000000..550b0aed6cef3be1fed799052e78442335f92562
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001312912501.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_000000131299335.png b/en/device-dev/quick-start/figures/en-us_image_000000131299335.png
new file mode 100644
index 0000000000000000000000000000000000000000..8cc4a4837e321d0d13f8fa456194931874a4477a
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_000000131299335.png differ
diff --git a/en/device-dev/quick-start/quickstart-docker-lite.md b/en/device-dev/quick-start/quickstart-docker-lite.md
deleted file mode 100644
index 666b1510ff7b2346251cea45601e990ff5100d3e..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-docker-lite.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Getting Started with Mini and Small Systems (Installation Package Mode)
-
-
-
-- **[Mini and Small System Overview](quickstart-lite-overview.md)**
-
-- **[Setting Up Environments for the Mini and Small Systems](quickstart-lite-env-setup.md)**
-
-- **[Running a Hello World Program](quickstart-lite-steps.md)**
-
-- **[FAQs](quickstart-lite-env-setup-faqs.md)**
-
-- **[Appendix](quickstart-lite-appendix.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-appendix.md b/en/device-dev/quick-start/quickstart-ide-lite-appendix.md
deleted file mode 100644
index 0f1cbeb874d3e95c5e15881892b3c09bd1e9facc..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-appendix.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-ide-lite-board-introduction.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-board-introduction.md b/en/device-dev/quick-start/quickstart-ide-lite-board-introduction.md
deleted file mode 100644
index 9ebaa5683f1a0102675883058586145478e04f1e..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-board-introduction.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md)**
-
-- **[Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-create-project.md b/en/device-dev/quick-start/quickstart-ide-lite-create-project.md
index 37002b081cb5f699498cd8114ad89ee3a32ecece..48c917609e0edf4c194aa7e3d13c3c2d02c7ef19 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-create-project.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-create-project.md
@@ -1,4 +1,4 @@
-# Creating a Source Code Project
+# Importing a Source Code Project
After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-lite-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:
@@ -15,7 +15,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st
-3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
+3. If this is the first time you import a project, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md b/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md
index f274a5f0ee452334be8fa93eac3844c62c79e73c..1a9929dbdb0820f71c9ab5b0bc02808896319b44 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md
@@ -11,15 +11,18 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
- Windows: Windows 10 (64-bit)
-- Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher.
+- Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher
-- User name: cannot contain Chinese characters
+- User name (Ubuntu): cannot contain Chinese characters
- DevEco Device Tool: 3.0 Release
## Setting Up the Ubuntu Development Environment
+>  **NOTE**
+> If the Ubuntu system has not been set up yet, set it up on a virtual machine running Windows. Then, configure the Ubuntu basic environment.
+
1. Make sure the Ubuntu shell environment is **bash**.
1. Run the following command and check whether the command output is **bash**. If the command output is not **bash**, go to step 2.
@@ -55,14 +58,15 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name.
- >  **NOTE**
- > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
-
-
```
sudo ./devicetool-linux-tool-3.0.0.401.sh
```
-
+ >  **NOTE**
+ > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
+ >
+ > During the installation, the page for agreeing to the user agreement and privacy statement is displayed. Read and agree to the user agreement and privacy statement.
+ >
+ > If this page is not displayed and the installation exits, run the apt-get install whiptail command, then the installation command.
Wait until the "Deveco Device Tool successfully installed." message is displayed.
@@ -76,7 +80,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**.
-3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
+3. Set the installation path of DevEco Device Tool to a path that does not contain any Chinese characters, and then click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
>  **NOTE**
> If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version.
@@ -101,11 +105,14 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
-5. In the dialog box shown below, click **Next** to download and install the tools..
+5. In the dialog box shown below, click **Next**.
-6. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard.
+6. Read the user agreement and privacy statement carefully, select I accept the licenses, and click **Next**.
+
+ 
+7. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard.
@@ -174,29 +181,9 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
5. In the displayed dialog box, select **Linux**, select **Continue**, and enter the password for logging in to the remote computer.
+ >  **NOTE**
+ > To eliminate the need for frequently entering the password for logging in to the remote computer, set an SSH public key.
After the connection is successful, the plug-in is automatically installed in the .vscode-server folder on the remote computer. After the installation is complete, reload Visual Studio Code in Windows as prompted. Then you can develop, compile, and burn source code in DevEco Device Tool on Windows.
-
-
-### Registering the Public Key for Accessing the Ubuntu Environment
-
-After the preceding operations are complete, you can remotely connect to the Ubuntu environment through Windows for development. However, you need to frequently enter the remote connection password. To eliminate this need, you can use the SSH public key.
-
-1. Open the Git bash CLI and run the following command to generate an SSH public key. During command execution, perform operations as prompted. Set **username** and **ip** to the user name and IP address you use for connecting to the Ubuntu system.
-
- ```
- ssh-keygen -t rsa
- ssh-copy-id -i ~/.ssh/id_rsa.pub username@ip
- ```
-
- 
-
-2. In Visual Studio Code, click the remote connection setting button and open the **config** file.
-
- 
-
-3. In the **config** file, add the SSK key file information, as shown below. Then save the file.
-
- 
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md b/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md
deleted file mode 100644
index e7461bde3df8da9ca14f7c3cbac5c36d1a37b6c5..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Environment Preparation
-
-
-
-- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-lite-env-setup-win-ubuntu.md)**
-
-- **[Obtaining Source Code](quickstart-ide-lite-sourcecode-acquire.md)**
-
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md
index b32ea6e794af6c80dcd9059d70cbe8816906f1a7..7c7152e314a778176e2f51aaddaf3b87ac7eed44 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md
@@ -7,7 +7,7 @@ Hi3861 is a 2 x 5 cm development board. It is a 2.4 GHz WLAN SoC chip that highl
**Figure 1** Hi3861 development board
- 
+
The Hi3861 development board can also be connected to the Hi3861 mother board to expand its peripheral capabilities. The following figure shows the Hi3861 mother board.
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-overview.md b/en/device-dev/quick-start/quickstart-ide-lite-overview.md
index f23028f755bd48bb7c7f6ce8f1c05370551565ab..2b3ee5c0f0257ec2c4a3d29c41a922a62114923a 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-overview.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-overview.md
@@ -10,7 +10,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
- IDE mode: DevEco Device Tool is used for one-stop development, covering dependency installation, building, burning, and running.
- Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool.
- OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.
+ OpenHarmony also provides the [Docker environment](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.
This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-overview.md).
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md b/en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md
index 32fcdc946a307400c48ce0ac2000e6720c84ef8c..585abbbd7a71e674fe1b9f545b459d59db7d172b 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md
@@ -10,7 +10,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
2. Register an SSH public key for access to Gitee.
-3. Install the git client and git-lfs.
+3. Install the git client and git-lfs if they are unavailable.
Update the software source:
@@ -18,7 +18,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
sudo apt-get update
```
- Run the following command to install the tools:
+ Run the following command to install the tools:
```
sudo apt-get install git git-lfs
@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
```
-## Procedure
+## Obtaining Source Code
>  **NOTE**
> Download the master code if you want to get quick access to the latest features for your development. Download the release code, which is more stable, if you want to develop commercial functionalities.
@@ -70,7 +70,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
For details about how to obtain the source code of an OpenHarmony release, see the [Release-Notes](../../release-notes/Readme.md).
-## Running prebuilts
+### Running prebuilts
Go to the root directory of the source code and run the following script to install the compiler and binary tool:
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md
index 36a19432f9e567609a7c7a3b92d006d71a91ef2b..3368ed019c26a482af6ae90de4602c23a59a9a45 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md
@@ -1,70 +1,68 @@
# Burning
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
+
+
Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows.
1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md).
+ >  **NOTE**
+ > If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
+ >
+ > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
+ >
+ > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
-2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
+2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
- If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
- If  is displayed, click the connect icon.
- >  **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
+ >  **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
-3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
- >  **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/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
-
-4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
-5. On the **hi3516dv300** tab page, set the burning options.
-
+6. On the **hi3516dv300** tab page, set the burning options.
- **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**.
-6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
-
- 1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
-
- 
-
- 2. In **Partition Options**, modify the items selected in the preceding step.
-
- >  **NOTE**
- > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+7. In **Partitions**, check the preset burning settings of the files to be burnt.
- 
+ 
- 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
+ To modify the burning settings for a specific file, click  next to the file.
+ >  **NOTE**
+ > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
-7. When you finish modifying, click **Save** on the top.
+ 
-8. Go to **hi3516dv300** > **Upload** to start burning.
+8. When you finish modifying, click **Save** on the top.
- >  **NOTE**
- > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
+9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning.
- 
+ 
-9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
+10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning.
- 
+ 
- If the following message is displayed, it indicates that the burning is successful.
+ If the following message is displayed, it indicates that the burning is successful.
- 
+ 
-10. When the burning is successful, perform the operations in Running an Image to start the system.
+11. When the burning is successful, perform the operations in Running to start the system.
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md
index a12915d4e335fc2f520812f8ea988a126128ed4d..1aeccedcc5bdef184f7b27cb2f95940cd6699e18 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md
@@ -30,13 +30,13 @@ After burning is completed, you need to configure the bootloader to run the Open
After the system is started, perform the following steps to run the Hello World program:
1. Go to the **bin** directory on the startup page.
-
+
```
cd bin
```
2. Run the following command to run the **helloworld** program:
-
+
```
./helloworld
```
@@ -48,4 +48,4 @@ After the system is started, perform the following steps to run the Hello World
## Next
-Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](https://gitee.com/openharmony/docs/blob/master/en/device-dev/guide/device-camera.md) to better familiarize yourself with OpenHarmony development.
+Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](../guide/device-camera-control-overview.md) to better familiarize yourself with OpenHarmony development.
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516.md
deleted file mode 100644
index 30a1760dc180b69e062eb15d51e825422c246b46..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-application-framework.md)**
-
-- **[Building](quickstart-ide-lite-steps-hi3516-building.md)**
-
-- **[Burning](quickstart-ide-lite-steps-hi3516-burn.md)**
-
-- **[Running](quickstart-ide-lite-steps-hi3516-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md
index 72a07f63239b0a79da9958a8b1dc77fe964e51ab..aa19ccf3d77feb92aa41c127887d9a66ecadacc6 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md
@@ -1,12 +1,15 @@
# Burning
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
Hi3861 V100 supports burning through the serial port. To burn source code through the serial port in Windows, perform the following steps:
1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3861 V100 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3861.md).
-2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
+2. If your computer does not have the USB-to-serial driver, install it by following the instructions in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
+
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
- If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
- If  is displayed, click the connect icon.
@@ -16,18 +19,17 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
>  **NOTE**
> This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
-3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
- >  **NOTE**
- > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
+
-4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
-5. On the **hi3861** tab page, set the burning options.
+6. On the **hi3861** tab page, set the burning options.
- **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-serial**.
@@ -35,22 +37,24 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
-6. Check the preset information of the files to be burnt and modify them when necessary.
+7. In **Partitions**, check the preset burning settings of the files to be burnt.
+
+ 
- On the **hi3861_app** tab page, select **partition_bin** from **New Option**, and set the path of the file to be burnt.
+ To modify the burning settings for a specific file, click  next to the file.
- 
+ 
-7. When you finish modifying, click **Save** on the top.
+8. When you finish modifying, click **Save** on the top.
-8. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning.
+9. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning.
-9. When the following information is displayed, press the RST button on the development board to restart it.
+10. When the following information is displayed, press the RST button on the development board within 15 seconds to restart it.
-10. Wait until the burning is complete. When the following message is displayed, the burning is successful.
+ When the following message is displayed, the burning is successful.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861.md
deleted file mode 100644
index 76066f541d0deb0be63aa4906d7edcfe6cf4f769..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Hi3861 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-application-framework.md)**
-
-- **[Building](quickstart-ide-lite-steps-hi3861-building.md)**
-
-- **[Burning](quickstart-ide-lite-steps-hi3861-burn.md)**
-
-- **[Networking](quickstart-ide-lite-steps-hi3861-netconfig.md)**
-
-- **[Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md)**
-
-- **[Running](quickstart-ide-lite-steps-hi3861-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps.md b/en/device-dev/quick-start/quickstart-ide-lite-steps.md
deleted file mode 100644
index 65831aac645d6edc634eb405a6c1e15cfc55543c..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Running a Hello World Program
-
-
-
-- **[Hi3861 Development Board](quickstart-ide-lite-steps-hi3861.md)**
-
-- **[Hi3516 Development Board](quickstart-ide-lite-steps-hi3516.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-lite.md b/en/device-dev/quick-start/quickstart-ide-lite.md
deleted file mode 100644
index 46a6f375f13c4f6d751e9c5cab62e7671bddb63f..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-lite.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Getting Started with Mini and Small Systems (IDE Mode)
-
-
-
-- **[Mini and Small System Overview](quickstart-ide-lite-overview.md)**
-
-- **[Environment Preparation](quickstart-ide-lite-env-setup.md)**
-
-- **[Creating a Source Code Project](quickstart-ide-lite-create-project.md)**
-
-- **[Running a Hello World Program](quickstart-ide-lite-steps.md)**
-
-- **[Appendix](quickstart-ide-lite-appendix.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-appendix.md b/en/device-dev/quick-start/quickstart-ide-standard-appendix.md
deleted file mode 100644
index 6df76026c9e35f243e192e909e2bfefd441c8a74..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-appendix.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-ide-standard-board-introduction.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction.md b/en/device-dev/quick-start/quickstart-ide-standard-board-introduction.md
deleted file mode 100644
index a0ed1297124e19198467f2e0479f276a8622e052..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)**
-
-- **[Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-create-project.md b/en/device-dev/quick-start/quickstart-ide-standard-create-project.md
index 03bc00d5cb32ef6fcf29899302b60b0e96014332..b9e8bb5ad690c6bdf8ffca8711e786d19fc433cf 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-create-project.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-create-project.md
@@ -1,4 +1,4 @@
-# Creating a Source Code Project
+# Importing a Source Code Project
After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-standard-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:
@@ -23,7 +23,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st
-5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**. The following figure uses **Hi3516DV300** as an example.
+5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. The following figure uses **Hi3516DV300** as an example.
>  **NOTE**
> - Set **Product** to **Hi3516DV300** for the Hi3516D V300 development board.
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md b/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md
deleted file mode 100644
index 8faf2853a5d319958d0ebb4eeb6ebf1268cb0be0..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Environment Preparation
-
-
-
-- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)**
-
-- **[Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
index 8aedb9388c4562140134d5ca4b5ad777ebc1ca47..dad8d48305a2b4451e397e06f13aa5976446ca96 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
@@ -1,84 +1,70 @@
# Burning
-Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
-
-
->  **NOTE**
-> - If you are using source code from the master branch released since May 9, 2022, use HiTool for burning.
->
-> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
-
-
To burn source code to Hi3516D V300 through the USB port in Windows, perform the following steps:
->  **NOTE**
-> This feature is available in DevEco Device Tool 2.2 Beta2 and later versions.
-
-
1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md).
- >  **NOTE**
- >
- > If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
- >
- > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
- >
- > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
-
-2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
-
-3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
+2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
- If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
- If  is displayed, click the connect icon.
- >  **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
+ >  **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
+
+3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
-4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+ 
- 
+ >  **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/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
-5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
-6. On the **hi3516dv300** tab page, set the burning options.
+5. On the **hi3516dv300** tab page, set the burning options.
- - **upload_partitions**: Select the files to be burnt. By default, **fastboot**, **boot**, **updater**, **misc**, **system**, **vendor**, and **userdata** are burnt at the same time.
+ - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**.
- 
+ 
+
+6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
+
+ 1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
+
+ 
-7. In **Partitions**, check the preset burning settings of the files to be burnt.
+ 2. In **Partition Options**, modify the items selected in the preceding step.
- 
+ >  **NOTE**
+ > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
- To modify the burning settings for a specific file, click  next to the file.
+ 
- >  **NOTE**
- >
- > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+ 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
- 
+7. When you finish modifying, click **Save** on the top.
-8. When you finish modifying, click **Save** on the top.
+8. Go to **hi3516dv300** > **Upload** to start burning.
-9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning.
+ >  **NOTE**
+ > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
- 
+ 
-10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning.
+9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
- 
+ 
- If the following message is displayed, it indicates that the burning is successful.
+ If the following message is displayed, it indicates that the burning is successful.
- 
+ 
-11. When the burning is successful, perform the operations in Running to start the system.
+10. When the burning is successful, perform the operations in Running an Image to start the system.
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md
index 52b12f3716f63be76df71cd5c307f29ebd8a3ea6..cec86501be9781ff64a262e838e512e3afc4040d 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md
@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board.
The complete code directory is as follows:
-
+
```
applications/sample/hello
│── BUILD.gn
@@ -34,7 +34,7 @@ Perform the steps below in the source code directory:
Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program.
-
+
```
#include
#include "helloworld.h"
@@ -55,7 +55,7 @@ Perform the steps below in the source code directory:
Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows:
-
+
```
#ifndef HELLOWORLD_H
#define HELLOWORLD_H
@@ -78,7 +78,7 @@ Perform the steps below in the source code directory:
2. Create a build file.
1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows:
-
+
```
import("//build/ohos.gni") # Import the build template.
ohos_executable("helloworld") {# Executable module.
@@ -99,7 +99,7 @@ Perform the steps below in the source code directory:
}
```
2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows:
-
+
```
{
"name": "@ohos/hello",
@@ -141,7 +141,7 @@ Perform the steps below in the source code directory:
Add the configuration of the new subsystem to the **build/subsystem_config.json** file.
-
+
```
"sample": {
"path": "applications/sample/hello",
@@ -151,9 +151,9 @@ Perform the steps below in the source code directory:
4. Modify the product configuration file.
- In the **vendor\hisilicon\Hi3516DV300\config.json** file, add the **hello** part after the existing part.
+ In the vendor\hisilicon\Hi3516DV300\config.json file, add the hello part after the existing part.
-
+
```
"usb:usb_manager_native":{},
"applications:prebuilt_hap":{},
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516.md
deleted file mode 100644
index 32080c7b30f6aae5e5c41f49f132408b2f949905..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-standard-running-hi3516-create.md)**
-
-- **[Building](quickstart-ide-standard-running-hi3516-build.md)**
-
-- **[Burning](quickstart-ide-standard-running-hi3516-burning.md)**
-
-- **[Running](quickstart-ide-standard-running-hi3516-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
index 59e1747952f0c0ed699808d492d36ac19748fa34..8c342589b7bf22a9e519be85b816110d946cf109 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
@@ -1,39 +1,24 @@
# Burning
-Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
-
-
->  **NOTE**
-> - If you are using source code from the master branch released since May 9, 2022, use RKDevTool for burning.
->
-> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
-
-
1. [Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) **DriverInstall.exe**. Double-click **DriverInstall.exe** to open the installer. Then click the install button to install the USB driver as prompted.
- >  **NOTE**
+ >  **NOTE**
> If the burning tool of an earlier version has been installed, uninstall it first.
2. Connect the computer to the target development board through the USB port.
- >  **NOTE**
If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
- >
- > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
- >
- > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
-
-3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
- If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
- If  is displayed, click the connect icon.
- >  **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
+ >  **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
-4. Open DevEco Device Tool, choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
@@ -44,28 +29,32 @@ Burning is the process of downloading compiled program files to a development bo
-6. In **Partitions**, check the preset burning settings of the files to be burnt.
+6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **loader**, **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata**.
- 
+ 1. On the **hh_scdy200_loader** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
- To modify the burning settings for a specific file, click  next to the file.
- >  **NOTE**
- >
- > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+ 
- 
+ 2. In **Partition Options**, modify the items selected in the preceding step.
+
+ >  **NOTE**
+ > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+
+ 
+
+ 3. Follow the same procedure to modify the information about the **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata** files.
7. When you finish modifying, click **Save** on the top.
-8. Choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
+8. Click **Open** to open the project file. Click  to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
9. If the message "Operation paused, Please press Enter key to continue" is displayed, press **Enter**.
- >  **NOTE**
If the message "The board is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
- >
+ >  **NOTE**
+ > If the message "The boad is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
-Wait until the burning is complete. If the following message is displayed, the burning is successful.
-
-
+10. Wait until the burning is complete. If the following message is displayed, the burning is successful.
+
+ 
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md
index 3f90e295cc6522bde5c430a8ef3d78ca8e9d52b1..6025ddf56951d33a8b0205f2368255273430f753 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md
@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board.
The complete code directory is as follows:
-
+
```
applications/sample/hello
│── BUILD.gn
@@ -33,7 +33,7 @@ Perform the steps below in the source code directory:
Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program.
-
+
```
#include
#include "helloworld.h"
@@ -54,7 +54,7 @@ Perform the steps below in the source code directory:
Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows:
-
+
```
#ifndef HELLOWORLD_H
#define HELLOWORLD_H
@@ -77,7 +77,7 @@ Perform the steps below in the source code directory:
2. Create a build file.
1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows:
-
+
```
import("//build/ohos.gni") # Import the build template.
ohos_executable("helloworld") {# Executable module.
@@ -98,7 +98,7 @@ Perform the steps below in the source code directory:
}
```
2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows:
-
+
```
{
"name": "@ohos/hello",
@@ -140,7 +140,7 @@ Perform the steps below in the source code directory:
Add the configuration of the new subsystem to the **build/subsystem_config.json** file.
-
+
```
"sample": {
"path": "applications/sample/hello",
@@ -150,7 +150,7 @@ Perform the steps below in the source code directory:
4. Modify the product configuration file.
- In the **vendor\hihope\rk3568\config.json** file, add the **hello** part after the existing part.
+ In the vendor\hihope\rk3568\config.json file, add the hello part after the existing part.
```
"usb:usb_manager_native":{},
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568.md
deleted file mode 100644
index 8ffc858557242c87460d2476a3aa26f2649d9304..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# RK3568 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-standard-running-rk3568-create.md)**
-
-- **[Building](quickstart-ide-standard-running-rk3568-build.md)**
-
-- **[Burning](quickstart-ide-standard-running-rk3568-burning.md)**
-
-- **[Running](quickstart-ide-standard-running-rk3568-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running.md b/en/device-dev/quick-start/quickstart-ide-standard-running.md
deleted file mode 100644
index 2a3ff8023f3508de5314490099c7be73b44ba098..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-ide-standard-running.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Running a Hello World Program
-
-
-
-- **[Hi3516 Development Board](quickstart-ide-standard-running-hi3516.md)**
-
-- **[RK3568 Development Board](quickstart-ide-standard-running-rk3568.md)**
diff --git a/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md b/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md
index 6e0f345c7b9d5749b296c8be584db6ad5e0c68a4..c84614b09578234a33cbec7223e1f88e93abbb77 100644
--- a/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md
+++ b/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md
@@ -4,7 +4,7 @@
In the Ubuntu environment, perform the following steps to obtain the OpenHarmony source code:
-## Preparations
+## Before You Start
1. Register your account with Gitee.
@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
```
-## Procedure
+## Obtaining Source Code
>  **NOTE**
> Download the master code if you want to get quick access to the latest features for your development. Download the release code, which is more stable, if you want to develop commercial functionalities.
diff --git a/en/device-dev/quick-start/quickstart-lite-appendix.md b/en/device-dev/quick-start/quickstart-lite-appendix.md
deleted file mode 100644
index e63539f9355627c8da77419114f565b28fb908a1..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-appendix.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-lite-board-introduction.md)**
-
-- **[Reference](quickstart-lite-reference.md)**
diff --git a/en/device-dev/quick-start/quickstart-lite-board-introduction.md b/en/device-dev/quick-start/quickstart-lite-board-introduction.md
deleted file mode 100644
index 30c06d28ebcb235c3677f625173e769ec8411c0b..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-board-introduction.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md)**
-
-- **[Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md)**
diff --git a/en/device-dev/quick-start/quickstart-lite-env-setup-faqs.md b/en/device-dev/quick-start/quickstart-lite-env-setup-faqs.md
deleted file mode 100644
index ff4411ade6d31c0a3e283c532a25235a41c51561..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-env-setup-faqs.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# FAQs
-
-
-
-- **[Fixing hb Installation Issues](quickstart-lite-faq-hb.md)**
-
-- **[Fixing Compilation Issues](quickstart-lite-faq-compose.md)**
-
-- **[Fixing Burning Issues](quickstart-lite-faq-burning.md)**
diff --git a/en/device-dev/quick-start/quickstart-lite-env-setup.md b/en/device-dev/quick-start/quickstart-lite-env-setup.md
index e3e2272b3d6bf18186391a56c0c14dd35f3a4fa2..894e3d8b8fb99afcfd005fa232c0945b0e990315 100644
--- a/en/device-dev/quick-start/quickstart-lite-env-setup.md
+++ b/en/device-dev/quick-start/quickstart-lite-env-setup.md
@@ -278,7 +278,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
```
-### Procedure
+### Obtaining Source Code
>  **NOTE**
> Download the master code if you want to get quick access to the latest features for your development. Download the release code, which is more stable, if you want to develop commercial functionalities.
@@ -309,7 +309,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
### Running prebuilts
-Go to the root directory of the source code and run the following script to install the compiler and binary tool:
+ 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
diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md
index ee5350b8a1166fda8273dd44fb98d8b305480300..9e453a954d7a3ee8a1e8ec5676c39e8ef30d0ca1 100644
--- a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md
+++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md
@@ -1,7 +1,7 @@
# Burning
-Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows.
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
### Importing Source Code
@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu
-5. On the **Import Project** page, select **ipcamera_hispark_taurus** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**.
+5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. Select **ipcamera_hispark_taurus**.
diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3516.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3516.md
deleted file mode 100644
index 0f6d8e0c88d63e24187add3cc4478b673179c174..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-steps-hi3516.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Hi3516 Development Board
-
-
-
-- **[Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)**
-
-- **[Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)**
-
-- **[Building](quickstart-lite-steps-hi3516-building.md)**
-
-- **[Burning](quickstart-lite-steps-hi3516-burn.md)**
-
-- **[Running](quickstart-lite-steps-hi3516-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md
index 2a76953abeebbff57fbd916f2f05baeca250f91c..46974e89328fec671bae02e748ea393b1d147914 100644
--- a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md
+++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md
@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu
-5. On the **Import Project** page, select **wifiiot_hispark_pegasus** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**.
+5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. Select **wifiiot_hispark_pegasus**.
diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3861.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3861.md
deleted file mode 100644
index 0f637821f518c0edcced32f369eb09eb594990c7..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-steps-hi3861.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Hi3861 Development Board
-
-
-
-- **[Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)**
-
-- **[Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md)**
-
-- **[Building](quickstart-lite-steps-hi3861-building.md)**
-
-- **[Burning](quickstart-lite-steps-hi3861-burn.md)**
-
-- **[Networking](quickstart-lite-steps-hi3861-netconfig.md)**
-
-- **[Debugging and Verification](quickstart-lite-steps-hi3861-debug.md)**
-
-- **[Running](quickstart-lite-steps-hi3861-running.md)**
-
diff --git a/en/device-dev/quick-start/quickstart-lite-steps.md b/en/device-dev/quick-start/quickstart-lite-steps.md
deleted file mode 100644
index 06ff9266b6e141eba935c90c690fc0405f4dae28..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-lite-steps.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Running a Hello World Program
-
-
-
-- **[Hi3861 Development Board](quickstart-lite-steps-hi3861.md)**
-
-- **[Hi3516 Development Board](quickstart-lite-steps-hi3516.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-appendix.md b/en/device-dev/quick-start/quickstart-standard-appendix.md
deleted file mode 100644
index 12642666b4a8b2a5000900fe078ad57805e8bc07..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-appendix.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-standard-board-introduction.md)**
-
-- **[Reference](quickstart-standard-reference.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-board-introduction.md b/en/device-dev/quick-start/quickstart-standard-board-introduction.md
deleted file mode 100644
index c339e4d8b9ad0f5df373b6a9a0d12099f1df9dcf..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-board-introduction.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)**
-
-- **[Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-docker.md b/en/device-dev/quick-start/quickstart-standard-docker.md
deleted file mode 100644
index 9c3eee01247037c1b019d260d7e09068045f0013..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-docker.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Getting Started with Standard System (Using the Installation Package)
-
-
-
-- **[Standard System Overview](quickstart-standard-overview.md)**
-
-- **[Setting Up Environments for Standard System](quickstart-standard-env-setup.md)**
-
-- **[Running a Hello World Project](quickstart-standard-running.md)**
-
-- **[FAQs](quickstart-standard-faqs.md)**
-
-- **[Appendix](quickstart-standard-appendix.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-env-setup.md b/en/device-dev/quick-start/quickstart-standard-env-setup.md
index 16b435d2b72fe59de7dc9bf64571e8f09f9fe2b7..9b55be45cee8bab38bcc23b23558f9b8d3806c16 100644
--- a/en/device-dev/quick-start/quickstart-standard-env-setup.md
+++ b/en/device-dev/quick-start/quickstart-standard-env-setup.md
@@ -32,14 +32,13 @@ In Ubuntu:
> - Java 8 or later is required. This section uses Java 8 as an example.
2. Set Python 3.8 as the default Python version.
-
-Check the location of Python 3.8:
-
+ Check the location of Python 3.8:
+
```
which python3.8
-```
-
+ ```
+
Change python and python3 to python3.8.
```
@@ -268,7 +267,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
```
-### Procedure
+### Obtaining Source Code
>  **NOTE**
> Download the master code if you want to get quick access to the latest features for your development. Download the release code, which is more stable, if you want to develop commercial functionalities.
@@ -299,7 +298,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
### Running prebuilts
-Go to the root directory of the source code and run the following script to install the compiler and binary tool:
+ 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
diff --git a/en/device-dev/quick-start/quickstart-standard-faqs.md b/en/device-dev/quick-start/quickstart-standard-faqs.md
deleted file mode 100644
index e4c33d7f1f467dbf995cfab823281b0791a45c64..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-faqs.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# FAQs
-
-
-
-- **[Fixing hb Installation Issues](quickstart-standard-faq-hb.md)**
-
-- **[Fixing Compilation Issues](quickstart-standard-faq-compose.md)**
-
-- **[Fixing Burning Issues](quickstart-standard-faq-burning.md)**
-
diff --git a/en/device-dev/quick-start/quickstart-standard-ide.md b/en/device-dev/quick-start/quickstart-standard-ide.md
deleted file mode 100644
index 034c53890ad98ed1bbad80cfadc6a8a971d5f397..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-ide.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Getting Started with Standard System (IDE Mode)
-
-
-
-- **[Standard System Overview](quickstart-ide-standard-overview.md)**
-
-- **[Environment Preparation](quickstart-ide-standard-env-setup.md)**
-
-- **[Creating a Source Code Project](quickstart-ide-standard-create-project.md)**
-
-- **[Running a Hello World Program](quickstart-ide-standard-running.md)**
-
-- **[Appendix](quickstart-ide-standard-appendix.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md
index 002f344776374b50a87c7d143210c4785712c59c..7b170d1e45d1e6670a75af371e5c313a51eb65b3 100644
--- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md
+++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md
@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
1. Set the build path.
-
+
```
hb set
```
2. Select the current path.
-
+
```
.
```
-3. Select **hispark_taurus_standard** under **hisilicon** and press **Enter**.
+3. Select **Hi3516D V300** under **built-in** and press **Enter**.
4. Start building.
@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
>
> This example builds a product from the scratch.
-
+
```
hb build -f
```
-
+
**Figure 1** Hi3516 build settings
diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md
index 1f17ffc4a6591e60444c423d77f472538ff01d9f..4c1e34c22be466aca3721ac696aa6ae306eae58b 100644
--- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md
+++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md
@@ -1,110 +1,104 @@
# Burning
-Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
-
-
->  **NOTE**
-> - If you are using source code from the master branch released since May 9, 2022, use HiTool for burning.
->
-> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
-
-
To burn source code to Hi3516D V300 through the USB port in Windows, perform the following steps.
-## Importing Source Code
+### Importing Source Code
-[Ensure that the Windows system can remotely access the Ubuntu environment](../quick-start/quickstart-standard-env-setup.md), and then perform the following steps to import source code:
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-standard-env-setup.md). Then, perform the following steps to import the source code before burning:
1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code.
- 
+ 
2. Select the target directory (in the Ubuntu environment) and click **Import**.
- >  **NOTE**
- > Make sure the selected directory does not contain Chinese characters or spaces.
- 
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail.
+
+ 
-3. If this is the first time you import the source code, the following dialog box will be displayed. Click **Import** when prompted.
+3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
- 
+ 
4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
-5. On the **Import Project** page, select **Hi3516DV300** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**.
+5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. In the figure below, **Hi3516DV300** is used as an example.
- 
+ 
6. Click **Open** to open the project or source code.
-## Burning
+### Burning
After the source code is imported, perform the following steps:
->  **NOTE**
-> This feature is available in DevEco Device Tool 2.2 Beta2 and later versions.
-
1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md).
- >  **NOTE**
- > If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
- >
- > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
- >
- > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
-2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
+2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
-3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
- If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
- If  is displayed, click the connect icon.
- >  **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
+ >  **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
-4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
- 
+ 
-5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+ >  **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/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
+
+4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
-6. On the **hi3516dv300** tab page, set the burning options.
- - **upload_partitions**: Select the files to be burnt. By default, **fastboot**, **boot**, **updater**, **misc**, **system**, **vendor**, and **userdata** are burnt at the same time.
+5. On the **hi3516dv300** tab page, set the burning options.
+
+ - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**.
- 
+ 
+
+6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
+
+ 1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
+
+ 
+
+ 2. In **Partition Options**, modify the items selected in the preceding step.
-7. In **Partitions**, check the preset burning settings of the files to be burnt.
+ >  **NOTE**
+ > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
- 
+ 
- To modify the burning settings for a specific file, click  next to the file.
- >  **NOTE**
- > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+ 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
- 
+7. When you finish modifying, click **Save** on the top.
-8. When you finish modifying, click **Save** on the top.
+8. Go to **hi3516dv300** > **Upload** to start burning.
-9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning.
+ >  **NOTE**
+ > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
- 
+ 
-10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning.
+9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
- 
+ 
- If the following message is displayed, it indicates that the burning is successful.
+ If the following message is displayed, it indicates that the burning is successful.
- 
+ 
-11. When the burning is successful, perform the operations in Running to start the system.
+10. When the burning is successful, perform the operations in Running an Image to start the system.
diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516.md
deleted file mode 100644
index e85603a4bcf66366ee435fe6ffc744c2f4385691..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-running-hi3516.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)**
-
-- **[Building](quickstart-standard-running-hi3516-build.md)**
-
-- **[Burning](quickstart-standard-running-hi3516-burning.md)**
-
-- **[Running](quickstart-standard-running-hi3516-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-running-rk3568-build.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-build.md
index 0e0beb671a570629e75c6adf7bd6e1518f55adab..7d1ad531ba40dec89afb7181ba192c4617d62bd4 100644
--- a/en/device-dev/quick-start/quickstart-standard-running-rk3568-build.md
+++ b/en/device-dev/quick-start/quickstart-standard-running-rk3568-build.md
@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
1. Set the build path.
-
+
```
hb set
```
2. Select the current path.
-
+
```
.
```
-3. Select **rk3568** under **hihope** and press **Enter**.
+3. Select **rk3568** under **built-in** and press **Enter**.
4. Start building.
@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
>
> This example builds a product from the scratch.
-
+
```
hb build -f
```
-
+
**Figure 1** RK3568 build settings
diff --git a/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md
index 509d6d54bcc852241b29c65b59faa24fe1634c57..d17d3881e3a921f358e502272bd87ab8d6521cd0 100644
--- a/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md
+++ b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md
@@ -1,78 +1,60 @@
# Burning
-Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
-
-
->  **NOTE**
-> - If you are using source code from the master branch released since May 9, 2022, use RKDevTool for burning.
->
-> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
-
-
To burn source code to RK3568 on Windows, perform the following steps:
-## Importing Source Code
+### Importing Source Code
-[Ensure that the Windows system can remotely access the Ubuntu environment](../quick-start/quickstart-standard-env-setup.md), and then perform the following steps to import source code:
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-standard-env-setup.md). Then, perform the following steps to import the source code before burning:
1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code.
- 
+ 
2. Select the target directory (in the Ubuntu environment) and click **Import**.
- >  **NOTE**
- > Make sure the selected directory does not contain Chinese characters or spaces.
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail.
- 
+ 
-3. If this is the first time you import the source code, the following dialog box will be displayed. Click **Import** when prompted.
+3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
- 
+ 
4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
-5. On the **Import Project** page, select **rk3568** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**.
+5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. Select **rk3568**.
- 
+ 
6. Click **Open** to open the project or source code.
-## Burning
+### Burning
After the source code is imported, perform the following steps:
1. [Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) **DriverInstall.exe**. Double-click **DriverInstall.exe** to open the installer. Then click the install button to install the USB driver as prompted.
-
- > **NOTE**
+ >  **NOTE**
> If the burning tool of an earlier version has been installed, uninstall it first.
2. Connect the computer to the target development board through the USB port.
- >  **NOTE**
- >
- > If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
- >
- > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
- >
- > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
-3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
-
- - If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
+ - If  is displayed on the right of **Local PC**, the remote computer is connected to the local computer. Inthis case, no further action is required.
- If  is displayed, click the connect icon.
- >  **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
+ >  **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
-4. Open DevEco Device Tool, choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
@@ -83,29 +65,32 @@ After the source code is imported, perform the following steps:
-6. In **Partitions**, check the preset burning settings of the files to be burnt.
+6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **loader**, **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata**.
+
+ 1. On the **hh_scdy200_loader** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
- 
+ 
- To modify the burning settings for a specific file, click  next to the file.
+ 2. In **Partition Options**, modify the items selected in the preceding step.
- >  **NOTE**
- > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+ >  **NOTE**
+ > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
- 
+ 
+
+ 3. Follow the same procedure to modify the information about the **parameter**, **uboot**, **boot_linuxv, **system**, **vendor**, and **userdata** files.
7. When you finish modifying, click **Save** on the top.
-8. Choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
+8. Click **Open** to open the project file. Click  to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
9. If the message "Operation paused, Please press Enter key to continue" is displayed, press **Enter**.
- >  **NOTE**
If the message "The board is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
- >
+ >  **NOTE**
+ > If the message "The boad is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
+10. Wait until the burning is complete. If the following message is displayed, the burning is successful.
-Wait until the burning is complete. If the following message is displayed, the burning is successful.
-
-
+ 
diff --git a/en/device-dev/quick-start/quickstart-standard-running-rk3568.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568.md
deleted file mode 100644
index c13877b26bb7cd3b50ec6e9970d3238db6c59bc1..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-running-rk3568.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# RK3568 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-standard-running-rk3568-create.md)**
-
-- **[Building](quickstart-standard-running-rk3568-build.md)**
-
-- **[Burning](quickstart-standard-running-rk3568-burning.md)**
-
-- **[Running](quickstart-standard-running-rk3568-running.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-running.md b/en/device-dev/quick-start/quickstart-standard-running.md
deleted file mode 100644
index 7bde76093cd3c045e32170c48de635388bcd7e0d..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart-standard-running.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Running a Hello World Program
-
-
-
-- **[Hi3516 Development Board](quickstart-standard-running-hi3516.md)**
-
-- **[RK3568 Development Board](quickstart-standard-running-rk3568.md)**
diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md b/en/device-dev/quick-start/quickstart-std-3516-create.md
similarity index 100%
rename from en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md
rename to en/device-dev/quick-start/quickstart-std-3516-create.md
diff --git a/en/device-dev/quick-start/quickstart.md b/en/device-dev/quick-start/quickstart.md
deleted file mode 100644
index 13fe6384e1491db3a347b4ef5784e37a75fd37a9..0000000000000000000000000000000000000000
--- a/en/device-dev/quick-start/quickstart.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Getting Started
-
-
-
-- **[Getting Started with Mini and Small Systems](quickstart-lite.md)**
-
-- **[Getting Started with Standard System](quickstart-standard.md)**
diff --git a/en/device-dev/website.md b/en/device-dev/website.md
index 57de9133c39ad64212a6fb1f8f0171999814f16b..7aa6c47b823301d3554a80d04b2c6f9a0c466270 100644
--- a/en/device-dev/website.md
+++ b/en/device-dev/website.md
@@ -76,7 +76,7 @@
- [Setting Up Environments for Standard System](quick-start/quickstart-standard-env-setup.md)
- Running a Hello World Program
- Hi3516 Development Board
- - [Writing a Hello World Program](quick-start/quickstart-standard-running-hi3516-create.md)
+ - [Writing a Hello World Program](quick-start/quickstart-std-3516-create.md)
- [Building](quick-start/quickstart-standard-running-hi3516-build.md)
- [Burning](quick-start/quickstart-standard-running-hi3516-burning.md)
- [Running](quick-start/quickstart-standard-running-hi3516-running.md)