同步操作将从 OpenHarmony/docs 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
Symptom
Error: Opening COMxx: Access denied is displayed after clicking Burn and selecting a serial port.
Possible Causes
The serial port has been used.
Solutions
Search for the terminal using serial-xx from the drop-down list in the TERMINAL panel.
Click the dustbin icon as shown in the following figure to disable the terminal using the serial port.
Click Burn, select the serial port, and start burning images again.
Symptom
The file image cannot be obtained after clicking Burn and selecting a serial port.
Figure 5 Failed to obtain the image file due to unavailable connection
Possible Causes
The board is disconnected from the Windows-based PC.
Windows Firewall does not allow Visual Studio Code to access the network.
Solutions
Check whether the network cable is properly connected.
Click Windows Firewall.
Click Firewall & network protection, and on the displayed page, click Allow applications to communicate through Windows Firewall.
Select the Visual Studio Code application
Select the Private and Public network access rights for the Visual Studio Code application.
Figure 9 Allowing the Visual Studio Code application to access the network
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.
Solutions
Restart the IDE.
Symptom
Possible Cause 1
Python is not installed.
Solutions
Install the Python environment by referring to Installing a Python Environment.
Possible Cause 2
Solutions
Run the following commands:
# cd /usr/bin/
# which python3
# ln -s /usr/local/bin/python3 python
# python --version
Example:
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.
Solutions
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.
Solutions
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:
Obtain the U-boot file.
NOTICE: The U-boot file of the two boards can be obtained from the following paths, respectively.
- Hi3516D V300: vendor\hisi\hi35xx\hi3516dv300\uboot\out\boot\u-boot-hi3516dv300.bin
- Hi3518E V300: vendor\hisi\hi35xx\hi3518ev300\uboot\out\boot\u-boot-hi3518ev300.bin
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 Programming Flash Memory on the Hi3516/Programming Flash Memory on the Hi3518
Log in to the serial port after the burning is complete.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。