diff --git a/en/application-dev/database/public_sys-resources/icon-caution.gif b/en/application-dev/database/public_sys-resources/icon-caution.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-caution.gif differ diff --git a/en/application-dev/database/public_sys-resources/icon-danger.gif b/en/application-dev/database/public_sys-resources/icon-danger.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-danger.gif differ diff --git a/en/application-dev/database/public_sys-resources/icon-note.gif b/en/application-dev/database/public_sys-resources/icon-note.gif new file mode 100644 index 0000000000000000000000000000000000000000..6314297e45c1de184204098efd4814d6dc8b1cda Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-note.gif differ diff --git a/en/application-dev/database/public_sys-resources/icon-notice.gif b/en/application-dev/database/public_sys-resources/icon-notice.gif new file mode 100644 index 0000000000000000000000000000000000000000..86024f61b691400bea99e5b1f506d9d9aef36e27 Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-notice.gif differ diff --git a/en/application-dev/database/public_sys-resources/icon-tip.gif b/en/application-dev/database/public_sys-resources/icon-tip.gif new file mode 100644 index 0000000000000000000000000000000000000000..93aa72053b510e456b149f36a0972703ea9999b7 Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-tip.gif differ diff --git a/en/application-dev/database/public_sys-resources/icon-warning.gif b/en/application-dev/database/public_sys-resources/icon-warning.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/application-dev/database/public_sys-resources/icon-warning.gif differ diff --git a/en/application-dev/dfx/hitracemeter-guidelines.md b/en/application-dev/dfx/hitracemeter-guidelines.md index e7e97631c240bb42358d3b0b630a92094f34bcfc..db5ebd75831bfd16fd66e5818bac2586c2b4cf7d 100644 --- a/en/application-dev/dfx/hitracemeter-guidelines.md +++ b/en/application-dev/dfx/hitracemeter-guidelines.md @@ -5,8 +5,8 @@ HiTraceMeter provides APIs for system performance tracing. You can call the APIs provided by HiTraceMeter module in your own service logic to effectively track service processes and check the system performance. ## Available APIs - -The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference]( ../reference/apis/js-apis-hitracemeter.md). + +The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference](../reference/apis/js-apis-hitracemeter.md). **APIs for performance tracing** diff --git a/en/contribute/OpenHarmony-hdf-coding-guide.md b/en/contribute/OpenHarmony-hdf-coding-guide.md index b28b7591c6467b04927d06d53d276e1f69f3b00f..5d1d92b4c2704e60a3e9664bb7ccdaab2ba975af 100644 --- a/en/contribute/OpenHarmony-hdf-coding-guide.md +++ b/en/contribute/OpenHarmony-hdf-coding-guide.md @@ -190,7 +190,7 @@ root { [Description] The HDF places the same type of devices in the same host. You can develop and deploy the driver functionalities of the host by layer, so that one driver has multiple nodes. The following figure shows the HDF driver model. -![HDFDriverModel.png]( ../device-dev/driver/figures/HDFDriverModel.png) +![HDFDriverModel.png](../device-dev/driver/figures/HDF-driver-model.png) Place devices of the same type in the same host. When adding a device, check whether the host of the same type already exists. If such a host already exists, configure the device in the host. Do not configure the same host again. A device belongs to only one driver. Therefore, do not configure the same device in different hosts. diff --git a/en/device-dev/faqs/faqs-burning.md b/en/device-dev/faqs/faqs-burning.md index 1e518ff1a7afc64f2b7333946d661df08f4a3034..bd6e8dcb08fd399c8b0dfa1e65e11a311e474fcc 100644 --- a/en/device-dev/faqs/faqs-burning.md +++ b/en/device-dev/faqs/faqs-burning.md @@ -71,7 +71,7 @@ 1. Obtain the U-Boot file. - >![](public_sys-resources/icon-notice.gif) **NOTICE:** + >![](../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** diff --git a/en/device-dev/faqs/faqs-startup.md b/en/device-dev/faqs/faqs-startup.md index cab83bad0559355247228160615a856826ccff9d..4964c1418f484922f387ca7d8346757eb0c97c20 100644 --- a/en/device-dev/faqs/faqs-startup.md +++ b/en/device-dev/faqs/faqs-startup.md @@ -9,7 +9,7 @@ During system startup, the error message "[Init] InitReadCfg, parse failed! plea **Figure 1** Error information - ![en-us_image_0000001200053087](figures/en-us_image_0000001200053087.png) + ![en-us_image_0000001200053087](figures/error-information.png) **Possible Cause** @@ -57,85 +57,3 @@ Permission verification has been enabled for **SetParameter** and **GetParameter No action is required. - -## ueventd Service Failed to Obtain a Socket upon Startup - -**Symptom** - -After the ueventd service is started, the error message "Failed to get uevent socket, try to create" is displayed, and the error information as shown in the following figure is logged. - - **Figure 2** Failure to obtain a socket - - ![ueventd_socket](figures/ueventd_socket.png) - -**Possible Cause** - -The ueventd service is started on demand. Upon startup, it first needs to check the environment variables for **fd** of the socket created by the init process. The preceding error information will be displayed if the ueventd service fails to obtain environment variables. The possible causes are as follows: -1. No socket has been configured for the ueventd service in the **.cfg** file. As a result, the init process does not create a socket for the ueventd service, and no socket ID is present in environment variables. -2. If a socket has been configured for the ueventd service in the **.cfg** file, it is probable that the ueventd service is also configured in another **.cfg** file but no socket is designated for it. - -**Solution** - -For case 1, configure a socket for the ueventd service in the **.cfg** file. For details, see [Development Guidelines](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-boot-init.md#development-guidelines). - -For case 2, check all **.cfg** files for any duplicate ueventd service and delete it. Retain only one ueventd service with valid configuration. - - -## ueventd Service Exits Because of a Socket Polling Timeout - -**Symptom** - -After the ueventd service is started for a period of time, the error message "poll ueventd socket timeout, ueventd exit" is displayed and the ueventd service automatically exits. - -**Possible Causes** - -The ueventd service is started on demand. When a uevent is reported, the init process receives a socket message and starts the ueventd service to process the message. After processing the message, the ueventd service polls the corresponding socket handle for 30s. If a new socket message is reported within this period of time, the ueventd service continues to process the message. After processing the message, the ueventd service polls the socket handle for 30s once again. If no new socket message is reported within this period of time, the ueventd service exits and returns the socket to the init process for polling. In this case, the preceding error message is displayed. - -**Solution** - -This is a normal phenomenon and no action is required. - - -## Service with the ondemand Attribute Failed to Start Because of a Configuration Parsing Error - -**Symptom** - -The service configuration in JSON format cannot be correctly parsed, and the error message "Service is invalid which has both critical and ondemand attribute" is displayed. When the service is started, the error message "Cannot find service" is displayed. - -**Possible Cause** - -The service configuration is not in the JSON format. This can result in a **.cfg** file parsing error, leading to a service parsing failure. For a service configured with the **ondemand** attribute, the **critical** attribute is set to **1**, or the first value in the **critical** attribute array is set to **1**. When the **ondemand** attribute is configured, the service is started on demand by default. The service exits when it is idle. However, when the **critical** attribute is configured, the service is regarded as a critical system service and is not allowed to exit. Therefore, a conflict occurs if both attributes are configured the same service. - -**Solution** - -Check whether the service needs to be started on demand. If not, do not configure the **ondemand** attribute. If yes, do not configure the **critical** attribute along with the **ondemand** attribute. To limit the number of times that a critical service exits abnormally, set the first value in the **critical** attribute array to **0** and then add a limitation on the exit times. For example, **"critical": [0, 15, 5]** means that, if a service exits for more than 15 times within 5s, the service will not be started and the system will not be restarted. - - -## Parallel Startup Is Not Effective for Services Configured with the ondemand Attribute - -**Symptom** - -Services configured with the **ondemand** attribute are not started in the parallel startup phase, regardless of whether **start-mode** is set to **boot**, **normal**, or the default value. - -**Possible Cause** - -Services configured with the **ondemand** attribute are started only when the startup conditions are met. Therefore, parallel startup is not effective for these services. - -**Solution** - -If you want to add a service to parallel startup, do not configure the **ondemand** attribute for it. - - -## SA Services Cannot Be Started on Demand - -**Symptom** - -When an SA service is configured with the **ondemand** attribute, the samgr process does not start the SA service after the SA client sends a request. - -**Possible Cause** - -At the initial implementation of on-demand startup, **SystemAbilityManager::CheckSystemAbility(int32_t systemAbilityId)** is used for all SA services. To distinguish SA services that are started on demand, **LoadSystemAbility(int32_t systemAbilityId, const sptr& callback)** provided by the samgr process is added. If an SA service is not started on demand, it is probable that the original API is used by mistake. - -**Solution** - -Use **LoadSystemAbility(int32_t systemAbilityId, const sptr& callback)** for any SA service that needs to be started on demand. diff --git a/en/device-dev/guide/device-iotcamera-control-example.md b/en/device-dev/guide/device-iotcamera-control-example.md index 0d2fbf23bf92862441b826088fbc42b55ba3beea..0519ebb57b512c8572787fd53f2538b68208f867 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/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/quickstart-lite-overview.md). 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 08fa2a01992eb40a3cc7927a3ec50510f48dbdae..d35ab0376543e37ae7957a92323b601e7ecd330f 100644 --- a/en/device-dev/guide/device-wlan-led-control.md +++ b/en/device-dev/guide/device-wlan-led-control.md @@ -97,7 +97,7 @@ Based on the Hi3861 platform, the OpenHarmony WLAN module provides abundant peri ## Verification -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_. +For details about the compilation and burning processes, see [Building](../quick-start/quickstart-lite-steps-hi3861-building.md) and [Burning](../quick-start/quickstart-lite-steps-hi3861-burn.md) 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. diff --git a/en/device-dev/porting/Readme-EN.md b/en/device-dev/porting/Readme-EN.md index ccb22e2f42b3853ba710af479a13a49de1b42f83..e2cb7f0cd3f01221a90f02c57d487716680db570 100644 --- a/en/device-dev/porting/Readme-EN.md +++ b/en/device-dev/porting/Readme-EN.md @@ -24,7 +24,7 @@ The download steps for other resources are the same as those in the mainline ver - [Mini System SoC Porting Guide](porting-minichip.md) - Porting Preparations - - [Before You Start](porting-chip-prepare-knows.md) + - [Before You Start](oem_transplant_chip_prepare_knows.md) - [Building Adaptation Process](porting-chip-prepare-process.md) - Kernel Porting - [Overview](porting-chip-kernel-overview.md) diff --git a/en/device-dev/porting/porting-chip-prepare.md b/en/device-dev/porting/porting-chip-prepare.md index 44cb5673ddc7e7f7a2df08defe0c70b0d9ee2277..52c6cc9bd81b9ad45a7841e4b1df4e92cb67d4a4 100644 --- a/en/device-dev/porting/porting-chip-prepare.md +++ b/en/device-dev/porting/porting-chip-prepare.md @@ -1,6 +1,6 @@ # Porting Preparations -- **[Before You Start](porting-chip-prepare-knows.md)** +- **[Before You Start](oem_transplant_chip_prepare_knows.md)** - **[Building Adaptation Process](porting-chip-prepare-process.md)** diff --git a/en/device-dev/porting/porting-minichip-cases.md b/en/device-dev/porting/porting-minichip-cases.md index 1b550e80b5b3864eaf47157b8306d64086411d0e..cd8de34c7551b3545f90f6079e1c496fe40ad656 100644 --- a/en/device-dev/porting/porting-minichip-cases.md +++ b/en/device-dev/porting/porting-minichip-cases.md @@ -1,4 +1,4 @@ # Mini System SoC Porting Cases - **[Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting-bes2600w-on-minisystem-display-demo.md)** -- **[Combo Solution – ASR Chip Porting Case](porting-asr582x-combo-demo.md)** + diff --git a/en/device-dev/quick-start/quickstart-lite-package-directory.md b/en/device-dev/quick-start/quickstart-lite-package-directory.md index 78fee5a65bc346220534309249b4b2cb19255d7c..9b60a97bd82f0d53d4eb9d433677a173b9d35037 100644 --- a/en/device-dev/quick-start/quickstart-lite-package-directory.md +++ b/en/device-dev/quick-start/quickstart-lite-package-directory.md @@ -9,7 +9,7 @@ - [Burning](quickstart-lite-steps-hi3861-burn.md) - [Networking](quickstart-lite-steps-hi3861-netconfig.md) - [Debugging and Verification](quickstart-lite-steps-hi3861-debug.md) - - [Running](quickstart-lite-steps-hi3816-running.md) + - [Running](quickstart-lite-steps-hi3861-running.md) - Hi3516 Development Board - [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md) - [Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md) diff --git a/en/device-dev/subsystems/public_sys-resources/icon-caution.gif b/en/device-dev/subsystems/public_sys-resources/icon-caution.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-caution.gif differ diff --git a/en/device-dev/subsystems/public_sys-resources/icon-danger.gif b/en/device-dev/subsystems/public_sys-resources/icon-danger.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-danger.gif differ diff --git a/en/device-dev/subsystems/public_sys-resources/icon-note.gif b/en/device-dev/subsystems/public_sys-resources/icon-note.gif new file mode 100644 index 0000000000000000000000000000000000000000..6314297e45c1de184204098efd4814d6dc8b1cda Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-note.gif differ diff --git a/en/device-dev/subsystems/public_sys-resources/icon-notice.gif b/en/device-dev/subsystems/public_sys-resources/icon-notice.gif new file mode 100644 index 0000000000000000000000000000000000000000..86024f61b691400bea99e5b1f506d9d9aef36e27 Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-notice.gif differ diff --git a/en/device-dev/subsystems/public_sys-resources/icon-tip.gif b/en/device-dev/subsystems/public_sys-resources/icon-tip.gif new file mode 100644 index 0000000000000000000000000000000000000000..93aa72053b510e456b149f36a0972703ea9999b7 Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-tip.gif differ diff --git a/en/device-dev/subsystems/public_sys-resources/icon-warning.gif b/en/device-dev/subsystems/public_sys-resources/icon-warning.gif new file mode 100644 index 0000000000000000000000000000000000000000..6e90d7cfc2193e39e10bb58c38d01a23f045d571 Binary files /dev/null and b/en/device-dev/subsystems/public_sys-resources/icon-warning.gif differ diff --git a/en/device-dev/subsystems/subsys-tel-guide.md b/en/device-dev/subsystems/subsys-tel-guide.md index 3392e0cdb9af636e9aad4a8226856b44d29a4dec..ff2da7245e8685578af920d6325eaaff4a28b4ff 100644 --- a/en/device-dev/subsystems/subsys-tel-guide.md +++ b/en/device-dev/subsystems/subsys-tel-guide.md @@ -1,4 +1,4 @@ -# Development Guidelines +# Telephony Development ## Initializing a Modem Vendor Library @@ -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/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](subsys-toolchain-hdc-guide.md#section05992022154916) 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/ @@ -241,7 +241,7 @@ The following table describes the APIs for responding to modem service requests, ### Debugging and Verification -1. Use the [hdc\_std](../subsystems/subsys-toolchain-hdc-guide.md) 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. +1. Use the [hdc\_std](subsys-toolchain-hdc-guide.md#section05992022154916) 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. ``` hdc_std file send libril_vendor.z.so /system/lib/ @@ -380,7 +380,7 @@ The following table describes the API for reporting modem events. ### Debugging and Verification -1. Use the [hdc\_std](subsystems/subsys-toolchain-hdc-guide.md) 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. +1. Use the [hdc\_std](subsys-toolchain-hdc-guide.md#section05992022154916) 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. ``` hdc_std file send libril_vendor.z.so /system/lib/ diff --git a/en/device-dev/subsystems/subsys-tel-overview.md b/en/device-dev/subsystems/subsys-tel-overview.md index 8ea0cfbad4b42ca98c019c95a2b552028b3f4fca..7ee561e36b48430058d26bae3ed4157d0ded9a6e 100644 --- a/en/device-dev/subsystems/subsys-tel-overview.md +++ b/en/device-dev/subsystems/subsys-tel-overview.md @@ -1,4 +1,4 @@ -# Telephony Service +# Telephony Overview ## Introduction diff --git a/en/readme/common-event-notification.md b/en/readme/common-event-notification.md index 5ee3cb26cd563348671d3c886d5ea9a075b8b4f8..eb0c1fd99ba1b789aeccbc017eacca8622eb6fe8 100644 --- a/en/readme/common-event-notification.md +++ b/en/readme/common-event-notification.md @@ -14,7 +14,7 @@ Each application can subscribe to common events as required. After your applicat ### Architecture -![]( figures/cesfwk_architecture_diagram.png "CES Architecture") +![](figures/cesfwk_architecture_diagram.png "CES Architecture") ## Directory Structure