Fixing Burning Issues

What should I do if Error: Opening COMxx: Access denied is displayed when I start burning

• Symptom

Error: Opening COMxx: Access denied is displayed after clicking Burn and selecting a serial port.

**Figure 1** Failed to open the serial port

![en-us_image_0000001226634728](figures/en-us_image_0000001226634728.png)

• Possible Causes

The serial port is in use.

• Solution

• 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

  

• Click the dustbin icon as shown below to disable the terminal using the serial port.

  Figure 3 Disabling the terminal using the serial port

  

• Click Burn, select the serial port, and start burning images again.

  Figure 4 Restarting the burning task

  

What should I do when 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 5** Failed to obtain the file image due to network disconnection

![en-us_image_0000001271234757](figures/en-us_image_0000001271234757.png)

• Possible Causes

The board is disconnected from the Windows-based PC.

Windows Firewall does not allow Visual Studio Code to access the network.

• Solution

• Check whether the network cable is properly connected.

• Click Windows Firewall.

  Figure 6 Network and firewall settings

  

• Click Firewall & network protection, and on the displayed page, click Allow an app through the firewall.

  Figure 7 Firewall & network protection

  

• Select Visual Studio Code.

  Figure 8 Selecting Visual Studio Code

  

• Select the Private and Public network access rights for Visual Studio Code.

  Figure 9 Allowing Visual Studio Code to access the network

  

What should I do when the image failed to be burnt?

• Symptom

The burning status is not displayed after clicking Burn and selecting a serial port.

• Possible Causes

The IDE is not restarted after the DevEco plug-in is installed.

• Solution

Restart the IDE.

What should I do if no information is displayed through the serial port? (Hi3516)

• Symptom

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

• Possible Cause 1

The serial port is connected incorrectly.

• Solution

Change the serial port number.

Open Device Manager to check whether the serial port connected to the board is the same as the serial port connected to the terminal. If they are different, change the serial port number by following the instructions provided in “ Error: Opening COMxx: Access denied”.

• Possible Cause 2

The U-Boot of the board is damaged.

• Solution

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:

1. Obtain the U-Boot file.

NOTICE The U-Boot file of the two boards can be obtained from the following paths, respectively.

Hi3516D V300: device\hisilicon\hispark_taurus\sdk_liteos\uboot\out\boot\u-boot-hi3516dv300.bin

Hi3518E V300: device\hisilicon\hispark_aries\sdk_liteos\uboot\out\boot\u-boot-hi3518ev300.bin

1. Burn the U-Boot file by following the procedures for burning a U-Boot file over USB.

Select the U-Boot files of corresponding development boards for burning by referring to Burning to Hi3516D V300/Burning to Hi3518E V300.

1. Log in to the serial port after the burning is complete.

   Figure 10 Information displayed through the serial port after the U-Boot file is burnt

   

你可能感兴趣的鸿蒙文章

harmony(鸿蒙)Getting Started

harmony(鸿蒙)Overall Description of Compilation Form Factors

harmony(鸿蒙)Importing a Source Code Project

harmony(鸿蒙)Setting Up the Windows+Ubuntu Hybrid Development Environment

harmony(鸿蒙)Introduction to the Hi3516 Development Board

harmony(鸿蒙)Introduction to the Hi3861 Development Board

harmony(鸿蒙)Mini and Small System Overview

harmony(鸿蒙)Obtaining Source Code

harmony(鸿蒙)Building

harmony(鸿蒙)Burning