diff --git a/en/application-dev/reference/arkui-ts/ts-basic-components-textinput.md b/en/application-dev/reference/arkui-ts/ts-basic-components-textinput.md index 0bb567a4ab037272e73c62c7dfe75a1df736c046..279471bbf8ae99a48673addb5fd64e17c2f1a760 100644 --- a/en/application-dev/reference/arkui-ts/ts-basic-components-textinput.md +++ b/en/application-dev/reference/arkui-ts/ts-basic-components-textinput.md @@ -1,114 +1,101 @@ # TextInput +> ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：** +> 该组件从API Version 7开始支持。后续版本如有新增内容，则采用上角标单独标记该内容的起始版本。 -> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** -> -> This component is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version. +提供单行文本输入组件。 -The **<TextInput>** component provides single-line text input. +## 权限列表 -## Required Permissions +无 -None +## 子组件 -## Child Components +无 -None - -## APIs +## 接口 TextInput(value?:{placeholder?: string controller?: TextInputController}) -- Parameters - | Name | Type | Mandatory | Default Value | Description | - | -------- | -------- | -------- | -------- | -------- | - | placeholder | string | No | - | Text displayed when there is no input. | - | controller8+ | [TextInputController](#textinputcontroller8) | No | - | Text input controller. | - - -## Attributes - -In addition to universal attributes, the following attributes are supported. - -| Name | Type | Default Value | Description | -| -------- | -------- | -------- | -------- | -| type | InputType | InputType.Normal | Input box type. | -| placeholderColor | Color | - | Placeholder color. | -| placeholderFont | {
size?: Length,
weight?: number\|[FontWeight](ts-universal-attributes-text-style.md),
family?: string,
style?: [FontStyle](ts-universal-attributes-text-style.md)
} | - | Placeholder text style.
- **size**: font size. If the value is of the number type, the unit fp is used.
- **weight**: font weight. For the number type, the value ranges from 100 to 900, at an interval of 100. The default value is **400**. A larger value indicates a larger font weight.
- **family**: font family. Use commas (,) to separate multiple fonts, for example, **'Arial, sans-serif'**. The priority of the fonts is the sequence in which they are placed.
- **style**: font style. | -| enterKeyType | EnterKeyType | EnterKeyType.Done | How the Enter key is labeled. | -| caretColor | Color | - | Color of the caret (also known as the text insertion cursor). | -| maxLength8+ | number | - | Maximum number of characters in the text input. | -| inputFilter8+ | {
value: [ResourceStr](../../ui/ts-types.md)8+,
error?: (value: string)
} | - | Regular expression for input filtering. Only inputs that comply with the regular expression can be displayed. Other inputs are ignored. The specified regular expression can match single characters, but not strings. Example: ^(? =.\*\d)(? =.\*[a-z])(? =.\*[A-Z]).{8,10}$. Strong passwords containing 8 to 10 characters cannot be filtered.
- **value**: indicates the regular expression to set.
- **error**: returns the ignored content when regular expression matching fails. | - -- EnterKeyType enums - | Name | Description | - | -------- | -------- | - | EnterKeyType.Go | The Enter key is labeled "Go." | - | EnterKeyType.Search | The Enter key is labeled "Search." | - | EnterKeyType.Send | The Enter key is labeled "Send." | - | EnterKeyType.Next | The Enter key is labeled "Next." | - | EnterKeyType.Done | The Enter key is labeled "Done." | - -- InputType enums - | Name | Description | - | -------- | -------- | - | InputType.Normal | Normal input mode. | - | InputType.Password | Password input mode. | - | InputType.Email | Email address input mode. | - | InputType.Number | Digit input mode. | - +- 参数 + | 参数名 | 参数类型 | 必填 | 默认值 | 参数描述 | + | ----------------------- | ---------------------------------------- | ---- | ---- | --------------- | + | placeholder | string | 否 | - | 无输入时的提示文本。 | + | controller8+ | [TextInputController](#textinputcontroller8) | 否 | - | 设置TextInput控制器。 | + + +## 属性 + +除支持通用属性外，还支持以下属性： + +| 名称 | 参数类型 | 默认值 | 描述 | +| ------------------------ | ---------------------------------------- | ----------------- | ---------------------------------------- | +| type | InputType | InputType.Normal | 设置输入框类型。 | +| placeholderColor | Color | - | 设置placeholder颜色。 | +| placeholderFont | {
size?: Length,
weight?: number\|[FontWeight](ts-universal-attributes-text-style.md),
family?: string,
style?: [FontStyle](ts-universal-attributes-text-style.md)
} | - | 设置placeholder文本样式：
- size: 设置文本尺寸，Length为number类型时，使用fp单位。
- weight: 设置文本的字体粗细，number类型取值[100, 900]，取值间隔为100，默认为400，取值越大，字体越粗。
- family: 设置文本的字体列表。使用多个字体，使用','进行分割，优先级按顺序生效。例如：'Arial, sans-serif'。
- style: 设置文本的字体样式。 | +| enterKeyType | EnterKeyType | EnterKeyType.Done | 设置输入法回车键类型。 | +| caretColor | Color | - | 设置输入框光标颜色。 | +| maxLength | number | - | 设置文本的最大输入字符数。 | +| inputFilter8+ | {
value: [ResourceStr](../../ui/ts-types.md)8+,
error?: (value: string)
} | - | 正则表达式，满足表达式的输入允许显示，不满足正则表达式的输入被忽略。仅支持单个字符匹配，不支持字符串匹配。例如：^(?=.\*\d)(?=.\*[a-z])(?=.\*[A-Z]).{8,10}$，8到10位的强密码不支持过滤。
- value：设置正则表达式。
- error：正则匹配失败时，返回被忽略的内容。 | + +- EnterKeyType枚举说明 + | 名称 | 描述 | + | ------------------- | --------- | + | EnterKeyType.Go | 显示Go文本。 | + | EnterKeyType.Search | 显示为搜索样式。 | + | EnterKeyType.Send | 显示为发送样式。 | + | EnterKeyType.Next | 显示为下一个样式。 | + | EnterKeyType.Done | 标准样式。 | + +- InputType枚举说明 + | 名称 | 描述 | + | ------------------ | ------------- | + | InputType.Normal | 基本输入模式。 | + | InputType.Password | 密码输入模式。 | + | InputType.Email | e-mail地址输入模式。 | + | InputType.Number | 纯数字输入模式。 | + + +## 事件 + +| 名称 | 功能描述 | +| ---------------------------------------- | ---------------------------------------- | +| onChange(value: string) => void | 输入发生变化时，触发回调。 | +| onSubmit(callback: (enterKey: EnterKeyType) => void) | 回车键或者软键盘回车键触发该回调，参数为当前软键盘回车键类型。 | +| onEditChanged(callback: (isEditing: boolean) => void)(deprecated) | 输入状态变化时，触发回调。 | +| onEditChange(callback: (isEditing: boolean) => void) 8+ | 输入状态变化时，触发回调。 | +| onCopy8+(callback:(value: string) => void) | 长按输入框内部区域弹出剪贴板后，点击剪切板复制按钮，触发回调。
value：复制的文本内容。 | +| onCut8+(callback:(value: string) => void) | 长按输入框内部区域弹出剪贴板后，点击剪切板剪切按钮，触发回调。
value：剪切的文本内容。 | +| onPaste8+(callback:(value: string) => void) | 长按输入框内部区域弹出剪贴板后，点击剪切板粘贴按钮，触发回调。
value：粘贴的文本内容。 | ### TextInputController8+ -Implements the controller of the **<TextInput>** component. - -| Name | Description | -| -------- | -------- | -| caretPosition(value: number):void | Position of the input cursor.
**value**: indicates the length from the start of the string to the position where the input cursor is located. | - - -### Objects to Import - +TextInput组件的控制器。 +#### 导入对象 ``` controller: TextInputController = new TextInputController() ``` +#### caretPosition +caretPosition(value: number): void -### controller.createPosition - -caretPosition(value: number): void +设置光标移动到指定位置。 +- 参数 -Sets the cursor in a specified position. + | 参数名 | 参数类型 | 必填 | 默认值 | 参数描述 | + | ----- | ------ | ---- | ---- | ---------------------------------------- | + | value | number | 是 | - | 设置输入光标的位置。
value：从字符串开始到光标所在位置的字符长度。 | -- Parameters - | Name | Type | Mandatory | Default Value | Description | - | -------- | -------- | -------- | -------- | -------- | - | value | number | Yes | - | Position of the input cursor.
**value**: indicates the length from the start of the string to the position where the input cursor is located. | +## 示例 -## Events - -| Name | Description | -| -------- | -------- | -| onChange(value: string) => void | Triggered when the input changes. | -| onSubmit(callback: (enterKey: EnterKeyType) => void) | Triggered when the Enter key on the physical or soft keyboard is pressed. | -| onEditChanged(callback: (isEditing: boolean) => void)(deprecated) | Triggered when the input status changes. | -| onEditChange(callback: (isEditing: boolean) => void) 8+ | Triggered when the input status changes. | -| onCopy8+(callback:(value: string) => void) | Triggered when the copy button on the pasteboard, which displays when the text box is long pressed, is clicked.
**value**: text to be copied. | -| onCut8+(callback:(value: string) => void) | Triggered when the cut button on the pasteboard, which displays when the text box is long pressed, is clicked.
**value**: text to be cut. | -| onPaste8+(callback:(value: string) => void) | Triggered when the paste button on the pasteboard, which displays when the text box is long pressed, is clicked.
**value**: text to be pasted. | - - -## Example - - -### Single-line Text Input +### 单行文本输入 ``` @Entry @@ -139,11 +126,10 @@ struct TextInputExample1 { ``` -![en-us_image_0000001212378402](figures/en-us_image_0000001212378402.gif) - +![zh-cn_image_0000001252769643](figures/zh-cn_image_0000001252769643.gif) -### Setting the Input Cursor +### 设置光标 ``` @Entry @@ -163,4 +149,4 @@ struct TextInputExample2 { } ``` -![en-us_image_0000001212058468](figures/en-us_image_0000001212058468.png) +![zh-cn_image_0000001208256092](figures/zh-cn_image_0000001208256092.png) diff --git a/en/application-dev/ui/ts-component-based-builder.md b/en/application-dev/ui/ts-component-based-builder.md index 94e75620e5a4d9c1f24cb7c0325d6f852017f797..a07b244ffdc2bd9105102058e6881b14289fdf34 100644 --- a/en/application-dev/ui/ts-component-based-builder.md +++ b/en/application-dev/ui/ts-component-based-builder.md @@ -1,8 +1,7 @@ # @Builder -The @Builder decorated method is used to define the declarative UI description of a component and quickly generate multiple layouts in a custom component. The functionality and syntax of the @Builder decorator are the same as those of the [build Function](ts-function-build.md). - +The **@Builder** decorated method is used to define the declarative UI description of a component and quickly generate multiple layouts in a custom component. The functionality and syntax of the **@Builder** decorator are the same as those of the [build Function](ts-function-build.md). ``` @@ -42,30 +41,29 @@ struct CompA { } } ``` - -## @BuilderParam8+ - -The @BuilderParam decorator is used to modify the function type attributes (for example, @BuilderParam content: () => any) in a custom component. When the custom component is initialized, the attributes modified by the @BuilderParam decorator must be assigned values. +## @BuilderParam8+ +The **@BuilderParam** decorator is used to modify the function type attributes (for example, `@BuilderParam content: () => any;`) in a custom component. When the custom component is initialized, the attributes modified by the **@BuilderParam** decorator must be assigned values. ### Background -In certain circumstances, you may need to add a specific function, such as a click-to-jump action, to a custom component. However, embedding an event method directly inside of the component can add the function to all places where the component is initialized. This is where the @BuilderParam decorator come into the picture. When initializing a custom component, you can assign a @Builder decorated method to the @BuilderParam decorated attribute, thereby adding the specific function to the custom component. +In certain circumstances, you may need to add a specific function, such as a click-to-jump action, to a custom component. However, embedding an event method directly inside of the component will add the function to all places where the component is initialized. This is where the **@BuilderParam** decorator comes into the picture. When initializing a custom component, you can assign a **@Builder** decorated method to the **@BuilderParam** decorated attribute, thereby adding the specific function to the custom component. ### Component Initialization Through Parameters - -When initializing a custom component through parameters, assign a @Builder decorated method to the @BuilderParam decorated attribute —content, and call the value of content in the custom component. +When initializing a custom component through parameters, assign a **@Builder** decorated method to the **@BuilderParam** decorated attribute — **content**, and call the value of **content** in the custom component. If no parameter is passed when assigning a value to the **@BuilderParam** decorated attribute (for example, `content: this.specificParam`), define the type of the attribute as a function without a return value (for example, `@BuilderParam content: () => void`). If any parameter is passed when assigning a value to the **@BuilderParam** decorated attribute (for example, `callContent: this.specificParam1("111")`), define the type of the attribute as `any` (for example,`@BuilderParam callContent: any;`). ``` @Component struct CustomContainer { header: string = ""; - @BuilderParam content: () => any; + @BuilderParam noParam: () => void; + @BuilderParam withParam: any; footer: string = ""; build() { Column() { Text(this.header) .fontSize(50) - this.content() + this.noParam() + this.withParam() Text(this.footer) .fontSize(50) } @@ -75,7 +73,12 @@ struct CustomContainer { @Entry @Component struct CustomContainerUser { - @Builder specificParam(label: string) { + @Builder specificNoParam() { + Column() { + Text("noParam").fontSize(50) + } + } + @Builder SpecificWithParam(label: string) { Column() { Text(label).fontSize(50) } @@ -85,25 +88,23 @@ struct CustomContainerUser { Column() { CustomContainer({ header: "Header", - content: this.specificParam("111") + noParam: this.specificNoParam, + withParam: this.SpecificWithParam("WithParam"), footer: "Footer", }) } } } ``` - ### Component Initialization Through Trailing Closure +In a custom component, use the **@BuilderParam** decorated attribute to receive a trailing closure. When the custom component is initialized, the component name is followed by a pair of braces ({}) to form a trailing closure (`CustomComponent(){}`). You can consider a trailing closure as a container and add content to it. For example, you can add a component (`{Column(){Text("content")}`) to a trailing closure. The syntax of the closure is the same as that of [build](../ui/ts-function-build.md). In this scenario, the custom component has one and only one **@BuilderParam** decorated attribute. -In a custom component, use the @BuilderParam decorated attribute to receive a trailing closure. When the custom component is initialized, the component name is followed by a pair of braces ({}) to form a trailing closure (CustomComponent(){}). You can consider a trailing closure as a container and add content to it. For example, you can add a component ({Column(){Text("content")}) to the closure. The syntax of the closure is the same as that of [build](ts-function-build.md). In this scenario, the custom component has one and only one @BuilderParam decorated attribute. - -Example: Add a <Column> component and a click event to the closure, and call the specificParam method decorated by @Builder in the new <Column> component. After the <Column> component is clicked, the value of the component's header attribute will be changed to changeHeader. In addition, when the component is initialized, the content of the trailing closure will be assigned to the closer attribute decorated by @BuilderParam. - +Example: Add a **\** component and a click event to the closure, and call the **specificParam** method decorated by **@Builder** in the new **\** component. After the **\** component is clicked, the value of the component's `header` attribute will change to `changeHeader`. In addition, when the component is initialized, the content of the trailing closure will be assigned to the `closer` attribute decorated by **@BuilderParam**. ``` @Component struct CustomContainer { header: string = ""; - @BuilderParam closer: () => any; + @BuilderParam closer: () => void; build() { Column() { Text(this.header) diff --git a/en/device-dev/guide/device-camera-control-demo-photoguide.md b/en/device-dev/guide/device-camera-control-demo-photoguide.md index e0046ccac0e5ce11729608e499db15ee02759bbc..de61ed05e5c83016c0669fe568d3db79cbe9a6fa 100644 --- a/en/device-dev/guide/device-camera-control-demo-photoguide.md +++ b/en/device-dev/guide/device-camera-control-demo-photoguide.md @@ -6,7 +6,7 @@ Use the camera module APIs to capture frames \(photographing\). ## Available APIs -**Table 1** APIs for photographing +**Table 1** APIs for photographing

