diff --git a/en/device-dev/driver/Readme-EN.md b/en/device-dev/driver/Readme-EN.md index 310db48cfb1623552eb51cd2c5b7211dbb528808..47851b4dbf94f87febcbc7364d29df31d2c283b8 100644 --- a/en/device-dev/driver/Readme-EN.md +++ b/en/device-dev/driver/Readme-EN.md @@ -19,18 +19,16 @@ - [SPI](driver-platform-spi-develop.md) - [UART](driver-platform-uart-develop.md) - [Watchdog](driver-platform-watchdog-develop.md) - - [MIPI CSI](driver-platform-mipicsi-develop.md) - [Platform Driver Usage](driver-platform.md) - [GPIO](driver-platform-gpio-des.md) - [I2C](driver-platform-i2c-des.md) + - [MIPI DSI](driver-platform-mipidsi-develop.md) + - [PWM](driver-platform-pwm-des.md) - [RTC](driver-platform-rtc-des.md) - [SDIO](driver-platform-sdio-des.md) - [SPI](driver-platform-spi-des.md) - [UART](driver-platform-uart-des.md) - [Watchdog](driver-platform-watchdog-des.md) - - [MIPI DSI](driver-platform-mipidsi-des.md) - - [PWM](driver-platform-pwm-des.md) - - [MIPI CSI](driver-platform-mipicsi-des.md) - [Peripheral Driver Usage](driver-peripherals.md) - [LCD](driver-peripherals-lcd-des.md) - [Touchscreen](driver-peripherals-touch-des.md) @@ -38,4 +36,4 @@ - [WLAN](driver-peripherals-external-des.md) - [Audio](driver-peripherals-audio-des.md) - [USB](driver-peripherals-usb-des.md) - - [CAMERA](driver-peripherals-camera-des.md) \ No newline at end of file + - [Camera](driver-peripherals-camera-des.md) \ No newline at end of file diff --git a/en/device-dev/driver/driver-hdf-development.md b/en/device-dev/driver/driver-hdf-development.md index e621198cf80240a8009212b3be53592fc2a9d179..2aa9fbb83ce3063b89642de8babf4f046c7a1a28 100644 --- a/en/device-dev/driver/driver-hdf-development.md +++ b/en/device-dev/driver/driver-hdf-development.md @@ -222,6 +222,6 @@ Driver development based on the HDF involves driver implementation and driver co > DEVICE_PRELOAD_INVALID > } DevicePreload; > ``` -> If the **preload** field in the configuration file is set to **0** (DEVICE\_PRELOAD\_ENABLE), the driver is loaded by default during the system boot process. If **preload** is set to **1** (DEVICE\_PRELOAD\_ENABLE\_STEP2), the driver is loaded after a quick start is complete if the system supports quick start. If the system does not support quick start, the value **1** has the same meaning as DEVICE\_PRELOAD\_ENABLE. If **preload** is set to **2** (DEVICE\_PRELOAD\_DISABLE), the driver is dynamically loaded instead of being loaded during the system boot process. When a user-mode process requests the driver service (for details, see [Driver Message Mechanism Management](driver-hdf-news.md)), the HDF attempts to dynamically load the driver if the driver service does not exist. +> If the **preload** field in the configuration file is set to **0** (DEVICE\_PRELOAD\_ENABLE), the driver is loaded by default during the system boot process. If **preload** is set to **1** (DEVICE\_PRELOAD\_ENABLE\_STEP2), the driver is loaded after a quick start is complete if the system supports quick start. If the system does not support quick start, the value **1** has the same meaning as DEVICE\_PRELOAD\_ENABLE. If **preload** is set to **2** (DEVICE\_PRELOAD\_DISABLE), the driver is dynamically loaded instead of being loaded during the system boot process. When a user-mode process requests the driver service (for details, see [Driver Message Mechanism Management](driver-hdf-message-managements.md)), the HDF attempts to dynamically load the driver if the driver service does not exist. >- Sequential loading \(drivers must be loaded by default\) > In the configuration file, the **priority** field \(the value is an integer ranging from 0 to 200\) indicates the priority of the host and driver. For drivers in different hosts, a smaller host priority value indicates a higher driver loading priority; for drivers in the same host, a smaller driver priority value indicates a higher driver loading priority. diff --git a/en/device-dev/faqs/faqs-overview.md b/en/device-dev/faqs/faqs-overview.md index 6d82025232efc2e33f1602c5dd292b3a20f8eec7..b16afa8836a62ed0439522db9ae18bae87165095 100644 --- a/en/device-dev/faqs/faqs-overview.md +++ b/en/device-dev/faqs/faqs-overview.md @@ -6,109 +6,109 @@ FAQs are used to help developers solve problems frequently encountered during de ### Mini and Small Systems -- [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) +- [What should I do if garbled characters and segmentation faults occur during hb installation?](faqs-environment-setup.md#section36351051193919) +- [What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation?](faqs-environment-setup.md#section48221013144011) +- [What should I do if the message "module 'platform' has no attribute 'linux\_distribution'" is displayed during hb installation?](faqs-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?](faqs-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?](faqs-environment-setup.md#section870082884217) +- [What should I do when the message -bash: make: command not found is displayed during Python 3 installation?](faqs-environment-setup.md#section198707170455) +- [What should I do when the message zlib not available is displayed during Python 3 installation?](faqs-environment-setup.md#section85401445204518) +- [What should I do when the message No module named '\_ctypes' is displayed during Python 3 installation?](faqs-environment-setup.md#section12202694460) +- [What should I do when an error with lsb\_release occurs during kconfiglib installation?](faqs-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?](faqs-environment-setup.md#section510820516515) ## Compilation and Building ### Mini and Small Systems -- [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) +- [Invalid -- w Option](faqs-building.md#section67961431372) +- [Library ncurses Not Found](faqs-building.md#section199631617371) +- [mcopy not Found](faqs-building.md#section937435175) +- [No riscv File or Directory](faqs-building.md#section1115535018713) +- [No Crypto](faqs-building.md#section17982573813) +- [Unexpected Operator](faqs-building.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?](faqs-building.md#section1917790845) +- [What should I do when the message cannot find -lgcc is displayed during compilation and building?](faqs-building.md#section141771701647) +- [What should I do when the message indicating Python cannot be found is displayed during compilation and building?](faqs-building.md#section51781202415) +- [What should I do when the message indicating Python 3 cannot be found is displayed during compilation and building?](faqs-building.md#section1917950148) ## Burning ### Mini and Small Systems -- ["Error: Opening COMxx: Access denied" Is Displayed After a Serial Port Is Selected for Burning](burning.md#section18988185615914) +- ["Error: Opening COMxx: Access denied" Is Displayed After a Serial Port Is Selected for Burning](faqs-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) +- [What should I do when the image failed to be burnt?](faqs-burning.md#section1370982513317) +- [What should I do when no command output is displayed?](faqs-burning.md#section183421944953) +- [What should I do when Windows-based PC failed to be connected to the board?](faqs-burning.md#section1215410450215) ## Kernel ### Basic Kernel -- [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) +- [What are the differences between APIs provided by LiteOS-A and LiteOS-M?](faqs-kernel.md#section447571122918) +- [How do I analyze thread stack overflow?](faqs-kernel.md#section8623141711293) ### File System -- [What should I do when the Hi3516 board fails to open the same file in write mode \(LiteOS-A\)?](kernel.md#section517972255311) +- [What should I do when the Hi3516 board fails to open the same file in write mode \(LiteOS-A\)?](faqs-kernel.md#section517972255311) ### Chip Adaptation -- [What hardware platforms are supported by the LiteOS kernel?](kernel.md#section868413518533) -- [What chip architectures are supported by the LiteOS kernel?](kernel.md#section1131661465417) +- [What hardware platforms are supported by the LiteOS kernel?](faqs-kernel.md#section868413518533) +- [What chip architectures are supported by the LiteOS kernel?](faqs-kernel.md#section1131661465417) ### Third-party Components -- [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) +- [What third-party components are supported by OpenHarmony?](faqs-kernel.md#section74138185411) +- [What should I do if the key length verification fails when OpenSSL is used on OpenHarmony?](faqs-kernel.md#section10564614135516) +- [Does setsockopt support SO\_RCVBUF and SO\_SNDBUF?](faqs-kernel.md#section2093373215556) ### Compilation and Linking -- [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) +- [How do I run an application developed by ARM Linux on LiteOS-A?](faqs-kernel.md#section1164175713557) +- [What system is used for OpenHarmony compilation? What compiler is used?](faqs-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?](faqs-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?](faqs-kernel.md#section193571012578) +- [What should I do when calling clock\_gettime obtains an incorrect time?](faqs-kernel.md#section8973152015717) ## Porting -- [How Do I Mount the Heap Memory to the Kernel?](porting.md#section21471536184914) +- [How Do I Mount the Heap Memory to the Kernel?](faqs-porting.md#section21471536184914) ## Startup and Recovery -- [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 startup interrupted due to "parse failed!" error](faqs-startup-and-recovery.md#section835662214302) +- [System automatically restarted again and again](faqs-startup-and-recovery.md#section3857921143117) +- [Failed to call the SetParameter or GetParameter API with correct parameter values](faqs-startup-and-recovery.md#section548818116328) ## System Services ### Utils -- [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) +- [1. Failure in running the KV store on the LiteOS-A kernel \(Hi3516 or Hi3518\) due to incorrect path setting for the KV store](faqs-system-applications.md#section16520347131511) ### Visual Applications -- [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 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 ?](system-applications.md#section690166112414) -- [What are the precautions for using an array?](system-applications.md#section1554552822414) +- [Is there a global variable that can be accessed by all pages?](faqs-system-applications.md#section187297991718) +- [How do I obtain DOM elements?](faqs-system-applications.md#section1833493719175) +- [How do I pass values between pages?](faqs-system-applications.md#section184283812183) +- [How do I scroll a list to an item?](faqs-system-applications.md#section11897734131811) +- [Does the component support multiple lines?](faqs-system-applications.md#section5872656121814) +- [Why is a component not displayed?](faqs-system-applications.md#section7397125317107) +- [How do I implement scrolling on a page?](faqs-system-applications.md#section338794422010) +- [Why do not the left and top attributes take effect?](faqs-system-applications.md#section2597193611217) +- [Why does not dynamic binding take effect?](faqs-system-applications.md#section6939050172115) +- [How do I implement relative and absolute positioning?](faqs-system-applications.md#section5547311192215) +- [How do I display or hide a component?](faqs-system-applications.md#section16107113352213) +- [What are the precautions for using the margin attribute?](faqs-system-applications.md#section1524910142314) +- [What are the precautions for event subscription?](faqs-system-applications.md#section1537132012231) +- [What are the precautions for using dynamic binding?](faqs-system-applications.md#section96561452236) +- [How does the loop attribute take effect for ?](faqs-system-applications.md#section690166112414) +- [What are the precautions for using an array?](faqs-system-applications.md#section1554552822414) ### HDC -- [hdc\_std Fails to Connect to a Device](system-applications.md#section1965012223257) -- [hdc\_std Fails to Run](system-applications.md#section1157575212515) +- [hdc\_std Fails to Connect to a Device](faqs-system-applications.md#section1965012223257) +- [hdc\_std Fails to Run](faqs-system-applications.md#section1157575212515) diff --git a/en/device-dev/guide/device-camera-control-example.md b/en/device-dev/guide/device-camera-control-example.md index 2d599c0ef0ddc2e7bf69630bf5832cb6ad8229ed..c9920f4b3bfa6aa40c3f315c86410cb56bc5cf84 100644 --- a/en/device-dev/guide/device-camera-control-example.md +++ b/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/oem_minitinier_des_3516.md#section26131214194212). +- 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#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. diff --git a/en/device-dev/guide/device-camera-visual-run.md b/en/device-dev/guide/device-camera-visual-run.md index 72814c352e68d8565f6c1b3e8570d643655cca91..d48ed33058c15611ecfc6d9fe0b10da038f2107f 100644 --- a/en/device-dev/guide/device-camera-visual-run.md +++ b/en/device-dev/guide/device-camera-visual-run.md @@ -1,6 +1,6 @@ # Running on the Device -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: +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: 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: diff --git a/en/device-dev/guide/device-iotcamera-control-example.md b/en/device-dev/guide/device-iotcamera-control-example.md index d2ab0fd2dbc859bd0f7e56ff1b3793896d409025..0d2fbf23bf92862441b826088fbc42b55ba3beea 100644 --- a/en/device-dev/guide/device-iotcamera-control-example.md +++ b/en/device-dev/guide/device-iotcamera-control-example.md @@ -1,6 +1,6 @@ # Use Case -- 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**. +- 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**. Modify **output\_dir** in **applications/sample/camera/media/BUILD.gn**. diff --git a/en/device-dev/guide/device-wlan-led-control.md b/en/device-dev/guide/device-wlan-led-control.md index 597b58c83925d78eabd602454f6509d0f221f2f9..08fa2a01992eb40a3cc7927a3ec50510f48dbdae 100644 --- a/en/device-dev/guide/device-wlan-led-control.md +++ b/en/device-dev/guide/device-wlan-led-control.md @@ -6,7 +6,7 @@ Based on the Hi3861 platform, the OpenHarmony WLAN module provides abundant peri ## Development -1. Complete the operations described in [Getting Started with Hi3861](../quick-start/oem_minitinier_des_3861.md#section19352114194115). +1. Complete the operations described in [Getting Started with Hi3861](../quick-start/quickstart-lite-introduction-hi3861.md#section19352114194115). LED control examples are stored in the file **applications/sample/wifi-iot/app/iothardware/led\_example.c**. diff --git a/en/device-dev/subsystems/Readme-EN.md b/en/device-dev/subsystems/Readme-EN.md index 3a729132c3e7be94fb19318a2e453000f10e2395..f695eec2f4ad88e5261d0e71ea615e6eee6ec11d 100644 --- a/en/device-dev/subsystems/Readme-EN.md +++ b/en/device-dev/subsystems/Readme-EN.md @@ -21,9 +21,9 @@ - [Development Guidelines on Media Playback](subsys-multimedia-video-play-guide.md) - [Development Guidelines on Media Recording](subsys-multimedia-video-record-guide.md) - [Utils](subsys-utils.md) - - [Utils Overview](oem_subsys_utils_des.md) - - [Utils Development Guidelines](oem_subsys_utils_guide.md) - - [Utils FAQ](oem_subsys_utils_faq.md) + - [Utils Overview](subsys_utils_overview.md) + - [Utils Development Guidelines](subsys_utils_guide.md) + - [Utils FAQ](subsys_utils_faqs.md) - [AI Framework](subsys-aiframework.md) - [AI Engine Framework](subsys-aiframework-guide.md) - [Development Environment](subsys-aiframework-envbuild.md) @@ -84,5 +84,5 @@ - [Development Guidelines on HiSysEvent](subsys-dfx-hisysevent.md) - [R&D Tools](subsys-toolchain.md) - [bytrace Usage Guidelines](subsys-toolchain-bytrace-guide.md) - - [hdc\_std Usage Guidelines](oem_subsys_toolchain_hdc_guide.md) + - [hdc\_std Usage Guidelines](subsys-toolchain-hdc-guide.md) - [XTS](subsys-xts-guide.md) \ No newline at end of file diff --git a/en/device-dev/subsystems/development-guidelines.md b/en/device-dev/subsystems/development-guidelines.md index 64a6bede8653025e29dd2331529177307e69ee4d..12a68e42514757dcc387b9ab0345253ed357337d 100644 --- a/en/device-dev/subsystems/development-guidelines.md +++ b/en/device-dev/subsystems/development-guidelines.md @@ -121,7 +121,7 @@ The following table describes the API for initializing a modem vendor library. ### Debugging and Verification -1. Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/oem_subsys_toolchain_hdc_guide.md#preparations) tool to connect to a debugging device. Then, run the following command to send the generated **libril\_vendor.z.so** library file to the **/system/lib/** directory of the device. For details about how to integrate a library file, see [Integrating Modem Vendor Libraries](#section590mcpsimp). +1. Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md#preparations) tool to connect to a debugging device. Then, run the following command to send the generated **libril\_vendor.z.so** library file to the **/system/lib/** directory of the device. For details about how to integrate a library file, see [Integrating Modem Vendor Libraries](#section590mcpsimp). ``` hdc_std file send libril_vendor.z.so /system/lib/ diff --git a/en/device-dev/subsystems/subsys-build-mini-lite.md b/en/device-dev/subsystems/subsys-build-mini-lite.md index 333c08354840b5687ff672968545fb11231af714..ce9e330cd78711067f1d4af027c1f2beab8be6a0 100644 --- a/en/device-dev/subsystems/subsys-build-mini-lite.md +++ b/en/device-dev/subsystems/subsys-build-mini-lite.md @@ -591,7 +591,7 @@ The following uses the RTL8720 development board provided by Realtek as an examp 1. Create a directory for the chipset solution. - To create a directory based on [1-Configuration Rules for Modules, Chipset Solutions, and Product Solutions](#section1625463413327), run the following command in the root code directory: + To create a directory based on [Configuration Rules](#section2345183962710), run the following command in the root code directory: ``` mkdir -p device/realtek/rtl8720 @@ -658,7 +658,7 @@ You can use the Compilation and Building subsystem to customize product solution 1. Create a product directory. - The following uses the Wi-Fi IoT module on the RTL8720 development board as an example. Run the following command in the root code directory to create a product directory based on [1-Configuration Rules for Modules, Chipset Solutions, and Product Solutions](#section1625463413327): + The following uses the Wi-Fi IoT module on the RTL8720 development board as an example. Run the following command in the root code directory to create a product directory based on [Configuration Rules](#section2345183962710): ``` mkdir -p vendor/my_company/wifiiot diff --git a/en/device-dev/subsystems/subsys-dfx-hisysevent-read.md b/en/device-dev/subsystems/subsys-dfx-hisysevent-listening.md similarity index 100% rename from en/device-dev/subsystems/subsys-dfx-hisysevent-read.md rename to en/device-dev/subsystems/subsys-dfx-hisysevent-listening.md diff --git a/en/device-dev/subsystems/subsys-dfx-hisysevent-write.md b/en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md similarity index 100% rename from en/device-dev/subsystems/subsys-dfx-hisysevent-write.md rename to en/device-dev/subsystems/subsys-dfx-hisysevent-logging.md diff --git a/en/device-dev/subsystems/subsys-dfx-hisysevent-select.md b/en/device-dev/subsystems/subsys-dfx-hisysevent-query.md similarity index 100% rename from en/device-dev/subsystems/subsys-dfx-hisysevent-select.md rename to en/device-dev/subsystems/subsys-dfx-hisysevent-query.md diff --git a/en/device-dev/subsystems/subsys-dfx-hisysevent.md b/en/device-dev/subsystems/subsys-dfx-hisysevent.md index 5ee871e36423b51e7bb3f1fd7ac6d8157a0d7ec1..cc5a1e165180ccfa698143e873070840fb3e3f25 100644 --- a/en/device-dev/subsystems/subsys-dfx-hisysevent.md +++ b/en/device-dev/subsystems/subsys-dfx-hisysevent.md @@ -6,6 +6,6 @@ - **[HiSysEvent Query](subsys-dfx-hisysevent-query.md)** -- **[HiSysEvent Tool Usage](subsys-dfx-hisysevent-tool-usage.md)** +- **[HiSysEvent Tool Usage](subsys-dfx-hisysevent-tool.md)** diff --git a/en/device-dev/subsystems/subsys-dfx.md b/en/device-dev/subsystems/subsys-dfx.md index 9d3f15bed025152621e32db997b4a81bb77c4ba8..c07acfa88e77ee52782574b5a239a0ee04454467 100644 --- a/en/device-dev/subsystems/subsys-dfx.md +++ b/en/device-dev/subsystems/subsys-dfx.md @@ -3,8 +3,6 @@ - [DFX Overview](subsys-dfx-overview.md) - [HiLog Development](subsys-dfx-hilog-rich.md) - [HiLog_Lite Development](subsys-dfx-hilog-lite.md) -- [HiTrace Development](subsys-dfx-hitrace-development.md) -- [HiCollie Development](subsys-dfx-hicollie-development.md) - [HiSysEvent Development](subsys-dfx-hisysevent.md) - [HiSysEvent Logging](subsys-dfx-hisysevent-logging.md) - [HiSysEvent Listening](subsys-dfx-hisysevent-listening.md) diff --git a/zh-cn/device-dev/faqs/faqs-overview.md b/zh-cn/device-dev/faqs/faqs-overview.md index e8ed3fc369d6e55bd18ebc1395fa9d941f59bbc4..2e4d56a587ea68cebf75dd0e7244e3f817855bac 100644 --- a/zh-cn/device-dev/faqs/faqs-overview.md +++ b/zh-cn/device-dev/faqs/faqs-overview.md @@ -30,16 +30,16 @@ ### 轻量和小型系统 -- [安装hb过程中出现乱码、段错误](faqs-environment-building.md#section36351051193919) -- [安装hb过程中，提示"cannot import 'sysconfig' from 'distutils'"](faqs-environment-building.md#section48221013144011) -- [安装hb过程中，提示"module 'platform' has no attribute 'linux\_distribution'"](faqs-environment-building.md#section8692735427) -- [安装hb过程中，提示"Could not find a version that satisfies the requirement ohos-build"](faqs-environment-building.md#section8692735427) -- [安装python3过程中，提示“configure: error: no acceptable C compiler found in $PATH”](faqs-environment-building.md#section870082884217) -- [安装python3过程中，提示“-bash: make: command not found”](faqs-environment-building.md#section198707170455) -- [安装python3过程中，提示“zlib not available”](faqs-environment-building.md#section85401445204518) -- [安装python3过程中，提示“No module named '\_ctypes'”](faqs-environment-building.md#section12202694460) -- [安装 kconfiglib时，遇到lsb\_release错误](faqs-environment-building.md#section5803174135115) -- [Linux编译服务器终端输入不识别的命令时提示“ImportError: No module named apt\_pkg”](faqs-environment-building.md#section510820516515) +- [安装hb过程中出现乱码、段错误](faqs-environment-setup.md#section36351051193919) +- [安装hb过程中，提示"cannot import 'sysconfig' from 'distutils'"](faqs-environment-setup.md#section48221013144011) +- [安装hb过程中，提示"module 'platform' has no attribute 'linux\_distribution'"](faqs-environment-setup.md#section8692735427) +- [安装hb过程中，提示"Could not find a version that satisfies the requirement ohos-build"](faqs-environment-setup.md#section8692735427) +- [安装python3过程中，提示“configure: error: no acceptable C compiler found in $PATH”](faqs-environment-setup.md#section870082884217) +- [安装python3过程中，提示“-bash: make: command not found”](faqs-environment-setup.md#section198707170455) +- [安装python3过程中，提示“zlib not available”](faqs-environment-setup.md#section85401445204518) +- [安装python3过程中，提示“No module named '\_ctypes'”](faqs-environment-setup.md#section12202694460) +- [安装 kconfiglib时，遇到lsb\_release错误](faqs-environment-setup.md#section5803174135115) +- [Linux编译服务器终端输入不识别的命令时提示“ImportError: No module named apt\_pkg”](faqs-environment-setup.md#section510820516515) ## 编译构建子系统 @@ -98,41 +98,41 @@ ## 移植 -- [如何将用户的堆内存挂载进内核](faqs-transplant.md#section21471536184914) +- [如何将用户的堆内存挂载进内核](faqs-porting.md#section21471536184914) ## 启动恢复 -- [系统启动过程中打印“parse failed!”错误后停止启动](faqs-init.md#section835662214302) -- [系统启动过程未结束就自动重启，如此反复持续](faqs-init.md#section3857921143117) -- [参数正确的情况下调用SetParameter/GetParameter返回失败](faqs-init.md#section548818116328) +- [系统启动过程中打印“parse failed!”错误后停止启动](faqs-startup-and-recovery.md#section835662214302) +- [系统启动过程未结束就自动重启，如此反复持续](faqs-startup-and-recovery.md#section3857921143117) +- [参数正确的情况下调用SetParameter/GetParameter返回失败](faqs-startup-and-recovery.md#section548818116328) ## 系统服务 ### 公共基础库 -- [LiteOS-A内核\(Hi3516、Hi3518平台\)KV存储路径设置错误，导致KV存储运行失败](faqs-system-using.md#section16520347131511) +- [LiteOS-A内核\(Hi3516、Hi3518平台\)KV存储路径设置错误，导致KV存储运行失败](faqs-system-applications.md#section16520347131511) ### 视觉应用常见问题 -- [是否存在一个全局变量，所有的页面都可以访问？](faqs-system-using.md#section187297991718) -- [如何获取dom中的元素](faqs-system-using.md#section1833493719175) -- [如何在页面间传值？](faqs-system-using.md#section184283812183) -- [list如何滚动到某个item？](faqs-system-using.md#section11897734131811) -- [text支持多行吗？](faqs-system-using.md#section5872656121814) -- [为什么控件不显示？](faqs-system-using.md#section7397125317107) -- [如何实现页面滑动？](faqs-system-using.md#section338794422010) -- [Left、Top为什么不生效？](faqs-system-using.md#section2597193611217) -- [动态绑定为什么不生效？](faqs-system-using.md#section6939050172115) -- [如何实现相对定位和绝对定位？](faqs-system-using.md#section5547311192215) -- [如何控制控件的显示与隐藏？](faqs-system-using.md#section16107113352213) -- [使用Margin时，有什么注意事项？](faqs-system-using.md#section1524910142314) -- [使用事件订阅时，有什么注意事项？](faqs-system-using.md#section1537132012231) -- [使用动态绑定时，有什么注意事项？](faqs-system-using.md#section96561452236) -- [swiper loop属性如何生效？](faqs-system-using.md#section690166112414) -- [使用数组时，有什么注意事项？](faqs-system-using.md#section1554552822414) +- [是否存在一个全局变量，所有的页面都可以访问？](faqs-system-applications.md#section187297991718) +- [如何获取dom中的元素](faqs-system-applications.md#section1833493719175) +- [如何在页面间传值？](faqs-system-applications.md#section184283812183) +- [list如何滚动到某个item？](faqs-system-applications.md#section11897734131811) +- [text支持多行吗？](faqs-system-applications.md#section5872656121814) +- [为什么控件不显示？](faqs-system-applications.md#section7397125317107) +- [如何实现页面滑动？](faqs-system-applications.md#section338794422010) +- [Left、Top为什么不生效？](faqs-system-applications.md#section2597193611217) +- [动态绑定为什么不生效？](faqs-system-applications.md#section6939050172115) +- [如何实现相对定位和绝对定位？](faqs-system-applications.md#section5547311192215) +- [如何控制控件的显示与隐藏？](faqs-system-applications.md#section16107113352213) +- [使用Margin时，有什么注意事项？](faqs-system-applications.md#section1524910142314) +- [使用事件订阅时，有什么注意事项？](faqs-system-applications.md#section1537132012231) +- [使用动态绑定时，有什么注意事项？](faqs-system-applications.md#section96561452236) +- [swiper loop属性如何生效？](faqs-system-applications.md#section690166112414) +- [使用数组时，有什么注意事项？](faqs-system-applications.md#section1554552822414) ### hdc -- [hdc\_std连接不到设备](faqs-system-using.md#section1965012223257) -- [hdc\_std运行不了](faqs-system-using.md#section1157575212515) +- [hdc\_std连接不到设备](faqs-system-applications.md#section1965012223257) +- [hdc\_std运行不了](faqs-system-applications.md#section1157575212515) diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-read.md b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-listening.md similarity index 100% rename from zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-read.md rename to zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-listening.md diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-write-config.md b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-logging-config.md similarity index 100% rename from zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-write-config.md rename to zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-logging-config.md diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-write.md b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-logging.md similarity index 100% rename from zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-write.md rename to zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-logging.md diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-select.md b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-querying.md similarity index 100% rename from zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-select.md rename to zh-cn/device-dev/subsystems/subsys-dfx-hisysevent-querying.md diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent.md b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent.md index cefb6adc2836733ea35533a733c4f8fb4bb50e69..26043db5cafd11df0b0166eb8c5acbbc0a77e5a3 100755 --- a/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent.md +++ b/zh-cn/device-dev/subsystems/subsys-dfx-hisysevent.md @@ -1,11 +1,11 @@ # HiSysEvent开发指导 -- **[HiSysEvent打点配置指导](subsys-dfx-hisysevent-write-config.md)** +- **[HiSysEvent打点配置指导](subsys-dfx-hisysevent-logging-config.md)** -- **[HiSysEvent打点指导](subsys-dfx-hisysevent-write.md)** +- **[HiSysEvent打点指导](subsys-dfx-hisysevent-logging.md)** -- **[HiSysEvent订阅指导](subsys-dfx-hisysevent-read.md)** +- **[HiSysEvent订阅指导](subsys-dfx-hisysevent-listening.md)** -- **[HiSysEvent查询指导](subsys-dfx-hisysevent-select.md)** +- **[HiSysEvent查询指导](subsys-dfx-hisysevent-query.md)** - **[HiSysEvent工具使用指导](subsys-dfx-hisysevent-tool.md)** \ No newline at end of file diff --git a/zh-cn/device-dev/subsystems/subsys-dfx.md b/zh-cn/device-dev/subsystems/subsys-dfx.md index a2f9b1a5d72ee279384803d03aca396d4963810c..8ffb1767d9e49f4b9654563d021496602134ffcd 100644 --- a/zh-cn/device-dev/subsystems/subsys-dfx.md +++ b/zh-cn/device-dev/subsystems/subsys-dfx.md @@ -8,11 +8,11 @@ - **[HiSysEvent开发指导](subsys-dfx-hisysevent.md)** - - [HiSysEvent打点指导](subsys-dfx-hisysevent-write.md) + - [HiSysEvent打点指导](subsys-dfx-hisysevent-logging.md) - - [HiSysEvent订阅指导](subsys-dfx-hisysevent-read.md) + - [HiSysEvent订阅指导](subsys-dfx-hisysevent-listening.md) - - [HiSysEvent查询指导](subsys-dfx-hisysevent-select.md) + - [HiSysEvent查询指导](subsys-dfx-hisysevent-query.md) - [HiSysEvent工具使用指导](subsys-dfx-hisysevent-tool.md)