diff --git a/en/device-dev/faqs/faqs-building.md b/en/device-dev/faqs/faqs-building.md index 86a92299d09be877872ebd616d3c68470532bb92..0d84a30fb835da8ce8a48458fa69ade53472eead 100644 --- a/en/device-dev/faqs/faqs-building.md +++ b/en/device-dev/faqs/faqs-building.md @@ -8,12 +8,13 @@ - **Symptom** -The compilation fails, and **usr/sbin/ninja: invalid option -- w** is displayed. - + + The compilation fails, and **usr/sbin/ninja: invalid option -- w** is displayed. + - **Possible Causes** - -The Ninja version in the compilation environment is outdated and does not support the **--w** option. - + + The Ninja version in the compilation environment is outdated and does not support the --w option. + - **Solution** Uninstall Ninja and GN in the environment and reinstall them by following instructions in [Obtaining Tools](../get-code/gettools-ide.md). @@ -23,16 +24,18 @@ The Ninja version in the compilation environment is outdated and does not suppor - **Symptom** -The compilation fails, and **/usr/bin/ld: cannot find -lncurses** is displayed. - + + The compilation fails, and **/usr/bin/ld: cannot find -lncurses** is displayed. + - **Possible Causes** -The ncurses library is not installed. - + + The ncurses library is not installed. + - **Solution** ``` - Run **sudo apt-get install lib32ncurses5-dev** to install the library. + sudo apt-get install lib32ncurses5-dev ``` @@ -40,16 +43,18 @@ The ncurses library is not installed. - **Symptom** -The compilation fails, and **line 77: mcopy: command not found** is displayed. - + + The compilation fails, and **line 77: mcopy: command not found** is displayed. + - **Possible Causes** -Mcopy is not installed. - + + Mcopy is not installed. + - **Solution** ``` - Run **sudo apt-get install dosfstools mtools** to install mcopy. + sudo apt-get install dosfstools mtools ``` @@ -57,40 +62,43 @@ Mcopy is not installed. - **Symptom** -The compilation fails, and the following information is displayed: **riscv32-unknown-elf-gcc: error trying to exec 'cc1': execvp: No such file or directory**. - + + The compilation fails, and the following information is displayed: **riscv32-unknown-elf-gcc: error trying to exec 'cc1': execvp: No such file or directory**. + - **Possible Causes** -Permission is required to access files in the **riscv** compiler path. - + + Permission is required to access files in the **riscv** compiler path. + - **Solution** - - Run the following command to query the directory where **gcc_riscv32** is located: + + 1. Run the following command to query the directory where **gcc_riscv32** is located: + ``` which riscv32-unknown-elf-gcc -``` + ``` - Run the **chmod** command to change the directory permission to **755**. + 2. Run the **chmod** command to change the directory permission to **755**. ### "No module named 'Crypto'" Displayed During the Build Process - **Symptom** -The compilation fails, and **No module named'Crypto loaded** is displayed. + The compilation fails, and **No module named'Crypto loaded** is displayed. - **Possible Causes** -Crypto is not installed in Python3. + Crypto is not installed in Python3. - **Solution** 1. Run the following command to query the Python version: - ``` +``` python3 --version - ``` +``` 2. Ensure that Python 3.7 or later is installed, and then run the following command to install pycryptodome: ``` @@ -102,12 +110,14 @@ Crypto is not installed in Python3. - **Symptom** -The compilation fails, and **xx.sh [: xx unexpected operator** is displayed. - + + The compilation fails, and **xx.sh [: xx unexpected operator** is displayed. + - **Possible Causes** -The compilation environment is shell instead of bash. - + + The compilation environment is shell instead of bash. + - **Solution** ``` @@ -120,29 +130,32 @@ The compilation environment is shell instead of bash. - **Symptom** -The following error occurs during compilation and building: - - + + The following error occurs during compilation and building: + + ``` Could not find a version that satisfies the requirement six>=1.9.0 -``` - + ``` + - **Possible Causes** -**six** is not installed. - + + **six** is not installed. + - **Solution** -Solution 1: Run the **pip3 install six** command to install **six** online. - -Method 2: Offline installation - -Download the installation package from [PyPI](https://pypi.org/project/six/#files). - -![en-us_image_0000001251276115](figures/en-us_image_0000001251276115.png) - -Save the source code to the Linux server and run the **pip3 install six-1.14.0-py2.py3-none-any.whl** command to install **six**. - + + Method 1: Run the **pip3 install six** command to install **six** online. + + Method 2: Offline installation + + Download the installation package from [PyPI](https://pypi.org/project/six/#files). + + ![en-us_image_0000001251276115](figures/en-us_image_0000001251276115.png) + + Save the source code to the Linux server and run the **pip3 install six-1.14.0-py2.py3-none-any.whl** command to install **six**. + After the preceding installation is complete, rebuild an environment. @@ -150,27 +163,30 @@ Save the source code to the Linux server and run the **pip3 install six-1.14.0-p - **Symptom** -The following error occurs during the build process: - - + + The following error occurs during the build process: + + ``` riscv32-unknown-elf-ld: cannot find -lgcc -``` - + ``` + - **Possible Causes** -The PATH is incorrectly written by **gcc_riscv32**. There is an extra slash (/). - - + + The gcc_riscv32 PATH is incorrect. There is an extra slash (/) after **bin**. + + ``` ~/gcc_riscv32/bin/:/data/toolchain/ -``` - + ``` + - **Solution** -Modify the PATH by deleting the slash (/). - - + + Modify the PATH as follows: + + ``` ~/gcc_riscv32/bin:/data/toolchain/ ``` @@ -180,46 +196,51 @@ Modify the PATH by deleting the slash (/). - **Symptom** -The following error occurs during the build process: - - + + The following error occurs during the build process: + + ``` -bash: /usr/bin/python: No such file or directory -``` - + ``` + - **Possible Cause 1** -Python is not installed. - + + Python is not installed. + - **Solution** -Run the following command to install Python. The following uses Python 3.8 as an example. - - + + Run the following command to install Python (Python 3.8 for example): + + ``` sudo apt-get install python3.8 -``` - + ``` + - **Possible Cause 2** -The soft link that points to the Python does not exist in the **usr/bin** directory. - -![en-us_image_0000001243200677](figures/en-us_image_0000001243200677.png) - + + The soft link that points to the Python does not exist in the **usr/bin** directory. + + ![en-us_image_0000001243200677](figures/en-us_image_0000001243200677.png) + - **Solution** -Run the following commands to add a soft link: - - + + Run the following commands to add a soft link: + + ``` # cd /usr/bin/ # which python3 # ln -s /usr/local/bin/python3 python # python --version -``` - + ``` + Example: - + ![en-us_image_0000001243320787](figures/en-us_image_0000001243320787.png) @@ -231,13 +252,15 @@ Example: - **Possible Causes** -Python 3 is not installed. - + + Python 3 is not installed. + - **Solution** -Run the following command to install Python 3: - - + + Run the following command to install Python 3: + + ``` sudo apt-get install python3.8 ``` diff --git a/en/device-dev/faqs/faqs-system-applications.md b/en/device-dev/faqs/faqs-system-applications.md index 6bd7928f2cc1831f4c552481f6f74b6c97a86c6d..b7c3bc6bdda88a16dac535768f306312bb372b99 100644 --- a/en/device-dev/faqs/faqs-system-applications.md +++ b/en/device-dev/faqs/faqs-system-applications.md @@ -181,8 +181,9 @@ Do not include too many elements in an array. Avoid frequent operations on a lar - **Symptom** + After the **hdc_std list targets** command is executed, **[Empty]** is displayed. - + - **Solution** 1. The device cannot be identified. @@ -197,8 +198,9 @@ After the **hdc_std list targets** command is executed, **[Empty]** is displayed - **Symptom** -After you click **hdc_std.exe**, the file fails to execute. - + + After you click **hdc_std.exe**, the file fails to execute. + - **Solution** **hdc_std.exe** requires no installation. You can use it after placing it to a local directory or adding the tool path to environment variables. Run the **cmd** command and then run the **hdc_std** command to start the tool.