Class

diff --git a/en/device-dev/guide/device-camera-control-demo.md b/en/device-dev/guide/device-camera-control-demo.md index 48b36ad9d6493fe655779cd63e2c9b8be7c2e1f4..0656cdd72908cb5fd9c21e373f478b09c3693406 100644 --- a/en/device-dev/guide/device-camera-control-demo.md +++ b/en/device-dev/guide/device-camera-control-demo.md @@ -1,4 +1,4 @@ -# Development Guidelines +# Screen and Camera Control Development - **[Photographing](device-camera-control-demo-photoguide.md)** diff --git a/en/device-dev/guide/device-camera-control-example.md b/en/device-dev/guide/device-camera-control-example.md index c9920f4b3bfa6aa40c3f315c86410cb56bc5cf84..dbe3e5744342b584ae913d8bca561323a67c1dd4 100644 --- a/en/device-dev/guide/device-camera-control-example.md +++ b/en/device-dev/guide/device-camera-control-example.md @@ -5,7 +5,7 @@ This use case takes **camera\_sample** \(contained in the source code\) as an - 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#section26131214194212). - >![](../public_sys-resources/icon-note.gif) **NOTE:** + >![](../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. >How to Remove: In **build/lite/components/applications.json**, comment out or delete the **//applications/sample/camera/launcher:launcher\_hap** line from the **target** field of **camera\_sample\_app**. @@ -18,7 +18,7 @@ This use case takes **camera\_sample** \(contained in the source code\) as an Recompile the source code repository and burn the code into the development board. Then you can find the **camera\_sample** file in the **bin** directory of the board. - >![](../public_sys-resources/icon-notice.gif) **NOTICE:** + >![](../public_sys-resources/icon-notice.gif) **NOTICE**
>You should insert a TF card \(up to 128 GB supported\) for photographing and video recording before system startup. This way, the TF card will be automatically mounted to the **/sdcard** directory. If you insert the TF card after the system is started, you have to manually mount the TF card. >To view the photos and videos in the TF card, copy them to a computer. If you just want to preview photos and videos, you do not need to insert a TF card. @@ -26,14 +26,14 @@ 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 + **Figure 1** 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 + **Figure 2** 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. @@ -41,24 +41,24 @@ This use case takes **camera\_sample** \(contained in the source code\) as an **Figure 3** 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. +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 + **Figure 4** 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 + **Figure 5** 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 + **Figure 6** 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 + **Figure 7** 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") diff --git a/en/device-dev/guide/device-camera-control-overview.md b/en/device-dev/guide/device-camera-control-overview.md index 61f5aa13eb0b6a3e4cdf4362bd5355846f7f4135..878d479a2fe586236b0679da452430b5257dce52 100644 --- a/en/device-dev/guide/device-camera-control-overview.md +++ b/en/device-dev/guide/device-camera-control-overview.md @@ -1,10 +1,10 @@ -# Overview +# Screen and Camera Control Overview This document describes how to use the IoT camera development board \(Hi3516D V300\) and its camera and screen to implement photographing, video recording, and video preview. This document helps you take a deep dive into OpenHarmony camera control. With this reference, you can develop devices, such as peephole cameras, smart rear-view mirrors, and smart displays. -If you want to view the running effect first, see [Use Case](device-camera-control-example.md). To customize application behavior, modify the sample code by referring to APIs described in the "Development Guidelines" section. +If you want to view the running effect first, see [Use Case](device-camera-control-example.md). To customize application behavior, modify the sample code by referring to APIs described in the "Development Guidelines" section. -For basic concepts of camera development, see [Camera Development Overview](../subsystems/subsys-multimedia-camera-overview.md). +For basic concepts of camera development, see [Camera Development Overview](../subsystems/subsys-multimedia-camera-overview.md). diff --git a/en/device-dev/guide/device-camera-control.md b/en/device-dev/guide/device-camera-control.md index 062b965f7a68b9f00b602b2dfb8fe3b1cbacfbc1..e57f328b6d90589b33abc16752c301b2ef78a158 100644 --- a/en/device-dev/guide/device-camera-control.md +++ b/en/device-dev/guide/device-camera-control.md @@ -1,8 +1,8 @@ # Screen and Camera Control -- **[Overview](device-camera-control-overview.md)** +- **[Screen and Camera Control Overview](device-camera-control-overview.md)** -- **[Development Guidelines](device-camera-control-demo.md)** +- **[Screen and Camera Control Development](device-camera-control-demo.md)** - **[Use Case](device-camera-control-example.md)** diff --git a/en/device-dev/guide/device-clock-guide.md b/en/device-dev/guide/device-clock-guide.md index aabc19dc53b98c03eb56b41de2080ee729ad3a46..6b651639cefe807571b3d111142d5a60288bbfe8 100644 --- a/en/device-dev/guide/device-clock-guide.md +++ b/en/device-dev/guide/device-clock-guide.md @@ -247,7 +247,7 @@ To build such an app, we can create a page that has a flexible layout with two r ## Signing and Packaging -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](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-debugging-and-running-0000001263040487#section17660437768)). +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](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-debugging-and-running-0000001263040487#section17660437768). ## Running on the Real Device diff --git a/en/device-dev/guide/device-iotcamera-control-demo.md b/en/device-dev/guide/device-iotcamera-control-demo.md index 6f187156291b9c813d199060c055e0d205e295db..2d711a2c708133b926a17f2f21ee576171b4541d 100644 --- a/en/device-dev/guide/device-iotcamera-control-demo.md +++ b/en/device-dev/guide/device-iotcamera-control-demo.md @@ -1,4 +1,4 @@ -# Development Guidelines +# Camera Control Development - **[Photographing](device-iotcamera-control-demo-photodevguide.md)** diff --git a/en/device-dev/guide/device-iotcamera-control-example.md b/en/device-dev/guide/device-iotcamera-control-example.md index 0b241bf85e5ebd5a774c2b23984e0525c5be9de9..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 -- A Hi318 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-iotcamera-control-overview.md b/en/device-dev/guide/device-iotcamera-control-overview.md index d5a493f3a209e1fd4dc4deb2b2c195956bcac273..d67f97231ed8c18469818d1d0e1c43cb69ab1141 100644 --- a/en/device-dev/guide/device-iotcamera-control-overview.md +++ b/en/device-dev/guide/device-iotcamera-control-overview.md @@ -1,10 +1,10 @@ -# Overview +# Camera Control Overview This document describes how to use the IoT camera development board and the built-in camera of the development kit to implement photographing and video recording. -You can perform operations provided in [Use Case](device-iotcamera-control-example.md) to learn more about development board peripheral control and then develop devices such as cameras. +You can perform operations provided in [Use Case](device-iotcamera-control-example.md) to learn more about development board peripheral control and then develop devices such as cameras. -If you want to view the sample effect first, see [Use Case](device-iotcamera-control-example.md). To customize application behavior, modify the sample code by referring to APIs described in the next section. +If you want to view the sample effect first, see [Use Case](device-iotcamera-control-example.md). To customize application behavior, modify the sample code by referring to APIs described in the next section. -For details about basic concepts for camera development, see the [camera development overview](../subsystems/subsys-multimedia-camera-overview.md). +For details about basic concepts for camera development, see [Camera Overview](../subsystems/subsys-multimedia-camera-overview.md). diff --git a/en/device-dev/guide/device-iotcamera-control.md b/en/device-dev/guide/device-iotcamera-control.md index f2720769bb74584a87e538a45093ee13bfb95869..35d1af547b6a0b579c201e01079c1429f5249492 100644 --- a/en/device-dev/guide/device-iotcamera-control.md +++ b/en/device-dev/guide/device-iotcamera-control.md @@ -1,8 +1,8 @@ # Camera Control -- **[Overview](device-iotcamera-control-overview.md)** +- **[Camera Control Overview](device-iotcamera-control-overview.md)** -- **[Development Guidelines](device-iotcamera-control-demo.md)** +- **[Camera Control Development](device-iotcamera-control-demo.md)** - **[Use Case](device-iotcamera-control-example.md)** diff --git a/en/device-dev/guide/device-wlan-led-control.md b/en/device-dev/guide/device-wlan-led-control.md index ba3f8f29838d810c92057077bda04cb25e1cf0d0..08fa2a01992eb40a3cc7927a3ec50510f48dbdae 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-ide-lite-steps-hi3861-building.md) and [Burning Images](../quick-start/quickstart-ide-lite-steps-hi3861-burn.md) 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. diff --git a/en/device-dev/porting/Readme-EN.md b/en/device-dev/porting/Readme-EN.md index 238773053ceba4a917225ceaa56b61272fe503d6..581aaf0bfcb8cdfda65617c9025c45cb4651a4ef 100644 --- a/en/device-dev/porting/Readme-EN.md +++ b/en/device-dev/porting/Readme-EN.md @@ -23,14 +23,14 @@ The download steps for other resources are the same as those in the mainline ver # Porting Procedure - [Mini System SoC Porting Guide](porting-minichip.md) - - [Porting Preparations](porting-chip-prepare.md) - - [Before You Start](oem_transplant_chip_prepare_knows.md) + - Porting Preparations + - [Before You Start](porting-chip-prepare-knows.md) - [Building Adaptation Process](porting-chip-prepare-process.md) - - [Kernel Porting](porting-chip-kernel.md) + - Kernel Porting - [Overview](porting-chip-kernel-overview.md) - [Basic Kernel Adaptation](porting-chip-kernel-adjustment.md) - [Kernel Porting Verification](porting-chip-kernel-verify.md) - - [Board-Level OS Porting](porting-chip-board.md) + - Board-Level OS Porting - [Overview](porting-chip-board-overview.md) - [Board-Level Driver Adaptation](porting-chip-board-driver.md) - [Implementation of APIs at the HAL](porting-chip-board-hal.md) @@ -38,22 +38,22 @@ The download steps for other resources are the same as those in the mainline ver - [lwIP Module Adaptation](porting-chip-board-lwip.md) - [Third-party Module Adaptation](porting-chip-board-bundle.md) - [XTS](porting-chip-board-xts.md) - - [FAQ](porting-chip-faqs.md) -- [Small System SoC Porting Guide](porting-smallchip.md) - - [Porting Preparations](porting-smallchip-prepare.md) + - [FAQs](porting-chip-faqs.md) +- Small System SoC Porting Guide + - Porting Preparations - [Before You Start](porting-smallchip-prepare-needs.md) - [Compilation and Building](porting-smallchip-prepare-building.md) - - [Kernel Porting](porting-smallchip-kernel.md) + - Kernel Porting - [LiteOS Cortex-A](porting-smallchip-kernel-a.md) - [Linux Kernel](porting-smallchip-kernel-linux.md) - - [Driver Porting](porting-smallchip-driver.md) + - Driver Porting - [Overview](porting-smallchip-driver-overview.md) - [Platform Driver Porting](porting-smallchip-driver-plat.md) - [Device Driver Porting](porting-smallchip-driver-oom.md) - Standard System SoC Porting Guide - [Standard System Porting Guide](standard-system-porting-guide.md) - [A Method for Rapidly Porting the OpenHarmony Linux Kernel](porting-linux-kernel.md) -- [Third-Party Library Porting Guide for Mini and Small Systems](porting-thirdparty.md) +- Third-Party Library Porting Guide for Mini and Small Systems - [Overview](porting-thirdparty-overview.md) - [Porting a Library Built Using CMake](porting-thirdparty-cmake.md) - [Porting a Library Built Using Makefile](porting-thirdparty-makefile.md) diff --git a/en/device-dev/porting/porting-bes2600w-on-minisystem-display-demo.md b/en/device-dev/porting/porting-bes2600w-on-minisystem-display-demo.md index 651407e8a549870d39f555ed9f7e614fe26d3488..0b46c948c81919ff969b3f2c321c157cb23c5b96 100644 --- a/en/device-dev/porting/porting-bes2600w-on-minisystem-display-demo.md +++ b/en/device-dev/porting/porting-bes2600w-on-minisystem-display-demo.md @@ -73,11 +73,11 @@ kernel_version = "3.0.0" --- Kernel version, which corresponds to Run the `hb set` command, enter the project root directory, and press `Enter`. The `hb` command traverses all `config.json` files in the `//vendor//` directory and provides product compilation options. In the `config.json` file, `product_name` indicates the product name, `device_company` and `board` are used to locate the `//device/board//` directory and find the matching `/config.gni` file. If multiple file matches are found, it indicates that the board has been adapted to multiple kernels. In this case, `kernel_type` and `kernel_version` in the `config.json` file can be used to uniquely match the `config.gni` file and thereby determine the board with which kernel needs to be compiled and adapted. If the information shown below is displayed, the `hb set` configuration is correct. - ![hb set](figure/bes2600_hb_set.png) + ![hb set](figures/bes2600_hb_set.png) ​ You can run the `hb env` command to view the selected precompilation environment variables. -![hb env](figure/bes2600_hb_env.png) +![hb env](figures/bes2600_hb_env.png) Before running the `hb build` command, complete the LiteOS-M kernel adaptation. For details, see [Kernel Porting](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/porting/porting-bes2600w-on-minisystem-display-demo.md#%E5%86%85%E6%A0%B8%E7%A7%BB%E6%A4%8D). @@ -263,7 +263,7 @@ In this example, the configuration file of `defconfig` is saved in `$(PRODUCT_PA When the configuration is complete, run the `make menuconfig` command in the `kernel/liteos_m` directory to select `SoC Series`/`SoC`/`Board`. -![board make menuconfig](figure/bes2600_board_make_menuconfig.png) +![board make menuconfig](figures/bes2600_board_make_menuconfig.png) The result is automatically saved in `$(PRODUCT_PATH)/kernel_configs/debug.config` and will be exported when `make menuconfig` is executed. @@ -432,7 +432,7 @@ static int32_t FsDriverInit(struct HdfDeviceObject *object) In the mini system, adapting the C library is a complex process. For details, see *Solution to Smooth Switchover Between musl and newlib for LiteOS-M Kernel*. The toolchain uses the `newlib` C library of the [gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2](https://gitee.com/link?target=https%3A%2F%2Fdeveloper.arm.com%2F-%2Fmedia%2FFiles%2Fdownloads%2Fgnu-rm%2F10.3-2021.10%2Fgcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2). In light of this, the `newlib` C library is used for system porting. Select `newlib` in `make menuconfig` of the kernel, as shown below. -![image-20211212191013553](figure/bes2600_newlib_make_menuconfig.png) +![image-20211212191013553](figures/bes2600_newlib_make_menuconfig.png) #### malloc Adaptation diff --git a/en/device-dev/porting/porting-chip-board-overview.md b/en/device-dev/porting/porting-chip-board-overview.md index a56d64f243fa088d5c31b5d5445e18d07a65c615..d2cb9a35d996a846b926327cbbbcde8a3659ac1a 100644 --- a/en/device-dev/porting/porting-chip-board-overview.md +++ b/en/device-dev/porting/porting-chip-board-overview.md @@ -1,4 +1,4 @@ -# Overview +# Porting Overview ## Porting Process @@ -10,7 +10,7 @@ After the minimum system is ported, you can port the board-level system by: 4. Verifying service functions **Figure 1** Process for board-level driver adaptation -![](figure/process-for-board-level-driver-adaptation.png "process-for-board-level-driver-adaptation") +![process-for-board-level-driver-adaptation](figures/process-for-board-level-driver-adaptation.png) ## Board-Level Directory Specifications diff --git a/en/device-dev/porting/porting-chip-board.md b/en/device-dev/porting/porting-chip-board.md index 0018646d943032fffef255c3d6bc513d0b42c14c..3776faeedf617c422ac7974c728af8f62a34e470 100644 --- a/en/device-dev/porting/porting-chip-board.md +++ b/en/device-dev/porting/porting-chip-board.md @@ -1,6 +1,6 @@ # Board-Level OS Porting -- **[Overview](porting-chip-board-overview.md)** +- **[Porting Overview](porting-chip-board-overview.md)** - **[Board-Level Driver Adaptation](porting-chip-board-driver.md)** diff --git a/en/device-dev/porting/porting-chip-faqs.md b/en/device-dev/porting/porting-chip-faqs.md index 878feb66498ac8a4042c0f02e9da78e0e35716a3..188747865c20ab9ce16bede0a7774c986cb827de 100644 --- a/en/device-dev/porting/porting-chip-faqs.md +++ b/en/device-dev/porting/porting-chip-faqs.md @@ -1,4 +1,4 @@ -# FAQ +# FAQs ## How Do I Mount the Heap Memory to the Kernel? diff --git a/en/device-dev/porting/porting-chip-kernel-adjustment.md b/en/device-dev/porting/porting-chip-kernel-adjustment.md index f1aca7b9503178b5a9d43a57528ed9ea76c8177c..0fe4f81cc54b315f2736e10259c9dbb71ac51afd 100644 --- a/en/device-dev/porting/porting-chip-kernel-adjustment.md +++ b/en/device-dev/porting/porting-chip-kernel-adjustment.md @@ -12,7 +12,7 @@ Basic adaptation consists of the following steps: **Figure 1** Startup process -![](figure/startup-process.png) +![](figures/startup-process.png) In the **startup.S** file, you must ensure that the entry function \(for example, **reset\_vector**\) of the interrupt vector table is stored in the RAM start address specified by the link configuration files. The link configuration files of IAR, Keil, and GCC projects are **xxx.icf**, **xxx.sct**, and **xxx.ld**, respectively. The startup file provided by the vendor does not need to be modified if the **startup.S** file has initialized the system clock and returned to the **main** function. Otherwise, the preceding functions need to be implemented. @@ -34,6 +34,7 @@ The following table shows some typical configuration items: **Table 1** Typical configuration items +

