!871 文档更新

Merge pull request !871 from duangavin123/master

en/device-dev/Readme-EN.md

@@ -76,7 +76,7 @@ In addition, OpenHarmony provides a series of optional system components that ca
 </td>
 <td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p155782037201518"><a name="p155782037201518"></a><a name="p155782037201518"></a>Developing smart devices based on system capabilities</p>
 </td>
-<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul257883731519"></a><a name="ul257883731519"></a><ul id="ul257883731519"><li><a href="guide/device-wifi.md">WLAN-connected Products</a></li><li><a href="guide/device-iotcamera-control.md">Cameras Without a Screen</a></li><li><a href="guide/device-camera.md">Cameras with a Screen</a></li></ul>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul257883731519"></a><a name="ul257883731519"></a><ul id="ul257883731519"><li><a href="guide/device-wlan-touch.md">OneHop</a></li><li><a href="guide/device-wifi.md">WLAN-connected Products</a></li><li><a href="guide/device-iotcamera-control.md">Cameras Without a Screen</a></li><li><a href="guide/device-camera.md">Cameras with a Screen</a></li></ul>
 </td>
 </tr>
 <tr id="row360273716155"><td class="cellrowborder" valign="top" width="28.472847284728473%" headers="mcps1.2.4.1.1 "><p id="p12579163711513"><a name="p12579163711513"></a><a name="p12579163711513"></a>Porting and adaptation</p>
@@ -97,7 +97,7 @@ In addition, OpenHarmony provides a series of optional system components that ca
 </td>
 <td class="cellrowborder" valign="top" width="35.61356135613561%" headers="mcps1.2.4.1.2 "><p id="p458073721519"><a name="p458073721519"></a><a name="p458073721519"></a>Referring to development specifications</p>
 </td>
-<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul175808372155"></a><a name="ul175808372155"></a><ul id="ul175808372155"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li></ul>
+<td class="cellrowborder" valign="top" width="35.91359135913591%" headers="mcps1.2.4.1.3 "><a name="ul175808372155"></a><a name="ul175808372155"></a><ul id="ul175808372155"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li><li><a href="faqs/Readme-EN" target="_blank" rel="noopener noreferrer">FAQs</a></li></ul>
 </td>
 </tr>
 </tbody>
@@ -167,7 +167,7 @@ In addition, OpenHarmony provides a series of optional system components that ca
 </td>
 <td class="cellrowborder" valign="top" width="36.053605360536054%" headers="mcps1.2.4.1.2 "><p id="p670135335116"><a name="p670135335116"></a><a name="p670135335116"></a>Referring to development specifications</p>
 </td>
-<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul177016538519"></a><a name="ul177016538519"></a><ul id="ul177016538519"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li></ul>
+<td class="cellrowborder" valign="top" width="36.07360736073608%" headers="mcps1.2.4.1.3 "><a name="ul177016538519"></a><a name="ul177016538519"></a><ul id="ul177016538519"><li><a href="https://device.harmonyos.com/en/docs/develop/apiref/js-framework-file-0000000000611396" target="_blank" rel="noopener noreferrer">API References</a></li><li><a href="faqs/Readme-EN" target="_blank" rel="noopener noreferrer">FAQs</a></li></ul>
 </td>
 </tr>
 </tbody>

en/device-dev/faqs/Readme-EN.md

+# FAQs
+
+-   [Overview of FAQs](overview-of-faqs.md)
+-   [Environment Setup](environment-setup.md)
+-   [Compilation and Building Subsystem](compilation-and-building-subsystem.md)
+-   [Burning](burning.md)
+-   [Kernel](kernel.md)
+-   [Porting](porting.md)
+-   [Startup and Recovery](startup-and-recovery.md)
+-   [System Applications](system-applications.md)
+

en/device-dev/faqs/burning.md

