faqs-2.md 3.9 KB
Newer Older
W
wenjun 已提交
1 2 3 4 5 6 7 8 9 10
# FAQs<a name="EN-US_TOPIC_0000001053942318"></a>

**Problem 1:** **What should I do when 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**.

-   **Possible Causes**
    -   The serial port is connected incorrectly.
N
NEEN 已提交
11
    -   The U-boot of the board is damaged.
W
wenjun 已提交
12 13 14

-   **Solutions**

N
NEEN 已提交
15 16
    **Solution 1: Change the serial port number.**

W
wenjun 已提交
17 18 19
    Start  **Device Manager**  to check whether the serial port connected to the board is the same as that connected to the terminal device. If not, perform the following steps to change the serial port number.

    **Figure  1**  Procedure for changing the serial port number<a name="fig16441825145717"></a>  
N
NEEN 已提交
20
    ![](figures/procedure-for-changing-the-serial-port-number-4.png "procedure-for-changing-the-serial-port-number-4")
W
wenjun 已提交
21 22 23 24 25 26 27


1.  Disconnect from the current serial port.
2.  Click  **Settings**.
3.  Change the serial port number in the dialog box and click  **OK**.
4.  Press  **Enter**  in the dialog box to check whether any command output is displayed after the connection is established.

N
NEEN 已提交
28 29 30
**Solution 2: 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:
W
wenjun 已提交
31

N
NEEN 已提交
32
1.  Obtain the U-boot file.
W
wenjun 已提交
33 34

    >![](public_sys-resources/icon-notice.gif) **NOTICE:** 
N
NEEN 已提交
35
    >The U-boot file of the board can be obtained from  **vendor\\hisi\\hi35xx\\hi3518ev300\\uboot\\out\\boot\\u-boot-hi3518ev300.bin**  in the open-source package.
W
wenjun 已提交
36

N
NEEN 已提交
37
2.  Use HiTool to burn the U-boot.
W
wenjun 已提交
38

N
NEEN 已提交
39
    **Figure  2**  Procedure for burning the U-boot using HiTool<a name="fig1353321514128"></a>  
W
wenjun 已提交
40 41 42 43 44 45
    ![](figures/procedure-for-burning-the-u-boot-using-hitool.png "procedure-for-burning-the-u-boot-using-hitool")

    1.  Select the COM7 serial port.
    2.  Select  **Serial**  for  **Transfer Mode**.
    3.  Select  **Burn Fastboot**.
    4.  Select  **spi nor**  for  **Flash Type**.
N
NEEN 已提交
46
    5.  Click  **Browse**  and select the corresponding U-boot file.
W
wenjun 已提交
47 48
    6.  Click  **Burn**  to start burning.

N
NEEN 已提交
49
3.  Power off the board and then power it on. Connect the serial port after the burning is complete. Serial ports shown in the following figure are displayed after the U-boot is burnt.
W
wenjun 已提交
50

N
NEEN 已提交
51 52
    **Figure  3**  Serial port displayed after the U-boot is burnt<a name="fig155914681910"></a>  
    ![](figures/serial-port-displayed-after-the-u-boot-is-burnt-5.png "serial-port-displayed-after-the-u-boot-is-burnt-5")
W
wenjun 已提交
53 54


N
NEEN 已提交
55
**Problem 2: What should I do when an error is reported when the U-boot is burnt using HiTool?**
W
wenjun 已提交
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112

-   **Symptom**

    **Figure  4**  Burning error<a name="fig466354874016"></a>  
    

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

-   **Possible Causes**

    The flash type selected by HiTool is incorrect.

-   **Solutions**

    Change the flash type in the area marked with  **1**  in the following figure.

    **Figure  5**  Incorrect flash type<a name="fig64931910194212"></a>  
    

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


**Question 3:** **What should I do when the message indicating Python cannot be found is displayed during compilation and building?**

-   **Symptom**

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


-   **Possible Cause 1**

    Python is not installed.

-   **Solutions**

    Install the Python environment by referring to  [Installing a Python Environment](setting-up-a-development-environment-1.md#section918195118487).

-   **Possible Cause 2**

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

-   **Solutions**

    If the soft link that points to the Python does not exist in the  **usr/bin**  directory, run the following command:

    ```
    # cd /usr/bin/
    # which python3
    # ln -s /usr/local/bin/python3 python
    # python --version
    ```

    Example:

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