Item

Description

diff --git a/en/device-dev/porting/porting-chip-kernel-overview.md b/en/device-dev/porting/porting-chip-kernel-overview.md index 7c8f1e457caabab74ff5a84e9efcc9d60c61dc13..00c50ec8944875ca6491391b25d12574906f792e 100644 --- a/en/device-dev/porting/porting-chip-kernel-overview.md +++ b/en/device-dev/porting/porting-chip-kernel-overview.md @@ -1,4 +1,4 @@ -# Overview +# Porting Overview ## Porting Scenario @@ -16,8 +16,7 @@ The kernel used by module chips is LiteOS Cortex-M, which consists of four modul **Figure 1** Architecture of the LiteOS Cortex-M kernel - -![](figure/architecture-of-the-liteos-cortex-m-kernel.png) + The directory structure of the kernel is described as follows: diff --git a/en/device-dev/porting/porting-chip-kernel.md b/en/device-dev/porting/porting-chip-kernel.md index 92a8b05ed0a95f0747a16b34afaddb258fa2bbb1..7b2a628f3481ac80a59be513df869d91e9acb298 100644 --- a/en/device-dev/porting/porting-chip-kernel.md +++ b/en/device-dev/porting/porting-chip-kernel.md @@ -1,6 +1,6 @@ # Kernel Porting -- **[Overview](porting-chip-kernel-overview.md)** +- **[Porting Overview](porting-chip-kernel-overview.md)** - **[Basic Kernel Adaptation](porting-chip-kernel-adjustment.md)** diff --git a/en/device-dev/porting/porting-chip-prepare.md b/en/device-dev/porting/porting-chip-prepare.md index 52c6cc9bd81b9ad45a7841e4b1df4e92cb67d4a4..44cb5673ddc7e7f7a2df08defe0c70b0d9ee2277 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](oem_transplant_chip_prepare_knows.md)** +- **[Before You Start](porting-chip-prepare-knows.md)** - **[Building Adaptation Process](porting-chip-prepare-process.md)** diff --git a/en/device-dev/porting/porting-linux-kernel.md b/en/device-dev/porting/porting-linux-kernel.md index 0b620c08d39bfb9f3abf49962823455f451da87f..05b66768aa52ddc24b638cf88b2adbe8747c8b97 100644 --- a/en/device-dev/porting/porting-linux-kernel.md +++ b/en/device-dev/porting/porting-linux-kernel.md @@ -12,7 +12,7 @@ For easy description, we divide the OpenHarmony architecture into two parts: OpenHarmony = Kernel mode layer + User mode layer -![](figure/technical-architecture.png) +![](figures/technical-architecture.png) The kernel mode layer is the OpenHarmony kernel layer \(purple part in the figure\). It consists of the kernel, such as Linux Kernel and LiteOS, and features, such as Hardware Driver Foundation \(HDF\), running in the kernel mode. @@ -35,7 +35,7 @@ Therefore, the OpenHarmony kernel mode layer includes the following: - OpenHarmony basic kernel-mode code - OpenHarmony kernel-mode features, such as HDF -![](figure/openharmony_kernel.png) +![](figures/openharmony_kernel.png) The standard LTS Linux kernel and third-party SoC chip platform code constitute the basis of a third-party Linux kernel. The OpenHarmony kernel mode layer can be composed of either of the following: @@ -84,7 +84,7 @@ The following uses Raspberry Pi 3b \(BCM2837\) as an example to describe how to # Configure the build environment, and use clang provided by the project to build the Raspberry Pi kernel source code. export PATH=$PROJ_ROOT/prebuilts/clang/ohos/linux-x86_64/llvm/bin:$PROJ_ROOT/prebuilts/gcc/linux-x86/arm/gcc-linaro-7.5.0-arm-linux-gnueabi/bin/:$PATH export MAKE_OPTIONS="ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- CC=clang HOSTCC=clang" - export PRODUCT_PATH=vendor/hisilicon/Hi3516DV300 + export PRODUCT_PATH=vendor/hisilicon/hispark_taurus_standard ``` 3. Comment out the flags that cannot be recognized by **clang**. @@ -175,7 +175,7 @@ For details about how to use the logs, see [Hilog\_lite](https://gitee.com/open The configuration \(in **Device Drivers** \> **HDF driver framework support**\) is as follows: - ![](figure/menuconfig.png) + ![](figures/menuconfig.png) ### Building the Image @@ -198,7 +198,7 @@ The HDF test cases are used to verify basic functions of the HDF framework and p **Test Case Build and Test Method** -Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/oem_subsys_toolchain_hdc_guide.md) tool to push the test case execution file to the device and execute the test cases. The procedure is as follows: +Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md) tool to push the test case execution file to the device and execute the test cases. The procedure is as follows: 1. Build the HDF test cases. 2. Use the **hdc\_std** tool to push the test case execution file to the device. @@ -211,14 +211,14 @@ The procedure is as follows: Run the following command: ``` - ./build.sh --product-name Hi3516DV300 --build-target hdf_test + ./build.sh --product-name hispark_taurus_standard --build-target hdf_test ``` Wait until the build is complete. 2. Copy the test files to the target device \(Raspberry Pi in this example\). - Method 1: Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/oem_subsys_toolchain_hdc_guide.md) tool. + Method 1: Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md) tool. 1. Create the **data/test** directory in Raspberry Pi. diff --git a/en/device-dev/porting/porting-smallchip-driver-oom.md b/en/device-dev/porting/porting-smallchip-driver-oom.md index 46ccf47b9d5eb1c4932aca068bf5344c3e5869b1..ea579c6746607029bc6d994f979d54fd18b137c7 100644 --- a/en/device-dev/porting/porting-smallchip-driver-oom.md +++ b/en/device-dev/porting/porting-smallchip-driver-oom.md @@ -157,7 +157,7 @@ The WLAN driver is divided into two parts. One of the parts manages WLAN devices **Figure 1** OpenHarmony WLAN driver architecture -![](figure/hdf_wifi.png) +![](figures/hdf_wifi.png) As shown in [Figure 1](#fig155920160203), the part on the left manages WLAN devices, and the part on the right manages WLAN traffic. The HDF WLAN framework abstracts these two parts. The porting process of the driver can be considered as the implementation of the APIs required by the two parts. These APIs are described as follows: diff --git a/en/device-dev/porting/porting-smallchip-driver-overview.md b/en/device-dev/porting/porting-smallchip-driver-overview.md index 117cd129bfdf88cd855693439c6542aef427212e..3a4fd33171a66dcb44d3266daf8ce41206742330 100644 --- a/en/device-dev/porting/porting-smallchip-driver-overview.md +++ b/en/device-dev/porting/porting-smallchip-driver-overview.md @@ -1,9 +1,9 @@ -# Overview +# Porting Overview Drivers can be classified as platform drivers or device drivers. The platform drivers are generally in the SoC, such as the GPIO, I2C, and SPI drivers. The device drivers are typically outside of the SoC, such as the LCD, TP, and WLAN drivers. **Figure 1** OpenHarmony driver classification -![](figure/openharmony-driver-classification.png "openharmony-driver-classification") +![](figures/openharmony-driver-classification.png "openharmony-driver-classification") The Hardware Driver Foundation \(HDF\) is designed to work across OSs. The HDF driver framework provides strong support for drivers to achieve this goal. During HDF driver development, you are advised to use only the APIs provided by the HDF driver framework. Otherwise, the driver cannot be used across OSs. Before driver development, familiarize yourself with the [HDF](../driver/driver-hdf-overview.md). diff --git a/en/device-dev/porting/porting-smallchip-driver.md b/en/device-dev/porting/porting-smallchip-driver.md index 57442da187da532394cd377020b4566e86727368..04eea1a6abd5ad0f7dcb8a54c96cd156fc8946a1 100644 --- a/en/device-dev/porting/porting-smallchip-driver.md +++ b/en/device-dev/porting/porting-smallchip-driver.md @@ -1,6 +1,6 @@ # Driver Porting -- **[Overview](porting-smallchip-driver-overview.md)** +- **[Porting Overview](porting-smallchip-driver-overview.md)** - **[Platform Driver Porting](porting-smallchip-driver-plat.md)** diff --git a/en/device-dev/porting/porting-smallchip-kernel-a.md b/en/device-dev/porting/porting-smallchip-kernel-a.md index 48204ad8b8e666bf327466f8f841c0a44dba3a32..4762f301ffb784ce9778c870b92ea1d4ed2413f9 100644 --- a/en/device-dev/porting/porting-smallchip-kernel-a.md +++ b/en/device-dev/porting/porting-smallchip-kernel-a.md @@ -27,7 +27,7 @@ The LiteOS Cortex-A initialization process consists of seven steps: The figure below shows the overall initialization process. **Figure 1** Overall initialization process -![](figure/overall-initialization-process.png "overall-initialization-process") +![](figures/overall-initialization-process.png "overall-initialization-process") As can be seen from preceding figure, kernel basic adaptation involves the following parts: @@ -108,7 +108,7 @@ As can be seen from preceding figure, kernel basic adaptation involves the follo - Implementing the **SystemInit** function to initialize services in the user space. Figure 2 shows a typical initialization scenario. **Figure 2** Service startup process - ![](figure/service-startup-process.png "service-startup-process") + ![](figures/service-startup-process.png "service-startup-process") - Implementing the **main** function for basic kernel initialization and initialization of services in the board kernel space. [Figure 3](#fig32611728133919) shows the initialization process, where the kernel startup framework takes the lead in the initialization process. The light blue part in the figure indicates the phase in which external modules can be registered and started in the startup framework. @@ -116,7 +116,7 @@ As can be seen from preceding figure, kernel basic adaptation involves the follo >Modules at the same layer cannot depend on each other. **Figure 3** Kernel startup framework - ![](figure/kernel-startup-framework.jpg "kernel-startup-framework") + ![](figures/kernel-startup-framework.jpg "kernel-startup-framework") **Table 2** Startup framework layers diff --git a/en/device-dev/porting/porting-smallchip-kernel-linux.md b/en/device-dev/porting/porting-smallchip-kernel-linux.md index a3a9c1dab04e7bd8052b21a2576bfaaf71572842..354b0430f39fb265e07230b71d749f8aa09ef90c 100644 --- a/en/device-dev/porting/porting-smallchip-kernel-linux.md +++ b/en/device-dev/porting/porting-smallchip-kernel-linux.md @@ -54,7 +54,7 @@ You can use the Bootloader provided by the chipset vendor or open-source U-Boot Debug the **init** process, start shell, and run a simple program in the user space to check whether the kernel porting is successful. Below is the OS image structure of the OpenHarmony [small system](../quick-start/quickstart-lite-overview.md) and the Linux user-space program startup process. **Figure 1** OS image structure and user-space program startup process based on the Linux kernel -![](figure/os-image-structure-and-user-space-program-startup-process-based-on-the-linux-kernel.png "os-image-structure-and-user-space-program-startup-process-based-on-the-linux-kernel") +![](figures/os-image-structure-and-user-space-program-startup-process-based-on-the-linux-kernel.png "os-image-structure-and-user-space-program-startup-process-based-on-the-linux-kernel") Based on the preceding process, the recommended verification procedure is as follows: @@ -91,12 +91,12 @@ Based on the preceding process, the recommended verification procedure is as fol If the init startup log contains the version number, the init program is started properly: **Figure 2** Log indicating that the init process is started properly - ![](figure/log-indicating-that-the-init-process-is-started-properly.png "log-indicating-that-the-init-process-is-started-properly") + ![](figures/log-indicating-that-the-init-process-is-started-properly.png "log-indicating-that-the-init-process-is-started-properly") After entering the shell, run the **ls** command. The following figure shows the information printed over the serial port. **Figure 3** Information printed after the ls command is executed in the shell - ![](figure/information-printed-after-the-ls-command-is-executed-in-the-shell.png "information-printed-after-the-ls-command-is-executed-in-the-shell") + ![](figures/information-printed-after-the-ls-command-is-executed-in-the-shell.png "information-printed-after-the-ls-command-is-executed-in-the-shell") 3. Configure the NFS. diff --git a/en/device-dev/porting/porting-thirdparty-cmake.md b/en/device-dev/porting/porting-thirdparty-cmake.md index d775d72204723789a72975ecede326087414c72b..7956e702ae20df460ab4026420557d8a625276da 100755 --- a/en/device-dev/porting/porting-thirdparty-cmake.md +++ b/en/device-dev/porting/porting-thirdparty-cmake.md @@ -218,12 +218,12 @@ The following steps show how to configure and modify the toolchains for cross-co 1. Set up the OpenHarmony environment. - Using Hi3518EV300 as an example, compile the OpenHarmony image and burn it to the development board. For details, see [Developing the First Example Program Running on Hi3518](../quick-start/quickstart-lite-steps-hi3516-running.md). + Using Hi3516D V300 as an example, compile the OpenHarmony image and burn it to the development board. For details, see [Developing the First Example Program Running on Hi3518](../quick-start/quickstart-lite-steps-hi3516-running.md). The following screen is displayed after a successful login to the OS. **Figure 1** Successful startup of OpenHarmony - ![](figure/successful-startup-of-openharmony.png "successful-startup-of-openharmony") + ![](figures/successful-startup-of-openharmony.png "successful-startup-of-openharmony") 2. Mount the **nfs** directory and put the executable file **cctest** into the **test** directory \(listed in [Table 2](#table1452412391911)\) to the **nfs** directory. 3. Perform the test cases. diff --git a/en/device-dev/porting/standard-system-porting-guide.md b/en/device-dev/porting/standard-system-porting-guide.md index c5a8cf6d902f884d3d284ee6055c626fbe8234b1..bb56dacfd1b8c575d6c5eab01b1f02c23440ee03 100644 --- a/en/device-dev/porting/standard-system-porting-guide.md +++ b/en/device-dev/porting/standard-system-porting-guide.md @@ -6,51 +6,60 @@ This document describes the general process for porting a development board, rat This document uses the process of porting a development board named **MyProduct** as an example. This development board is provided by **MyProductVendor** and uses the SoC **MySOC** produced by **MySoCVendor**. -### Defining an SoC - -Create a JSON file named after the SoC name in the **//productdefine/common/device** directory and specify the CPU architecture. +### Defining a Product -For example, to port **MySOC**, which uses a 32-bit ARM kernel, configure the file as follows: +Create a config.json file in the directory with the name "//vendor/MyProductVendor/{product_name}. This file is used to describe the SoC used by the product and the required subsystems. configure the file as follows: -//productdefine/common/device/MySOC.json +//vendor/MyProductVendor/MyProduct/config.json + ``` { - "target_os": "ohos", - "target_cpu": "arm" + "product_name": "MyProduct", + "version": "3.0", + "type": "standard", + "target_cpu": "arm", + "ohos_version": "OpenHarmony 1.0", + "device_company": "MyProductVendor", + "board": "MySOC", + "enable_ramdisk": true, + "subsystems": [ + { + "subsystem": "ace", + "components": [ + { "component": "ace_engine_lite", "features":[""] } + ] + }， + … + ] } + + ``` -Currently, **target\_cpu** can be set to **arm** only. In the future, you can set the value depending on the CPU architecture, such as **arm64**, **riscv**, or **x86**. +The main configurations are as follows: -### Defining a Product +product_name：The product name.Required -Create a JSON file named after the product name in the **//productdefine/common/products** directory. This file is used to describe the SoC used by the product and the required subsystems. Configure the file as follows: +version：version.Required -//productdefine/common/products/MyProduct.json +type：Configured at the system level, select from (mini, small, standard).Required -``` -{ - "product_name": "MyProduct", - "product_company" : "MyProductVendor", - "product_device": "MySOC", - "version": "2.0", - "type": "standard", - "parts":{ - "ace:ace_engine_standard":{}, - "ace:napi":{}, - ... - "xts:phone_tests":{} - } -} +target_cpu ：The CPU type of the device (depending on the actual situation, the target_cpu here may also be arm64, riscv, x86, etc..).Required -``` +ohos_version：Operating system version.Optional -The main configurations are as follows: +device_company：device manufacturer name.Required + +board：Board name.Required + +enable_ramdisk：Whether to start ramdisk.Required + +kernel_type and kernel_version: kernel_type with kernel_version is fixed in the standard and does not need to be written.Optional + +subsystems:The subsystem that the system needs to be enabled. Subsystems can simply understand a piece of function that is built independently. Required -1. **product\_device**: SoC used by the product. -2. **type**: system level. In this example, set it to **standard**. -3. **parts**: subsystem to enable. A subsystem can be treated as an independently built functional block. +product_company：Not reflected in the configuration, but in the directory name, the next directory of the vendor is product_company, build.gn script can still be accessed. You can find available subsystems in **//build/subsystem\_config.json**. You can also customize subsystems. @@ -83,7 +92,7 @@ Add the following subsystem configuration to the **//build/subsystem\_config.js }, ``` -Then, open the configuration file **//productdefine/common/products/MyProduct.json**, which is used to define the product, and add the new subsystem to the product. +Then, open the configuration file **//vendor/MyProductVendor/MyProduct/config.json**, which is used to define the product, and add the new subsystem to the product. ### 2. Building the Kernel @@ -277,7 +286,7 @@ For details about driver development, see [TOUCHSCREEN](../driver/driver-periph The WLAN driver is divided into two parts. One of the parts manages WLAN devices, and the other part manages WLAN traffic. HDF WLAN provides abstraction for the two parts. Currently, only the WLAN with the SDIO interface is supported. **Figure 1** WLAN chip -![](figure/wlan-chip.png "wlan-chip") +![](figures/wlan-chip.png "wlan-chip") To support a chip, implement a **ChipDriver** for it. The major task is to implement the following interfaces provided by **HDF\_WLAN\_CORE** and **NetDevice**. diff --git a/en/device-dev/quick-start/Readme-EN.md b/en/device-dev/quick-start/Readme-EN.md index b49cc0253248c313bc339b1e86ee6e1a8b28dba7..1fb06af53be58306f25c68033f8db5dbd811e53f 100644 --- a/en/device-dev/quick-start/Readme-EN.md +++ b/en/device-dev/quick-start/Readme-EN.md @@ -2,7 +2,7 @@ - Getting Started with Mini and Small Systems (IDE Mode, Recommended) - [Mini and Small System Overview](quickstart-ide-lite-overview.md) - Environment Preparation - - [Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-lite-env-setup-win-ubuntu.md) + - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-lite-env-setup-win-ubuntu.md) - [Obtaining Source Code](quickstart-ide-lite-sourcecode-acquire.md) - [Creating a Source Code Project](quickstart-ide-lite-create-project.md) - Running a Hello World Program @@ -19,8 +19,9 @@ - [Burning](quickstart-ide-lite-steps-hi3516-burn.md) - [Running](quickstart-ide-lite-steps-hi3516-running.md) - Appendix - - [Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md) - - [Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md) + - Introduction to Development Boards + - [Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md) + - [Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md) - Getting Started with Mini and Small Systems (Installation Package Mode) - [Mini and Small System Overview](quickstart-lite-overview.md) - [Environment Preparation](quickstart-lite-env-setup.md) @@ -51,7 +52,7 @@ - Getting Started with Standard System (IDE Mode, Recommended) - [Standard System Overview](quickstart-ide-standard-overview.md) - Environment Preparation - - [Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-standard-env-setup-win-ubuntu.md) + - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md) - [Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md) - [Creating a Source Code Project](quickstart-ide-standard-create-project.md) - Running a Hello World Program @@ -66,8 +67,9 @@ - [Burning](quickstart-ide-standard-running-rk3568-burning.md) - [Running](quickstart-ide-standard-running-rk3568-running.md) - Appendix - - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md) - - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md) + - Introduction to Development Boards + - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md) + - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md) - Getting Started with Standard System (Installation Package Mode) - [Standard System Overview](quickstart-standard-overview.md) - [Setting Up Environments for Standard System](quickstart-standard-env-setup.md) diff --git a/en/device-dev/quick-start/quickstart-docker-lite.md b/en/device-dev/quick-start/quickstart-docker-lite.md index b0dedbd30e13ea886381add1820506fdf9e0d2d3..666b1510ff7b2346251cea45601e990ff5100d3e 100644 --- a/en/device-dev/quick-start/quickstart-docker-lite.md +++ b/en/device-dev/quick-start/quickstart-docker-lite.md @@ -4,7 +4,7 @@ - **[Mini and Small System Overview](quickstart-lite-overview.md)** -- **[Environment Preparation](quickstart-lite-env-setup.md)** +- **[Setting Up Environments for the Mini and Small Systems](quickstart-lite-env-setup.md)** - **[Running a Hello World Program](quickstart-lite-steps.md)** diff --git a/en/device-dev/quick-start/quickstart-ide-lite-create-project.md b/en/device-dev/quick-start/quickstart-ide-lite-create-project.md index 9227e669b4d34ca5453d2e392a3bc64604e055f5..37002b081cb5f699498cd8114ad89ee3a32ecece 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-create-project.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-create-project.md @@ -10,7 +10,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st 2. Select the source code directory to be imported and click **Import**. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** + > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail. ![en-us_image_0000001271477045](figures/en-us_image_0000001271477045.png) diff --git a/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md b/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md index fbed65d9a8e1c2f7c55c30c440d4a84a35e93ef1..f274a5f0ee452334be8fa93eac3844c62c79e73c 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md @@ -1,10 +1,10 @@ # Setting Up the Windows+Ubuntu Hybrid Development Environment -In embedded development, Windows-based tools, such as Visual Studio Code, are widely used in code editing. Yet, as the source code of most development boards, such as Hi3861 and Hi3516, cannot be built in Windows, these development boards require the Ubuntu build environment. +In embedded development, Windows-based tools, such as Visual Studio Code, are widely used in code editing. Yet, as the source code of most development boards, such as Hi3861 and Hi3516, cannot be built in Windows, these development boards require the Ubuntu development environment. -In the Windows+Ubuntu hybrid build environment, you can enjoy the benefits of both DevEco Device Tool for Windows and DevEco Device Tool for Ubuntu (where Visual Studio Code is optional). +In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits of both DevEco Device Tool for Windows and DevEco Device Tool for Ubuntu (where Visual Studio Code is optional). ## System Requirements @@ -18,9 +18,7 @@ In the Windows+Ubuntu hybrid build environment, you can enjoy the benefits of bo - DevEco Device Tool: 3.0 Release -## Setting Up the Ubuntu Build Environment - -The setup procedure varies, depending on whether you need a GUI. If you need a GUI, you need to install Visual Studio Code. In this case, follow the instructions in [Setting Up the Ubuntu Development Environment](https://device.harmonyos.com/en/docs/documentation/guide/ide-install-ubuntu-0000001072959308). If you do not need a GUI, perform the steps below: +## Setting Up the Ubuntu Development Environment 1. Make sure the Ubuntu shell environment is **bash**. 1. Run the following command and check whether the command output is **bash**. If the command output is not **bash**, go to step 2. @@ -116,7 +114,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ![en-us_image_0000001225760456](figures/en-us_image_0000001225760456.png) -## Configuring Windows to Remotely Access the Ubuntu Build Environment +## Configuring Windows to Remotely Access the Ubuntu Development Environment ### Installing the SSH Service and Obtaining the IP Address for Remote Access diff --git a/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md b/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md index a3722cf56712286e6bd5776e74b88470306f3261..e7461bde3df8da9ca14f7c3cbac5c36d1a37b6c5 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-env-setup.md @@ -2,6 +2,7 @@ -- **[Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-lite-env-setup-win-ubuntu.md)** +- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-lite-env-setup-win-ubuntu.md)** - **[Obtaining Source Code](quickstart-ide-lite-sourcecode-acquire.md)** + diff --git a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3516.md b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3516.md index 4c85bdc37bd008627762569ba55a7bf7275ecaf8..68ec899169449ae2a1efced40511e095840d0de9 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3516.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3516.md @@ -5,16 +5,16 @@ Hi3516D V300 is a next-generation system on chip (SoC) designed for the industry-dedicated smart HD IP camera. It introduces a next-generation image signal processor (ISP), the H.265 video compression encoder, and a high-performance NNIE engine, leading the industry in terms of low bit rate, high image quality, intelligent processing and analysis, and low power consumption. - **Figure 1** Hi3516 front view - +**Figure 1** Hi3516 front view + ![en-us_image_0000001271234717](figures/en-us_image_0000001271234717.png) ## Development Board Specifications - **Table 1** Hi3516 specifications +**Table 1** Hi3516 specifications -| Item| Description| +| Item| Description| | -------- | -------- | -| Processor and internal memory| - Hi3516D V300 chip
- DDR3 1GB
- eMMC 4.5, 8 GB capacity| -| External components| - Ethernet port
- Audio and video
  - 1 voice input
  - 1 mono channel (AC_L) output, connected to a 3 W power amplifier (LM4871)
  - MicroHDMI (1-channel HDMI 1.4)
