From fe6b0ccfd872689fa862658bbc44c985eb515921 Mon Sep 17 00:00:00 2001 From: "ester.zhou" Date: Thu, 19 May 2022 20:14:46 +0800 Subject: [PATCH] update docs Signed-off-by: ester.zhou --- .../notification/notification.md | 2 +- en/application-dev/quick-start/Readme-EN.md | 3 +- .../quick-start/stage-structure.md | 16 +- en/application-dev/reference/Readme-EN.md | 7 +- .../reference/arkui-js/Readme-EN.md | 4 +- .../js-framework-multiple-languages.md | 196 ------------------ en/device-dev/device-dev-guide.md | 4 +- .../device-camera-control-demo-photoguide.md | 2 +- .../guide/device-camera-control-demo.md | 2 +- .../guide/device-camera-control-example.md | 18 +- .../guide/device-camera-control-overview.md | 6 +- en/device-dev/guide/device-camera-control.md | 4 +- .../guide/device-iotcamera-control-demo.md | 2 +- .../device-iotcamera-control-overview.md | 8 +- .../guide/device-iotcamera-control.md | 4 +- en/device-dev/quick-start/Readme-EN.md | 4 +- .../quick-start/quickstart-docker-lite.md | 2 +- .../quickstart-ide-lite-create-project.md | 2 +- ...uickstart-ide-lite-env-setup-win-ubuntu.md | 8 +- .../quickstart-ide-lite-env-setup.md | 3 +- ...quickstart-ide-lite-introduction-hi3516.md | 12 +- ...quickstart-ide-lite-introduction-hi3861.md | 48 ++--- .../quickstart-ide-lite-steps-hi3516-burn.md | 6 +- .../quickstart-ide-lite-steps-hi3861-burn.md | 4 +- ...-ide-standard-board-introduction-hi3516.md | 10 +- ...-ide-standard-board-introduction-rk3568.md | 2 +- .../quickstart-ide-standard-create-project.md | 4 +- ...start-ide-standard-env-setup-win-ubuntu.md | 10 +- .../quickstart-ide-standard-env-setup.md | 2 +- ...art-ide-standard-running-hi3516-burning.md | 4 +- ...art-ide-standard-running-hi3516-running.md | 10 +- ...art-ide-standard-running-rk3568-burning.md | 4 +- ...art-ide-standard-running-rk3568-running.md | 2 +- ...ckstart-ide-standard-sourcecode-acquire.md | 14 +- .../quick-start/quickstart-lite-env-setup.md | 2 +- .../quickstart-lite-ide-directory.md | 4 +- .../quickstart-lite-package-directory.md | 2 +- .../quick-start/quickstart-lite-reference.md | 2 +- .../quickstart-lite-steps-hi3516-burn.md | 4 +- .../quickstart-lite-steps-hi3861-burn.md | 4 +- .../quickstart-standard-env-setup.md | 2 +- .../quickstart-standard-ide-directory.md | 2 +- ...ckstart-standard-running-hi3516-burning.md | 4 +- ...ckstart-standard-running-rk3568-burning.md | 4 +- en/device-dev/website.md | 1 + 45 files changed, 132 insertions(+), 328 deletions(-) delete mode 100644 en/application-dev/reference/arkui-js/js-framework-multiple-languages.md diff --git a/en/application-dev/notification/notification.md b/en/application-dev/notification/notification.md index 129db615d8..8aee267205 100644 --- a/en/application-dev/notification/notification.md +++ b/en/application-dev/notification/notification.md @@ -133,7 +133,7 @@ var subscriber = { ##### Enabling Notification -Before publishing a notification, check whether the notification feature is enabled for your application. By default, the feature is disabled. The application can use **Notification.requestEnableNotification** to prompt the user to enable the feature. +Before publishing a notification, check whether the notification feature is enabled for your application. By default, the feature is disabled. The application calls **Notification.requestEnableNotification** to prompt the user to enable the feature. ```js Notification.requestEnableNotification() .then((data) => { diff --git a/en/application-dev/quick-start/Readme-EN.md b/en/application-dev/quick-start/Readme-EN.md index 502646515c..228d2f0442 100644 --- a/en/application-dev/quick-start/Readme-EN.md +++ b/en/application-dev/quick-start/Readme-EN.md @@ -6,10 +6,9 @@ - [Getting Started with eTS in the Low-Code Approach](start-with-ets-low-code.md) - [Getting Started with JavaScript in the Traditional Coding Approach](start-with-js.md) - [Getting Started with JavaScript in the Low-Code Approach](start-with-js-low-code.md) - - Development Fundamentals - [Application Package Structure Configuration File (FA Model)](package-structure.md) - - [Application Package Structure Configuration File (Stage Model)](module-structure.md) + - [Application Package Structure Configuration File (Stage Model)](stage-structure.md) - [Resource File Categories](basic-resource-file-categories.md) - [SysCap](syscap.md) diff --git a/en/application-dev/quick-start/stage-structure.md b/en/application-dev/quick-start/stage-structure.md index ef19d2b394..7d733b1b06 100644 --- a/en/application-dev/quick-start/stage-structure.md +++ b/en/application-dev/quick-start/stage-structure.md @@ -175,12 +175,12 @@ Table 2 Internal structure of the app tag | vendor | Application vendor. The value is a string with a maximum of 255 bytes.| String | Yes (initial value: left empty) | | versionCode | Version number of the application. The value is a 32-bit non-negative integer and less than 2 to the power of 31. It is used only to determine whether a version is later than another version. A larger value indicates a later version. Ensure that a new version of the application uses a value greater than any of its predecessors. | Number | No | | versionName | Text description of the version number, which is displayed to users.
The value consists of only digits and dots. The four-segment format *A.B.C.D* is recommended, wherein:
Segment 1: major version number, which ranges from 0 to 99. A major version consists of major new features or large changes.
Segment 2: minor version number, which ranges from 0 to 99. A minor version consists of some new features and large bug fixes.
Segment 3: feature version number, which ranges from 0 to 99. A feature version consists of scheduled new features.
Segment 4: maintenance release number or patch number, which ranges from 0 to 999. A maintenance release or patch consists of resolution to security flaws or minor bugs.| String | No | -| minCompatibleVersionCode | Minimum API version required for running the application. | Number | Yes (initial value: value of **versionCode**)| -| minAPIVersion | Target API version required for running the application. | Number | No | +| minCompatibleVersionCode | Minimum API version compatible with the application. | Number | Yes (initial value: value of **versionCode**)| +| minAPIVersion | Minimum API version required for running the application. | Number | No | | targetAPIVersion | Target API version required for running the application. | Integer | No | | apiReleaseType | Type of the target API version required for running the application. The value can be **CanaryN**, **BetaN**, or **Release**, where **N** represents a positive integer.
**Canary**: indicates a restricted release.
**Beta**: indicates a publicly released beta version.
**Release**: indicates a publicly released official version.| String | Yes (initial value: **"Release"**) | | distributedNotificationEnabled | Whether the distributed notification feature is enabled for the application. | Boolean | Yes (initial value: **true**) | -| entityType | Category of the application, which can be **game**, **media**, **communication**, **news**, **travel**, **utility**, **shopping**, **education**, **kids**, **business**, and **photography**.| String | Yes (initial value: unspecified) | +| entityType | Type of the application, which can be **game**, **media**, **communication**, **news**, **travel**, **utility**, **shopping**, **education**, **kids**, **business**, and **photography**.| String | Yes (initial value: unspecified) | ### Internal Structure of the module Tag @@ -212,9 +212,9 @@ Table 4 System-defined deviceTypes values | Device Type | Value | Description | | ------------ | ------------ | -------------------------------------------------------- | | tablet | tablet | Tablet, speaker with a screen | -| smart TV | tv | | +| smart TV | tv | N/A | | smart watch | wearable | Smart watch, kids' watch, especially a watch that provides call features| -| head unit | car | | +| head unit | car | N/A | | router | router | Router | Example of the **deviceTypes** attribute structure: @@ -309,7 +309,7 @@ Table 6 Internal structure of the abilities attribute | icon | Icon of the ability. The value is the index to the resource file. This attribute can be left empty, and the default value is an empty array.
If **ability** is set to **MainElement**, this attribute is mandatory.| String | Yes (initial value: left empty)
If **ability** is set to **MainElement**, this attribute is mandatory.| | permissions | A set of permissions that need to be applied for when the capability of another application is invoked. The value is a string array. Each array element is a permission name, which is usually represented by a reverse domain name (a maximum of 255 bytes). The permission can be predefined by the system or customized by the application. For the latter, the value must be the same as the **name** value of a permission defined in the **defPermissions** attribute. | String array| Yes (initial value: left empty) | | metadata | Metadata about the ability. For details about metadata, see [Internal Structure of the metadata Attribute](#internal-structure-of-the-metadata-attribute).| Array | Yes (initial value: left empty) | -| visible | Indicates whether the ability can be invoked by other applications. The value **true** means that the ability can be invoked by other applications, and **false** means the opposite.| Boolean | Yes (initial value: **false**) | +| visible | Whether the ability can be invoked by other applications. The value **true** means that the ability can be invoked by other applications, and **false** means the opposite.| Boolean | Yes (initial value: **false**) | | continuable | Whether the ability can be migrated. The value **true** means that the ability can be migrated, and **false** means the opposite.| Boolean | Yes (initial value: **false**) | | skills | Feature set of wants that can be received by the ability.
Configuration rule: In an entry package, you can configure multiple abilities with the **skills** attribute (where **action.system.home** and **entity.system.home** are configured) that has the entry capability. The **label** and **icon** in the first ability that has **skills** configured are used as the **label** and **icon** of the entire service/application.
The **skills** attribute with the entry capability can be configured for the feature package of an OpenHarmony application,
but not for an OpenHarmony service.
For details about the internal structure of **skills**, see [Internal Structure of the skills Attribute](#internal-structure-of-the-skills-attribute).| Array | Yes (initial value: left empty) | | backgroundModes | Continuous task modes of the ability.
Continuous tasks are classified into the following types:
**dataTransfer**: service for downloading, backing up, sharing, or transferring data from the network or peer devices
**audioPlayback**: audio playback service
**audioRecording**: audio recording service
**location**: location and navigation services
**bluetoothInteraction**: Bluetooth scanning, connection, and transmission services (wearables)
**multiDeviceConnection**: multi-device interconnection service
**wifiInteraction**: Wi-Fi scanning, connection, and transmission services (multi-screen cloning)
**voip**: voice/video call and VoIP services
**taskKeeping**: computing service
| String | Yes (initial value: left empty) | @@ -361,7 +361,7 @@ Table 7 Internal structure of the skills attribute | -------- | ------------------------------------------------------------ | ---------- | -------------------- | | actions | A set of want action values that can be received. The value can be a value predefined by the system or a custom value.| String array| Yes (initial value: left empty)| | entities | Categories of abilities that can receive the want. The value can be a value predefined by the system or a custom value.| String array| Yes (initial value: left empty)| -| uris | Data specifications to be added to the want filter. The specification can be of data type only (**mimeType** attribute), URI only, or both. For details about the internal structure of **uris**, see Table 8.| Object array | Yes (initial value: left empty)| +| uris | Data specification to be added to the want filter. The specification can be of data type only (**mimeType** attribute), URI only, or both. For details about the internal structure of **uris**, see Table 8.| Object array | Yes (initial value: left empty)| Table 8 Internal structure of the uris attribute @@ -612,7 +612,7 @@ Table 13 Internal structure of the shortcuts attribute | Attribute | Description | Data Type| Initial Value Allowed | | ---------- | ------------------------------------------------------------ | -------- | -------------------------- | -| shortcutId | Shortcut ID. The value is a string with a maximum of 63 bytes. | String | No | +| shortcutId | ID of the shortcut. The value is a string with a maximum of 63 bytes. | String | No | | label | Label of the shortcut, that is, the text description displayed by the shortcut. The value can be a string or a resource index to the description. The value is a string with a maximum of 63 bytes.| String | Yes (initial value: left empty) | | icon | Icon of the shortcut. The value is the index to the resource file. | String | Yes (initial value: left empty)| | wants | Wants to which the shortcut points. The attribute consists of the **bundleName** and **abilityName** sub-attributes.
**bundleName**: target bundle name of the shortcut; string type.
**abilityName**: target component name of the shortcut; string type.| Object | Yes (initial value: left empty) | diff --git a/en/application-dev/reference/Readme-EN.md b/en/application-dev/reference/Readme-EN.md index c2252e1a8f..30bb3aacd8 100644 --- a/en/application-dev/reference/Readme-EN.md +++ b/en/application-dev/reference/Readme-EN.md @@ -4,7 +4,8 @@ - [TypeScript-based Declarative Development Paradigm](arkui-ts/Readme-EN.md) - [APIs](apis/Readme-EN.md) - - [JS (eTS Included) APIs](reference/apis/Readme-EN.md) + - [JS (eTS Included) APIs](apis/Readme-EN.md) - Native APIs - - [Standard Library](reference/native-lib/third_party_libc/musl.md) - - [Node_API](reference/native-lib/third_party_napi/napi.md) \ No newline at end of file + - [Standard Library](native-lib/third_party_libc/musl.md) + - [Node_API](native-lib/third_party_napi/napi.md) + diff --git a/en/application-dev/reference/arkui-js/Readme-EN.md b/en/application-dev/reference/arkui-js/Readme-EN.md index f0b0e7b6c9..fd00b650bc 100644 --- a/en/application-dev/reference/arkui-js/Readme-EN.md +++ b/en/application-dev/reference/arkui-js/Readme-EN.md @@ -106,5 +106,5 @@ - [Event Parameter](js-components-custom-event-parameter.md) - [slot](js-components-custom-slot.md) - [Lifecycle Definition](js-components-custom-lifecycle.md) -- [Type Attributes](js-appendix-types.md) - +- Appendix + - [Type Attributes](js-appendix-types.md) diff --git a/en/application-dev/reference/arkui-js/js-framework-multiple-languages.md b/en/application-dev/reference/arkui-js/js-framework-multiple-languages.md deleted file mode 100644 index 30b72ecc29..0000000000 --- a/en/application-dev/reference/arkui-js/js-framework-multiple-languages.md +++ /dev/null @@ -1,196 +0,0 @@ -# Multi-Language Capability - - -Applications designed based on the JS UI framework apply to different countries and regions. With the multi-language capability, you do not need to develop application versions in different languages, and your users can switch between various locales. This also facilitates project maintenance. - - -You only need to perform operations in [Resource Files](#resource-files) and [Resource Reference](#resource-reference) to use the multi-language capability of this framework. For details about how to obtain the current system language, see [Language Acquisition](#language-acquisition). - - -## Resource Files - -Resource files store application content in multiple languages. This framework uses JSON files to store resource definitions. Place the resource file of each locale in the i18n directory described in [File Organization](js-framework-file.md). - -Resource files should be named in _language-script-region_.json format. For example, the resource file for Hong Kong Chinese in the traditional script is named zh-Hant-HK. You can omit the region, for example, zh-CN for simplified Chinese, or omit both the script and region, for example, zh for Chinese. - - -``` -language[-script-region].json -``` - -The following table describes the requirements for the qualifiers of resource file names. - -Table 1 Requirements for qualifier values - -| Qualifier Type | Description and Value Range | -| -------- | -------- | -| Language | Indicates the language used by the device. The value consists of two or three lowercase letters, for example, zh indicates Chinese, en indicates English, and mai indicates Maithili.
For details about the value range, refer to ISO 639 (codes for the representation of names of languages). | -| Script | Indicates the script type used by the device. The value starts with one uppercase letter followed by three lowercase letters, for example, Hans indicates simplified Chinese and Hant indicates traditional Chinese.
For details about the value range, refer to ISO 15924 (codes for the representation of names of scripts). | -| Country/Region | Indicates the country or region where a user is located. The value consists of two or three uppercase letters or three digits, for example, CN indicates China and GB indicates the United Kingdom.
For details about the value range, refer to ISO 3166-1 (codes for the representation of names of countries and their subdivisions). | - -If there is no resource file of the locale that matches the system language, content in the en-US.json file will be used by default. - -The format of the resource file content is as follows: - -**en-US.json** - -``` -{ - "strings": { - "hello": "Hello world!", - "object": "Object parameter substitution-{name}", - "array": "Array type parameter substitution-{0}", - "symbol": "@#$%^&*()_+-={}[]\\|:;\"'<>,./?" - }, - - "files": { - "image": "image/en_picture.PNG" - } -} -``` - - -Different languages have different matching rules for singular and plural forms. In the resource file, zero, one, two, few, many, and other are used to define the string content in different singular and plural forms. For example, there is only the other scenario in Chinese since the language does not have singular and plural forms. one and other scenarios are applicable to English. All six scenarios are needed for Arabic. - - -The following example takes en-US.json and ar-AE.json as examples: - -**en-US.json** - - -``` -{ - "strings": { - "people": { - "one": "one person", - "other": "{count} people" - } - } -} -``` - - -ar-AE.json - - -``` -{ - "strings": { - "people": { - "zero": "لا أحد", - "one": "وحده", - "two": "اثنان", - "few": "ستة اشخاص", - "many": "خمسون شخص", - "other": "مائة شخص" - } - } -} -``` - - -## Resource Reference - -Multi-language syntax used on application development pages (including simple formatting and singular-plural formatting) can be used in .hml or .js files. - -- Simple formatting - - Use the `$t` function to reference to resources of different locales. The `$t` function is available for both .hml and .js files. The system displays content based on a resource file path specified via $t and the specified resource file whose locale matches the current system language. - - Table 2 Simple formatting - - | Attribute | Type | Parameter | Mandatory | Description | - | -------- | -------- | -------- | -------- | -------- | - | $t | Function | See Table3 | Yes | Sets the parameters based on the system language, for example, this.$t('strings.hello'). | - - -Table 3 $t function parameters - -| Parameter | Type | Mandatory | Description | -| -------- | -------- | -------- | -------- | -| path | string | Yes | Path of the language resource key | -| params | Array\|Object | No | Content used to replace placeholders during runtime. There are two types of placeholders available:
- Named placeholder, for example, {name}. The actual content must be of the object type, for example, \```$t('strings.object', {name:'Hello world'})```.
- Digit placeholder, for example, {0}. The actual content must be of the array type, for example, \```$t('strings.array', [Hello world']```. | - -- Example code for simple formatting - - ``` - -
- - {{ $t('strings.hello') }} - - {{ $t('strings.object', { name: 'Hello world' }) }} - - {{ $t('strings.array', ['Hello world']) }} - - {{ hello }} - - {{ replaceObject }} - - {{ replaceArray }} - - - - - -
- ``` - - - ``` - // xxx.js - // The following example uses the $t function in the .js file. - export default { - data: { - hello: '', - replaceObject: '', - replaceArray: '', - replaceSrc: '', - }, - onInit() { - this.hello = this.$t('strings.hello'); - this.replaceObject = this.$t('strings.object', { name: 'Hello world' }); - this.replaceArray = this.$t('strings.array', ['Hello world']); - this.replaceSrc = this.$t('files.image'); - }, - } - ``` - -- Singular-plural formatting - Table 4 Singular-plural formatting - - | Attribute | Type | Parameter | Mandatory | Description | - | -------- | -------- | -------- | -------- | -------- | - | $tc | Function | See Table 5. | Yes | Converts between the singular and plural forms based on the system language, for example, this.$tc('strings.people').
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> The resource content is distinguished by the following JSON keys: zero, one, two, few, many, and other. | - - Table 5 $tc function parameters - - | Parameter | Type | Mandatory | Description | - | -------- | -------- | -------- | -------- | - | path | string | Yes | Path of the language resource key | - | count | number | Yes | Number | - -- Sample code for singular-plural formatting - - ``` - -
- - {{ $tc('strings.people', 0) }} - - {{ $tc('strings.people', 1) }} - - {{ $tc('strings.people', 2) }} - - {{ $tc('strings.people', 6) }} - - {{ $tc('strings.people', 50) }} - - {{ $tc('strings.people', 100) }} -
- ``` - - -## Language Acquisition - -For details about how to obtain the language, see the Application Configuration section. diff --git a/en/device-dev/device-dev-guide.md b/en/device-dev/device-dev-guide.md index 8a891ecc8c..b255de5e06 100644 --- a/en/device-dev/device-dev-guide.md +++ b/en/device-dev/device-dev-guide.md @@ -27,7 +27,7 @@ In addition, OpenHarmony provides a wide array of system components that can be ## Document Outline -**Table 1** Mini and small system development guidelines (reference memory < 128 MB) +**Table 1** Mini and small system development guidelines (reference memory < 128 MiB) | Topic| Development Scenario| Related Documentation| | -------- | -------- | -------- | @@ -41,7 +41,7 @@ In addition, OpenHarmony provides a wide array of system components that can be | Reference| Referring to development specifications| [FAQs](faqs/faqs-overview.md) | -**Table 2** Standard system development guidelines (reference memory ≥ 128 MB) +**Table 2** Standard system development guidelines (reference memory ≥ 128 MiB) | Topic| Development Scenario| Related Documentation| | -------- | -------- | -------- | | About OpenHarmony| Getting familiar with OpenHarmony| - [About OpenHarmony](https://gitee.com/openharmony)
- [Glossary](../glossary.md) | 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 e0046ccac0..de61ed05e5 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 48b36ad9d6..0656cdd729 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 c9920f4b3b..dbe3e57443 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 61f5aa13eb..878d479a2f 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 062b965f7a..e57f328b6d 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-iotcamera-control-demo.md b/en/device-dev/guide/device-iotcamera-control-demo.md index 6f18715629..2d711a2c70 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-overview.md b/en/device-dev/guide/device-iotcamera-control-overview.md index d5a493f3a2..d67f97231e 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 f2720769bb..35d1af547b 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/quick-start/Readme-EN.md b/en/device-dev/quick-start/Readme-EN.md index 93481265a2..1fb06af53b 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 @@ -52,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 diff --git a/en/device-dev/quick-start/quickstart-docker-lite.md b/en/device-dev/quick-start/quickstart-docker-lite.md index b0dedbd30e..666b1510ff 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 9227e669b4..37002b081c 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 fbed65d9a8..b16ef9ebb0 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,7 +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 +## Setting Up the Ubuntu Development 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: @@ -116,7 +116,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 a3722cf567..e7461bde3d 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 4c85bdc37b..68ec899169 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 fa6235602d..b32ea6e794 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 2c23f4eec8..36a19432f9 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 3ebd031b51..72a07f6323 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 250a2a496e..e27bfe3de9 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 6f74a5fa51..e076fca68d 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 5e1e39d880..3ac2873105 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 af96bb9caf..0618faf0c0 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 cb161ced75..8faf2853a5 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-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md index f618b545c4..dad8d48305 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-running.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-running.md index a0e31a6a05..0031532533 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 57f29832e5..8c342589b7 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-running.md b/en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-running.md index cf86116a18..e21d612fa7 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 997e0ee227..c84614b095 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 5820ee61fb..894e3d8b8f 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-ide-directory.md b/en/device-dev/quick-start/quickstart-lite-ide-directory.md index 88773504a4..49ae1c33bc 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 96f3578b05..78fee5a65b 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 c6fa6d023f..a17f5f0854 100644 --- a/en/device-dev/quick-start/quickstart-lite-reference.md +++ b/en/device-dev/quick-start/quickstart-lite-reference.md @@ -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 a8065841e5..cd0b1434eb 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 5a2d1a31a5..46974e8932 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 ff6fccdf75..9b55be45ce 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-ide-directory.md b/en/device-dev/quick-start/quickstart-standard-ide-directory.md index 297424cb26..5285337d78 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-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md index 231e6fea28..4c1e34c22b 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-rk3568-burning.md b/en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md index 961c8f0040..d17d3881e3 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/website.md b/en/device-dev/website.md index d8cffc4d61..8f6c8f6d83 100644 --- a/en/device-dev/website.md +++ b/en/device-dev/website.md @@ -479,6 +479,7 @@ - [HiSysEvent Tool Usage](subsystems/subsys-dfx-hisysevent-tool.md) - [HiDumper Development](subsystems/subsys-dfx-hidumper.md) - [HiChecker Development](subsystems/subsys-dfx-hichecker.md) + - [FaultLogger Development](subsystems/subsys-dfx-faultlogger.md) - Featured Topics - HPM Part - [HPM Part Overview](hpm-part/hpm-part-about.md) -- GitLab