diff --git a/en/device-dev/faqs/faqs-burning.md b/en/device-dev/faqs/faqs-burning.md
index 09f3a076e11ad20c3a539746954c3a7221bb62fa..2390fcde0049a6d96f58ae4f25b3ab6599e6233f 100644
--- a/en/device-dev/faqs/faqs-burning.md
+++ b/en/device-dev/faqs/faqs-burning.md
@@ -4,44 +4,45 @@
 ## Mini and Small Systems
 
 
-### "Error: Opening COMxx: Access denied" Displayed When I Start Burning
+### "Error: Opening COMxx: Access denied" Is Displayed When I Start Burning
 
 - **Symptom**
-  
+
   After I click **Burn** and select a serial port, **Error: Opening COMxx: Access denied** is displayed.
 
   **Figure 1** Access denied error
   
   ![failed-to-open-the-serial-port](figures/failed-to-open-the-serial-port.png)
-- **Possible Causes**
   
+- **Possible Causes**
+
   The serial port is in use.
 
 - **Solution**
 
   1. Search for the terminal using serial-xx from the drop-down list in the **TERMINAL** panel.
-
+  
      **Figure 2** Checking whether the serial port is in use
-     
-     ![en-us_image_0000001243481989](figures/en-us_image_0000001243481989.png)
   
+     ![en-us_image_0000001243481989](figures/en-us_image_0000001243481989.png)
+
   2. Click the dustbin icon as shown below to disable the terminal using the serial port.
-  
+    
      **Figure 3** Disabling the terminal using the serial port
-     
+
      ![en-us_image_0000001243082093](figures/en-us_image_0000001243082093.png)
 
   3. Click **Burn**, select the serial port, and start burning images again.
-  
+    
      **Figure 4** Restarting the burning task
-     
+
      ![en-us_image_0000001198322224](figures/en-us_image_0000001198322224.png)
 
 
 ### The Image Failed To Be Burnt
 
 - **Symptom**
-  
+
   The image failed to be burnt over a serial port.
 
 - **Possible Causes**
@@ -87,29 +88,28 @@
       > 
       > Hi3518E V300: **device\hisilicon\hispark_aries\sdk_liteos\uboot\out\boot\u-boot-hi3518ev300.bin**
 
-	2. Burn the U-Boot file by following the procedures for burning a U-Boot file over USB.
-       Select the U-Boot files of the corresponding development board for burning by referring to [Burning an Image](../quick-start/quickstart-ide-3516-burn.md).
+  2. Burn the U-Boot file.
+  
+     Select the U-Boot files of the corresponding development board for burning. For details, see [Burning an Image](../quick-start/quickstart-ide-3516-burn.md).
 
-	3. Log in to the serial port after the burning is complete.
+  3. Log in to the serial port after the burning is complete.
 
-       **Figure 5** Information displayed through the serial port after the U-Boot file is burnt
+     **Figure 5** Information displayed through the serial port after the U-Boot file is burnt
 
-       ![en-us_image_0000001243484907](figures/en-us_image_0000001243484907.png)
+     ![en-us_image_0000001243484907](figures/en-us_image_0000001243484907.png)
 
 
 ### Windows-based PC Failed to Be Connected to the Board
 
 - **Symptom**
-  
 
   The file image cannot be obtained after clicking **Burn** and selecting a serial port.
 
   **Figure 6** Failed to obtain the file image due to network disconnection
-
+  
   ![en-us_image_0000001198322428](figures/en-us_image_0000001198322428.png)
 
 - **Possible Causes**
-  
 
   The board is disconnected from the Windows-based PC.
 
@@ -117,23 +117,55 @@
 
 - **Solution**
 
-  1. Check whether the network cable is properly connected.
-  2. Click **Windows Firewall**.
+  1. Make sure the network cable is properly connected.
 
-	   **Figure 7** Setting the firewall
+  2. Click **Windows Firewall**.
+    
+     **Figure 7** Setting the firewall
+     
      ![en-us_image_0000001198162584](figures/en-us_image_0000001198162584.png)
 
   3. Click **Firewall & network protection**. On the displayed page, click **Allow an app through the firewall**.
-
+    
      **Figure 8** Firewall & network protection
+     
      ![en-us_image_0000001198323146](figures/en-us_image_0000001198323146.png)
 
   4. Select Visual Studio Code.
-
+    
      **Figure 9** Selecting Visual Studio Code
+    
      ![en-us_image_0000001198003232](figures/en-us_image_0000001198003232.png)
 
   5. Select the **Private** and **Public** network access rights for Visual Studio Code.
-
+    
      **Figure 10** Allowing Visual Studio Code to access the network
-     ![en-us_image_0000001243084579](figures/en-us_image_0000001243084579.png)
\ No newline at end of file
+  
+     ![en-us_image_0000001243084579](figures/en-us_image_0000001243084579.png)
+
+### The Development Board Failed to Be Identified by the Burning Tool
+
+- **Symptom**
+
+  During image burning, the burning tool displays a message indicating that no device is found.
+
+- **Possible Causes**
+
+  The cable between the Windows computer and the development board is not connected. (The cable required varies. In this example, the USB cable is used.) 
+
+  The driver corresponding to the cable between the Windows computer and the development board is not installed.
+
+- **Solution**
+
+  1. Make sure the cable between the Windows computer and the development board is connected.
+
+  2. Open Device Manager in Windows.
+
+  3. Open the Universal Serial Bus controllers list.
+    
+  4. Check whether the USB device driver has been installed. If an alarm is displayed, the driver has not been installed.
+
+  5. Depending on the Windows environment, install the desired USB device driver, such as FT23R USB UART Driver. Then try again.
+
+  6. If any other issue occurs, consult the relevant FAQ entry.
+