- Camera
  - Sensor IMX335
  - M12 lens, 4 mm focal length, and 1.8 aperture
- Display
  - LCD connector (2.35-inch)
  - LCD connector (5.5-inch)
- External components and ports
  - Memory card port
  - JTAG/I2S port
  - ADC port
  - Steering gear port
  - Grove connector
  - USB 2.0 (Type-C)
  - Three function keys, two user-defined keys, and one upgrade key
  - LED indicator, green or red| +| Processor and internal memory| - Hi3516D V300 chip
- DDR3 1GB
- eMMC 4.5, 8 GB capacity| +| External components| - Ethernet port
- Audio and video
  - 1 voice input
  - 1 mono channel (AC_L) output, connected to a 3 W power amplifier (LM4871)
  - MicroHDMI (1-channel HDMI 1.4)
- Camera
  - Sensor IMX335
  - M12 lens, 4 mm focal length, and 1.8 aperture
- Display
  - LCD connector (2.35-inch)
  - LCD connector (5.5-inch)
- External components and ports
  - Memory card port
  - JTAG/I2S port
  - ADC port
  - Steering gear port
  - Grove connector
  - USB 2.0 (Type-C)
  - Three function keys, two user-defined keys, and one upgrade key
  - LED indicator, green or red| diff --git a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md index fa6235602d1b4e080b703ff85a6651cc3bd19105..b32ea6e794af6c80dcd9059d70cbe8816906f1a7 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md @@ -5,14 +5,14 @@ Hi3861 is a 2 x 5 cm development board. It is a 2.4 GHz WLAN SoC chip that highly integrates the IEEE 802.11b/g/n baseband and radio frequency (RF) circuit. It supports OpenHarmony and provides an open and easy-to-use development and debugging environment. - **Figure 1** Hi3861 development board +**Figure 1** Hi3861 development board ![en-us_image_0000001226634692](figures/en-us_image_0000001226634692.png) The Hi3861 development board can also be connected to the Hi3861 mother board to expand its peripheral capabilities. The following figure shows the Hi3861 mother board. - **Figure 2** Hi3861 mother board - +**Figure 2** Hi3861 mother board + ![en-us_image_0000001226794660](figures/en-us_image_0000001226794660.png) - The RF circuit includes modules such as the power amplifier (PA), low noise amplifier (LNA), RF Balun, antenna switch, and power management. It supports a standard bandwidth of 20 MHz and a narrow bandwidth of 5 MHz or 10 MHz, and provides a maximum rate of 72.2 Mbit/s at the physical layer. @@ -35,34 +35,34 @@ The resources of the Hi3861 development board are limited. The entire board has ## Development Board Specifications - **Table 1** Hi3861 specifications +**Table 1** Hi3861 specifications -| Item| Description| +| Item| Description| | -------- | -------- | -| General specifications| - 1 x 1 2.4 GHz frequency band (ch1–ch14)
