• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1# FAQs<a name="EN-US_TOPIC_0000001128470856"></a>
2
3-   [What should I do when the images failed to be burnt over the selected serial port?](#section627268185113)
4-   [What should I do when Windows-based PC failed to be connected to the board?](#section195391036568)
5-   [What should I do when the image failed to be burnt?](#section571164016565)
6-   [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](#section1039835245619)
7-   [What should I do when no command output is displayed?](#section14871149155911)
8
9## What should I do when the images failed to be burnt over the selected serial port?<a name="section627268185113"></a>
10
11-   **Symptom**
12
13    **Error: Opening COMxx: Access denied**  is displayed after clicking  **Burn**  and selecting a serial port.
14
15    **Figure  1**  Failed to open the serial port<a name="fig1756105874814"></a>
16    ![](figure/failed-to-open-the-serial-port.png "failed-to-open-the-serial-port")
17
18-   **Possible Causes**
19
20    The serial port has been used.
21
22-   **Solutions**
23
241.  Search for the terminal using serial-xx from the drop-down list in the  **TERMINAL**  panel.
25
26    **Figure  2**  Checking whether the serial port is used<a name="fig723433664916"></a>
27    ![](figure/checking-whether-the-serial-port-is-used.png "checking-whether-the-serial-port-is-used")
28
292.  Click the dustbin icon as shown in the following figure to disable the terminal using the serial port.
30
31    **Figure  3**  Disabling the terminal using the serial port<a name="fig197211713185012"></a>
32    ![](figure/disabling-the-terminal-using-the-serial-port.png "disabling-the-terminal-using-the-serial-port")
33
343.  Click  **Burn**, select the serial port, and start burning images again.
35
36    **Figure  4**  Restarting burning<a name="fig2196042514"></a>
37    ![](figure/restarting-burning.png "restarting-burning")
38
39
40## What should I do when Windows-based PC failed to be connected to the board?<a name="section195391036568"></a>
41
42-   **Symptom**
43
44    The file image cannot be obtained after clicking  **Burn**  and selecting a serial port.
45
46    **Figure  5**  Failed to obtain the image file due to unavailable connection<a name="fig135261439195819"></a>
47    ![](figure/failed-to-obtain-the-image-file-due-to-unavailable-connection.png "failed-to-obtain-the-image-file-due-to-unavailable-connection")
48
49-   **Possible Causes**
50
51    The board is disconnected from the Windows-based PC.
52
53    Windows Firewall does not allow Visual Studio Code to access the network.
54
55-   **Solutions**
56
571.  Check whether the network cable is properly connected.
582.  Click  **Windows Firewall**.
59
60    **Figure  6**  Network and firewall setting<a name="fig168416458311"></a>
61    ![](figure/network-and-firewall-setting.png "network-and-firewall-setting")
62
633.  Click  **Firewall & network protection**, and on the displayed page, click  **Allow applications to communicate through Windows Firewall**.
64
65    **Figure  7**  Firewall and network protection<a name="fig19866154513414"></a>
66    ![](figure/firewall-and-network-protection.png "firewall-and-network-protection")
67
684.  Select the Visual Studio Code application.
69
70    **Figure  8**  Selecting the Visual Studio Code application<a name="fig9213244657"></a>
71    ![](figure/selecting-the-visual-studio-code-application.png "selecting-the-visual-studio-code-application")
72
735.  Select the  **Private**  and  **Public**  network access rights for the Visual Studio Code application.
74
75    **Figure  9**  Allowing the Visual Studio Code application to access the network<a name="fig019395421210"></a>
76    ![](figure/allowing-the-visual-studio-code-application-to-access-the-network.png "allowing-the-visual-studio-code-application-to-access-the-network")
77
78
79## What should I do when the image failed to be burnt?<a name="section571164016565"></a>
80
81-   **Symptom**
82
83    The burning status is not displayed after clicking  **Burn**  and selecting a serial port.
84
85-   **Possible Causes**
86
87    The IDE is not restarted after the DevEco plug-in is installed.
88
89-   **Solutions**
90
91    Restart the IDE.
92
93
94## What should I do when the message indicating Python cannot be found is displayed during compilation and building?<a name="section1039835245619"></a>
95
96-   **Symptom**
97
98    ![](figure/symptom.png)
99
100
101-   **Possible Cause 1**: Python is not installed.
102-   **Solutions**
103
104    Install Python as instructed in  [Installing and Configuring Python](quickstart-lite-env-setup-linux.md#section1238412211211).
105
106-   **Possible Cause 2**: The soft link that points to the Python does not exist in the usr/bin directory.
107
108    ![](figure/reason-for-not-finding-python.png)
109
110-   **Solutions**
111
112    Run the following commands:
113
114    ```
115    # cd /usr/bin/
116    # which python3
117    # ln -s /usr/local/bin/python3 python
118    # python --version
119    ```
120
121    Example:
122
123    ![](figure/solution-7.png)
124
125
126## What should I do when no command output is displayed?<a name="section14871149155911"></a>
127
128-   **Symptom**
129
130    The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when you press  **Enter**.
131
132-   **Possible Cause 1**
133
134    The serial port is connected incorrectly.
135
136-   **Solutions**
137
138    Change the serial port number.
139
140    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](#section627268185113)  in the  **Running an Image**  section to change the serial port number.
141
142
143-   **Possible Cause 2**
144
145    The U-Boot of the board is damaged.
146
147-   **Solutions**
148
149    Burn the U-Boot.
150
151    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:
152
153
1541.  Obtain the U-Boot file.
155
156    >![](../public_sys-resources/icon-notice.gif) **NOTICE:**
157    >The U-Boot file of the two boards can be obtained from the following paths, respectively.
158    >Hi3516D V300:  **device\\hisilicon\\hispark\_taurus\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3516dv300.bin**
159    >Hi3518E V300:  **device\\hisilicon\\hispark\_aries\\sdk\_liteos\\uboot\\out\\boot\\u-boot-hi3518ev300.bin**
160
1612.  Burn the U-Boot file by following the procedures for burning a U-Boot file over USB.
162
163    Select the U-Boot files of corresponding development boards for burning by referring to  [Programming Flash Memory on the Hi3516](https://device.harmonyos.com/en/docs/ide/user-guides/hi3516_upload-0000001052148681)/[Programming Flash Memory on the Hi3518](https://device.harmonyos.com/en/docs/ide/user-guides/hi3518_upload-0000001057313128)
164
1653.  Log in to the serial port after the burning is complete.
166
167    **Figure  10**  Serial port displayed after the U-Boot is burnt<a name="en-us_topic_0000001053466255_fig155914681910"></a>
168    ![](figure/serial-port-displayed-after-the-u-boot-is-burnt.png "serial-port-displayed-after-the-u-boot-is-burnt")
169
170
171