+# Burning<a name="EN-US_TOPIC_0000001170009518"></a>
+
+-   [Mini and Small Systems](#section278314413530)
+    -   ["Error: Opening COMxx: Access denied" Is Displayed After a Serial Port Is Selected for Burning](#section18988185615914)
+    -   [What should I do when the image failed to be burnt?](#section1370982513317)
+    -   [What should I do when no command output is displayed?](#section183421944953)
+    -   [What should I do when Windows-based PC failed to be connected to the board?](#section1215410450215)
+
+
+## Mini and Small Systems<a name="section278314413530"></a>
+
+### "Error: Opening COMxx: Access denied" Is Displayed After a Serial Port Is Selected for Burning<a name="section18988185615914"></a>
+
+-   **Symptom**
+
+    **Error: Opening COMxx: Access denied**  is displayed after clicking  **Burn**  and selecting a serial port.
+
+    ![](figures/failed-to-open-the-serial-port.png)
+
+-   **Possible Causes**
+
+    The serial port has been used.
+
+-   Solution
+
+    The serial port may be in use. Perform the following steps to troubleshoot:
+
+    1.  Search for the serial port from the drop-down list in the  **TERMINAL**  panel.
+
+        ![](figures/terminal-list.png)
+
+    2.  Click the dustbin for the terminal using the serial port to disable the terminal.
+
+
+### What should I do when the image failed to be burnt?<a name="section1370982513317"></a>
+
+-   **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.
+
+
+### What should I do when no command output is displayed?<a name="section183421944953"></a>
+
+-   **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:
+
+
+1.  Obtain the U-Boot file.
+
+    >![](public_sys-resources/icon-notice.gif) **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**
+
+2.  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](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)
+
+3.  Log in to the serial port after the burning is complete.
+
+    **Figure  1**  Serial port displayed after the U-Boot is burnt<a name="en-us_topic_0000001128470856_en-us_topic_0000001053466255_fig155914681910"></a>  
+    ![](figures/serial-port-displayed-after-the-u-boot-is-burnt.png "serial-port-displayed-after-the-u-boot-is-burnt")
+
+
+### What should I do when Windows-based PC failed to be connected to the board?<a name="section1215410450215"></a>
+
+-   **Symptom**
+
+    The file image cannot be obtained after clicking  **Burn**  and selecting a serial port.
+
+    **Figure  2**  Failed to obtain the image file due to unavailable connection<a name="en-us_topic_0000001128470856_fig135261439195819"></a>  
+    ![](figures/failed-to-obtain-the-image-file-due-to-unavailable-connection.png "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**
+
+1.  Check whether the network cable is properly connected.
+2.  Click  **Windows Firewall**.
+
+    ![](figures/hi3516-network-and-firewall-setting.png)
+
+3.  Click  **Firewall & network protection**, and on the displayed page, click  **Allow applications to communicate through Windows Firewall**.
+
+    ![](figures/hi3516-firewall-and-network-protection.png)
+
+4.  Select the Visual Studio Code application.
+
+    ![](figures/hi3516-selecting-the-visual-studio-code-application.png)
+
+5.  Select the  **Private**  and  **Public**  network access rights for the Visual Studio Code application.
+
+    ![](figures/hi3516-allowing-the-visual-studio-code-application-to-access-the-network.png)
+
+

en/device-dev/faqs/compilation-and-building-subsystem.md

+# Compilation and Building Subsystem<a name="EN-US_TOPIC_0000001215530845"></a>
+
+-   [Mini and Small Systems](#section78686441462)
+    -   [Invalid -- w Option](#section67961431372)
+    -   [Library ncurses Not Found](#section199631617371)
+    -   [mcopy not Found](#section937435175)
+    -   [No riscv File or Directory](#section1115535018713)
+    -   [No Crypto](#section17982573813)
+    -   [Unexpected Operator](#section53663205819)
+    -   [What should I do when the message Could not find a version that satisfies the requirement six\>=1.9.0 is displayed during compilation and building?](#section1917790845)
+    -   [What should I do when the message cannot find -lgcc is displayed during compilation and building?](#section141771701647)
+    -   [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](#section51781202415)
+    -   [What should I do when the message indicating Python 3 cannot be found is displayed during compilation and building?](#section1917950148)
+
+
+## Mini and Small Systems<a name="section78686441462"></a>
+
+### Invalid -- w Option<a name="section67961431372"></a>
+
+-   **Symptom**
+
+    The build fails, and "usr/sbin/ninja: invalid option -- w" is displayed.
+
+-   **Cause**
+
+    The Ninja version in the build environment is outdated and does not support the  **--w**  option.
+
+-   **Solution**
+
+    Uninstall Ninja and GN and follow the instructions provided in  [IDE](../get-code/gettools-ide.md)  to install Ninja and GN of the required version.
+
+
+### Library ncurses Not Found<a name="section199631617371"></a>
+
+-   **Symptom**
+
+    The build fails, and "/usr/bin/ld: cannot find -lncurses" is displayed.
+
+-   **Cause**
+
+    The ncurses library is not installed.
+
+-   **Solution**
+
+    ```
+    sudo apt-get install lib32ncurses5-dev
+    ```
+
+
+### mcopy not Found<a name="section937435175"></a>
+
+-   **Symptom**
+
+    The build fails, and "line 77: mcopy: command not found" is displayed.
+
+-   **Cause**
+
+    mcopy is not installed.
+
+-   **Solution**
+
+    ```
+    ​sudo apt-get install dosfstools mtools
+    ```
+
+
+### No riscv File or Directory<a name="section1115535018713"></a>
+
+-   **Symptom**
+
+    The build fails, and the following information is displayed:
+
+    riscv32-unknown-elf-gcc: error trying to exec 'cc1': execvp: No such file or directory.
+
+-   **Cause**
+
+    Permission is required to access files in the  **riscv**  compiler directory.
+
+-   **Solution**
+
+    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**.
+
+
+### No Crypto<a name="section17982573813"></a>
+
+-   **Symptom**
+
+    The build fails, and "No module named 'Crypto'" is displayed.
+
+-   **Cause**
+
+    Crypto is not installed in Python 3.
+
+-   **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:
+
+        ```
+        sudo pip3 install pycryptodome
+        ```
+
+
+
+### Unexpected Operator<a name="section53663205819"></a>
+
+-   **Symptom**
+
+    The build fails, and "xx.sh \[: xx unexpected operator" is displayed.
+
+-   **Cause**
+
+    The build environment is shell, not bash.
+
+-   **Solution**
+
+    ```
+    sudo rm -rf /bin/sh
+    sudo ln -s /bin/bash /bin/sh
+    ```
+
+
+### What should I do when the message  **Could not find a version that satisfies the requirement six\>=1.9.0**  is displayed during compilation and building?<a name="section1917790845"></a>
+
+-   **Symptom**
+
+    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.
+
+
+-   **Solutions**
+
+    Solution 1: Run the  **pip3 install six**  command to install  **six**  online.
+
+    Solution 2: Install  **six**  offline.
+
+    -   Download the installation package from  [https://pypi.org/project/six/\#files](https://pypi.org/project/six/#files).
+
+    ![](figures/download-six.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**.
+    -   Rebuild an environment.
+
+
+### What should I do when the message  **cannot find -lgcc**  is displayed during compilation and building?<a name="section141771701647"></a>
+
+-   **Symptom**
+
+    The following error occurs during compilation and building:
+
+    ```
+    riscv32-unknown-elf-ld: cannot find -lgcc
+    ```
+
+
+-   **Possible Causes**
+
+    The PATH is incorrectly written by  **gcc\_riscv32**. There is an extra slash \(/\).
+
+    ```
+    ~/gcc_riscv32/bin/:/data/toolchain/
+    ```
+
+
+-   **Solutions**
+
+    Modify the PATH by deleting the slash \(/\).
+
+    ```
+    ~/gcc_riscv32/bin:/data/toolchain/
+    ```
+
+
+### What should I do when the message indicating Python cannot be found is displayed during compilation and building?<a name="section51781202415"></a>
+
+-   **Symptom**
+
+    The following error occurs during compilation and building:
+
+    ```
+    -bash: /usr/bin/python: No such file or directory
+    ```
+
+
+-   **Possible Cause 1:**  Python is not installed.
+-   **Solutions**
+
+    [Install Python](../quick-start/quickstart-lite-env-setup-linux.md).
+
+-   **Possible Cause 2:**  The soft link that points to the Python does not exist in the  **usr/bin**  directory.
+
+    ![](figures/reason-no-python-soft-link.png)
+
+-   **Solutions**
+
+    Run the following commands to add a soft link:
+
+    ```
+    # cd /usr/bin/
+    # which python3
+    # ln -s /usr/local/bin/python3 python
+    # python --version
+    ```
+
+    Example:
+
+    ![](figures/solution-add-soft-link.png)
+
+
+### What should I do when the message indicating Python 3 cannot be found is displayed during compilation and building?<a name="section1917950148"></a>
+
+-   **Symptom**
+
+    ![](figures/11.png)
+
+
+-   **Possible Causes**
+
+    Python 3 is not installed.
+
+-   **Solutions**
+
+    [Install Python](../quick-start/quickstart-lite-env-setup-linux.md).
+
+

en/device-dev/faqs/environment-setup.md

+# Environment Setup<a name="EN-US_TOPIC_0000001215650793"></a>
+
+-   [Mini and Small Systems](#section1742119306399)
+    -   [What should I do if garbled characters and segmentation faults occur during hb installation?](#section36351051193919)
+    -   [What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation?](#section48221013144011)
+    -   [What should I do if the message "module 'platform' has no attribute 'linux\_distribution'" is displayed during hb installation?](#section10307193044111)
+    -   [What should I do if the message "Could not find a version that satisfies the requirement ohos-build" is displayed during hb installation?](#section8692735427)
+    -   [What should I do when the message configure: error: no acceptable C compiler found in $PATH is displayed during Python 3 installation?](#section870082884217)
+    -   [What should I do when the message -bash: make: command not found is displayed during Python 3 installation?](#section198707170455)
+    -   [What should I do when the message zlib not available is displayed during Python 3 installation?](#section85401445204518)
+    -   [What should I do when the message No module named '\_ctypes' is displayed during Python 3 installation?](#section12202694460)
+    -   [What should I do when an error with lsb\_release occurs during kconfiglib installation?](#section5803174135115)
+    -   [What should I do if the message "ImportError: No module named apt\_pkg" is displayed during the execution of an unidentifiable command?](#section510820516515)
+
+
+## Mini and Small Systems<a name="section1742119306399"></a>
+
+### What should I do if garbled characters and segmentation faults occur during hb installation?<a name="section36351051193919"></a>
+
+-   **Symptom**
+
+    Garbled characters and segmentation faults occur during the execution of the  **python3 -m pip install --user ohos-build**  command.
+
+
+-   **Possible Causes**
+
+    pip is of an early version.
+
+-   **Solutions**
+
+    Upgrade pip.
+
+    ```
+    python3 -m pip install -U pip
+    ```
+
+
+### What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation?<a name="section48221013144011"></a>
+
+-   **Symptom**
+
+    The message "cannot import 'sysconfig' from 'distutils'" is displayed during the execution of the  **python3 -m pip install --user ohos-build**  command.
+
+
+-   **Possible Causes**
+
+    The  **distutils**  module is unavailable.
+
+-   **Solutions**
+
+    Install  **distutils**.
+
+    ```
+    sudo apt-get install python3.8-distutils
+    ```
+
+
+### What should I do if the message "module 'platform' has no attribute 'linux\_distribution'" is displayed during hb installation?<a name="section10307193044111"></a>
+
+-   **Symptom**
+
+    The message "module 'platform' has no attribute 'linux\_distribution'" is displayed during the execution of the  **python3 -m pip install --user ohos-build**  command.
+
+
+-   **Possible Causes**
+
+    There is a compatibility issue of python3-pip.
+
+-   **Solutions**
+
+    Reinstall pip.
+
+    ```
+    sudo apt remove python3-pip
+    curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
+    python get-pip.py
+    ```
+
+
+### What should I do if the message "Could not find a version that satisfies the requirement ohos-build" is displayed during hb installation?<a name="section8692735427"></a>
+
+-   **Symptom**
+
+    The message "Could not find a version that satisfies the requirement ohos-build" is displayed during the execution of the  **python3 -m pip install --user ohos-build**  command.
+
+
+-   **Possible Causes**
+
+    The installation fails due to poor network connectivity.
+
+-   **Solutions**
+    1.  Ensure that your computer has a good network connection. If the network connection is unstable, rectify the network fault and reinstall hb.
+    2.  If the network is functional, run the following commands to install hb by specifying a temporary PyPI source:
+
+        ```
+        python3 -m pip install -i https://pypi.tuna.tsinghua.edu.cn/simple ohos-build
+        ```
+
+
+
+### What should I do when the message  **configure: error: no acceptable C compiler found in $PATH**  is displayed during Python 3 installation?<a name="section870082884217"></a>
+
+-   **Symptom**
+
+    The following error occurs during Python 3 installation:
+
+    ```
+    configure: error: no acceptable C compiler found in $PATH. See 'config.log' for more details
+    ```
+
+-   **Possible Causes**
+
+    **GCC**  is not installed.
+
+-   **Solutions**
+
+    1. Run the  **apt-get install gcc**  command to install  **GCC**  online.
+
+    2. After the installation, reinstall Python 3.
+
+
+### What should I do when the message  **-bash: make: command not found**  is displayed during Python 3 installation?<a name="section198707170455"></a>
+
+-   **Symptom**
+
+    The following error occurs during Python 3 installation:
+
+    ```
+    -bash: make: command not found
+    ```
+
+-   **Possible Causes**
+
+    **Make**  is not installed.
+
+-   **Solutions**
+
+    1. Run the  **apt-get install make**  command to install  **Make**  online.
+
+    2. After the installation, reinstall Python 3.
+
+
+### What should I do when the message  **zlib not available**  is displayed during Python 3 installation?<a name="section85401445204518"></a>
+
+-   **Symptom**
+
+    The following error occurs during Python 3 installation:
+
+    ```
+    zipimport.ZipImportError: can't decompress data; zlib not available
+    ```
+
+-   **Possible Causes**
+
+    **zlib**  is not installed.
+
+-   **Solutions**
+
+    Solution 1: Run the  **apt-get install zlib**  command to install  **zlib**  online.
+
+    Solution 2: If the software source does not contain  **zlib**, download the source code from  https://www.zlib.net/.
+
+    ![](figures/download-zlib.png)
+
+    Then run the following commands to install  **zlib**  offline:
+
+    ```
+    # tar xvf zlib-1.2.11.tar.gz
+    # cd zlib-1.2.11
+    # ./configure
+    # make && make install
+    ```
+
+    After the installation, reinstall Python 3.
+
+
+### What should I do when the message  **No module named '\_ctypes'**  is displayed during Python 3 installation?<a name="section12202694460"></a>
+
+-   **Symptom**
+
+    The following error occurs during Python 3 installation:
+
+    ```
+    ModuleNotFoundError: No module named '_ctypes'
+    ```
+
+
+-   **Possible Causes**
+
+    **libffi**  and  **libffi-devel**  are not installed.
+
+
+-   **Solutions**
+
+    1. Run the  **apt-get install libffi\* -y**  command to install  **libffi**  and  **libffi-devel**  online.
+
+    2. After the installation, reinstall Python 3.
+
+
+### What should I do when an error with  **lsb\_release**  occurs during  **kconfiglib**  installation?<a name="section5803174135115"></a>
+
+-   **Symptom**
+
+    The following error occurs during  **kconfiglib**  installation:
+
+    ```
+    subprocess.CalledProcessError: Command '('lsb_release', '-a')' returned non-zero exit status 1.
+    ```
+
+-   **Possible Causes**
+
+    The Python version matched with the  **lsb\_release**  module is different from the current Python version.
+
+-   **Solutions**
+
+    Run the  **find / -name lsb\_release**  command, for example,  **sudo rm -rf /usr/bin/lsb\_release**  to locate and delete  **lsb\_release**.
+
+
+### What should I do if the message "ImportError: No module named apt\_pkg" is displayed during the execution of an unidentifiable command?<a name="section510820516515"></a>
+
+-   **Symptom**
+
+    The message "ImportError: No module named apt\_pkg" is displayed when an unidentifiable command is executed on the Linux server.
+
+
+-   **Possible Causes**
+
+    There is a compatibility issue of python3-apt.
+
+-   **Solutions**
+
+    Reinstall python3-apt.
+
+    ```
+    sudo apt-get remove  python3-apt
+    sudo apt-get install python3-apt
+    ```
+
+

en/device-dev/faqs/kernel.md

+# Kernel<a name="EN-US_TOPIC_0000001169850498"></a>
+
+-   [Basic Kernel](#section263912372168)
+    -   [What are the differences between APIs provided by LiteOS-A and LiteOS-M?](#section447571122918)
+    -   [How do I analyze thread stack overflow?](#section8623141711293)
+
+-   [File System](#section098519592162)
+    -   [What should I do when the Hi3516 board fails to open the same file in write mode \(LiteOS-A\)?](#section517972255311)
+    -   [What hardware platforms are supported by the LiteOS kernel?](#section868413518533)
+    -   [What chip architectures are supported by the LiteOS kernel?](#section1131661465417)
+
+-   [Third-party Components](#section971818231178)
+    -   [What third-party components are supported by OpenHarmony?](#section74138185411)
+    -   [What should I do if the key length verification fails when OpenSSL is used on OpenHarmony?](#section10564614135516)
+    -   [Does setsockopt support SO\_RCVBUF and SO\_SNDBUF?](#section2093373215556)
+
+-   [Compilation and Linking](#section10955302179)
+    -   [How do I run an application developed by ARM Linux on LiteOS-A?](#section1164175713557)
+    -   [What system is used for OpenHarmony compilation? What compiler is used?](#section132287223567)
+    -   [For a third-party component that is independently compiled into a static library and used on LiteOS-M, what should I do when the component's global variable value is incorrect or the system is suspended after the component's function is called?](#section15189154225619)
+    -   [What should I do if the message "use VFP register arguments, xxx.o does not" is displayed when LiteOS-A generates a target executable file?](#section193571012578)
+    -   [What should I do when calling clock\_gettime obtains an incorrect time?](#section8973152015717)
+
+
+## Basic Kernel<a name="section263912372168"></a>
+
+### What are the differences between APIs provided by LiteOS-A and LiteOS-M?<a name="section447571122918"></a>
+
+Basic kernel APIs are different. LiteOS-A provides the standard Portable Operating System Interface \(POSIX\), and LiteOS-M provides standard POSIX and Common Microcontroller Software Interface Standard \(CMSIS\) interfaces. To support cross-platform functions, standard interfaces such as POSIX are recommended for third-party adaptation.
+
+### How do I analyze thread stack overflow?<a name="section8623141711293"></a>
+
+**Symptom**
+
+The system is abnormal, and the message "CURRENT task  _ThreadName_  stack overflow!" is displayed.
+
+**Solution**
+
+1.  When creating the thread, double the thread stack size. If the problem does not recur after multiple attempts, the task stack size is insufficient and needs to be increased.
+2.  If the problem persists after the thread stack size is increased, check whether an ultra-large array is defined in the thread or whether recursive invoking exists in the process.
+3.  If the preceding causes are excluded, check whether memory corruption occurs.
+
+## File System<a name="section098519592162"></a>
+
+### What should I do when the Hi3516 board fails to open the same file in write mode \(LiteOS-A\)?<a name="section517972255311"></a>
+
+When a file is already open, it is not allowed to open the file in write mode again, because the Hi3516 board uses the FAT file system.
+
+### What hardware platforms are supported by the LiteOS kernel?<a name="section868413518533"></a>
+
+LiteOS-A supports the Hi3516 and Hi3518 development boards. LiteOS-M supports the Hi3861 development board, STM32F103, STM32F429IGTb, and Nucleo\_f767zi. For details, see the  **README.md**  file in the  **kernel/liteos\_m**  directory.
+
+### What chip architectures are supported by the LiteOS kernel?<a name="section1131661465417"></a>
+
+LiteOS-M supports RISC-V, Cortex-M3, Cortex-M4, Cortex-M7, Cortex-M33, and Arm 9, and will support c-sky and Xtensa. LiteOS-A supports ARMv7-A and will support ARMv8-A. Any new update will be released in the OpenHarmony community.
+
+## Third-party Components<a name="section971818231178"></a>
+
+### What third-party components are supported by OpenHarmony?<a name="section74138185411"></a>
+
+Open-source components \(such as mbedTLS and LwIP\) and third-party libraries have been provided and can be directly used. In addition, standard POSIX is provided for adaptation.
+
+### What should I do if the key length verification fails when OpenSSL is used on OpenHarmony?<a name="section10564614135516"></a>
+
+Check whether the architecture type \(such as ARM and x86\) and the number of system bits \(32-bit and 64-bit\) are correctly selected in OpenSSL compilation options.
+
+### Does setsockopt support SO\_RCVBUF and SO\_SNDBUF?<a name="section2093373215556"></a>
+
+No. It does not support SO\_RCVBUF or SO\_SNDBUF.
+
+## Compilation and Linking<a name="section10955302179"></a>
+
+### How do I run an application developed by ARM Linux on LiteOS-A?<a name="section1164175713557"></a>
+
+The application must be recompiled using the cross-compiler provided in OpenHarmony before it can run.
+
+### What system is used for OpenHarmony compilation? What compiler is used?<a name="section132287223567"></a>
+
+LiteOS-A is compiled in the Linux environment by using the LLVM compiler. LiteOS-M can be compiled in the Linux or Windows environment by using compilers such as IAR, Keil, and GCC.
+
+### For a third-party component that is independently compiled into a static library and used on LiteOS-M, what should I do when the component's global variable value is incorrect or the system is suspended after the component's function is called?<a name="section15189154225619"></a>
+
+Check whether address-irrelevant compilation options, such as  **-fPIE**,  **-fpie**,  **-fPIC**, and  **-fpic**, exist in the third-party component compilation options. If yes, delete them and recompile the third-party component into a static library.
+
+### What should I do if the message "use VFP register arguments, xxx.o does not" is displayed when LiteOS-A generates a target executable file?<a name="section193571012578"></a>
+
+Check whether the  **-mfloat-abi=xxx**,  **-mcpu=xxx**, and  **-mfpu=xxx**  compilation options are added during the compilation of  **xxx.o**. If not, add them.
+
+### What should I do when calling clock\_gettime obtains an incorrect time?<a name="section8973152015717"></a>
+
+In  **struct timespec**,  **tv\_sec**  is  **time\_t**, which is of the long long type, and the print control character is  **%lld**. Check whether the print control character in use is correct.
+

en/device-dev/faqs/overview-of-faqs.md

+# Overview of FAQs<a name="EN-US_TOPIC_0000001169691604"></a>
+
+-   [Environment Setup](#section93289248249)
+    -   [Mini and Small Systems](#section197234983111)
+
+-   [Compilation and Building](#section18826114693810)
+    -   [Mini and Small Systems](#section693410399)
+
+-   [Burning](#section6556741113712)
+    -   [Mini and Small Systems](#section1029933713812)
+
+-   [Kernel](#section13741125564211)
+    -   [Basic Kernel](#section1723365191114)
+    -   [File System](#section14523145918136)
+    -   [Chip Adaptation](#section141541939159)
+    -   [Third-party Components](#section4988163321816)
+    -   [Compilation and Linking](#section080219574225)
+
+-   [Porting](#section129331824154313)
+-   [Startup and Recovery](#section83501764443)
+-   [System Services](#section19567132114455)
+    -   [Utils](#section3214181711465)
+    -   [Visual Applications](#section295651815466)
+    -   [HDC](#section178081876506)
+
+
+FAQs are used to help developers solve problems frequently encountered during development. They cover a wide range of topics.
+
+## Environment Setup<a name="section93289248249"></a>
+
+### Mini and Small Systems<a name="section197234983111"></a>
+
+-   [What should I do if garbled characters and segmentation faults occur during hb installation?](environment-setup.md#section36351051193919)
+-   [What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation?](environment-setup.md#section48221013144011)
+-   [What should I do if the message "module 'platform' has no attribute 'linux\_distribution'" is displayed during hb installation?](environment-setup.md#section10307193044111)
+-   [What should I do if the message "Could not find a version that satisfies the requirement ohos-build" is displayed during hb installation?](environment-setup.md#section8692735427)
+-   [What should I do when the message configure: error: no acceptable C compiler found in $PATH is displayed during Python 3 installation?](environment-setup.md#section870082884217)
+-   [What should I do when the message -bash: make: command not found is displayed during Python 3 installation?](environment-setup.md#section198707170455)
+-   [What should I do when the message zlib not available is displayed during Python 3 installation?](environment-setup.md#section85401445204518)
+-   [What should I do when the message No module named '\_ctypes' is displayed during Python 3 installation?](environment-setup.md#section12202694460)
+-   [What should I do when an error with lsb\_release occurs during kconfiglib installation?](environment-setup.md#section5803174135115)
+-   [What should I do if the message "ImportError: No module named apt\_pkg" is displayed during the execution of an unidentifiable command?](environment-setup.md#section510820516515)
+
+## Compilation and Building<a name="section18826114693810"></a>
+
+### Mini and Small Systems<a name="section693410399"></a>
+
+-   [Invalid -- w Option](compilation-and-building-subsystem.md#section67961431372)
+-   [Library ncurses Not Found](compilation-and-building-subsystem.md#section199631617371)
+-   [mcopy not Found](compilation-and-building-subsystem.md#section937435175)
+-   [No riscv File or Directory](compilation-and-building-subsystem.md#section1115535018713)
+-   [No Crypto](compilation-and-building-subsystem.md#section17982573813)
+-   [Unexpected Operator](compilation-and-building-subsystem.md#section53663205819)
+-   [What should I do when the message Could not find a version that satisfies the requirement six\>=1.9.0 is displayed during compilation and building?](compilation-and-building-subsystem.md#section1917790845)
+-   [What should I do when the message cannot find -lgcc is displayed during compilation and building?](compilation-and-building-subsystem.md#section141771701647)
+-   [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](compilation-and-building-subsystem.md#section51781202415)
+-   [What should I do when the message indicating Python 3 cannot be found is displayed during compilation and building?](compilation-and-building-subsystem.md#section1917950148)
+
+## Burning<a name="section6556741113712"></a>
+
+### Mini and Small Systems<a name="section1029933713812"></a>
+
+-   ["Error: Opening COMxx: Access denied" Is Displayed After a Serial Port Is Selected for Burning](burning.md#section18988185615914)
+
+-   [What should I do when the image failed to be burnt?](burning.md#section1370982513317)
+-   [What should I do when no command output is displayed?](burning.md#section183421944953)
+-   [What should I do when Windows-based PC failed to be connected to the board?](burning.md#section1215410450215)
+
+## Kernel<a name="section13741125564211"></a>
+
+### Basic Kernel<a name="section1723365191114"></a>
+
+-   [What are the differences between APIs provided by LiteOS-A and LiteOS-M?](kernel.md#section447571122918)
+-   [How do I analyze thread stack overflow?](kernel.md#section8623141711293)
+
+### File System<a name="section14523145918136"></a>
+
+-   [What should I do when the Hi3516 board fails to open the same file in write mode \(LiteOS-A\)?](kernel.md#section517972255311)
+
+### Chip Adaptation<a name="section141541939159"></a>
+
+-   [What hardware platforms are supported by the LiteOS kernel?](kernel.md#section868413518533)
+-   [What chip architectures are supported by the LiteOS kernel?](kernel.md#section1131661465417)
+
+### Third-party Components<a name="section4988163321816"></a>
+
+-   [What third-party components are supported by OpenHarmony?](kernel.md#section74138185411)
+-   [What should I do if the key length verification fails when OpenSSL is used on OpenHarmony?](kernel.md#section10564614135516)
+-   [Does setsockopt support SO\_RCVBUF and SO\_SNDBUF?](kernel.md#section2093373215556)
+
+### Compilation and Linking<a name="section080219574225"></a>
+
+-   [How do I run an application developed by ARM Linux on LiteOS-A?](kernel.md#section1164175713557)
+-   [What system is used for OpenHarmony compilation? What compiler is used?](kernel.md#section132287223567)
+-   [For a third-party component that is independently compiled into a static library and used on LiteOS-M, what should I do when the component's global variable value is incorrect or the system is suspended after the component's function is called?](kernel.md#section15189154225619)
+-   [What should I do if the message "use VFP register arguments, xxx.o does not" is displayed when LiteOS-A generates a target executable file?](kernel.md#section193571012578)
+-   [What should I do when calling clock\_gettime obtains an incorrect time?](kernel.md#section8973152015717)
+
+## Porting<a name="section129331824154313"></a>
+
+-   [How Do I Mount the Heap Memory to the Kernel?](porting.md#section21471536184914)
+
+## Startup and Recovery<a name="section83501764443"></a>
+
+-   [System startup interrupted due to "parse failed!" error](startup-and-recovery.md#section835662214302)
+-   [System automatically restarted again and again](startup-and-recovery.md#section3857921143117)
+-   [Failed to call the SetParameter or GetParameter API with correct parameter values](startup-and-recovery.md#section548818116328)
+
+## System Services<a name="section19567132114455"></a>
+
+### Utils<a name="section3214181711465"></a>
+
+-   [1. Failure in running the KV store on the LiteOS-A kernel \(Hi3516 or Hi3518\) due to incorrect path setting for the KV store](system-applications.md#section16520347131511)
+
+### Visual Applications<a name="section295651815466"></a>
+
+-   [Is there a global variable that can be accessed by all pages?](system-applications.md#section187297991718)
+-   [How do I obtain DOM elements?](system-applications.md#section1833493719175)
+-   [How do I pass values between pages?](system-applications.md#section184283812183)
+-   [How do I scroll a list to an item?](system-applications.md#section11897734131811)
+-   [Does the <text\> component support multiple lines?](system-applications.md#section5872656121814)
+-   [Why is a component not displayed?](system-applications.md#section7397125317107)
+-   [How do I implement scrolling on a page?](system-applications.md#section338794422010)
+-   [Why do not the left and top attributes take effect?](system-applications.md#section2597193611217)
+-   [Why does not dynamic binding take effect?](system-applications.md#section6939050172115)
+-   [How do I implement relative and absolute positioning?](system-applications.md#section5547311192215)
+-   [How do I display or hide a component?](system-applications.md#section16107113352213)
+-   [What are the precautions for using the margin attribute?](system-applications.md#section1524910142314)
+-   [What are the precautions for event subscription?](system-applications.md#section1537132012231)
+-   [What are the precautions for using dynamic binding?](system-applications.md#section96561452236)
+-   [How does the loop attribute take effect for <swiper\>?](system-applications.md#section690166112414)
+-   [What are the precautions for using an array?](system-applications.md#section1554552822414)
+
+### HDC<a name="section178081876506"></a>
+
+-   [hdc\_std Fails to Connect to a Device](system-applications.md#section1965012223257)
+-   [hdc\_std Fails to Run](system-applications.md#section1157575212515)
+

en/device-dev/faqs/porting.md

+# Porting<a name="EN-US_TOPIC_0000001215769367"></a>
+
+-   [How Do I Mount the Heap Memory to the Kernel?](#section21471536184914)
+
+## How Do I Mount the Heap Memory to the Kernel?<a name="section21471536184914"></a>
+
+-   The following table describes the macros for configuring the kernel heap memory. You can configure them as required in the  **target\_config.h**  file.
+
+**Table  1**  Macros for configuring the kernel heap memory
+
+<a name="en-us_topic_0000001153683024_table04172020563"></a>
+<table><thead align="left"><tr id="en-us_topic_0000001153683024_row5462035616"><th class="cellrowborder" valign="top" width="39.12%" id="mcps1.2.3.1.1"><p id="en-us_topic_0000001153683024_p1456204569"><a name="en-us_topic_0000001153683024_p1456204569"></a><a name="en-us_topic_0000001153683024_p1456204569"></a>Macro</p>
+</th>
+<th class="cellrowborder" valign="top" width="60.88%" id="mcps1.2.3.1.2"><p id="en-us_topic_0000001153683024_p19502005618"><a name="en-us_topic_0000001153683024_p19502005618"></a><a name="en-us_topic_0000001153683024_p19502005618"></a>Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="en-us_topic_0000001153683024_row14522018560"><td class="cellrowborder" valign="top" width="39.12%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001153683024_p35112025620"><a name="en-us_topic_0000001153683024_p35112025620"></a><a name="en-us_topic_0000001153683024_p35112025620"></a>LOSCFG_SYS_EXTERNAL_HEAP</p>
+</td>
+<td class="cellrowborder" valign="top" width="60.88%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001153683024_p5127138175710"><a name="en-us_topic_0000001153683024_p5127138175710"></a><a name="en-us_topic_0000001153683024_p5127138175710"></a>Specifies whether the internal kernel heap memory or the user heap memory will be used. The default value is <strong id="en-us_topic_0000001153683024_b161891157141719"><a name="en-us_topic_0000001153683024_b161891157141719"></a><a name="en-us_topic_0000001153683024_b161891157141719"></a>0</strong> and indicates that the internal heap memory whose size is <strong id="en-us_topic_0000001153683024_b116218121820"><a name="en-us_topic_0000001153683024_b116218121820"></a><a name="en-us_topic_0000001153683024_b116218121820"></a>0x10000</strong> will be used. If you want to use the external heap memory, set this macro to <strong id="en-us_topic_0000001153683024_b2744657141814"><a name="en-us_topic_0000001153683024_b2744657141814"></a><a name="en-us_topic_0000001153683024_b2744657141814"></a>1</strong>.</p>
+</td>
+</tr>
+<tr id="en-us_topic_0000001153683024_row20514209567"><td class="cellrowborder" valign="top" width="39.12%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001153683024_p5532017563"><a name="en-us_topic_0000001153683024_p5532017563"></a><a name="en-us_topic_0000001153683024_p5532017563"></a>LOSCFG_SYS_HEAP_ADDR</p>
+</td>
+<td class="cellrowborder" valign="top" width="60.88%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001153683024_p65520125619"><a name="en-us_topic_0000001153683024_p65520125619"></a><a name="en-us_topic_0000001153683024_p65520125619"></a>Specifies the start address of the kernel heap memory.</p>
+</td>
+</tr>
+<tr id="en-us_topic_0000001153683024_row15302929115615"><td class="cellrowborder" valign="top" width="39.12%" headers="mcps1.2.3.1.1 "><p id="en-us_topic_0000001153683024_p113021529145612"><a name="en-us_topic_0000001153683024_p113021529145612"></a><a name="en-us_topic_0000001153683024_p113021529145612"></a>LOSCFG_SYS_HEAP_SIZE</p>
+</td>
+<td class="cellrowborder" valign="top" width="60.88%" headers="mcps1.2.3.1.2 "><p id="en-us_topic_0000001153683024_p1030252965619"><a name="en-us_topic_0000001153683024_p1030252965619"></a><a name="en-us_topic_0000001153683024_p1030252965619"></a>Specifies the size of the kernel heap memory, that is, size of the memory block specified by <strong id="en-us_topic_0000001153683024_b1611815991419"><a name="en-us_topic_0000001153683024_b1611815991419"></a><a name="en-us_topic_0000001153683024_b1611815991419"></a>LOSCFG_SYS_HEAP_ADDR</strong>.</p>
+</td>
+</tr>
+</tbody>
+</table>
+
+-   Note:
+
+Ensure that the specified heap memory range is not used by other modules. Otherwise, functions of the heap memory will be damaged due to the heap memory corruption.
+

en/device-dev/faqs/startup-and-recovery.md

+# Startup and Recovery<a name="EN-US_TOPIC_0000001215449321"></a>
+
+-   [System startup interrupted due to "parse failed!" error](#section835662214302)
+-   [System automatically restarted again and again](#section3857921143117)
+-   [Failed to call the SetParameter or GetParameter API with correct parameter values](#section548818116328)
+
+## System startup interrupted due to "parse failed!" error<a name="section835662214302"></a>
+
+**Problem**
+
+During system startup, the error message "\[Init\] InitReadCfg, parse failed! please check file /etc/init.cfg format." is displayed, and the startup is interrupted, as shown in the following figure.
+
+**Figure  1**  Error information<a name="en-us_topic_0000001063231870_fig15217111545118"></a>  
+![](figures/error-information.png "error-information")
+
+**Cause**
+
+During the modification of the  **init.cfg**  file, required commas \(,\) or parentheses are missing or unnecessary ones are added. As a result, the file's JSON format becomes invalid.
+
+**Solution**
+
+Check the  **init.cfg**  file and ensure that its format meets the JSON specifications.
+
+## System automatically restarted again and again<a name="section3857921143117"></a>
+
+**Problem**
+
+After the image burning is complete, the system keeps restarting.
+
+**Cause**
+
+Each service started by the init process has the  **importance**  attribute, as described in Table 3 in init Module.
+
+-   If the attribute value is  **0**, the init process does not need to restart the development board when the current service process exits.
+-   If the attribute value is  **1**, the init process needs to restart the development board when the current service process exits.
+
+During the startup of a service whose  **importance**  is  **1**, if the service exits due to a process crash or an error, the init process automatically restarts the development board.
+
+**Solution**
+
+1.  View logs to identify the service that encounters a process crash or exits due to an error, rectify the issue, and then burn the image again.
+2.  Alternatively, change the value of  **importance**  to  **0**  for the service that exits due to a process crash or an error, and then burn the image again. In this way, the development board will not be restarted even if the service exits.
+
+## Failed to call the  **SetParameter**  or  **GetParameter**  API with correct parameter values<a name="section548818116328"></a>
+
+**Problem**
+
+Calling the  **SetParameter**  or  **GetParameter**  API fails even if correct values are passed to all input parameters.
+
+**Cause**
+
+Permission verification has been enabled for the  **SetParameter**  and  **GetParameter**  APIs. If the UID of the caller is greater than 1000, that is, the caller does not have the permission to call these APIs, API calls will fail even if the parameters are correct.
+
+**Solution**
+
+No action is required.
+

en/device-dev/faqs/system-applications.md

+# System Applications<a name="EN-US_TOPIC_0000001169690992"></a>
+
+-   [Utils](#section639433461512)
+    -   [1. Failure in running the KV store on the LiteOS-A kernel \(Hi3516 or Hi3518\) due to incorrect path setting for the KV store](#section16520347131511)
+
+-   [Visual Applications](#section787718474161)
+    -   [Is there a global variable that can be accessed by all pages?](#section187297991718)
+    -   [How do I obtain DOM elements?](#section1833493719175)
+    -   [How do I pass values between pages?](#section184283812183)
+    -   [How do I scroll a list to an item?](#section11897734131811)
+    -   [Does the <text\> component support multiple lines?](#section5872656121814)
+    -   [Why is a component not displayed?](#section7397125317107)
+    -   [How do I implement scrolling on a page?](#section338794422010)
+    -   [Why do not the left and top attributes take effect?](#section2597193611217)
+    -   [Why does not dynamic binding take effect?](#section6939050172115)
+    -   [How do I implement relative and absolute positioning?](#section5547311192215)
+    -   [How do I display or hide a component?](#section16107113352213)
+    -   [What are the precautions for using the margin attribute?](#section1524910142314)
+    -   [What are the precautions for event subscription?](#section1537132012231)
+    -   [What are the precautions for using dynamic binding?](#section96561452236)
+    -   [How does the loop attribute take effect for <swiper\>?](#section690166112414)
+    -   [What are the precautions for using an array?](#section1554552822414)
+
+-   [HDC](#section412357182518)
+    -   [hdc\_std Fails to Connect to a Device](#section1965012223257)
+    -   [hdc\_std Fails to Run](#section1157575212515)
+
+
+## Utils<a name="section639433461512"></a>
+
+### 1. Failure in running the KV store on the LiteOS-A kernel \(Hi3516 or Hi3518\) due to incorrect path setting for the KV store<a name="section16520347131511"></a>
+
+**Problem**
+
+When the LiteOS-A kernel \(Hi3516 or Hi3518 platform\) directly calls the API provided by the KV store, the compiled executable program fails to run.
+
+**Possible Causes**
+
+The compiled executable program is run directly without being converted to an application using  **AbilityKit**  APIs. In this case, the Bundle Manager Service \(BMS\) cannot correctly set the path for storing application data during application installation. As a result, the KV store fails to run.
+
+**Solution**
+
+Call the  **UtilsSetEnv**  function of the KV store to set the data storage path.
+
+```
+UtilsSetEnv("/storage/com.huawei.kv");
+```
+
+## Visual Applications<a name="section787718474161"></a>
+
+### Is there a global variable that can be accessed by all pages?<a name="section187297991718"></a>
+
+There is no such a global variable.
+
+### How do I obtain DOM elements?<a name="section1833493719175"></a>
+
+You can obtain DOM elements via the  **ref**  attribute. You can use methods of the obtained elements but cannot change their attributes. The sample code is as follows:
+
+```
+<!--index.hml-->
+<div class="container">
+   <!-- Set the ref attribute of the component to animator -->.
+   <image-animator class="image-player" ref="animator" images="{{images}}" duration="1s" onclick="handleClick"></image-animator>
+</div>
+
+/* index.js */
+export default {
+    data: {
+        images:[
+            {src:"common/frame1.png"},
+            {src:"common/frame2.png"},
+            {src:"common/frame3.png"}
+        ]
+    },
+    handleClick(){
+        // Obtain the component through the $refs attribute. (The ref attribute of the component has been set to animator in the HML file.)
+        const animator = this.$refs.animator;
+        const state = animator.getState();
+        if(state == "paused"){
+            animator.resume();
+        }else if(state == "stopped"){
+            animator.start();
+        }else{
+            animator.pause();
+        }
+    }
+}
+```
+
+### How do I pass values between pages?<a name="section184283812183"></a>
+
+You can pass values through  **params**  of the  **router.replace**  method. The sample code is as follows:
+
+Set  **params**  to the values to be passed on a page.
+
+```
+router.replace({
+     uri:'pages/detail/detail',  // URI of the page to switch to.
+    params:{transferData:this.data} // Data to be transferred. You need to define the data amount and name.
+});
+```
+
+Receive the passed values on another page.
+
+```
+onInit(){
+    const data = this.transferData; // Receive the transferred data by the onInit function.
+}  
+```
+
+### How do I scroll a list to an item?<a name="section11897734131811"></a>
+
+Call the  **scrollTo**  method of the list. The input parameter of this method is the index of the target item. You can specify an item index, or obtain the index through the  **scrollend**  event.
+
+### Does the  **<text\>**  component support multiple lines?<a name="section5872656121814"></a>
+
+Yes. You can use the Enter key to start a new line. Alternatively, the component automatically starts a new line based on the content, without the need to set the height attribute of the text.
+
+### Why is a component not displayed?<a name="section7397125317107"></a>
+
+**Description**
+
+The component added to the  **.hml**  file cannot be displayed.
+
+**Possible Causes**
+
+-   The width and height of the component may not be set.
+-   The style setting may be incorrect.
+
+**Solution**
+
+\(1\) Check whether the width and height values are set explicitly.
+
+\(2\) Check whether the style of the component is set correctly.
+
+### How do I implement scrolling on a page?<a name="section338794422010"></a>
+
+There are three ways to implement page scrolling:  **scroll**,  **<list\>**, or  **<swiper\>**. For a root component with  **scroll**  set, the scrolling effect is automatically implemented when the component size exceeds the screen size. For details, see the development specifications.
+
+### Why do not the  **left**  and  **top**  attributes take effect?<a name="section2597193611217"></a>
+
+**left**  and  **top**  attributes must work with the  **<stack\>**  component in addition to the root component.
+
+### Why does not dynamic binding take effect?<a name="section6939050172115"></a>
+
+The object or its attributes are not defined before dynamic binding.
+
+### How do I implement relative and absolute positioning?<a name="section5547311192215"></a>
+
+You can use the  **<div\>**  and  **<stack\>**  \(with  **top**  and  **left**  attributes\) components.
+
+### How do I display or hide a component?<a name="section16107113352213"></a>
+
+You can use  **display**,  **show**, or  **if**. When an  **if**  clause evaluates to  **false**, the corresponding component will be removed from the VDOM. When  **show**  is set to  **false**, the component will be invisible during rendering, but will not be removed from the VDOM.
+
+### What are the precautions for using the  **margin**  attribute?<a name="section1524910142314"></a>
+
+The  **margin**  attribute cannot be set for child components of the  **<stack\>**  component.
+
+### What are the precautions for event subscription?<a name="section1537132012231"></a>
+
+Only one page exists when the application is running. Therefore, the  **router.replace**  function destroys the previous page and then creates a new one. For pages involving event subscription, an event should be subscribed every time a page is created, and unsubscribed before page switching.
+
+### What are the precautions for using dynamic binding?<a name="section96561452236"></a>
+
+Do not use too many dynamic bindings because they consume too much memory.
+
+### How does the  **loop**  attribute take effect for  **<swiper\>**?<a name="section690166112414"></a>
+
+If the total length of the child components, except for the first and last ones, is greater than the length of  **<swiper\>**, the  **loop**  attribute takes effect.
+
+### What are the precautions for using an array?<a name="section1554552822414"></a>
+
+Do not include too many elements in an array. Avoid frequent operations on a large array.
+
+## HDC<a name="section412357182518"></a>
+
+### hdc\_std Fails to Connect to a Device<a name="section1965012223257"></a>
+
+-   **Symptom**
+
+    **\[Empty\]**  is displayed in the output after the  **hdc\_std list targets**  command is executed.
+
+-   **Solutions**
+    1.  The device cannot be identified.
+
+        Check whether  **HDC Device**  exists in the universal serial bus device of the device manager. If  **HDC Device**  does not exist, the device cannot be connected. In this case, remove and then insert the device or burn the latest image for the device.
+
+    2.  hdc\_std works improperly.
+
+        Run the  **hdc kill**  or  **hdc start -r**  command to kill or restart the hdc service. Then, run the  **hdc list targets**  command to check whether device information can be obtained.
+
+    3.  hdc\_std does not match the device.
+
+        If the latest image is burnt on the device, the latest hdc\_std version must be used. As hdc\_std is updated continuously, obtain hdc\_std of the latest version from the  **developtools\_hdc\_standard**  repository in the  **prebuilt**  directory.
+
+
+
+### hdc\_std Fails to Run<a name="section1157575212515"></a>
+
+-   **Symptom**
+
+    The  **hdc\_std.exe**  file does not run after being clicked.
+
+-   **Solutions**
+
+    **hdc\_std.exe**  requires no installation. It can be directly used on a disk or added to environment variables. Open the cmd window and run the  **hdc\_std**  command to use  **hdc\_std.exe**.
+
+

en/device-dev/get-code/sourcecode-acquire.md

-# Source Code Acquisition<a name="EN-US_TOPIC_0000001150448437"></a>
+# Obtaining Source Code<a name="EN-US_TOPIC_0000001150448437"></a>
 
 -   [About OpenHarmony](#section6370143622110)
 -   [Overview of Source Code Acquisition](#section12763342204)
@@ -6,15 +6,14 @@
     -   [When to Use](#section10881513459)
     -   [Prerequisites](#section102871547153314)
     -   [How to Use](#section429012478331)
-
 -   [Method 2: Acquiring Source Code from DevEco Marketplace](#section463013147412)
     -   [When to Use](#section26661067443)
     -   [Prerequisites](#section17544943123315)
     -   [How to Use](#section954619433333)
-
 -   [Method 3: Acquiring Source Code from a Mirror Site](#section1186691118430)
 -   [Method 4: Acquiring Source Code from the GitHub Image Repository \(at 23:00 UTC Every Day\)](#section23448418360)
--   [Source Code Directories](#section1072115612811)
+-   [ Source Code Directories](#section1072115612811)
+
 
 ## About OpenHarmony<a name="section6370143622110"></a>
 
@@ -174,9 +173,7 @@ You must install  **Node.js**  and HPM on your local PC. The installation proced
 
 To ensure the download performance, you are advised to download the source code or the corresponding solution from the image library of the respective site listed in the table below.
 
->![](../public_sys-resources/icon-note.gif) **NOTE:** 
->-   The table below provides only the sites for downloading the latest OpenHarmony master and LTS code. For details about how to obtain the source code of earlier versions, see the  [Release-Notes](../../release-notes/Readme.md).
->-   The Master 1.0 version is no longer maintained.
+The table below provides only the sites for downloading the latest OpenHarmony master and LTS code. For details about how to obtain the source code of earlier versions, see the  [Release-Notes](../../release-notes/Readme.md).
 
 **Table  1**  Sites for acquiring source code
 
@@ -248,7 +245,7 @@ To ensure the download performance, you are advised to download the source code
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p141101436193911"><a name="p141101436193911"></a><a name="p141101436193911"></a>3.0</p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p88931840195416"><a name="p88931840195416"></a><a name="p88931840195416"></a><a href="https://gitee.com/openharmony/docs/blob/OpenHarmony-3.0-LTS/zh-cn/release-notes/Readme.md" target="_blank" rel="noopener noreferrer">Download</a></p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p88931840195416"><a name="p88931840195416"></a><a name="p88931840195416"></a><a href="https://gitee.com/openharmony/docs/blob/master/en/release-notes/OpenHarmony-v3.0-LTS.md" target="_blank" rel="noopener noreferrer">Download</a></p>
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p039662242117"><a name="p039662242117"></a><a name="p039662242117"></a>-</p>
 </td>
@@ -257,9 +254,9 @@ To ensure the download performance, you are advised to download the source code
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p194141849163919"><a name="p194141849163919"></a><a name="p194141849163919"></a><strong id="b1094411391670"><a name="b1094411391670"></a><a name="b1094411391670"></a>Version Information</strong></p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p8414649193919"><a name="p8414649193919"></a><a name="p8414649193919"></a><strong id="b1926765243"><a name="b1926765243"></a><a name="b1926765243"></a>Site</strong></p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p8414649193919"><a name="p8414649193919"></a><a name="p8414649193919"></a><strong id="b1789439821"><a name="b1789439821"></a><a name="b1789439821"></a>Site</strong></p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p13415149133914"><a name="p13415149133914"></a><a name="p13415149133914"></a><strong id="b143972604"><a name="b143972604"></a><a name="b143972604"></a>SHA-256 Verification Code</strong></p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p13415149133914"><a name="p13415149133914"></a><a name="p13415149133914"></a><strong id="b533148863"><a name="b533148863"></a><a name="b533148863"></a>SHA-256 Verification Code</strong></p>
 </td>
 </tr>
 <tr id="row18518114121312"><td class="cellrowborder" valign="top" width="25%"><p id="p4437184283419"><a name="p4437184283419"></a><a name="p4437184283419"></a>Beta version (for standard systems)</p>
@@ -271,56 +268,11 @@ To ensure the download performance, you are advised to download the source code
 <td class="cellrowborder" valign="top" width="25%"><p id="p13437842103414"><a name="p13437842103414"></a><a name="p13437842103414"></a><a href="https://repo.huaweicloud.com/harmonyos/os/2.2-Beta2/code-v2.2-beta2_20210730.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
 </td>
 </tr>
-<tr id="row4769431134919"><td class="cellrowborder" valign="top" width="25%"><p id="p97691031124913"><a name="p97691031124913"></a><a name="p97691031124913"></a>Full code (for standard systems)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p1076916315492"><a name="p1076916315492"></a><a name="p1076916315492"></a>2.0 Canary</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p67696314491"><a name="p67696314491"></a><a name="p67696314491"></a><a href="https://repo.huaweicloud.com/harmonyos/os/2.0/code-2.0-canary_20210601.tar.gz" target="_blank" rel="noopener noreferrer">Download (Site 1)</a> <a href="https://mirror.iscas.ac.cn/OpenHarmony/os/2.0/code-2.0-canary.tar.gz" target="_blank" rel="noopener noreferrer">Download (Site 2)</a></p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p4769123184918"><a name="p4769123184918"></a><a name="p4769123184918"></a><a href="https://repo.huaweicloud.com/harmonyos/os/2.0/code-2.0-canary_20210601.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-</tr>
-<tr id="row273762316398"><td class="cellrowborder" valign="top" width="25%"><p id="p54150491393"><a name="p54150491393"></a><a name="p54150491393"></a>Full code (for mini and small systems)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p16415124923914"><a name="p16415124923914"></a><a name="p16415124923914"></a>1.0 (no longer maintained)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p44151449203917"><a name="p44151449203917"></a><a name="p44151449203917"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/code-1.0.tar.gz" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p1441515495392"><a name="p1441515495392"></a><a name="p1441515495392"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/code-1.0.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-</tr>
-<tr id="row107374239397"><td class="cellrowborder" valign="top" width="25%"><p id="p5415949123910"><a name="p5415949123910"></a><a name="p5415949123910"></a>Hi3861 solution (binary)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p15415949183914"><a name="p15415949183914"></a><a name="p15415949183914"></a>1.0 (no longer maintained)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p1415649123916"><a name="p1415649123916"></a><a name="p1415649123916"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/wifiiot-1.0.tar.gz" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p11415549153913"><a name="p11415549153913"></a><a name="p11415549153913"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/wifiiot-1.0.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-</tr>
-<tr id="row9738182319392"><td class="cellrowborder" valign="top" width="25%"><p id="p241524910391"><a name="p241524910391"></a><a name="p241524910391"></a>Hi3518 solution (binary)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p6415849193915"><a name="p6415849193915"></a><a name="p6415849193915"></a>1.0 (no longer maintained)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p841584919394"><a name="p841584919394"></a><a name="p841584919394"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/ipcamera_hi3518ev300-1.0.tar.gz" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p9415124983911"><a name="p9415124983911"></a><a name="p9415124983911"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/ipcamera_hi3518ev300-1.0.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-</tr>
-<tr id="row17381233399"><td class="cellrowborder" valign="top" width="25%"><p id="p44151149153918"><a name="p44151149153918"></a><a name="p44151149153918"></a>Hi3516 solution (binary)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p15415164917397"><a name="p15415164917397"></a><a name="p15415164917397"></a>1.0 (no longer maintained)</p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p154151049113914"><a name="p154151049113914"></a><a name="p154151049113914"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/ipcamera_hi3516dv300-1.0.tar.gz" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p164164491394"><a name="p164164491394"></a><a name="p164164491394"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/ipcamera_hi3516dv300-1.0.tar.gz.sha256" target="_blank" rel="noopener noreferrer">Download</a></p>
-</td>
-</tr>
 <tr id="row1873817234394"><td class="cellrowborder" valign="top" width="25%"><p id="p1341618491393"><a name="p1341618491393"></a><a name="p1341618491393"></a>RELEASE-NOTES</p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p7416184953916"><a name="p7416184953916"></a><a name="p7416184953916"></a>1.0 (no longer maintained)</p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p7416184953916"><a name="p7416184953916"></a><a name="p7416184953916"></a>2.2 Beta2</p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p194161849133911"><a name="p194161849133911"></a><a name="p194161849133911"></a><a href="https://repo.huaweicloud.com/harmonyos/os/1.0/RELEASE-NOTES.txt" target="_blank" rel="noopener noreferrer">Download</a></p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p194161849133911"><a name="p194161849133911"></a><a name="p194161849133911"></a><a href="https://gitee.com/openharmony/docs/blob/master/en/release-notes/OpenHarmony-v2.2-beta2.md" target="_blank" rel="noopener noreferrer">Download</a></p>
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p1841619490395"><a name="p1841619490395"></a><a name="p1841619490395"></a>-</p>
 </td>
@@ -329,7 +281,7 @@ To ensure the download performance, you are advised to download the source code
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p1093810218417"><a name="p1093810218417"></a><a name="p1093810218417"></a><strong id="b1124015405556"><a name="b1124015405556"></a><a name="b1124015405556"></a>Version Information</strong></p>
 </td>
-<td class="cellrowborder" valign="top" width="25%"><p id="p9938132648"><a name="p9938132648"></a><a name="p9938132648"></a><strong id="b1495715178"><a name="b1495715178"></a><a name="b1495715178"></a>Site</strong></p>
+<td class="cellrowborder" valign="top" width="25%"><p id="p9938132648"><a name="p9938132648"></a><a name="p9938132648"></a><strong id="b1225148075"><a name="b1225148075"></a><a name="b1225148075"></a>Site</strong></p>
 </td>
 <td class="cellrowborder" valign="top" width="25%"><p id="p12520113711011"><a name="p12520113711011"></a><a name="p12520113711011"></a><strong id="b19256751175516"><a name="b19256751175516"></a><a name="b19256751175516"></a>SHA-256 Verification Code</strong></p>
 </td>
@@ -364,7 +316,7 @@ repo sync -c
 repo forall -c 'git lfs pull'
 ```
 
-## Source Code Directories<a name="section1072115612811"></a>
+##  Source Code Directories<a name="section1072115612811"></a>
 
 The following table describes the OpenHarmony source code directories.
 

en/device-dev/guide/Readme-EN.md

 # Development Examples
 
-- [WLAN-connected Products](device-wifi.md)
-  - [LED Peripheral Control](device-wlan-led-outcontrol.md)
-  - [Third-Party SDK Integration](device-wlan-sdk.md)
-- [Cameras Without a Screen](device-iotcamera.md)
-  - [Camera Control](device-iotcamera-control.md)
-    - [Overview](device-iotcamera-control-overview.md)
-    - [Development Guidelines](device-iotcamera-control-demo.md)
-      - [Photographing](device-iotcamera-control-demo-photodevguide.md)
-      - [Video Recording](device-iotcamera-control-demo-videodevguide.md)
-    - [Use Case](device-iotcamera-control-example.md)
-- [Cameras with a Screen](device-camera.md)
-  - [Screen and Camera Control](device-camera-control.md)
-    - [Overview](device-camera-control-overview.md)
-    - [Development Guidelines](device-camera-control-demo.md)
-      - [Photographing](device-camera-control-demo-photoguide.md)
-      - [Video Recording](device-camera-control-demo-videoguide.md)
-      - [Previewing](device-camera-control-demo-previewguide.md)
-    - [Use Case](device-camera-control-example.md)
-  - [Visual Application Development](device-camera-visual.md)
-    - [Overview](device-camera-visual-overview.md)
-    - [Preparations](device-camera-visual-prepare.md)
-    - [Adding Pages](device-camera-visual-addpage.md)
-    - [Building the Home Page](device-camera-visual-firstpage.md)
-    - [Building the Details Page](device-camera-visual-details.md)
-    - [Debugging and Packaging](device-camera-visual-debug.md)
-    - [Running on the Device](device-camera-visual-run.md)
-    - [FAQs](device-camera-visual-faqs.md)
-- [Development Guidelines on Clock Apps](device-clock-guide.md)
-- [Development Example for Platform Drivers](device-driver-demo.md)
-- [Development Example for Peripheral Drivers](device-outerdriver-demo.md)
+- [Mini- and Small-System Devices](device-lite.md)
+  - [WLAN-connected Products](device-wlan.md)
+    - [LED Peripheral Control](device-wlan-led.md)
+      - [LED Peripheral Control](device-wlan-led-outcontrol.md)
+    - [Third-Party SDK Integration](device-wlan-sdk.md)
+  - [Cameras Without a Screen](device-iotcamera.md)
+    - [Camera Control](device-iotcamera-control.md)
+      - [Overview](device-iotcamera-control-overview.md)
+      - [Development Guidelines](device-iotcamera-control-demo.md)
+        - [Photographing](device-iotcamera-control-demo-photodevguide.md)
+        - [Video Recording](device-iotcamera-control-demo-videodevguide.md)
+      - [Use Case](device-iotcamera-control-example.md)
+  - [Cameras with a Screen](device-camera.md)
+    - [Screen and Camera Control](device-camera-control.md)
+      - [Overview](device-camera-control-overview.md)
+      - [Development Guidelines](device-camera-control-demo.md)
+        - [Photographing](device-camera-control-demo-photoguide.md)
+        - [Video Recording](device-camera-control-demo-videoguide.md)
+        - [Previewing](device-camera-control-demo-previewguide.md)
+      - [Use Case](device-camera-control-example.md)
+    - [Visual Application Development](device-camera-visual.md)
+      - [Overview](device-camera-visual-overview.md)
+      - [Preparations](device-camera-visual-prepare.md)
+      - [Adding Pages](device-camera-visual-addpage.md)
+      - [Building the Home Page](device-camera-visual-firstpage.md)
+      - [Building the Details Page](device-camera-visual-details.md)
+      - [Debugging and Packaging](device-camera-visual-debug.md)
+      - [Running on the Device](device-camera-visual-run.md)
+      - [FAQs](device-camera-visual-faqs.md)
+- [Standard-System Devices](device-standard.md)
\ No newline at end of file
+  - [Development Guidelines on Clock Apps](device-clock-guide.md)
+  - [Development Example for Platform Drivers](device-driver-demo.md)
+  - [Development Example for Peripheral Drivers](device-outerdriver-demo.md)
\ No newline at end of file

en/device-dev/guide/device-camera-control-demo-photoguide.md

@@ -363,7 +363,7 @@ None
     camKit->CreateCamera(camId, CamStateMng, eventHdlr);
     ```
 
-6.  In the main process, synchronize configurations set by callback functions implemented in  [step 1](#en-us_topic_0000001052170554_li378084192111),  [step 2](#en-us_topic_0000001052170554_li8716104682913), and  [step 3](#en-us_topic_0000001052170554_li6671035102514).
+6.  Based on the callback design in  [1](#en-us_topic_0000001052170554_li378084192111),  [2](#en-us_topic_0000001052170554_li8716104682913), and  [3](#en-us_topic_0000001052170554_li6671035102514), perform related operations until the  **OnCreated**  callback obtains  **cam\_**.
 
     ```
     void OnCreated(Camera &c) override

en/device-dev/guide/device-camera-control-example.md

@@ -3,7 +3,7 @@
 This use case takes  **camera\_sample**  \(contained in the source code\) as an example for photographing, recording, and previewing on the development board.
 
 -   You can obtain source code of the sample from  **applications/sample/camera/media/camera\_sample.cpp**.
--   Before running the sample camera, you need to compile, burn, and run the image. For details, see  [Hi3516 Development Board](../quick-start/quickstart-lite-introduction-hi3516.md#section26131214194212).
+-   Before running the sample camera, you need to compile, burn, and run the image. For details, see  [Hi3516 Development Board](../quick-start/oem_minitinier_des_3516.md#section26131214194212).
 
     >![](../public_sys-resources/icon-note.gif) **NOTE:** 
     >After the development board is started, the home screen is loaded and displayed above the media layer by default. To prevent covering  **camera\_sample**, you should remove the home screen during compilation or packaging.
@@ -27,38 +27,38 @@ This use case takes  **camera\_sample**  \(contained in the source code\) as an
 1.  Run the  **cd**  command to go to the end path of the executable program and start  **camera\_sample**  by running the command in the following figure.
 
     **Figure  1**  Starting camera\_sample<a name="fig380985885020"></a>  
-    ![](figure/starting-camera_sample.png "starting-camera_sample")
+    ![](figures/starting-camera_sample.png "starting-camera_sample")
 
     The control commands are displayed as shown in the preceding figure. Press  **S**  to stop the current operation \(including video recording and preview\), and press  **Q**  to exit the program.
 
 2.  Press  **1**  to take a photo in JPG format. The photo is saved in the  **/sdcard**  directory and named  **Capture\***.
 
     **Figure  2**  Serial port logs displayed after the photographing command is executed<a name="fig17819185018384"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-photographing-command-is-executed.png "serial-port-logs-displayed-after-the-photographing-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-photographing-command-is-executed.png "serial-port-logs-displayed-after-the-photographing-command-is-executed")
 
     To view the saved file, exit the program and enter the file system. To start the program again, return to the previous step.
 
     **Figure  3**  Saved files<a name="fig166391743154619"></a>  
-    ![](figure/saved-files.png "saved-files")
+    ![](figures/saved-files.png "saved-files")
 
 3.  Press  **2**  to start recording. The video file is in MP4 format and saved in the  **/sdcard**  directory with the name  **Record\***. Press  **S**  to stop recording.
 
     **Figure  4**  Serial port logs displayed after the recording command is executed<a name="fig6340814174317"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-recording-command-is-executed.png "serial-port-logs-displayed-after-the-recording-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-recording-command-is-executed.png "serial-port-logs-displayed-after-the-recording-command-is-executed")
 
 4.  Press  **3**  to start preview. The preview is displayed on the screen. Press  **S**  to stop preview.
 
     **Figure  5**  Serial port logs displayed after the preview command is executed<a name="fig9658148124414"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-preview-command-is-executed.png "serial-port-logs-displayed-after-the-preview-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-preview-command-is-executed.png "serial-port-logs-displayed-after-the-preview-command-is-executed")
 
     The following figure shows the preview.
 
     **Figure  6**  Preview effect<a name="fig24541759597"></a>  
-    ![](figure/preview-effect.jpg "preview-effect")
+    ![](figures/preview-effect.jpg "preview-effect")
 
 5.  Press  **Q**  to exit.
 
     **Figure  7**  Serial port logs displayed after the exit command is executed<a name="fig1755682174514"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-exit-command-is-executed.png "serial-port-logs-displayed-after-the-exit-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-exit-command-is-executed.png "serial-port-logs-displayed-after-the-exit-command-is-executed")
 
 

en/device-dev/guide/device-camera-visual-addpage.md

@@ -8,7 +8,7 @@
 Upon creation of the project, the  **index**  page is automatically generated, which is the home page of AirQuality.  [Figure 1](#fig16545205773718)  shows the project directory.
 
 **Figure  1**  Project directory<a name="fig16545205773718"></a>  
-![](figure/project-directory.png "project-directory")
+![](figures/project-directory.png "project-directory")
 
 ## Creating the Details Page<a name="section122131729173819"></a>
 
@@ -17,18 +17,18 @@ To the details page, perform the following steps:
 1.  Right-click  **pages**  and choose  **New**  \>  **JS Page**  from the shortcut menu.
 
     **Figure  2**  Adding a page<a name="fig18740145216410"></a>  
-    ![](figure/adding-a-page.png "adding-a-page")
+    ![](figures/adding-a-page.png "adding-a-page")
 
 2.  Enter the page name.
 
     **Figure  3**  Entering the page name<a name="fig48491266714"></a>  
-    ![](figure/entering-the-page-name.png "entering-the-page-name")
+    ![](figures/entering-the-page-name.png "entering-the-page-name")
 
 3.  Confirm the creation.
 
     The following figure shows the application project directory after the  **detail**  page is created. It contains a  **.hml**  layout file, a  **.css**  file, and a  **.js**  file \(containing service logic code\).
 
     **Figure  4**  Complete project directory<a name="fig103015177819"></a>  
-    ![](figure/complete-project-directory.png "complete-project-directory")
+    ![](figures/complete-project-directory.png "complete-project-directory")
 
 

en/device-dev/guide/device-camera-visual-faqs.md

 # FAQs<a name="EN-US_TOPIC_0000001055049072"></a>
 
-1.  Is there a global variable that can be accessed by all pages?
-
-    There is no such a global variable.
-
-2.  How do I obtain DOM elements?
-
-    You can obtain DOM elements via the  **ref**  attribute. You can use methods of the obtained elements but cannot change their attributes. The sample code is as follows:
-
-    ```
-    <!--index.hml-->
-    <div class="container">
-       <!-- Set the ref attribute of the component to animator -->.
-       <image-animator class="image-player" ref="ainmator" images="{{images}}" duration="1s" onclick="handleClick"></image-animator>
-    </div>
-    
-    /* index.js */
-    export default {
-        data: {
-            images:[
-                {src:"common/frame1.png"},
-                {src:"common/frame2.png"},
-                {src:"common/frame3.png"}
-            ]
-        },
-        handleClick(){
-            // Obtain the component through the $refs attribute. (The ref attribute of the component has been set to animator in the HML file.)
-            const animator = this.$refs.animator;
-            const state = animator.getState();
-            if(state == "paused"){
-                animator.resume();
-            }else if(state == "stopped"){
-                animator.start();
-            }else{
-                animator.pause();
-            }
+-   [Visual Application FAQs](#section147421736145813)
+    -   [Is there a global variable that can be accessed by all pages?](#section294382614018)
+    -   [How do I obtain DOM elements?](#section1423713435019)
+    -   [How do I pass values between pages?](#section119822143117)
+    -   [How do I scroll a list to an item?](#section188663819111)
+    -   [Does the <text\> component support multiple lines?](#section205741157418)
+    -   [Why is a component not displayed?](#section1345810151025)
+    -   [How do I implement scrolling on a page?](#section1724052813218)
+    -   [Why do not the left and top attributes take effect?](#section34659571520)
+    -   [Why does not dynamic binding take effect?](#section1758881511313)
+    -   [How do I implement relative and absolute positioning?](#section1378730235)
+    -   [How do I display or hide a component?](#section1243424718312)
+    -   [What are the precautions for using the margin attribute?](#section7923357414)
+    -   [What are the precautions for event subscription?](#section91641925548)
+    -   [What are the precautions for using dynamic binding?](#section1292412431744)
+    -   [How does the loop attribute take effect for <swiper\>?](#section1136434952)
+    -   [What are the precautions for using an array?](#section1979819133510)
+
+
+## Visual Application FAQs<a name="section147421736145813"></a>
+
+### Is there a global variable that can be accessed by all pages?<a name="section294382614018"></a>
+
+There is no such a global variable.
+
+### How do I obtain DOM elements?<a name="section1423713435019"></a>
+
+You can obtain DOM elements via the  **ref**  attribute. You can use methods of the obtained elements but cannot change their attributes. The sample code is as follows:
+
+```
+<!--index.hml-->
+<div class="container">
+   <!-- Set the ref attribute of the component to animator -->.
+   <image-animator class="image-player" ref="animator" images="{{images}}" duration="1s" onclick="handleClick"></image-animator>
+</div>
+
+/* index.js */
+export default {
+    data: {
+        images:[
+            {src:"common/frame1.png"},
+            {src:"common/frame2.png"},
+            {src:"common/frame3.png"}
+        ]
+    },
+    handleClick(){
+        // Obtain the component through the $refs attribute. (The ref attribute of the component has been set to animator in the HML file.)
+        const animator = this.$refs.animator;
+        const state = animator.getState();
+        if(state == "paused"){
+            animator.resume();
+        }else if(state == "stopped"){
+            animator.start();
+        }else{
+            animator.pause();
         }
     }
-    ```
+}
+```
 
-3.  How do I pass values between pages?
+### How do I pass values between pages?<a name="section119822143117"></a>
 
-    You can pass values through  **params**  of the  **router.replace**  method. The sample code is as follows:
+You can pass values through  **params**  of the  **router.replace**  method. The sample code is as follows:
 
-    Set  **params**  to the values to be passed on a page.
+Set  **params**  to the values to be passed on a page.
 
-    ```
-    router.replace({
-         uri:'pages/detail/detail',  // URI of the page to switch to.
-        params:{transferData:this.data} // Data to be transferred. You need to define the data amount and name.
-    });
-    ```
+```
+router.replace({
+     uri:'pages/detail/detail',  // URI of the page to switch to.
+    params:{transferData:this.data} // Data to be transferred. You need to define the data amount and name.
+});
+```
 
-    Receive the passed values on another page.
+Receive the passed values on another page.
 
-    ```
-    onInit(){
-        const data = this.transferData; // Receive the transferred data by the onInit function.
-    }  
-    ```
+```
+onInit(){
+    const data = this.transferData; // Receive the transferred data by the onInit function.
+}  
+```
 
-4.  How do I scroll a list to an item?
+### How do I scroll a list to an item?<a name="section188663819111"></a>
 
-    Call the  **scrollTo**  method of the list. The input parameter of this method is the index of the target item. You can specify an item index, or obtain the index through the  **scrollend**  event.
+Call the  **scrollTo**  method of the list. The input parameter of this method is the index of the target item. You can specify an item index, or obtain the index through the  **scrollend**  event.
 
-5.  Does the  **<text\>**  component support multiple lines?
+### Does the  **<text\>**  component support multiple lines?<a name="section205741157418"></a>
 
-    Yes. You can use the Enter key to start a new line. Alternatively, the component automatically starts a new line based on the content, without the need to set the height attribute of the text.
+Yes. You can use the Enter key to start a new line. Alternatively, the component automatically starts a new line based on the content, without the need to set the height attribute of the text.
 
-6.  Why is a component not displayed?
+### Why is a component not displayed?<a name="section1345810151025"></a>
 
-    **Description**
+**Description**
 
-    The component added to the  **.hml**  file cannot be displayed.
+The component added to the  **.hml**  file cannot be displayed.
 
-    **Possible Causes**
+**Possible Causes**
 
-    -   The width and height of the component may not be set.
-    -   The style setting may be incorrect.
+-   The width and height of the component may not be set.
+-   The style setting may be incorrect.
 
-    **Solution**
+**Solution**
 
-    \(1\) Check whether the width and height values are set explicitly.
+\(1\) Check whether the width and height values are set explicitly.
 
-    \(2\) Check whether the style of the component is set correctly.
+\(2\) Check whether the style of the component is set correctly.
 
-7.  How do I implement scrolling on a page?
+### How do I implement scrolling on a page?<a name="section1724052813218"></a>
 
-    There are three ways to implement page scrolling:  **scroll**,  **<list\>**, or  **<swiper\>**. For a root component with  **scroll**  set, the scrolling effect is automatically implemented when the component size exceeds the screen size. For details, see the development specifications.
+There are three ways to implement page scrolling:  **scroll**,  **<list\>**, or  **<swiper\>**. For a root component with  **scroll**  set, the scrolling effect is automatically implemented when the component size exceeds the screen size. For details, see the development specifications.
 
-8.  Why do not the  **left**  and  **top**  attributes take effect?
+### Why do not the  **left**  and  **top**  attributes take effect?<a name="section34659571520"></a>
 
-    **left**  and  **top**  attributes must work with the  **<stack\>**  component in addition to the root component.
+**left**  and  **top**  attributes must work with the  **<stack\>**  component in addition to the root component.
 
-9.  Why does not dynamic binding take effect?
+### Why does not dynamic binding take effect?<a name="section1758881511313"></a>
 
-    The object or its attributes are not defined before dynamic binding.
+The object or its attributes are not defined before dynamic binding.
 
-10. How do I implement relative and absolute positioning?
+### How do I implement relative and absolute positioning?<a name="section1378730235"></a>
 
-    You can use the  **<div\>**  and  **<stack\>**  \(with  **top**  and  **left**  attributes\) components.
+You can use the  **<div\>**  and  **<stack\>**  \(with  **top**  and  **left**  attributes\) components.
 
-11. How do I display or hide a component?
+### How do I display or hide a component?<a name="section1243424718312"></a>
 
-    You can use  **display**,  **show**, or  **if**. When an  **if**  clause evaluates to  **false**, the corresponding component will be removed from the VDOM. When  **show**  is set to  **false**, the component will be invisible during rendering, but will not be removed from the VDOM.
+You can use  **display**,  **show**, or  **if**. When an  **if**  clause evaluates to  **false**, the corresponding component will be removed from the VDOM. When  **show**  is set to  **false**, the component will be invisible during rendering, but will not be removed from the VDOM.
 
-12. What are the precautions for using the  **margin**  attribute?
+### What are the precautions for using the  **margin**  attribute?<a name="section7923357414"></a>
 
-    The  **margin**  attribute cannot be set for child components of the  **<stack\>**  component.
+The  **margin**  attribute cannot be set for child components of the  **<stack\>**  component.
 
-13. What are the precautions for event subscription?
+### What are the precautions for event subscription?<a name="section91641925548"></a>
 
-    Only one page exists when the application is running. Therefore, the  **router.replace**  function destroys the previous page and then creates a new one. For event subscription pages, the event should be subscribed every time a page is created, and unsubscribed before page switching.
+Only one page exists when the application is running. Therefore, the  **router.replace**  function destroys the previous page and then creates a new one. For pages involving event subscription, an event should be subscribed every time a page is created, and unsubscribed before page switching.
 
-14. What are the precautions for using dynamic binding?
+### What are the precautions for using dynamic binding?<a name="section1292412431744"></a>
 
-    Do not use too many dynamic bindings because they consume too much memory.
+Do not use too many dynamic bindings because they consume too much memory.
 
-15. How does the  **loop**  attribute take effect for  **<swiper\>**?
+### How does the  **loop**  attribute take effect for  **<swiper\>**?<a name="section1136434952"></a>
 
-    If the total length of the child components, except for the first and last ones, is greater than the length of  **<swiper\>**, the  **loop**  attribute takes effect.
+If the total length of the child components, except for the first and last ones, is greater than the length of  **<swiper\>**, the  **loop**  attribute takes effect.
 
-16. What are the precautions for using an array?
-
-    Do not include too many elements in an array. Avoid frequent operations on a large array.
+### What are the precautions for using an array?<a name="section1979819133510"></a>
 
+Do not include too many elements in an array. Avoid frequent operations on a large array.
 

en/device-dev/guide/device-camera-visual-firstpage.md

@@ -2,7 +2,7 @@
 
 The application home page displays air quality information of different cities. The home page provides two screens \(for two information bars\), which can be added as required. Each screen displays the air quality information of one city, including the Air Quality Index \(AQI\), city name, pollution level, update time, and data source.
 
-The home page of AirQuality consists of three parts:
+The home page of  [AirQuality](device-camera-visual-overview.md)  consists of three parts:
 
 -   Title bar: displays the page title and provides an exit button. The title bar is fixed at the top of the page.
 -   Information bar: displays air quality information. Multiple information bars can be added based on user requirements and support looping scroll.
@@ -83,7 +83,7 @@ The following steps describe how to build the home page with a flexible layout t
     After the code is compiled, run the project on the simulator. The following figure shows the display effect.
 
     **Figure  1**  Title bar<a name="fig14273162465317"></a>  
-    ![](figure/title-bar.png "title-bar")
+    ![](figures/title-bar.png "title-bar")
 
 3.  The  **<swiper\>**  component is required to implement the switching between screens.
 
@@ -175,7 +175,7 @@ The following steps describe how to build the home page with a flexible layout t
     After the code is compiled, the display effect on the simulator is as follows.
 
     **Figure  2**  Title bar and information bar<a name="fig177003454238"></a>  
-    ![](figure/title-bar-and-information-bar.png "title-bar-and-information-bar")
+    ![](figures/title-bar-and-information-bar.png "title-bar-and-information-bar")
 
 5.  Add the indicator bar. Currently, the  **<swiper\>**  component does not support indicator settings. You need to implement a dots indicator by adding  **<div\>**  components and setting the style. Add a  **<div\>**  as a child component to the root node and set the style. Add two  **<div\>**  to the parent  **<div\>**, set  **border-radius**  for the two child  **<div\>**, and dynamically change the background colors of the  **<div\>**  components in the swiping event.
 
@@ -187,7 +187,7 @@ The following steps describe how to build the home page with a flexible layout t
     ```
 
     **Figure  3**  Indicator bar<a name="fig767374119496"></a>  
-    ![](figure/indicator-bar.png "indicator-bar")
+    ![](figures/indicator-bar.png "indicator-bar")
 
 6.  Set the style, animation effect, and dynamic data binding for all components. The complete sample code is as follows:
 

en/device-dev/guide/device-camera-visual-overview.md

@@ -8,8 +8,6 @@ This document describes how to quickly set up an application development environ
 
 AirQuality displays information about the urban air quality on two pages, the home page and details page. The following GIF shows AirQuality on the DevEco Studio simulator.
 
-**Figure  1**  Display effects of the AirQuality<a name="fig18250512195914"></a>  
-
-
-![](figure/video_2020-07-25_173141.gif)
+**Figure  1**  Display effect of the AirQuality application<a name="fig1760214255613"></a>  
+![](figures/display-effect-of-the-airquality-application.gif "display-effect-of-the-airquality-application")
 

en/device-dev/guide/device-camera-visual-prepare.md

@@ -15,13 +15,13 @@ Download and install DevEco Studio. For details, see the  [HUAWEI DevEco Studio
 
 2.  Choose the  **Smart Vision**  for  **Device**  and  **Empty Feature Ability**  for  **Template**.
 
-    ![](figure/en-us_image_0000001082434703.png)
+    ![](figures/empty-feature-ability.png)
 
 3.  Click  **Next**  and configure the project.
     -   **Project Name**: project name.
     -   **Package Name**: software package name. By default, this name will also be used as your application ID. Your application must have a unique ID to be released.
     -   **Save Location**: path for storing project files. The path cannot contain Chinese characters or spaces.
-    -   **Compatible API Version**: compatible API version.
+    -   **Compatible API Version**: compatible API version of the SDK.
 
 4.  Click  **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
 

en/device-dev/guide/device-camera-visual-run.md

 # Running on the Device<a name="EN-US_TOPIC_0000001054809161"></a>
 
-Before you install the application and run it on the development board, install the DevEco Device Tool by following operations provided in  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905). Burn OpenHarmony into the development board, and run it on the board. For details about how to compile, burn, and run an image, see the  [Hi3516 Development Board](../quick-start/quickstart-lite-introduction-hi3516.md#section26131214194212). After the image is running normally and the system is started properly, perform the following steps to install or uninstall the application:
+Before you install the application and run it on the development board, install the DevEco Device Tool by following operations provided in  [HUAWEI DevEco Device Tool User Guide](https://device.harmonyos.com/en/docs/ide/user-guides/service_introduction-0000001050166905). Burn OpenHarmony into the development board, and run it on the board. For details about how to compile, burn, and run an image, see the  [Hi3516 Development Board](../quick-start/oem_minitinier_des_3516.md#section26131214194212). After the image is running normally and the system is started properly, perform the following steps to install or uninstall the application:
 
 1.  Store the compiled unsigned application installation package and installation tool in an SD card and insert the SD card into the development board slot. The installation tool is in  **dev\_tools**  of the directory where the image file is generated.
 2.  Run the following command to disable signature verification, which is enabled by default for application installation:
@@ -20,7 +20,7 @@ Before you install the application and run it on the development board, install
 4.  After the application is installed, touch the application icon on the home screen to enter the application.
 
     **Figure  1**  Home screen<a name="fig146361926155516"></a>  
-    ![](figure/home-screen.png "home-screen")
+    ![](figures/home-screen.png "home-screen")
 
 5.  \(Optional\) Uninstall the application.
 

en/device-dev/guide/device-clock-guide.md

@@ -19,11 +19,11 @@ The clock app displays the current time, as shown in the following figure.
 **Figure  1**  Clock display effect<a name="fig7763172132019"></a>  
 
 
-![](figure/clock.png)
+![](figures/clock.png)
 
 ## Preparations<a name="section6592121861218"></a>
 
-Download and install DevEco Studio. For details, see the  [HUAWEI DevEco Studio User Guide](../../application-dev/quick-start/deveco-studio-(openharmony)-user-guide.md). 
+Download and install DevEco Studio. For details, see the  [HUAWEI DevEco Studio User Guide](../../application-dev/quick-start/deveco-studio-user-guide-for-openharmony.md). 
 
 ## How to Develop<a name="section19901741111312"></a>
 
@@ -257,7 +257,7 @@ To build such an app, we can create a page that has a flexible layout with two r
 
 ## Signing and Packaging<a name="section10601181101516"></a>
 
-After finishing writing the app code, you need to sign and package the app before running it on a real device. For details, see  [Configuring the OpenHarmony App Signature](../../application-dev/quick-start/configuring-the-openharmony-app-signature.md).
+After finishing writing the app code, you need to sign and package the app before running it on a real device. For details, see  [Signing and Packaging Guide](../../application-dev/quick-start/configuring-openharmony-app-signature.md).
 
 ## Running on the Real Device<a name="section092721731511"></a>
 

en/device-dev/guide/device-driver-demo.md

@@ -19,18 +19,10 @@ This document uses the I2C driver as an example to describe how to develop platf
 
 The HDF provides a standard driver framework for common peripherals. To use the APIs provided by the HDF to perform operations on peripherals, you only need to adapt the specific driver to the HDF.
 
-In this example, an I2C driver is used.  [Figure 1](#fig148041484161)  shows the sequence diagram of the I2C driver.
+In this example, an I2C driver is used.  [Figure 1](#fig9596628607)  shows the sequence diagram of the I2C driver.
 
-**Figure  1**  I2C driver sequence diagram<a name="fig148041484161"></a>  
-
-
-![](figure/en-us_image_0000001169991055.png)
-
--   User Business: business-triggered driver
--   i2cManagerEntry: entry to the I2C manager, which is used to register the I2C manager with the HDF
--   I2cManager: I2C manager, which manages the I2C controller
--   I2cCntlr: I2C controller
--   i2cDriverEntry: entry to the I2C controller, which is used to register the I2C controller with the HDF
+**Figure  1**  I2C driver sequence diagram<a name="fig9596628607"></a>  
+![](figures/i2c-driver-sequence-diagram.png "i2c-driver-sequence-diagram")
 
 ## Preparations<a name="section6926133918422"></a>
 

en/device-dev/guide/device-iotcamera-control-demo-photodevguide.md

@@ -363,7 +363,7 @@ None
     camKit->CreateCamera(camId, CamStateMng, eventHdlr);
     ```
 
-6.  In the main process, synchronize configurations set by callback functions implemented in  [step 1](#en-us_topic_0000001052170554_li378084192111),  [step 2](#en-us_topic_0000001052170554_li8716104682913), and  [step 3](#en-us_topic_0000001052170554_li6671035102514).
+6.  Based on the callback design in  [1](#en-us_topic_0000001052170554_li378084192111),  [2](#en-us_topic_0000001052170554_li8716104682913), and  [3](#en-us_topic_0000001052170554_li6671035102514), perform related operations until the  **OnCreated**  callback obtains  **cam\_**.
 
     ```
     void OnCreated(Camera &c) override

en/device-dev/guide/device-iotcamera-control-example.md

 # Use Case<a name="EN-US_TOPIC_0000001055686082"></a>
 
--   For details about the development board, compilation, burning, and image running, see  [Hi3518 Development Board](../quick-start/quickstart-lite-introduction-hi3518.md#section14815247616). A compilation result file of sample code is stored in  **out/ipcamera\_hi3518ev300/dev\_tools/bin/camera\_sample**. You can copy the file to a TF card, or modify the compilation script of  **camera\_sample**  to copy the result to  **rootfs.img**.
+-   For details about the development board, compilation, burning, and image running, see  [Hi3518 Development Board](../quick-start/oem_minitinier_des_3518.md#section14815247616). A compilation result file of sample code is stored in  **out/ipcamera\_hi3518ev300/dev\_tools/bin/camera\_sample**. You can copy the file to a TF card, or modify the compilation script of  **camera\_sample**  to copy the result to  **rootfs.img**.
 
     Modify  **output\_dir**  in  **applications/sample/camera/media/BUILD.gn**.
 
@@ -18,28 +18,28 @@
 1.  Run the  **cd**  command to go to the end path of the executable program and start  **camera\_sample**  by running the command in the following figure.
 
     **Figure  1**  Starting camera\_sample<a name="en-us_topic_0000001055301733_fig380985885020"></a>  
-    ![](figure/starting-camera_sample.png "starting-camera_sample")
+    ![](figures/starting-camera_sample.png "starting-camera_sample")
 
     The control commands are displayed as shown in the preceding figure. Press  **S**  to stop the current operation \(including video recording and preview\), and press  **Q**  to exit the program.
 
 2.  Press  **1**  to take a photo in JPG format. The photo is saved in the  **/sdcard**  directory and named  **Capture\***.
 
     **Figure  2**  Serial port logs displayed after the photographing command is executed<a name="en-us_topic_0000001055301733_fig17819185018384"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-photographing-command-is-executed.png "serial-port-logs-displayed-after-the-photographing-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-photographing-command-is-executed.png "serial-port-logs-displayed-after-the-photographing-command-is-executed")
 
     To view the saved file, exit the program and enter the file system. To start the program again, return to the previous step.
 
     **Figure  3**  Saved files<a name="en-us_topic_0000001055301733_fig166391743154619"></a>  
-    ![](figure/saved-files.png "saved-files")
+    ![](figures/saved-files.png "saved-files")
 
 3.  Press  **2**  to start recording. The video file is in MP4 format and saved in the  **/sdcard**  directory with the name  **Record\***. Press  **S**  to stop recording.
 
     **Figure  4**  Serial port logs displayed after the recording command is executed<a name="en-us_topic_0000001055301733_fig6340814174317"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-recording-command-is-executed.png "serial-port-logs-displayed-after-the-recording-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-recording-command-is-executed.png "serial-port-logs-displayed-after-the-recording-command-is-executed")
 
 4.  Press  **Q**  to exit.
 
     **Figure  5**  Serial port logs displayed after the exit command is executed<a name="en-us_topic_0000001055301733_fig1755682174514"></a>  
-    ![](figure/serial-port-logs-displayed-after-the-exit-command-is-executed.png "serial-port-logs-displayed-after-the-exit-command-is-executed")
+    ![](figures/serial-port-logs-displayed-after-the-exit-command-is-executed.png "serial-port-logs-displayed-after-the-exit-command-is-executed")
 
 

en/device-dev/guide/device-lite.md

+# Mini- and Small-System Devices<a name="EN-US_TOPIC_0000001135844126"></a>
+
+-   **[WLAN-connected Products](device-wlan.md)**  
+
+-   **[Cameras Without a Screen](device-iotcamera.md)**  
+
+-   **[Cameras with a Screen](device-camera.md)**  
+
+

en/device-dev/guide/device-outerdriver-demo.md

@@ -28,7 +28,7 @@ This document describes how to develop a touchscreen driver on the Hi3516D V300
 
 The touchscreen integrated circuit \(IC\) provided by the Hi3516D V300 development board is GT911, which uses the standard inter-integrated circuit \(I2C\) to communicate with the development board and connects to the main board through the 6-pin flexible flat cable. The following figure shows the distribution of the 6 pins and their connection.
 
-![](figure/绘图1.png)
+![](figures/6-pin-distribution-and-physical-connection.png)
 
 ### Input Driver Model<a name="section53684425430"></a>
 
@@ -44,7 +44,7 @@ For details about the input driver model, see  [Touchscreen Overview](../driver/
 
 ## Setting Up the Environment<a name="section661075474418"></a>
 
-Follow the instructions in  [Environment Setup for Standard System](../quick-start/quickstart-standard.md).
+Follow the instructions in  [Environment Setup for Standard System](../quick-start/quickstart-standard-overview.md).
 
 >![](../public_sys-resources/icon-notice.gif) **NOTICE:** 
 >This development example applies to standard, small, and mini OpenHarmony systems. The following sections use the standard system as an example. You can refer to the specific guide for your system to set up the environment.
@@ -335,7 +335,7 @@ The input driver model consists of three parts of drivers. To develop a brand-ne
 
     **touch\_gt911.o**  is the content added in this example.
 
-2.  Build source code and burn images. For details, see the related sections in  [Getting Started for Standard System](../nottoctopics/en-us_topic_0000001135402541.md#section375234715135).
+2.  Build source code and burn images. For details, see the related sections in  [Getting Started for Standard System](../quick-start/quickstart-standard.md).
 
 ## Debugging and Verification<a name="section62577313482"></a>
 

en/device-dev/guide/device-standard.md

+# Standard-System Devices<a name="EN-US_TOPIC_0000001135684346"></a>
+
+-   **[Development Guidelines on Clock Apps](device-clock-guide.md)**  
+
+-   **[Development Example for Platform Drivers](device-driver-demo.md)**  
+
+-   **[Development Example for Peripheral Drivers](device-outerdriver-demo.md)**  
+
+

en/device-dev/guide/device-wlan-led-outcontrol.md

@@ -10,7 +10,7 @@ Based on the Hi3861 platform, the OpenHarmony WLAN module provides abundant peri
 
 ## Development<a name="section13857170163412"></a>
 
-1.  Complete the operations described in  [Getting Started with Hi3861](../quick-start/quickstart-lite-introduction-hi3861.md#section19352114194115).
+1.  Complete the operations described in  [Getting Started with Hi3861](../quick-start/oem_minitinier_des_3861.md#section19352114194115).
 
     LED control examples are stored in the file  **applications/sample/wifi-iot/app/iothardware/led\_example.c**.
 
@@ -101,10 +101,10 @@ Based on the Hi3861 platform, the OpenHarmony WLAN module provides abundant peri
 
 ## Verification<a name="section1949121910344"></a>
 
-For details about the compilation and burning processes, see  [Building Source Code](../quick-start/quickstart-lite-steps-board3861-connection.md#section191121332125319)  and  [Burning Images](../quick-start/quickstart-lite-steps-board3861-connection.md#section19458165166)  in the  _Getting Started with Hi3861_.
+For details about the compilation and burning processes, see  [Building Source Code](../quick-start/quickstart-lite-steps-hi3861-connection.md#section191121332125319)  and  [Burning Images](../quick-start/quickstart-lite-steps-hi3861-connection.md#section3288165814218)  in the  _Getting Started with Hi3861_.
 
 After the preceding two steps are complete, press the  **RST**  button to reset the module. If the LED blinks periodically as expected, the verification is passed.
 
 **Figure  1**  LED blinking<a name="fig20768175218527"></a>  
-![](figure/led-blinking.gif "led-blinking")
+![](figures/led-blinking.gif "led-blinking")
 

en/device-dev/guide/device-wlan-led.md

+# LED Peripheral Control<a name="EN-US_TOPIC_0000001157319393"></a>
+
+-   **[LED Peripheral Control](device-wlan-led-outcontrol.md)**  
+
+

en/device-dev/guide/device-wlan-sdk.md

@@ -121,7 +121,7 @@ Before building  **libs**, you must perform the following steps:
 
 After the preceding operations are complete, run the  **hb build -T //domains/iot/link:iot**  command in the root directory of the code and then check whether the target library file is generated in the  **out/hispark\_pegasus/wifiiot\_hispark\_pegasus/libs/**  directory.
 
-![](figure/en-us_image_0000001078563230.png)
+![](figures/device-wlan-sdk-files.png)
 
 Copy the library file to the  **device/hisilicon/hispark\_pegasus/sdk\_liteos/3rd\_sdk/demolink/libs/**  directory and delete the  **.c**  and  **.h**  files from the  **domains/iot/link/libbuild/**  directory.
 

en/device-dev/guide/device-wlan-touch.md

+# OneHop<a name="EN-US_TOPIC_0000001111039538"></a>
+
+-   **[Overview](onehop-overview.md)**  
+
+-   **[Preparations](onehop-dev-prerequisites.md)**  
+
+-   **[Developing the Hi3861 Development Board](onehop-dev-hi3861.md)**  
+
+-   **[Developing Atomic Services](onehop-dev-atomic-service.md)**  
+
+-   **[Writing an NFC Tag](onehop-write-nfc-info.md)**  
+
+-   **[Configuring a Service Association Intent](onehop-configuration-device-tag.md)**  
+
+-   **[Tapping to Launch an Atomic Service](onehop-open-atomic-service.md)**  
+
+-   **[References](onehop-reference-info.md)**  
+
+

en/device-dev/guide/device-wifi.md → en/device-dev/guide/device-wlan.md

 # WLAN-connected Products<a name="EN-US_TOPIC_0000001157479363"></a>
 
--   **[LED Peripheral Control](device-wlan-led-outcontrol.md)**  
+-   **[OneHop](device-wlan-touch.md)**  
+
+-   **[LED Peripheral Control](device-wlan-led.md)**  
 
 -   **[Third-Party SDK Integration](device-wlan-sdk.md)**  
 

en/device-dev/guide/device.md

-# Device Development Guidelines<a name="EN-US_TOPIC_0000001111039536"></a>
+# Devices<a name="EN-US_TOPIC_0000001182003649"></a>
 
--   **[WLAN-connected Products](device-wifi.md)**  
+-   **[Mini- and Small-System Devices](device-lite.md)**  
 
--   **[Cameras Without a Screen](device-iotcamera.md)**  
-
--   **[Cameras with a Screen](device-camera.md)**  
-
--   **[Development Guidelines on Clock Apps](device-clock-guide.md)**  
-
--   **[Development Example for Platform Drivers](device-driver-demo.md)**  
-
--   **[Development Example for Peripheral Drivers](device-outerdriver-demo.md)**  
+-   **[Standard-System Devices](device-standard.md)**