- PHY supports IEEE 802.11b/g/n.
- MAC supports IEEE802.11d/e/h/i/k/v/w.
- Built-in PA and LNA; integrated TX/RX switch and Balun
- Support for STA and AP modes. When functioning as an AP, it supports a maximum of 6 STAs.
- Support for WFA WPA/WPA2 personal and WPS2.0.
- 2/3/4-line PTA solution that coexists with BT/BLE chips.
- Input voltage range: 2.3 V to 3.6 V
- I/O power voltage: 1.8 V or 3.3 V.
- RF self-calibration
- Low power consumption:
  - Ultra Deep Sleep mode: 5 μA@3.3 V
  - DTIM1: 1.5 mA \@3.3V
  - DTIM3: 0.8 mA \@3.3V| -| PHY features| - Supports all data rates of the IEEE802.11b/g/n single antenna.
- Supported maximum rate: 72.2 Mbps\@HT20 MCS7
- 20 MHz standard bandwidth and 5 MHz/10 MHz narrow bandwidth.
-  STBC.
- Short-GI.| -| MAC features| - A-MPDU and A-MSDU.
- Blk-ACK.
- QoS to meet the quality requirements of different services.| -| CPU subsystem| -  High-performance 32-bit microprocessor with a maximum working frequency of 160 MHz.
- Embedded SRAM of 352 KB; ROM of 288 KB
- Embedded 2 MB flash memory| -| Peripheral ports| - One SDIO interface, two SPI interfaces, two I2C interfaces, three UART interfaces, 15 GPIO interfaces, seven ADC inputs, six PWM interfaces, and one I2S interface (Note: These interfaces are all multiplexed.)
- Frequency of the external main crystal: 40 MHz or 24 MHz| -| Others| - Package: QFN-32, 5 mm x 5 mm
- Working temperature: -40°C to +85°C| +| General specifications| - 1 x 1 2.4 GHz frequency band (ch1–ch14)
- PHY supports IEEE 802.11b/g/n.
- MAC supports IEEE802.11d/e/h/i/k/v/w.
- Built-in PA and LNA; integrated TX/RX switch and Balun
- Support for STA and AP modes. When functioning as an AP, it supports a maximum of 6 STAs.
- Support for WFA WPA/WPA2 personal and WPS2.0.
- 2/3/4-line PTA solution that coexists with BT/BLE chips.
- Input voltage range: 2.3 V to 3.6 V
- I/O power voltage: 1.8 V or 3.3 V.
- RF self-calibration
- Low power consumption:
  - Ultra Deep Sleep mode: 5 μA@3.3 V
  - DTIM1: 1.5 mA \@3.3V
  - DTIM3: 0.8 mA \@3.3V| +| PHY features| - Supports all data rates of the IEEE802.11b/g/n single antenna.
