update doc

Signed-off-by: N ester.zhou <ester.zhou@huawei.com>

update doc
Signed-off-by: N ester.zhou <ester.zhou@huawei.com>
43c6059c · ester.zhou · 0112189b · 43c6059c
显示空白变更内容
内联并排

Showing with 67 addition and 69 deletion

en/device-dev/faqs/faqs-burning.md en/device-dev/faqs/faqs-burning.md +67 -69

未找到文件。
--- a/en/device-dev/faqs/faqs-burning.md
+++ b/en/device-dev/faqs/faqs-burning.md
@@ -8,30 +8,30 @@

 - **Symptom**
  
-**Error: Opening COMxx: Access denied** is displayed after clicking **Burn** and selecting a serial port.
+  After I click **Burn** and select a serial port, **Error: Opening COMxx: Access denied** is displayed.

-    **Figure 1** Failed to open the serial port
-  ![en-us_image_0000001243481961](figures/en-us_image_0000001243481961.png)
+  **Figure 1** Access denied error
  
+  ![failed-to-open-the-serial-port](figures/failed-to-open-the-serial-port.png)
 - **Possible Causes**
  
-The serial port is in use.
+  The serial port is in use.

 - **Solution**

-1. Search for the terminal using serial-xx from the drop-down list in the **TERMINAL** panel.
-   
+  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)
  
-2. Click the dustbin icon as shown below to disable the terminal using the serial port.
+  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.
+  3. Click **Burn**, select the serial port, and start burning images again.
  
     **Figure 4** Restarting the burning task
     
@@ -42,44 +42,44 @@ The serial port is in use.

 - **Symptom**
  
-The burning status is not displayed after clicking **Burn** and selecting a serial port.
+  The image failed to be burnt over a serial port.

 - **Possible Causes**
  
-The IDE is not restarted after the DevEco plug-in is installed.
+  The DevEco Device Tool plug-in is not restarted after being installed.

 - **Solution**
  
-  Restart the IDE.
+  Restart DevEco Device Tool.


 ### No Command Output Is Displayed

 - **Symptom**
  
-The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when you press **Enter**.
+  The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when I press **Enter**.

 - **Possible Cause 1**
  
-The serial port is connected incorrectly.
+  The serial port is connected incorrectly.

 - **Solution**
  
-Change the serial port number.
+  Change the serial port number.

-Start **Device Manager** to check whether the serial port connected to the board is the same as that connected to the terminal device. If the serial ports are different, perform step 1 in the **Running an Image** section to change the serial port number.
+  Start **Device Manager** to check whether the serial port connected to the board is the same as that connected to the terminal device. If the serial ports are different, perform step 1 in the **Running an Image** section to change the serial port number.

 - **Possible Cause 2**
  
-The U-Boot of the board is damaged.
+  The U-Boot of the board is damaged.

 - **Solution**
  
-Burn the U-Boot.
+  Burn the U-Boot.

-  If the fault persists after you perform the preceding operations, the U-Boot of the board may be damaged. You can burn the U-Boot by performing the following steps:
+  If the fault persists after you perform the preceding operations, the U-Boot of the board may be damaged. In this case, burn the U-Boot by performing the following steps:

-1. Obtain the U-Boot file.
+   1. Obtain the U-Boot file.
      > ![icon-notice.gif](public_sys-resources/icon-notice.gif) **NOTICE**
      > The U-Boot file of the two boards can be obtained from the following paths, respectively.
      > 
@@ -87,10 +87,10 @@ Burn the U-Boot.
      > 
      > 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.
+	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 to Hi3516D V300](../quick-start/quickstart-ide-lite-steps-hi3516-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

@@ -101,7 +101,8 @@ Burn the U-Boot.

 - **Symptom**
  
-The file image cannot be obtained after clicking **Burn** and selecting a serial port.
+
+  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

@@ -109,33 +110,30 @@ The file image cannot be obtained after clicking **Burn** and selecting a serial

 - **Possible Causes**
  
-The board is disconnected from the Windows-based PC.

-Windows Firewall does not allow Visual Studio Code to access the network.
+  The board is disconnected from the Windows-based PC.
+
+  Windows Firewall does not allow Visual Studio Code to access the network.

 - **Solution**

  1. Check whether the network cable is properly connected.
  2. Click **Windows Firewall**.

-**Figure 7** Setting the firewall
-
-![en-us_image_0000001198162584](figures/en-us_image_0000001198162584.png)
-
-3. Click **Firewall & network protection**, and 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)
+	   **Figure 7** Setting the firewall
+     ![en-us_image_0000001198162584](figures/en-us_image_0000001198162584.png)

-4. Select Visual Studio Code.
+  3. Click **Firewall & network protection**. On the displayed page, click **Allow an app through the firewall**.

-**Figure 9** Selecting Visual Studio Code
+     **Figure 8** Firewall & network protection
+     ![en-us_image_0000001198323146](figures/en-us_image_0000001198323146.png)

-![en-us_image_0000001198003232](figures/en-us_image_0000001198003232.png)
+  4. Select Visual Studio Code.

-5. Select the **Private** and **Public** network access rights for Visual Studio Code.
+     **Figure 9** Selecting Visual Studio Code
+     ![en-us_image_0000001198003232](figures/en-us_image_0000001198003232.png)

-**Figure 10** Allowing Visual Studio Code to access the network
+  5. Select the **Private** and **Public** network access rights for Visual Studio Code.

-![en-us_image_0000001243084579](figures/en-us_image_0000001243084579.png)
\ No newline at end of file
+     **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