From c8b52d16a8264f68b83e8a5db3b2b45951e269a3 Mon Sep 17 00:00:00 2001 From: shawn_he Date: Tue, 29 Nov 2022 14:05:37 +0800 Subject: [PATCH] update doc Signed-off-by: shawn_he --- .../subsystems/subsys-boot-init-plugin.md | 6 ++++-- en/device-dev/subsystems/subsys-boot-overview.md | 15 ++++++++------- .../subsystems/subsys-dfx-hitracemeter.md | 2 +- 3 files changed, 13 insertions(+), 10 deletions(-) diff --git a/en/device-dev/subsystems/subsys-boot-init-plugin.md b/en/device-dev/subsystems/subsys-boot-init-plugin.md index 700aa2036b..9f04f40f32 100644 --- a/en/device-dev/subsystems/subsys-boot-init-plugin.md +++ b/en/device-dev/subsystems/subsys-boot-init-plugin.md @@ -175,7 +175,7 @@ bootchart and bootevent are available only for the standard system, and begetctl Expected result: - A **bootchart.pdf** file is generated in the **bootchart-master** directory. + A **bootchart.pdf** file is generated in the **bootchart-master** directory. #### bootevent @@ -189,7 +189,9 @@ bootchart and bootevent are available only for the standard system, and begetctl ```json bootevents : ["bootevent.xxxbootevent1", "bootevent.xxxbootevent2.xxx"], ``` -> **Note:** The configured event must start with **bootevent**. +> **NOTE** +> +> The configured event must start with **bootevent**. 2. Send the boot events. diff --git a/en/device-dev/subsystems/subsys-boot-overview.md b/en/device-dev/subsystems/subsys-boot-overview.md index 8d3852f9dc..4effe51956 100644 --- a/en/device-dev/subsystems/subsys-boot-overview.md +++ b/en/device-dev/subsystems/subsys-boot-overview.md @@ -7,7 +7,7 @@ The following figure shows the context structure of the Startup subsystem. **Figure 1** Context structure of the Startup subsystem - ![context-structure-of-the-startup-subsystem](figure/context-structure-of-the-startup-subsystem.png) + ![context-structure-of-the-Startup-subsystem](figure/context-structure-of-the-Startup-subsystem.png) When the system is powered on, the kernel loads and starts services and applications as follows: @@ -281,10 +281,11 @@ On each development board, you need to partition the memory to store the precedi ``` The key variables in the code are as follows: - **bus**: a string that saves the path of the bus connected to the current device. - **parent**: a string that stores the device path obtained from **syspath** in the uevent message. - **links**: a pointer to the memory that stores the soft link path. - **bootDevice**: a string that stores the value of **default_boot_device** in **bootargs** + - **bus**: a string that saves the path of the bus connected to the current device. + - **parent**: a string that stores the device path obtained from **syspath** in the uevent message. + - **links**: a pointer to the memory that stores the soft link path. + - **bootDevice**: a string that stores the value of **default_boot_device** in **bootargs** + According to the code, the corresponding soft link is created for the device only when the type of the connected bus is **platform**. The path of the soft link is as follows: ``` /dev/block/platform/soc/10100000.himci.eMMC/by-name @@ -415,7 +416,7 @@ Currently, OpenHarmony supports booting from partitions A and B (active and stan } ``` -- Development Example +- Development example The following uses the rk3568 platform as an example to illustrate how to change from default partition booting to partition A/B booting. @@ -457,7 +458,7 @@ Currently, OpenHarmony supports booting from partitions A and B (active and stan 2) Run the **partitionslot getslot** command to check the configured slot. - ![View Slot](figures/ABStartup_6.png) + ![View Slot](figure/ABStartup_6.png) If **current slot** is **2**, the slot of the active partition is successfully set to **2**. diff --git a/en/device-dev/subsystems/subsys-dfx-hitracemeter.md b/en/device-dev/subsystems/subsys-dfx-hitracemeter.md index e151004e3d..e5e02d1479 100644 --- a/en/device-dev/subsystems/subsys-dfx-hitracemeter.md +++ b/en/device-dev/subsystems/subsys-dfx-hitracemeter.md @@ -132,7 +132,7 @@ The trace data of **StartAsyncTrace** and **FinishAsyncTrace** is matched based | API | Function |Parameter Description | | ------------------------------------------------------------ | --------- |--------- | -| void CountTrace(uint64_t label, const std::string& name, int64_t); | Count trace.|**label**: trace category.
**name**: trace name displayed in the IDE.| +| void CountTrace(uint64_t label, const std::string& name, int64_t); | Performs a count trace.|**label**: trace category.
**name**: trace name displayed in the IDE.| ## How to Develop -- GitLab