- Supported maximum rate: 72.2 Mbps\@HT20 MCS7
- 20 MHz standard bandwidth and 5 MHz/10 MHz narrow bandwidth.
-  STBC.
- Short-GI.| +| MAC features| - A-MPDU and A-MSDU.
- Blk-ACK.
- QoS to meet the quality requirements of different services.| +| CPU subsystem| -  High-performance 32-bit microprocessor with a maximum working frequency of 160 MHz.
- Embedded SRAM of 352 KB; ROM of 288 KB
- Embedded 2 MB flash memory| +| Peripheral ports| - One SDIO interface, two SPI interfaces, two I2C interfaces, three UART interfaces, 15 GPIO interfaces, seven ADC inputs, six PWM interfaces, and one I2S interface (Note: These interfaces are all multiplexed.)
- Frequency of the external main crystal: 40 MHz or 24 MHz| +| Others| - Package: QFN-32, 5 mm x 5 mm
- Working temperature: -40°C to +85°C| ## OpenHarmony Key Features OpenHarmony provides a wide array of available capabilities based on the Hi3861 platform. The following table describes the available key components. - **Table 2** Key components of OpenHarmony +**Table 2** Key components of OpenHarmony -| Component| Capability| +| Component| Capability| | -------- | -------- | -| WLAN| Provides the WLAN service capability. For example, connecting to or disconnecting from a station or hotspot, and querying the status of a station or hotspot.| -| IoT controller| Provides the capability of operating peripherals, including the I2C, I2S, ADC, UART, SPI, SDIO, GPIO, PWM and flash memory.| -| DSoftBus| Provides the capabilities of device discovery and data transmission in the distributed network.| -| hichainsdk| Provides the capability of securely transferring data between devices when they are interconnected.| -| huks| Provides capabilities of key management, encryption, and decryption.| -| System service management| Provides a unified OpenHarmony service development framework based on the service-oriented architecture.| -| Boot| Provides the entry identifier for starting a system service. When the system service management is started, the function identified by bootstrap is called to start a system service.| -| System attribute| Provides capabilities of obtaining and setting system attributes.| -| Base library| Provides the common basic library capability, including file operations and KV storage management.| -| DFX | Provides the DFX capability, such as logging and printing.| -| XTS | Provides a set of OpenHarmony certification test suites.| +| WLAN| Provides the WLAN service capability. For example, connecting to or disconnecting from a station or hotspot, and querying the status of a station or hotspot.| +| IoT controller| Provides the capability of operating peripherals, including the I2C, I2S, ADC, UART, SPI, SDIO, GPIO, PWM and flash memory.| +| DSoftBus| Provides the capabilities of device discovery and data transmission in the distributed network.| +| hichainsdk| Provides the capability of securely transferring data between devices when they are interconnected.| +| huks| Provides capabilities of key management, encryption, and decryption.| +| System service management| Provides a unified OpenHarmony service development framework based on the service-oriented architecture.| +| Boot| Provides the entry identifier for starting a system service. When the system service management is started, the function identified by bootstrap is called to start a system service.| +| System attribute| Provides capabilities of obtaining and setting system attributes.| +| Base library| Provides the common basic library capability, including file operations and KV storage management.| +| DFX | Provides the DFX capability, such as logging and printing.| +| XTS | Provides a set of OpenHarmony certification test suites.| diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md index 2c23f4eec8a31da21b836de69b535b12ca8b9875..36a19432f9e567609a7c7a3b92d006d71a91ef2b 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md @@ -6,15 +6,15 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+ > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md index 3ebd031b51f4d1b0273c1ccb45990b0293c43436..72a07f63239b0a79da9958a8b1dc77fe964e51ab 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md @@ -6,7 +6,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3861 V100 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3861.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -14,7 +14,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-hi3516.md b/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-hi3516.md index 250a2a496ed1f7e3aa84a564a3498fadedc5ad01..e27bfe3de9d731e002b47a69440684783b572069 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-hi3516.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-hi3516.md @@ -5,16 +5,16 @@ Hi3516D V300 is a next-generation system on chip (SoC) designed for industry-dedicated smart HD IP cameras. It introduces a next-generation image signal processor (ISP), the H.265 video compression encoder, and a high-performance NNIE engine, leading the industry in terms of low bit rate, high image quality, intelligent processing and analysis, and low power consumption. - **Figure 1** Hi3516 front view +**Figure 1** Hi3516 front view ![en-us_image_0000001227082182](figures/en-us_image_0000001227082182.png) ## Development Board Specifications - **Table 1** Hi3516 specifications +**Table 1** Hi3516 specifications -| Item| Description| +| Item| Description| | -------- | -------- | -| Processor and internal memory| - Hi3516D V300 chip
- DDR3 1GB
- eMMC 4.5, 8 GB capacity| -| External components| - Ethernet port
- Audio and video
  - 1 voice input
  - 1 mono channel (AC_L) output, connected to a 3 W power amplifier (LM4871)
  - MicroHDMI (1-channel HDMI 1.4)
- Camera
  - Sensor IMX335
  - M12 lens, 4 mm focal length, and 1.8 aperture
- Display
  - LCD connector (2.35-inch)
  - LCD connector (5.5-inch)
- External components and ports
  - Memory card port
  - JTAG/I2S port
  - ADC port
  - Steering gear port
  - Grove connector
  - USB 2.0 (Type-C)
  - Three function keys, two user-defined keys, and one upgrade key
  - LED indicator, green or red| +| Processor and internal memory| - Hi3516D V300 chip
- DDR3 1GB
- eMMC 4.5, 8 GB capacity| +| External components| - Ethernet port
- Audio and video
  - 1 voice input
  - 1 mono channel (AC_L) output, connected to a 3 W power amplifier (LM4871)
  - MicroHDMI (1-channel HDMI 1.4)
- Camera
  - Sensor IMX335
  - M12 lens, 4 mm focal length, and 1.8 aperture
- Display
  - LCD connector (2.35-inch)
  - LCD connector (5.5-inch)
