diff --git a/en/device-dev/quick-start/Readme-EN.md b/en/device-dev/quick-start/Readme-EN.md
index 294cd1ec35ccdb16369b610eed0d38ae06bc93d0..5f8a202dccc6a7827964233c80d61f55fe05a526 100644
--- a/en/device-dev/quick-start/Readme-EN.md
+++ b/en/device-dev/quick-start/Readme-EN.md
@@ -49,6 +49,7 @@
- [Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md)
- [Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md)
- [Reference](quickstart-lite-reference.md)
+ - [Burning Code by Using HiTool](quickstart-lite-hitool.md)
- [Overall Description of Compilation Form Factors](quickstart-build.md)
- Getting Started with Standard System (IDE Mode, Recommended)
- [Standard System Overview](quickstart-ide-standard-overview.md)
@@ -94,4 +95,5 @@
- [Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)
- [Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)
- [Reference](quickstart-standard-reference.md)
+ - [Burning Code by Using HiTool](quickstart-standard-hitool.md)
- [Overall Description of Compilation Form Factors](quickstart-build.md)
diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-building.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-building.md
index 9d0404f86ff7a9608be8f4a901a44fd2e86cd55d..f28df25233dec4b056950f23f7f6caea642a1be0 100644
--- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-building.md
+++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-building.md
@@ -1,31 +1,35 @@
# Building
-1. In **Projects**, click **Settings**. The Hi3516D V300 configuration page is displayed.
+1. Click **Project Settings** on the menu bar to access the Hi3516D V300 project configuration page.
-2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools.
-
- >  **NOTE**
- > If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again.
-
+2. On the **Tool Chain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **Install** to automatically install the required tools.
+
+3. Install the toolchain related to Hi3516D V300. Certain tools may require the root access to install. In this case, enter the user password in the **TERMINAL** window.
+
+ >  **NOTE**
+ > If the pip component fails to be installed, [change the Python source](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) and try again.
+
+ 
+
After the toolchain is automatically installed, the figure below is displayed.
-
+
+
+4. On the **hi3516dv300** tab page, set **build_type**. The default value is **debug**. Click **Save** to save the settings.
-3. On the **hi3516dv300** tab page, set **build_type**. The default value is **debug**. Click **Save** to save the settings.
-
- 
+ 
-4. Choose **PROJECT TASKS** > **hi3516dv300** > **Build** to start building.
+5. Choose **PROJECT TASKS** > **hi3516dv300** > **Build** to start building.
-5. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the compilation is complete.
+6. Wait until **SUCCESS** is displayed in the **TERMINAL** window, indicating that the compilation is complete.
- After the building is complete, go to the out directory of the project to view the generated files, which are needed in [burning](https://device.harmonyos.com/en/docs/documentation/guide/ide-hi3516-upload-0000001052148681).
+ After the building is complete, go to the **out** directory of the project to view the generated files, which are needed in [burning](quickstart-ide-lite-steps-hi3516-burn.md).
diff --git a/en/device-dev/quick-start/quickstart-lite-hitool.md b/en/device-dev/quick-start/quickstart-lite-hitool.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec554b85f4eb49a635d6a3612fb149fddc7cc7a3
--- /dev/null
+++ b/en/device-dev/quick-start/quickstart-lite-hitool.md
@@ -0,0 +1,107 @@
+# Burning Code by Using HiTool
+
+
+To burn code to the Hi3516D V300 development board, you can use HiTool in addition to DevEco Device Tool.
+
+
+## Prerequisites
+
+- The source code of the development board has been compiled into files for burning.
+
+- [HiTool](http://www.hihope.org/download/download.aspx) has been installed on the client platform (for example, a Windows-based computer).
+
+- The USB driver has been installed on the client platform. For details, see [Installing the USB Port Driver on the Hi3516D V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393).
+
+- A serial port terminal tool, such as IPOP, has been installed on the client platform.
+
+- The client platform and development board are connected using a USB cable and serial cable.
+
+
+## Procedure
+
+1. Prepare the files to be burnt.
+
+ 1. On the client platform, create a folder for storing the files to be burnt, for example, **D:\liteos** or **D:\linux**.
+
+ 2. Save the burning configuration file and boot file to the new folder.
+
+ - For the small system using the LiteOS kernel, the burning configuration file is **L1_3516_liteos.xml**, and the boot file is [u-boot-hi3516dv300.bin](https://gitee.com/openharmony/device_board_hisilicon/tree/master/hispark_taurus/uboot/out/boot).
+
+
+ You need to prepare the **L1_3516_liteos.xml** file on your own by applying the template below:
+
+ ```
+
+
+
+
+
+
+
+ ```
+
+ - For the small system using the Linux kernel, the burning configuration file is **L1_3516_linux.xml**, and the boot file is [u-boot-hi3516dv300.bin](https://gitee.com/openharmony/device_board_hisilicon/tree/master/hispark_taurus/uboot/out/boot).
+ You need to prepare the **L1_3516_linux.xml** file on your own by applying the template below:
+
+
+ ```
+
+
+
+
+
+
+
+
+ ```
+ 3. Download the compiled source package to the client platform, decompress the package, and copy the files required for burning to the folder created in step 1.
+
+ For the Hi3516 development board, the files required for burning of the small system are as follows:
+
+ - LiteOS: **OHOS_Image.bin**, **rootfs_vfat.img**, and **userfs_vfat.img**
+ - Linux: **uImage_hi3516dv300_smp**, **rootfs_ext4.img**, **userfs_ext4.img**, and **userdata_ext4.img**
+
+2. Burn the image files using HiTool.
+
+ 1. Open HiTool.
+
+ 2. Set up HiTool.
+
+ Set the transfer mode to USB and burning mode to eMMC (the storage medium of the development board is eMMC).
+
+ 3. Click **Browse** and select the burning configuration file (for example, **L1_3516_linux.xml**) from the folder created in step 1.
+
+ 4. After clicking the **Burn** button, press and hold the **Update** key next to the serial port on the development board, and remove and insert the USB cable.
+
+ After the burning starts, logs are displayed in the console area at the bottom of HiTool.
+
+ When the burning is complete, HiTool displays a dialog box indicating that the burning is successful.
+
+ 5. Click **OK**.
+
+3. Import startup parameters.
+
+ 1. Use the terminal tool to enable the serial port.
+
+ 2. Restart the development board by removing and inserting its power supply. Press **Enter** in the serial port terminal tool within 3 seconds.
+
+ If **hisilicon \#** is displayed on the terminal tool page, the serial port of the development board is connected.
+
+ 3. Copy the following startup parameters in the serial port terminal tool and press **Enter** to complete the setup.
+
+ - The startup parameters for the small system using the LiteOS kernel are as follows:
+
+ ```
+ setenv bootcmd "mmc read 0x0 0x80000000 0x800 0x4800;go 0x80000000";
+ setenv bootargs "console=ttyAMA0,115200n8 root=emmc fstype=vfat rootaddr=10M rootsize=50M rw";
+ saveenv
+ reset
+ ```
+ - The startup parameters for the small system using the Linux kernel are as follows:
+
+ ```
+ setenv bootargs "mem=128M console=ttyAMA0,115200 root=/dev/mmcblk0p3 rw rootfstype=ext4 rootwait blkdevparts=mmcblk0:1M(boot),9M(kernel),50M(rootfs),50M(userfs),1024M(userdata)"
+ setenv bootcmd "mmc read 0x0 0x82000000 0x800 0x4800; mw 0x10FF0044 0x0600;mw 0x120D2010 0x00000000;mw 0x120D2400 0x000000ff;mw 0x120D2010 0x00000000; bootm 0x82000000"
+ saveenv;
+ reset
+ ```
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 3d0fa106dad97fd0d0085664b5a844d32d013627..10166bab83937ee9ac2b6da11dcf9691aa42ff4c 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
@@ -4,101 +4,84 @@
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
+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 in Windows.
-After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-lite-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**.
+## Importing Source Code
- >  **NOTE**
- > Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail.
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](quickstart-lite-env-setup.md). Then, perform the following steps to import the source code before burning:
- 
-
-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.
+1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code.
- 
+ 
-4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
+2. Select the root directory of the OpenHarmony source code (in Ubuntu), select **Import OpenHarmony Source**, and click **Import**.
- 
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces.
-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**.
+ 
- 
+3. On the **Import Project** page, select a product, and the SoC, 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.
+ 
+4. Click **Open** to open the project or source code.
-### Burning
+## Burning
After the source code is imported, 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 Hi3516D V300 Development Board](quickstart-lite-introduction-hi3516.md).
+1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516 Development Board](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).
+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 Serial Port Driver on the Hi3516D V300 or Hi3751 V350 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695) or [Installing the USB Port Driver on the Hi3516D V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393), 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.
+ - If  is displayed, click the connect icon. During the connection, DevEco Device Tool will restart. Therefore, to avoid task interruptions, do not connect to DevEco Device Tool when downloading or building source code.
- >  **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**
- > 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**.
+4. Click **Project Settings** on the menu bar to access the Hi3516D V300 project configuration page.
-5. On the **hi3516dv300** tab page, set the burning options.
+5. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
- - **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. On the **hi3516dv300** tab page, set the burning options.
-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**.
+ - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time. Check the preset information of the files to be burnt and modify them when necessary. To modify the burning settings for a specific file, click  next to the file.
- 1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
+ >  **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.
+ - **upload_protocol**: Select the burning protocol **hiburn-usb**.
- 
+ - **upload_port**: Select the serial port number obtained.
- 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. Go to **hi3516dv300** > **Upload** 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.
+8. Choose **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows.
- 
+ 
-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.
+ 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.
- If the following message is displayed, it indicates that the burning is successful.
+9. When the following information is displayed in the **TERMINAL** window, press and hold the **Update** key within 15 seconds, remove and insert the USB cable, and then release the **Update** key to start burning.
+
+ 
+
+ When the "SUCCESS" 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.
+10. When the burning is successful, perform the operations in "Running" to start the system.
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 ae60ee8b8894a07cdf00f6cba807d44a469d93fc..e6c4c869ed59f1cdeee93b3f142974146b9dff4c 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
@@ -1,90 +1,75 @@
# Burning
-Burn the source code to Hi3861 through the serial port 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
+Hi3861 V100 supports burning through the serial port. To burn source code through the serial port in Windows, perform the following steps:
-After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-lite-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**.
+## Importing Source Code
- >  **NOTE**
- > Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail.
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](quickstart-lite-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.
-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.
+ 
- 
+2. Select the root directory of the OpenHarmony source code (in Ubuntu), select **Import OpenHarmony Source**, and click **Import**.
-4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces.
- 
+ 
-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**.
+3. On the **Import Project** page, select a product, and the SoC, 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.
+4. Click **Open** to open the project or source code.
-### Burning
+## Burning
After the source code is imported, 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](quickstart-lite-introduction-hi3861.md).
+1. Connect the computer and the target development board through the USB port. For details, see [Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md).
+
+2. If your computer does not have the USB-to-serial adapter driver, install it by following the instructions in [Installing the USB-Serial Adapter Driver](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
-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.
+ - If  is displayed, click the connect icon. During the connection, DevEco Device Tool will restart. Therefore, to avoid task interruptions, do not connect to DevEco Device Tool when downloading or building source code.
- >  **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. Click **Project Settings** on the menu bar to access the Hi3861 V100 project configuration page.
- 
+ 
- >  **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. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
-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**.
- - **upload_partitions**: Select the files to be burnt. **hi3861_app** is selected by default.
+ - **upload_partitions**: Select the file for burning. To modify the burning settings for a specific file, click  next to the file.
-6. Check the preset information of the files to be burnt and modify them when necessary.
-
- On the **hi3861_app** tab page, select **partition_bin** from **New Option**, and set the path of the file to be burnt.
-
- 
-
7. 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. When the following information is displayed, press the RST button on the development board to restart it.
+9. When the following information is displayed, press the RST key 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.
-
- 
\ No newline at end of file
+ Wait until the burning is complete. When the following message is displayed, the burning is successful.
+
+ 
diff --git a/en/device-dev/quick-start/quickstart-standard-hitool.md b/en/device-dev/quick-start/quickstart-standard-hitool.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a31e081782d583c2aa8e52c578e2a013989c31c
--- /dev/null
+++ b/en/device-dev/quick-start/quickstart-standard-hitool.md
@@ -0,0 +1,67 @@
+# Burning Code by Using HiTool
+
+
+To burn code to the Hi3516D V300 development board, you can use HiTool in addition to DevEco Device Tool.
+
+
+## Prerequisites
+
+- The source code of the development board has been compiled into files for burning.
+
+- [HiTool](http://www.hihope.org/download/download.aspx) has been installed on the client platform (for example, a Windows-based computer).
+
+- The USB driver has been installed on the client platform. For details, see [Installing the USB Port Driver on the Hi3516D V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393).
+
+- A serial port terminal tool, such as IPOP, has been installed on the client platform.
+
+- The client platform and development board are connected using a USB cable and serial cable.
+
+
+## Procedure
+
+1. Prepare the files to be burnt.
+
+ 1. On the client platform, create a folder for storing the files to be burnt, for example, **D:\L2**.
+
+ 2. Download the compiled source package to the client platform, decompress the package, and copy the files required for burning to the folder created in step 1.
+
+ For the Hi3516D V300 development board, the files required for burning of the standard system are as follows: **boot.img**, **Hi3516DV300-emmc.xml**, **system.img**, **u-boot-hi3516dv300_emmc.bin**, **uImage**, **updater.img**, **userdata.img**, and **vendor.img**.
+
+2. Burn the image files using HiTool.
+
+ 1. Open HiTool.
+
+ 2. Set up HiTool.
+
+ Set the transfer mode to USB and burning mode to eMMC (the storage medium of the development board is eMMC).
+
+ 3. Click **Browse** and select the burning configuration file (for example, **Hi3516DV300-emmc.xml**) from the folder created in step 1.
+
+ 4. After clicking the **Burn** button, press and hold the **Update** key next to the serial port on the development board, and remove and insert the USB cable.
+
+ After the burning starts, logs are displayed in the console area at the bottom of HiTool.
+
+ When the burning is complete, HiTool displays a dialog box indicating that the burning is successful.
+
+ 5. Click **OK**.
+
+3. Import startup parameters.
+
+ 1. Use the terminal tool to enable the serial port.
+
+ 2. Restart the development board by removing and inserting its power supply. Press **Enter** in the serial port terminal tool within 3 seconds.
+
+ If **hisilicon \#** is displayed on the terminal tool page, the serial port of the development board is connected.
+
+ 3. Copy the following startup parameters in the serial port terminal tool and press **Enter** to complete the setup.
+
+ ```
+ setenv bootargs 'mem=640M console=ttyAMA0,115200 mmz=anonymous,0,0xA8000000,384M clk_ignore_unused androidboot.selinux=permissive rootdelay=10 hardware=Hi3516DV300 init=/init root=/dev/ram0 rw blkdevparts=mmcblk0:1M(boot),15M(kernel),20M(updater),2M(misc),3307M(system),256M(vendor),-(userdata)';setenv bootcmd 'mmc read 0x0 0x82000000 0x800 0x4800; bootm 0x82000000'
+
+ saveenv
+
+ reset
+ ```
+
+ >  **NOTICE**
+ > When entering startup parameters, do not delete blank lines.
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 4f5338ea93dc190c43af70fa96f68483d9ab37a6..ffe86523e728e63b698de307c92a7722815d061b 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,89 @@
# Burning
-To burn source code to Hi3516D V300 through the USB port in Windows, perform the following steps.
+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 for the small system through the USB port, network port, and serial port. This document describes how to burn source code through the USB port.
-### 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:
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](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**.
+2. Select the root directory of the OpenHarmony source code (in Ubuntu), select **Import OpenHarmony Source**, 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. On the **Import Project** page, select a product, and the SoC, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**.
-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. Click **Open** to open the project or source code.
-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.
-
- 
-
-6. Click **Open** to open the project or source code.
-
-
-### Burning
+## Burning
After the source code is imported, 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 Hi3516D V300 Development Board](quickstart-lite-introduction-hi3516.md).
+>  **NOTE**
+> This feature is available in DevEco Device Tool 2.2 Beta2 and later versions.
-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).
+1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md).
- - 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.
+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 Serial Port Driver on the Hi3516D V300 or Hi3751 V350 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695) or [Installing the USB Port Driver on the Hi3516D V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393), 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. During the connection, DevEco Device Tool will restart. Therefore, to avoid task interruptions, do not connect to DevEco Device Tool when downloading or building source code.
+
-
- >  **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**
- > 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**.
+
+4. Click **Project Settings** on the menu bar to access the Hi3516D V300 project configuration page.
-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.
+5. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
+
+ 
+
+6. On the **hi3516dv300** tab page, set the burning options.
+
+ - **upload_partitions**: Select the burning profile file (preset by default), which specifies the files to be burnt, start address and length of the partition, and other burning settings. In addition, select **Enable to use upload_partitions_profile**.
+
+ >  **NOTE**
+ >
+ > In the burning profile file, you can change 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 do not overlap.
+ >
+ > If this is the first time you burn files to the development board, select **Enable to use upload_partitions_profile for upload** so that the upload_partitions file will be automatically generated. Afterward, select **Enable to use upload_partitions_profile for upload** only when you need to generate a new **upload_partitions** file.
+
- **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.
-
- 
-
- 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
-
+
+ - **upload_port**: Select the serial port number obtained.
+
+ 
+
7. When you finish modifying, click **Save** on the top.
-8. Go to **hi3516dv300** > **Upload** to start burning.
+8. Choose **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows.
+
+ 
- >  **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.
+ 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.
+9. When the following information is displayed in the **TERMINAL** window, press and hold the **Update** key within 15 seconds, remove and insert the USB cable, and then release the **Update** key to start burning.
- 
+ 
- If the following message is displayed, it indicates that the burning is successful.
+ When the "SUCCESS" 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.
+10. 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..fffab323813034153d5fd2c40ca538bd277bd1a1 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,96 +1,86 @@
# Burning
-To burn source code to RK3568 on Windows, perform the following steps:
+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.
+For the RK3568 development board, image files are burnt in Windows.
-### 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:
+## Importing 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.
+After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](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.
-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.
+ 
- 
+2. Select the root directory of the OpenHarmony source code (in Ubuntu), select **Import OpenHarmony Source**, and click **Import**.
-4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
+ >  **NOTE**
+ > Make sure the selected directory does not contain Chinese characters or spaces.
- 
+ 
-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**.
+3. On the **Import Project** page, select a product, and the SoC, 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.
+4. 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**
+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) and install **DriverInstall.exe**.
+
+ >  **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.
+2. Connect the computer and the target development board through the USB port. For details, see [Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md).
-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. Inthis case, no further action is required.
- - If  is displayed, click the connect icon.
+ - 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. During the connection, DevEco Device Tool will restart. Therefore, to avoid task interruptions, do not connect to DevEco Device Tool when downloading or building source code.
- >  **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. Click **Project Settings** on the menu bar to access the RK3568 project configuration page.
-4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
-
- 
+ 
-5. On the **hh_scdy200** tab page, set the burning options.
+5. On the **Tool Chain** tab page, set the Uploader burning tool. You can click **Install** on this page to install the tool online.
- - **upload_partitions**: Select the files to be burnt.
- - **upload_protocol**: Select the burning protocol **upgrade**.
-
- 
-
-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. On the **hh_scdy200** tab page, set the burning options.
- 2. In **Partition Options**, modify the items selected in the preceding step.
+ - **upload_partitions_profile**: Select the burning profile file, which specifies the files to be burnt, start address and length of the partition, and other burning settings. In addition, select **Enable to use upload_partitions_profile**.
- >  **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**
+ >
+ > In the burning profile file, you can change 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 do not overlap.
+ >
+ > If this is the first time you burn files to the development board, select **Enable to use upload_partitions_profile for upload** so that the upload_partitions file will be automatically generated. Afterward, select **Enable to use upload_partitions_profile for upload** only when you need to generate a new **upload_partitions** file.
- 
+ - **upload_protocol**: Select the burning protocol **upgrade**.
- 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.
-
-10. Wait until the burning is complete. If the following message is displayed, the burning is successful.
+ >  **NOTE**
+ >
+ > If the message "The board is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
+
+ Wait until the burning is complete. If the following message is displayed, the burning is successful.
