diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001177478136.png b/en/device-dev/quick-start/figures/en-us_image_0000001177478136.png
new file mode 100644
index 0000000000000000000000000000000000000000..fcaf25e47e2e47ecad8aebe463aeccdf1d8bf85e
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001177478136.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001235266636.png b/en/device-dev/quick-start/figures/en-us_image_0000001235266636.png
new file mode 100644
index 0000000000000000000000000000000000000000..c55a6ddd1aa319adfa05987ff3f5c79231e7208d
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001235266636.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001264982466.png b/en/device-dev/quick-start/figures/en-us_image_0000001264982466.png
new file mode 100644
index 0000000000000000000000000000000000000000..1b65359c06202a8c394b2415865a9639e0d9bffd
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001264982466.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001265041892.png b/en/device-dev/quick-start/figures/en-us_image_0000001265041892.png
new file mode 100644
index 0000000000000000000000000000000000000000..175094e3de4ad493ab634061f4280f57a6a128bf
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001265041892.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001265201928.png b/en/device-dev/quick-start/figures/en-us_image_0000001265201928.png
new file mode 100644
index 0000000000000000000000000000000000000000..7480c81115dedf35cc0d1f74900ff1ba81571d89
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001265201928.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001265361888.png b/en/device-dev/quick-start/figures/en-us_image_0000001265361888.png
new file mode 100644
index 0000000000000000000000000000000000000000..b048f3fda0aa3d64edffdd26948ef732bad31b17
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001265361888.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001267532292.png b/en/device-dev/quick-start/figures/en-us_image_0000001267532292.png
new file mode 100644
index 0000000000000000000000000000000000000000..8ed1535a6bc23dc5bd02fbd5a3f1392f46ad8d83
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001267532292.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001267932252.png b/en/device-dev/quick-start/figures/en-us_image_0000001267932252.png
new file mode 100644
index 0000000000000000000000000000000000000000..c1816c41bceaeeca5385b6353ef94576db30d84a
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001267932252.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001278358765.png b/en/device-dev/quick-start/figures/en-us_image_0000001278358765.png
new file mode 100644
index 0000000000000000000000000000000000000000..96b251c58071d4203ff51f28317f378d6ec71ebb
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001278358765.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001279426717.png b/en/device-dev/quick-start/figures/en-us_image_0000001279426717.png
new file mode 100644
index 0000000000000000000000000000000000000000..53cbcb8b0d0c30cb289b746d20b6c73927019d1a
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001279426717.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_000000127958708.png b/en/device-dev/quick-start/figures/en-us_image_000000127958708.png
new file mode 100644
index 0000000000000000000000000000000000000000..0e1bebbb79fd4281b41173171d4a96fb0e84c166
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_000000127958708.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001312541849.png b/en/device-dev/quick-start/figures/en-us_image_0000001312541849.png
new file mode 100644
index 0000000000000000000000000000000000000000..b423de5e8231bef79979b09d09d600e3d2a8adaa
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001312541849.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001314076609.png b/en/device-dev/quick-start/figures/en-us_image_0000001314076609.png
new file mode 100644
index 0000000000000000000000000000000000000000..27fe1d133a31b275a2788cab1f5b37dd3450a7df
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001314076609.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001315910101.png b/en/device-dev/quick-start/figures/en-us_image_0000001315910101.png
new file mode 100644
index 0000000000000000000000000000000000000000..c1816c41bceaeeca5385b6353ef94576db30d84a
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001315910101.png differ
diff --git a/en/device-dev/quick-start/figures/en-us_image_0000001315932049.png b/en/device-dev/quick-start/figures/en-us_image_0000001315932049.png
new file mode 100644
index 0000000000000000000000000000000000000000..8ed1535a6bc23dc5bd02fbd5a3f1392f46ad8d83
Binary files /dev/null and b/en/device-dev/quick-start/figures/en-us_image_0000001315932049.png differ
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 3ac2873105b2f43ad674ea99d4b698a5f5940451..03bc00d5cb32ef6fcf29899302b60b0e96014332 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
@@ -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 **ohosVersion**. 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 **Ohos Ver**. 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-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
index dad8d48305a2b4451e397e06f13aa5976446ca96..8aedb9388c4562140134d5ca4b5ad777ebc1ca47 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,70 +1,84 @@
# 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).
-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).
+ >  **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).
- 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.
-
-3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+ >  **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.
- 
+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_partitions**: Select the files to be burnt. By default, **fastboot**, **boot**, **updater**, **misc**, **system**, **vendor**, and **userdata** 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.
- 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
+ >  **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-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
index 8c342589b7bf22a9e519be85b816110d946cf109..59e1747952f0c0ed699808d492d36ac19748fa34 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,24 +1,39 @@
# 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.
-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).
+ >  **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).
- 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.
-4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
+4. Open DevEco Device Tool, choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
@@ -29,32 +44,28 @@
-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**.
+6. In **Partitions**, check the preset burning settings of the files to be burnt.
- 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. Click **Open** to open the project file. Click  to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
+8. 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 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.
+ >  **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.
+ >
-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-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md
index cd0b1434eb03b1f237c69eb3dc1b4a5a66382dbb..ee5350b8a1166fda8273dd44fb98d8b305480300 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
@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu
-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**.
+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**.
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 46974e89328fec671bae02e748ea393b1d147914..2a76953abeebbff57fbd916f2f05baeca250f91c 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 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**.
+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**.
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 e815cd2617071cf655bd573407f803999ccd9276..16b435d2b72fe59de7dc9bf64571e8f09f9fe2b7 100644
--- a/en/device-dev/quick-start/quickstart-standard-env-setup.md
+++ b/en/device-dev/quick-start/quickstart-standard-env-setup.md
@@ -32,13 +32,14 @@ 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.
```
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 4c1e34c22be466aca3721ac696aa6ae306eae58b..1f17ffc4a6591e60444c423d77f472538ff01d9f 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,104 +1,110 @@
# 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
-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:
+[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:
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 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 the source code, the following dialog box will be displayed. Click **Import** when prompted.
- 
+ 
4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
-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.
+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**.
- 
+ 
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. 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.
-
- - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
+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.
- **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-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md
index d17d3881e3a921f358e502272bd87ab8d6521cd0..509d6d54bcc852241b29c65b59faa24fe1634c57 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,60 +1,78 @@
# 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
-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:
+[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:
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. Otherwise, the building may fail.
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces.
- 
+ 
-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 the source code, the following dialog box will be displayed. Click **Import** when prompted.
- 
+ 
4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
-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**.
+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**.
- 
+ 
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.
-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).
+ >  **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.
- - 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.
+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.
-4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
+4. Open DevEco Device Tool, choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
@@ -65,32 +83,29 @@ After the source code is imported, perform the following steps:
-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**.
+6. 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.
+ 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.
+ >  **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. Click **Open** to open the project file. Click  to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
+8. 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 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.
+ >  **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.
+ >
-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.
+
+