- External components and ports
  - Memory card port
  - JTAG/I2S port
  - ADC port
  - Steering gear port
  - Grove connector
  - USB 2.0 (Type-C)
  - Three function keys, two user-defined keys, and one upgrade key
  - LED indicator, green or red| diff --git a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-rk3568.md b/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-rk3568.md index 6f74a5fa510bcea8b73cfff9cb70e29f50d6bf8f..e076fca68d808468d8eef98ff1bd46a89094f45e 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-rk3568.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-board-introduction-rk3568.md @@ -5,7 +5,7 @@ Bolstered by the Rockchip RK3568 chip, the RK3568 development board integrates a dual-core GPU and high-efficiency NPU. Its quad-core 64-bit Cortex-A55 processor uses the advanced 22 nm manufacturing process and is clocked at up to 2.0 GHz. The development board is packed with Bluetooth, Wi-Fi, audio, video, and camera features, with a wide range of expansion ports as well as video input and output ports. It comes with dual GE auto-sensing RJ45 ports, so it can be used in multi-connectivity products, such as NVRs and industrial gateways. - **Figure 1** Front view of the RK3568 development board +**Figure 1** Front view of the RK3568 development board ![en-us_image_0000001271442261](figures/en-us_image_0000001271442261.png) diff --git a/en/device-dev/quick-start/quickstart-ide-standard-create-project.md b/en/device-dev/quick-start/quickstart-ide-standard-create-project.md index 5e1e39d880cc945e06b35db0607bc8752838d4d1..3ac2873105b2f43ad674ea99d4b698a5f5940451 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-create-project.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-create-project.md @@ -10,7 +10,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st 2. Select the source code directory to be imported and click **Import**. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** + > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail. ![en-us_image_0000001271562277](figures/en-us_image_0000001271562277.png) @@ -25,7 +25,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st 5. On the **Import Project** page, select a product, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. The following figure uses **Hi3516DV300** as an example. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** + > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> - Set **Product** to **Hi3516DV300** for the Hi3516D V300 development board. > > - Set **Product** to **rk3568** for the RK3568 development board. diff --git a/en/device-dev/quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md b/en/device-dev/quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md index af96bb9caf70d0b72becd22ac8164ec08ba03d0b..0618faf0c02e4e5a3c72edeec4d204a6083026a6 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md @@ -1,10 +1,10 @@ # Setting Up the Windows+Ubuntu Hybrid Development Environment -In embedded development, Windows-based tools, such as Visual Studio Code, are widely used in code editing. Yet, as the source code of most development boards, such as Hi3861 and Hi3516, cannot be built in Windows, these development boards require the Ubuntu build environment. +In embedded development, Windows-based tools, such as Visual Studio Code, are widely used in code editing. Yet, as the source code of most development boards, such as Hi3861 and Hi3516, cannot be built in Windows, these development boards require the Ubuntu development environment. -In the Windows+Ubuntu hybrid build environment, you can enjoy the benefits of both DevEco Device Tool for Windows and DevEco Device Tool for Ubuntu (where Visual Studio Code is optional). +In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits of both DevEco Device Tool for Windows and DevEco Device Tool for Ubuntu (where Visual Studio Code is optional). ## System Requirements @@ -18,9 +18,7 @@ In the Windows+Ubuntu hybrid build environment, you can enjoy the benefits of bo - DevEco Device Tool: 3.0 Release -## Setting Up the Ubuntu Build Environment - -The setup procedure varies, depending on whether you need a GUI. If you need a GUI, you need to install Visual Studio Code. In this case, follow the instructions in [Setting Up the Ubuntu Development Environment](https://device.harmonyos.com/en/docs/documentation/guide/ide-install-ubuntu-0000001072959308). If you do not need a GUI, perform the steps below: +## Setting Up the Ubuntu Development Environment 1. Make sure the Ubuntu shell environment is **bash**. @@ -116,7 +114,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ![en-us_image_0000001225760456](figures/en-us_image_0000001225760456.png) -## Configuring Windows to Remotely Access the Ubuntu Build Environment +## Configuring Windows to Remotely Access the Ubuntu Development Environment ### Installing the SSH Service and Obtaining the IP Address for Remote Access diff --git a/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md b/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md index cb161ced75854ad67c97d548d0beb24bae637bfb..8faf2853a5d319958d0ebb4eeb6ebf1268cb0be0 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-env-setup.md @@ -2,6 +2,6 @@ -- **[Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)** +- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)** - **[Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md)** diff --git a/en/device-dev/quick-start/quickstart-ide-standard-overview.md b/en/device-dev/quick-start/quickstart-ide-standard-overview.md index 28485c75534254c9d286168ff94eadf3971ac0a4..c6a87ed86cf78b9c3f5bffadd84b838193f6f3f1 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-overview.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-overview.md @@ -12,7 +12,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool. OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode. -This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Standard System (Installation Package Mode)](../quick-start/quickstart-standard-overview.md). +This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Standard System (Installation Package Mode)](../quick-start/quickstart-standard-package-directory.md). ## Development Environment @@ -28,7 +28,7 @@ This document describes how to develop OpenHarmony in the Windows+Ubuntu environ ## Development Boards -In this document, two development board models are used as examples: Hi3516D V300 and RK3568. For details about these development boards, see [Appendix](../quick-start/quickstart-ide-standard-board-introduction-hi3516.md). You can purchase the development board as required. +In this document, two development board models are used as examples: Hi3516D V300 and RK3568. For details about these development boards, see [Appendix](../quick-start/quickstart-standard-board-introduction.md). You can purchase the development board as required. ## Development Process diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md index f618b545c42ac566bb5d5ae9a51c7c7337ee028a..dad8d48305a2b4451e397e06f13aa5976446ca96 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md @@ -6,7 +6,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -14,7 +14,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md index 652e16454a7fd5eeb31b5cb9e577b27f78eb112b..cec86501be9781ff64a262e838e512e3afc4040d 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md @@ -19,9 +19,9 @@ applications/sample/hello ├── bundle.json build └── subsystem_config.json -productdefine/common -└── products - └── Hi3516DV300.json +vendor/hisilicon +└── Hi3516DV300 + └── config.json ``` @@ -151,7 +151,7 @@ Perform the steps below in the source code directory: 4. Modify the product configuration file. - In the productdefine\common\products\Hi3516DV300.json file, add the hello part after the existing part. + In the vendor\hisilicon\Hi3516DV300\config.json file, add the hello part after the existing part. ``` diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-running.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-running.md index a0e31a6a05ca740c4ad8c23e5c7ca3c60557076f..0031532533dbe6bcd2994a6f161632732459ab49 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-running.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-running.md @@ -5,7 +5,7 @@ After the burning is complete, perform the following steps to start the system: -> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** +> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> This operation procedure is required only if this is the first time you burn an image for the standard system. 1. In DevEco Device Tool, click **Monitor** to open the serial port tool. @@ -17,12 +17,12 @@ After the burning is complete, perform the following steps to start the system: ![en-us_image_0000001271202289](figures/en-us_image_0000001271202289.gif) 3. Run the following commands to set system boot parameters: - + ``` setenv bootargs 'mem=640M console=ttyAMA0,115200 mmz=anonymous,0,0xA8000000,384M clk_ignore_unused rootdelay=10 hardware=Hi3516DV300 init=/init root=/dev/ram0 rw blkdevparts=mmcblk0:1M(boot),15M(kernel),20M(updater),2M(misc),3307M(system),256M(vendor),-(userdata)'; ``` - + ``` setenv bootcmd 'mmc read 0x0 0x82000000 0x800 0x4800; bootm 0x82000000' ``` @@ -30,7 +30,7 @@ After the burning is complete, perform the following steps to start the system: ![en-us_image_0000001271562269](figures/en-us_image_0000001271562269.png) 4. Save the parameter settings. - + ``` save ``` @@ -38,7 +38,7 @@ After the burning is complete, perform the following steps to start the system: ![en-us_image_0000001226762210](figures/en-us_image_0000001226762210.png) 5. Restart the development board to start the system. - + ``` reset ``` diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md index 57f29832e59d419fb000706cff30b7b7e9941208..8c342589b7bf22a9e519be85b816110d946cf109 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md @@ -8,7 +8,7 @@ 2. Connect the computer to the target development board through the USB port. -3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -16,7 +16,7 @@ ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings. diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md index 527fee8b3cb06cb90f6eca444cac2150d9b0fbb9..6025ddf56951d33a8b0205f2368255273430f753 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md @@ -19,9 +19,9 @@ applications/sample/hello ├── bundle.json build └── subsystem_config.json -productdefine/common -└── products - └── rk3568.json +vendor/hihope +└── rk3568 + └── config.json ``` @@ -150,7 +150,7 @@ Perform the steps below in the source code directory: 4. Modify the product configuration file. - In the productdefine\common\products\rk3568.json file, add the hello part after the existing part. + In the vendor\hihope\rk3568\config.json file, add the hello part after the existing part. ``` "usb:usb_manager_native":{}, diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-running.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-running.md index cf86116a18cf1c428dd4ad0bd8a8f29bd12f260a..e21d612fa72e3e02527d4235bc70400d5a3a1ba5 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-running.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-running.md @@ -5,7 +5,7 @@ After the image is burnt and the development board is restarted, the system automatically starts. If the following page is displayed on the screen of the development board, the system is running properly. - **Figure 1** System startup effect +**Figure 1** System startup effect ![en-us_image_0000001226762222](figures/en-us_image_0000001226762222.jpg) diff --git a/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md b/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md index 997e0ee227d706351e8b4c5c42d74e3858d86074..c84614b09578234a33cbec7223e1f88e93abbb77 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md @@ -19,13 +19,13 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ``` Run the following command to install the tools: - + ``` sudo apt-get install git git-lfs ``` 4. Configure user information. - + ``` git config --global user.name "yourname" git config --global user.email "your-email-address" @@ -33,7 +33,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ``` 5. Run the following commands to install the **repo** tool: - + ``` curl https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 -o /usr/local/bin/repo # If you do not have the access permission to this directory, download the tool to any other accessible directory and configure the directory to the environment variable. chmod a+x /usr/local/bin/repo @@ -43,7 +43,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ## Obtaining Source Code -> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** +> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> Download the master code if you want to get quick access to the latest features for your development. Download the release code, which is more stable, if you want to develop commercial functionalities. - **Obtaining OpenHarmony master code** @@ -58,7 +58,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony Method 2: Use the **repo** tool to download the source code over HTTPS. - + ``` repo init -u https://gitee.com/openharmony/manifest.git -b master --no-repo-verify repo sync -c @@ -72,8 +72,8 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ## Running prebuilts - Go to the root directory of the source code and run the following script to install the compiler and binary tool: - +Go to the root directory of the source code and run the following script to install the compiler and binary tool: + ``` bash build/prebuilts_download.sh ``` diff --git a/en/device-dev/quick-start/quickstart-lite-env-setup.md b/en/device-dev/quick-start/quickstart-lite-env-setup.md index 5820ee61fb0a66a76ad7e8afaf0f8e3b823d0c31..894e3d8b8fb99afcfd005fa232c0945b0e990315 100644 --- a/en/device-dev/quick-start/quickstart-lite-env-setup.md +++ b/en/device-dev/quick-start/quickstart-lite-env-setup.md @@ -148,7 +148,7 @@ To remotely access the Ubuntu environment through Windows to perform operations ![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png) -## Configuring Windows to Remotely Access the Ubuntu Build Environment +## Configuring Windows to Remotely Access the Ubuntu Development Environment ### Installing the SSH Service and Obtaining the IP Address for Remote Access diff --git a/en/device-dev/quick-start/quickstart-lite-faq-burning.md b/en/device-dev/quick-start/quickstart-lite-faq-burning.md index d8555b3cc7c816d6e4cc6ce30c5f9918ddf40eb2..02fc1cfa341525b77efbe6391418ba52099b2525 100644 --- a/en/device-dev/quick-start/quickstart-lite-faq-burning.md +++ b/en/device-dev/quick-start/quickstart-lite-faq-burning.md @@ -7,9 +7,9 @@ Error: Opening COMxx: Access denied is displayed after clicking Burn and selecting a serial port. - **Figure 1** Failed to open the serial port + **Figure 1** Failed to open the serial port - ![en-us_image_0000001226634728](figures/en-us_image_0000001226634728.png) + ![en-us_image_0000001226634728](figures/en-us_image_0000001226634728.png) - **Possible Causes** @@ -42,9 +42,9 @@ The file image cannot be obtained after clicking Burn and selecting a serial port. - **Figure 5** Failed to obtain the file image due to network disconnection + **Figure 5** Failed to obtain the file image due to network disconnection - ![en-us_image_0000001271234757](figures/en-us_image_0000001271234757.png) + ![en-us_image_0000001271234757](figures/en-us_image_0000001271234757.png) - **Possible Causes** @@ -125,12 +125,15 @@ 1. Obtain the U-Boot file. > ![icon-notice.gif](public_sys-resources/icon-notice.gif) **NOTICE** - > - > The U-Boot file can be obtained from the following path: device\hisilicon\hispark_taurus\sdk_liteos\uboot\out\boot\u-boot-hi3516dv300.bin. + > 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 [Burning to Hi3516D V300](https://device.harmonyos.com/en/docs/documentation/guide/ide-hi3516-upload-0000001052148681). + Select the U-Boot files of corresponding development boards for burning by referring to [Burning to Hi3516D V300](https://device.harmonyos.com/en/docs/documentation/guide/ide-hi3516-upload-0000001052148681)/[Burning to Hi3518E V300](https://device.harmonyos.com/en/docs/documentation/guide/ide-hi3518-upload-0000001057313128#section93591711580). 3. Log in to the serial port after the burning is complete. diff --git a/en/device-dev/quick-start/quickstart-lite-ide-directory.md b/en/device-dev/quick-start/quickstart-lite-ide-directory.md index 88773504a4830ba8b23f3265f197630b853d8d74..49ae1c33bc4dce0fecda7b7cd0a1b8ea4e52400f 100644 --- a/en/device-dev/quick-start/quickstart-lite-ide-directory.md +++ b/en/device-dev/quick-start/quickstart-lite-ide-directory.md @@ -1,7 +1,7 @@ ## Getting Started with Mini and Small Systems (IDE Mode) - [Mini and Small System Overview](quickstart-ide-lite-overview.md) - - Environment Preparation - - [Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-lite-env-setup-win-ubuntu.md) + - Setting Up Environments for the Mini and Small Systems + - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-lite-env-setup-win-ubuntu.md) - [Obtaining Source Code](quickstart-ide-lite-sourcecode-acquire.md) - [Creating a Source Code Project](quickstart-ide-lite-create-project.md) - Running a Hello World Program 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 96f3578b058936d5f757e3cd0fa677257f5f4b9b..78fee5a65bc346220534309249b4b2cb19255d7c 100644 --- a/en/device-dev/quick-start/quickstart-lite-package-directory.md +++ b/en/device-dev/quick-start/quickstart-lite-package-directory.md @@ -1,6 +1,6 @@ ## Getting Started with Mini and Small Systems (Installation Package Mode) - [Mini and Small System Overview](quickstart-lite-overview.md) -- [Environment Preparation](quickstart-lite-env-setup.md) +- [Setting Up Environments for the Mini and Small Systems](quickstart-lite-env-setup.md) - Running a Hello World Program - Hi3861 Development Board - [Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md) diff --git a/en/device-dev/quick-start/quickstart-lite-reference.md b/en/device-dev/quick-start/quickstart-lite-reference.md index c6fa6d023fbb1468e99b3c2ad2274ec64b5799bf..46ee65fc6593c280b1946d24d1e7e4fa3f9cf3d1 100644 --- a/en/device-dev/quick-start/quickstart-lite-reference.md +++ b/en/device-dev/quick-start/quickstart-lite-reference.md @@ -11,7 +11,7 @@ ``` > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > _name_ indicates the product name, for example, **Hi3516D V300** and **rk3568**. + > _name_ indicates the product name, for example, **hispark_taurus_standard** and **rk3568**. 2. Check the build result. After the build is complete, the following information is displayed in the log: @@ -21,7 +21,7 @@ ``` Files generated during the build are stored in the **out/{device_name}/** directory, and the generated image is stored in the **out/{device_name}/packages/phone/images/** directory. - > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** + > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> For details about other modular compilation operations, see [Building a Standard System](../subsystems/subsys-build-standard-large.md). diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md index a8065841e5ffd0d3b72d2d6a52929118b7b13ffe..cd0b1434eb03b1f237c69eb3dc1b4a5a66382dbb 100644 --- a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md +++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md @@ -40,7 +40,7 @@ After the source code is imported, perform the following steps: 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -48,7 +48,7 @@ After the source code is imported, perform the following steps: ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md index 5a2d1a31a5d0ebfe4a890f41441e0aab0f37061d..46974e89328fec671bae02e748ea393b1d147914 100644 --- a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md +++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md @@ -40,7 +40,7 @@ After the source code is imported, perform the following steps: 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3861 V100 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3861.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -48,7 +48,7 @@ After the source code is imported, perform the following steps: ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-standard-env-setup.md b/en/device-dev/quick-start/quickstart-standard-env-setup.md index ff6fccdf759439a321deee7569cc069f1d261c9f..9b55be45cee8bab38bcc23b23558f9b8d3806c16 100644 --- a/en/device-dev/quick-start/quickstart-standard-env-setup.md +++ b/en/device-dev/quick-start/quickstart-standard-env-setup.md @@ -140,7 +140,7 @@ To remotely access the Ubuntu environment through Windows to perform operations ![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png) -## Configuring Windows to Remotely Access the Ubuntu Build Environment +## Configuring Windows to Remotely Access the Ubuntu Development Environment ### Installing the SSH Service and Obtaining the IP Address for Remote Access diff --git a/en/device-dev/quick-start/quickstart-standard-faq-hb.md b/en/device-dev/quick-start/quickstart-standard-faq-hb.md index f70d8caa2fcad74a10961a3b4612ba5b82e390f4..b10a92e12834e6af30cc953604fff4246e8ba4f0 100644 --- a/en/device-dev/quick-start/quickstart-standard-faq-hb.md +++ b/en/device-dev/quick-start/quickstart-standard-faq-hb.md @@ -4,15 +4,18 @@ ## What should I do if garbled characters and segmentation faults occur during hb installation? - **Symptom** - Garbled characters and segmentation faults occur during the execution of the **python3 -m pip install --user ohos-build** command. - + +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. - + +pip is of an early version. + - **Solution** - Upgrade pip. - - + +Upgrade pip. + + ``` python3 -m pip install -U pip ``` @@ -21,15 +24,18 @@ ## What should I do if the message "cannot import 'sysconfig' from 'distutils'" is displayed during hb installation? - **Symptom** - The message "cannot import 'sysconfig' from 'distutils'" is displayed during the execution of the **python3 -m pip install --user ohos-build** command. - + +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. - + +The **distutils** module is unavailable. + - **Solution** - Install distutils. - - + +Install distutils. + + ``` sudo apt-get install python3.8-distutils ``` @@ -38,15 +44,18 @@ ## What should I do if the message "module 'platform' has no attribute 'linux_distribution'" is displayed during hb installation? - **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. - + +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. - + +There is a compatibility issue of python3-pip. + - **Solution** - Reinstall pip. - - + +Reinstall pip. + + ``` sudo apt remove python3-pip curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py @@ -57,15 +66,18 @@ ## What should I do if the message "Could not find a version that satisfies the requirement ohos-build" is displayed during hb installation? - **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. - + +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. - + +The installation fails due to poor network connectivity. + - **Solution** + 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 ``` diff --git a/en/device-dev/quick-start/quickstart-standard-ide-directory.md b/en/device-dev/quick-start/quickstart-standard-ide-directory.md index 297424cb26da0d60a9500e2a78623eb232e523a9..5285337d788ce1d7e97b286419f7beabfa59faef 100644 --- a/en/device-dev/quick-start/quickstart-standard-ide-directory.md +++ b/en/device-dev/quick-start/quickstart-standard-ide-directory.md @@ -1,7 +1,7 @@ ## Getting Started with Standard System (IDE Mode) - [Standard System Overview](quickstart-ide-standard-overview.md) - Environment Preparation - - [Setting Up the Windows+Ubuntu Hybrid Build Environment](quickstart-ide-standard-env-setup-win-ubuntu.md) + - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md) - [Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md) - [Creating a Source Code Project](quickstart-ide-standard-create-project.md) - Running a Hello World Program diff --git a/en/device-dev/quick-start/quickstart-standard-reference.md b/en/device-dev/quick-start/quickstart-standard-reference.md index 2c20ea41430d7201815a82058950a99f53847d28..ada4dac3c77729838792875bc4e1c61f603be0cb 100644 --- a/en/device-dev/quick-start/quickstart-standard-reference.md +++ b/en/device-dev/quick-start/quickstart-standard-reference.md @@ -11,7 +11,7 @@ ``` > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > _name_ indicates the product name, for example, **Hi3516D V300** and **rk3568**. + > _name_ indicates the product name, for example, **hispark_taurus_standard** and **rk3568**. 2. Check the build result. After the build is complete, the following information is displayed in the log: diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md index f40fa3b05b2f3cd16f86a2f9f8c11bf20945188b..7b170d1e45d1e6670a75af371e5c313a51eb65b3 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md +++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md @@ -45,4 +45,4 @@ Go to the root directory of the source code in the Ubuntu environment and perfor 5. Check the build result. If "build success" is displayed, the building is successful. > ![icon-notice.gif](public_sys-resources/icon-notice.gif) **NOTICE** - > The build result and log files are stored in **out/hi3516dv300**. + > The build result and log files are stored in **out/hispark_taurus**. diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md index 231e6fea28ebeed249fc93799efe21e891232f61..4c1e34c22be466aca3721ac696aa6ae306eae58b 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md +++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md @@ -40,7 +40,7 @@ After the source code is imported, perform the following steps: 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). -2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -48,7 +48,7 @@ After the source code is imported, perform the following steps: ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** - > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md index 7462695f2fd07300520ab566434c6082589d3bf4..7bae60ad6f2a1bc4a6bdb36c6c8593fc4ce4f581 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md +++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-create.md @@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board. The complete code directory is as follows: - + ``` applications/sample/hello │ │── BUILD.gn @@ -19,9 +19,9 @@ applications/sample/hello │ └── bundle.json build └── subsystem_config.json -productdefine/common -└── products - └── Hi3516DV300.json +vendor/hisilicon +└── Hi3516DV300 + └── config.json ``` @@ -34,7 +34,7 @@ Perform the steps below in the source code directory: Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OH**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program. - + ``` #include #include "helloworld.h" @@ -55,7 +55,7 @@ Perform the steps below in the source code directory: Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows: - + ``` #ifndef HELLOWORLD_H #define HELLOWORLD_H @@ -78,7 +78,7 @@ Perform the steps below in the source code directory: 2. Create a build file. 1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows: - + ``` import("//build/ohos.gni") # Import the build template. ohos_executable("helloworld") {# Executable module. @@ -99,7 +99,7 @@ Perform the steps below in the source code directory: } ``` 2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows: - + ``` { "name": "@ohos/hello", @@ -141,7 +141,7 @@ Perform the steps below in the source code directory: Add the configuration of the new subsystem to the **build/subsystem_config.json** file. - + ``` "sample": { "path": "applications/sample/hello", @@ -151,9 +151,9 @@ Perform the steps below in the source code directory: 4. Modify the product configuration file. - In the **productdefine/common/products/Hi3516DV300.json** file, add the **hello** part after the existing part. + In the **vendor\hisilicon\Hi3516DV300\config.json** file, add the **hello** part after the existing part. - + ``` "usb:usb_manager_native":{}, "applications:prebuilt_hap":{}, diff --git a/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md index 961c8f00406560b536d28dc7fa40cca77fc7d239..d17d3881e3a921f358e502272bd87ab8d6521cd0 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md +++ b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md @@ -44,7 +44,7 @@ After the source code is imported, perform the following steps: 2. Connect the computer to the target development board through the USB port. -3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment). +3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment). - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. Inthis case, no further action is required. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon. @@ -52,7 +52,7 @@ After the source code is imported, perform the following steps: ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
- > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step. + > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step. 4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings. diff --git a/en/device-dev/quick-start/quickstart-standard-running-rk3568-create.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-create.md index 523e9f334d4269af91a3244470d4d8438f14fe06..aa730ed0aa81d4f2aac49c4ea9b5b3cfe4c3b247 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-rk3568-create.md +++ b/en/device-dev/quick-start/quickstart-standard-running-rk3568-create.md @@ -18,9 +18,9 @@ applications/sample/hello │ └── bundle.json build └── subsystem_config.json -productdefine/common -└── products - └── rk3568.json +vendor/hihope +└── rk3568 + └── config.json ``` @@ -149,7 +149,7 @@ Perform the steps below in the source code directory: 4. Modify the product configuration file. - In the **productdefine/common/products/rk3568.json** file, add the **hello** part after the existing part. + In the **vendor\hihope\rk3568\config.json** file, add the **hello** part after the existing part. ``` "usb:usb_manager_native":{},