Skip to content

D
Docs

OpenHarmony / Docs
大约 2 年 前同步成功

通知 161
Star 293
Fork 28
D
Docs
“3d3f5506d261fe31b8217b5e5d59d14b48346216”上不存在“...fluid/tests/git@gitcode.net:paddlepaddle/Paddle.git”
未验证 提交 3893e225 编写于 作者: O openharmony_ci 提交者： Gitee
浏览文件
操作

!15120 【3.1 Release】翻译完成 12150+14491+14804 

Merge pull request !15120 from ester.zhou/C01-0223
上级 e05d8cd1 78ac8654
隐藏空白更改
内联 并排
Showing with 117 addition and 80 deletion
en/application-dev/reference/arkui-ts/ts-container-badge.md
浏览文件 @ 3893e225
...@@ -14,9 +14,9 @@ This component supports only one child component. ...@@ -14,9 +14,9 @@ This component supports only one child component.
## APIs ## APIs
**Method 1**: Badge(value: {count: number, position?: BadgePosition, maxCount?: number, style: BadgeStyle}) **API 1**: Badge(value: {count: number, position?: BadgePosition, maxCount?: number, style: BadgeStyle})
Create a badge. Creates a badge.
**Parameters** **Parameters**
| Name| Type| Mandatory| Default Value| Description| | Name| Type| Mandatory| Default Value| Description|
...@@ -26,7 +26,7 @@ Create a badge. ...@@ -26,7 +26,7 @@ Create a badge.
| maxCount | number | No| 99 | Maximum number of notifications. When the maximum number is reached, only **maxCount+** is displayed.| | maxCount | number | No| 99 | Maximum number of notifications. When the maximum number is reached, only **maxCount+** is displayed.|
| style | [BadgeStyle](#badgestyle) | Yes| - | Style of the badge, including the font color, font size, badge color, and badge size.| | style | [BadgeStyle](#badgestyle) | Yes| - | Style of the badge, including the font color, font size, badge color, and badge size.|
**Method 2**: Badge(value: {value: string, position?: BadgePosition, style: BadgeStyle}) **API 2**: Badge(value: {value: string, position?: BadgePosition, style: BadgeStyle})
Creates a badge based on the given string. Creates a badge based on the given string.
...@@ -69,7 +69,7 @@ struct BadgeExample { ...@@ -69,7 +69,7 @@ struct BadgeExample {
Column() { Column() {
Text('numberBadge').width('80%') Text('numberBadge').width('80%')
Row({ space: 10 }) { Row({ space: 10 }) {
// Number badge. The default value of maxCount is 99. If the number of notifications exceeds 99, 99+ is displayed. // Number badge in the upper right corner. The default value of maxCount is 99. If the number of notifications exceeds 99, 99+ is displayed.
Badge({ Badge({
count: this.counts, count: this.counts,
maxCount: 99, maxCount: 99,
...@@ -83,7 +83,7 @@ struct BadgeExample { ...@@ -83,7 +83,7 @@ struct BadgeExample {
.width(100).height(50).backgroundColor(0x317aff) .width(100).height(50).backgroundColor(0x317aff)
}.width(100).height(50) }.width(100).height(50)
// Number badge // Number badge on the left.
Badge({ Badge({
count: this.counts, count: this.counts,
maxCount: 99, maxCount: 99,
...@@ -98,7 +98,7 @@ struct BadgeExample { ...@@ -98,7 +98,7 @@ struct BadgeExample {
}.width(100).height(50) }.width(100).height(50)
// Number badge // Number badge on the right.
Badge({ Badge({
count: this.counts, count: this.counts,
maxCount: 99, maxCount: 99,
......
en/application-dev/reference/js-service-widget-ui/js-service-widget-syntax-hml.md
浏览文件 @ 3893e225
...@@ -25,15 +25,14 @@ The OpenHarmony Markup Language (HML) is an HTML-like language that allows you t ...@@ -25,15 +25,14 @@ The OpenHarmony Markup Language (HML) is an HTML-like language that allows you t
<!-- xxx.hml --> <!-- xxx.hml -->
<div class="item-container"> <div class="item-container">
<text>{{content}}</text> <!-- Display Hello World!--> <text>{{content}}</text> <!-- Display Hello World!-->
<text>{{key1}} {{key2}}</text> <!-- Display Hello World--> <text>{{key1}} {{key2}}</text> <!-- Display Hello World6+-->
<text>key1 {{key1}}</text> <!-- Display key1 Hello--> <text>key1 {{key1}}</text> <!-- Display key1 Hello6+-->
<text>{{flag1 && flag2}}</text> <!-- Display false--> <text>{{flag1 && flag2}}</text> <!-- Display false6+-->
<text>{{flag1 || flag2}}</text> <!-- Display true--> <text>{{flag1 || flag2}}</text> <!-- Display true6+-->
<text>{{!flag1}}</text> <!-- Display false--> <text>{{!flag1}}</text> <!-- Display false6+-->
</div> </div>
``` ```
Declare the variables used in the XML file for service widgets in the **data** field in the JSON file.
```json ```json
{ {
...@@ -50,7 +49,7 @@ Declare the variables used in the XML file for service widgets in the **data** f ...@@ -50,7 +49,7 @@ Declare the variables used in the XML file for service widgets in the **data** f
> **NOTE** > **NOTE**
> - When using data binding, you can use the object operator or array operator on a key to access the bound data, for example, **{{key.value}}** and **{{key[0]}}**. > - When using data binding, you can use the object operator or array operator on a key to access the bound data, for example, **{{key.value}}** and **{{key[0]}}**.
> >
> - String concatenation, logical operations, and ternary expressions are supported. > - String concatenation, logical operations, and ternary expressions are supported since API version 6.
> - String concatenation: > - String concatenation:
> - A variable can be followed by another variable, for example, **{{key1}}{{key2}}**. > - A variable can be followed by another variable, for example, **{{key1}}{{key2}}**.
> - A variable can also be followed by a constant, for example, **"my name is {{name}}, i am from {{city}}." "key1 {{key1}}"**. > - A variable can also be followed by a constant, for example, **"my name is {{name}}, i am from {{city}}." "key1 {{key1}}"**.
...@@ -80,6 +79,7 @@ Declare the events for service widgets in the **actions** field in the JSON file ...@@ -80,6 +79,7 @@ Declare the events for service widgets in the **actions** field in the JSON file
```json ```json
// xxx.json
{ {
"data": { "data": {
"mainAbility": "xxx.xxx.xxx" "mainAbility": "xxx.xxx.xxx"
...@@ -94,40 +94,6 @@ Declare the events for service widgets in the **actions** field in the JSON file ...@@ -94,40 +94,6 @@ Declare the events for service widgets in the **actions** field in the JSON file
} }
``` ```
You can also implement redirection to the target application using a **want**, which contains the **abilityName**, **bundleName**, and **parameters** fields.
| Selector | Type | Default Value | Description |
| ------ | ------ | -------- | ---------------------------------------- |
| action | string | "router" | Event type.<br>- **"router"**: redirection event.<br>- **"message"**: message event.|
| want | [Want](../apis/js-apis-application-Want.md) | - | Information about the target application. For details, see the **want** format. |
```json
{
"data": {
"mainAbility": "xxx.xxx.xxx"
},
"actions": {
"routerEventName1": {
"action": "router",
"want": {
"bundleName": "com.example.myapplication",
"abilityName": "com.example.entry.MainAbility"
}
},
"routerEventName2": {
"action": "router",
"want": {
"action": "xxx.intent.action.DIAL",
"uri": "tel:12345678"
}
}
}
}
```
In API version 8, the [featureAbility.getWant](../apis/js-apis-featureAbility.md) API in the **onCreate** method of the **app.js** or **app.ets** file must be called for the **want** parameter to receive related parameters.
- Message event properties - Message event properties
| Selector | Example | Default Value | Description | | Selector | Example | Default Value | Description |
...@@ -137,6 +103,7 @@ You can also implement redirection to the target application using a **want**, w ...@@ -137,6 +103,7 @@ You can also implement redirection to the target application using a **want**, w
```json ```json
// xxx.json
{ {
"actions": { "actions": {
"activeEvent": { "activeEvent": {
...@@ -184,6 +151,7 @@ You can also implement redirection to the target application using a **want**, w ...@@ -184,6 +151,7 @@ You can also implement redirection to the target application using a **want**, w
```json ```json
// xxx.json
{ {
"data": { "data": {
"array": [ "array": [
...@@ -232,6 +200,7 @@ The **if-elif-else** statements must be used in sibling nodes. Otherwise, the co ...@@ -232,6 +200,7 @@ The **if-elif-else** statements must be used in sibling nodes. Otherwise, the co
```json ```json
// xxx.json
{ {
"data": { "data": {
"show": false, "show": false,
...@@ -250,6 +219,7 @@ If **show** is **true**, the node is rendered properly; if it is **false**, the ...@@ -250,6 +219,7 @@ If **show** is **true**, the node is rendered properly; if it is **false**, the
```json ```json
// xxx.json
{ {
"data": { "data": {
"visible": false "visible": false
...@@ -275,6 +245,7 @@ If **show** is **true**, the node is rendered properly; if it is **false**, the ...@@ -275,6 +245,7 @@ If **show** is **true**, the node is rendered properly; if it is **false**, the
```json ```json
// xxx.json
{ {
"data": { "data": {
"show": true "show": true
......
en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md
浏览文件 @ 3893e225
...@@ -39,6 +39,10 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -39,6 +39,10 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
2. Download the [DevEco Device Tool 3.0 Release Linux version](https://device.harmonyos.com/cn/ide#download). 2. Download the [DevEco Device Tool 3.0 Release Linux version](https://device.harmonyos.com/cn/ide#download).
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Setting Up the Ubuntu Environment] (https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-env-ubuntu.md).
3. Decompress the DevEco Device Tool software package and assign permission on the folder obtained from the decompression. 3. Decompress the DevEco Device Tool software package and assign permission on the folder obtained from the decompression.
1. Go to the directory where the DevEco Device Tool software package is stored and run the following command to decompress the software package. In the command, change **devicetool-linux-tool-3.0.0.401.zip** to the actual software package name. 1. Go to the directory where the DevEco Device Tool software package is stored and run the following command to decompress the software package. In the command, change **devicetool-linux-tool-3.0.0.401.zip** to the actual software package name.
...@@ -55,16 +59,17 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -55,16 +59,17 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name. 4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python. > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
``` ```
sudo ./devicetool-linux-tool-3.0.0.401.sh sudo ./devicetool-linux-tool-3.0.0.401.sh
``` ```
Wait until the "Deveco Device Tool successfully installed." message is displayed. Wait until the "Deveco Device Tool successfully installed." message is displayed.
![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png) ![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png)
...@@ -74,13 +79,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -74,13 +79,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. Download the [DevEco Device Tool 3.0 Release](https://device.harmonyos.com/cn/ide#download) Windows edition. 1. Download the [DevEco Device Tool 3.0 Release](https://device.harmonyos.com/cn/ide#download) Windows edition.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Setting Up the Ubuntu Environment] (https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-env-win.md).
2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**. 2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**.
3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive. 3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version. > If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version.
> >
> ![en-us_image_0000001239275843](figures/en-us_image_0000001239275843.png) > ![en-us_image_0000001239275843](figures/en-us_image_0000001239275843.png)
![en-us_image_0000001270076961](figures/en-us_image_0000001270076961.png) ![en-us_image_0000001270076961](figures/en-us_image_0000001270076961.png)
...@@ -89,16 +99,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -89,16 +99,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. On the **VSCode installation confirm** page, select **Install VScode 1.62.2 automatically** and click **Next**. 1. On the **VSCode installation confirm** page, select **Install VScode 1.62.2 automatically** and click **Next**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If Visual Studio Code 1.62 or later has been installed, this step will be skipped. > If Visual Studio Code 1.62 or later has been installed, this step will be skipped.
![en-us_image_0000001237801283](figures/en-us_image_0000001237801283.png) ![en-us_image_0000001237801283](figures/en-us_image_0000001237801283.png)
2. On the displayed **Python select page**, select **Download from Huawei mirror** and click **Next**. 2. On the displayed **Python select page**, select **Download from Huawei mirror** and click **Next**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If Python 3.8 or 3.9 has been installed, select **Use one of compatible on your PC**. > If Python 3.8 or 3.9 has been installed, select **Use one of compatible on your PC**.
![en-us_image_0000001193983334](figures/en-us_image_0000001193983334.png) ![en-us_image_0000001193983334](figures/en-us_image_0000001193983334.png)
5. In the dialog box shown below, click **Next** to download and install the tools.. 5. In the dialog box shown below, click **Next** to download and install the tools..
...@@ -121,22 +133,23 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -121,22 +133,23 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. In Ubuntu, open the Terminal tool and run the following command to install the SSH service: 1. In Ubuntu, open the Terminal tool and run the following command to install the SSH service:
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the command fails to be executed and the system displays a message indicating that the openssh-server and openssh-client depend on different versions, install the openssh-client of the required version (for example, **sudo apt-get install openssh-client=1:8.2p1-4**) as prompted on the command-line interface (CLI) and run the command again to install the openssh-server. > If the command fails to be executed and the system displays a message indicating that the openssh-server and openssh-client depend on different versions, install the openssh-client of the required version (for example, **sudo apt-get install openssh-client=1:8.2p1-4**) as prompted on the command-line interface (CLI) and run the command again to install the openssh-server.
``` ```
sudo apt-get install openssh-server sudo apt-get install openssh-server
``` ```
2. Run the following command to start the SSH service:
2. Run the following command to start the SSH service:
``` ```
sudo systemctl start ssh sudo systemctl start ssh
``` ```
3. Run the following command to obtain the IP address of the current user for remote access to the Ubuntu environment from Windows: 3. Run the following command to obtain the IP address of the current user for remote access to the Ubuntu environment from Windows:
``` ```
ifconfig ifconfig
``` ```
......
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-building.md
浏览文件 @ 3893e225
# Building # Building
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Building Source Code](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3516-build.md).
1. In **Projects**, click **Settings**. The Hi3516D V300 configuration page is displayed. 1. In **Projects**, click **Settings**. The Hi3516D V300 configuration page is displayed.
...@@ -8,6 +10,7 @@ ...@@ -8,6 +10,7 @@
2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools. 2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again. > If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again.
![en-us_image_0000001265652869](figures/en-us_image_0000001265652869.png) ![en-us_image_0000001265652869](figures/en-us_image_0000001265652869.png)
......
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md
浏览文件 @ 3893e225
# Burning # Burning
Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows. Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Burning an Image](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3516-burn.md).
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). 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).
...@@ -13,7 +16,8 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por ...@@ -13,7 +16,8 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por
![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/> > ![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. > 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. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
...@@ -21,6 +25,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por ...@@ -21,6 +25,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por
![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png) ![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695). > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**. 4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
...@@ -44,6 +49,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por ...@@ -44,6 +49,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por
2. In **Partition Options**, modify the items selected in the preceding step. 2. In **Partition Options**, modify the items selected in the preceding step.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap. > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png) ![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png)
...@@ -55,6 +61,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por ...@@ -55,6 +61,7 @@ Hi3516D V300 supports burning through the USB port, network port, and serial por
8. Go to **hi3516dv300** > **Upload** to start burning. 8. Go to **hi3516dv300** > **Upload** to start burning.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again. > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png) ![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png)
......
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-building.md
浏览文件 @ 3893e225
# Building # Building
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Building Source Code](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3861-build.md).
1. In **Projects**, click **Settings**. The Hi3861 configuration page is displayed. 1. In **Projects**, click **Settings**. The Hi3861 configuration page is displayed.
...@@ -8,6 +10,7 @@ ...@@ -8,6 +10,7 @@
2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools. 2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again. > If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again.
![en-us_image_0000001221025048](figures/en-us_image_0000001221025048.png) ![en-us_image_0000001221025048](figures/en-us_image_0000001221025048.png)
......
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md
浏览文件 @ 3893e225
# Burning # Burning
Hi3861 V100 supports burning through the serial port. To burn source code through the serial port in Windows, perform the following steps: Hi3861 V100 supports burning through the serial port. To burn source code through the serial port in Windows, perform the following steps:
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Burning an Image](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3861-burn.md).
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). 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).
...@@ -14,6 +17,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug ...@@ -14,6 +17,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![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. > 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. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
...@@ -21,6 +25,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug ...@@ -21,6 +25,7 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
![en-us_image_0000001216274840](figures/en-us_image_0000001216274840.png) ![en-us_image_0000001216274840](figures/en-us_image_0000001216274840.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433). > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**. 4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
......
en/device-dev/quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md
浏览文件 @ 3893e225
...@@ -40,6 +40,10 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -40,6 +40,10 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
2. Download the [DevEco Device Tool 3.0 Release Linux version](https://device.harmonyos.com/cn/ide#download). 2. Download the [DevEco Device Tool 3.0 Release Linux version](https://device.harmonyos.com/cn/ide#download).
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Setting Up the Ubuntu Environment](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-env-ubuntu.md).
3. Decompress the DevEco Device Tool software package and assign permission on the folder obtained from the decompression. 3. Decompress the DevEco Device Tool software package and assign permission on the folder obtained from the decompression.
1. Go to the directory where the DevEco Device Tool software package is stored and run the following command to decompress the software package. In the command, change **devicetool-linux-tool-3.0.0.401.zip** to the actual software package name. 1. Go to the directory where the DevEco Device Tool software package is stored and run the following command to decompress the software package. In the command, change **devicetool-linux-tool-3.0.0.401.zip** to the actual software package name.
...@@ -55,16 +59,17 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -55,16 +59,17 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name. 4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python. > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
``` ```
sudo ./devicetool-linux-tool-3.0.0.401.sh sudo ./devicetool-linux-tool-3.0.0.401.sh
``` ```
Wait until the "Deveco Device Tool successfully installed." message is displayed. Wait until the "Deveco Device Tool successfully installed." message is displayed.
![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png) ![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png)
...@@ -74,13 +79,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -74,13 +79,18 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. Download the [DevEco Device Tool 3.0 Release](https://device.harmonyos.com/cn/ide#download) Windows edition. 1. Download the [DevEco Device Tool 3.0 Release](https://device.harmonyos.com/cn/ide#download) Windows edition.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Setting Up the Windows Environment](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-env-win.md).
2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**. 2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**.
3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive. 3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version. > If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version.
> >
> ![en-us_image_0000001239275843](figures/en-us_image_0000001239275843.png) > ![en-us_image_0000001239275843](figures/en-us_image_0000001239275843.png)
![en-us_image_0000001270076961](figures/en-us_image_0000001270076961.png) ![en-us_image_0000001270076961](figures/en-us_image_0000001270076961.png)
...@@ -90,15 +100,17 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -90,15 +100,17 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. On the **VSCode installation confirm** page, select **Install VScode 1.62.2 automatically** and click **Next**. 1. On the **VSCode installation confirm** page, select **Install VScode 1.62.2 automatically** and click **Next**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If Visual Studio Code 1.62 or later has been installed, this step will be skipped. > If Visual Studio Code 1.62 or later has been installed, this step will be skipped.
![en-us_image_0000001237801283](figures/en-us_image_0000001237801283.png) ![en-us_image_0000001237801283](figures/en-us_image_0000001237801283.png)
2. On the displayed **Python select page**, select **Download from Huawei mirror** and click **Next**. 2. On the displayed **Python select page**, select **Download from Huawei mirror** and click **Next**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If Python 3.8 or 3.9 has been installed, select **Use one of compatible on your PC**. > If Python 3.8 or 3.9 has been installed, select **Use one of compatible on your PC**.
![en-us_image_0000001193983334](figures/en-us_image_0000001193983334.png) ![en-us_image_0000001193983334](figures/en-us_image_0000001193983334.png)
5. In the dialog box shown below, click **Next** to download and install the tools.. 5. In the dialog box shown below, click **Next** to download and install the tools..
...@@ -121,10 +133,11 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -121,10 +133,11 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
1. In Ubuntu, open the Terminal tool and run the following command to install the SSH service: 1. In Ubuntu, open the Terminal tool and run the following command to install the SSH service:
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the command fails to be executed and the system displays a message indicating that the openssh-server and openssh-client depend on different versions, install the openssh-client of the required version (for example, **sudo apt-get install openssh-client=1:8.2p1-4**) as prompted on the command-line interface (CLI) and run the command again to install the openssh-server. > If the command fails to be executed and the system displays a message indicating that the openssh-server and openssh-client depend on different versions, install the openssh-client of the required version (for example, **sudo apt-get install openssh-client=1:8.2p1-4**) as prompted on the command-line interface (CLI) and run the command again to install the openssh-server.
``` ```
sudo apt-get install openssh-server sudo apt-get install openssh-server
``` ```
......
en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-build.md
浏览文件 @ 3893e225
# Building # Building
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Getting Started with the Standard System with Hi3516 (IDE Mode)](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-appendix-hi3516-ide.md).
1. In **Projects**, click **Settings**. The Hi3516D V300 configuration page is displayed. 1. In **Projects**, click **Settings**. The Hi3516D V300 configuration page is displayed.
...@@ -8,6 +11,7 @@ ...@@ -8,6 +11,7 @@
2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools. 2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again. > If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again.
![en-us_image_0000001227277128](figures/en-us_image_0000001227277128.png) ![en-us_image_0000001227277128](figures/en-us_image_0000001227277128.png)
......
en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
浏览文件 @ 3893e225
...@@ -3,6 +3,9 @@ ...@@ -3,6 +3,9 @@
To burn source code to Hi3516D V300 through the USB port in Windows, perform the following steps: To burn source code to Hi3516D V300 through the USB port in Windows, perform the following steps:
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Getting Started with the Standard System with Hi3516 (IDE Mode)](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-appendix-hi3516-ide.md).
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). 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).
...@@ -14,6 +17,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the ...@@ -14,6 +17,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) ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![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. > 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. 3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
...@@ -21,6 +25,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the ...@@ -21,6 +25,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the
![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png) ![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695). > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**. 4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
...@@ -44,6 +49,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the ...@@ -44,6 +49,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the
2. In **Partition Options**, modify the items selected in the preceding step. 2. In **Partition Options**, modify the items selected in the preceding step.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap. > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png) ![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png)
...@@ -55,6 +61,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the ...@@ -55,6 +61,7 @@ To burn source code to Hi3516D V300 through the USB port in Windows, perform the
8. Go to **hi3516dv300** > **Upload** to start burning. 8. Go to **hi3516dv300** > **Upload** to start burning.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again. > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png) ![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png)
......
en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-build.md
浏览文件 @ 3893e225
# Building # Building
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Building Source Code](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3568-build.md).
1. In **Projects**, click **Settings**. The HH-SCDY200 configuration page is displayed. 1. In **Projects**, click **Settings**. The HH-SCDY200 configuration page is displayed.
...@@ -8,6 +11,7 @@ ...@@ -8,6 +11,7 @@
2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools. 2. On the **toolchain** tab page, DevEco Device Tool automatically checks whether the dependent compilation toolchain is complete. If a message is displayed indicating that some tools are missing, click **SetUp** to automatically install the required tools.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again. > If the pip component fails to be installed, [change the Python](https://device.harmonyos.com/en/docs/documentation/guide/ide-set-python-source-0000001227639986) source and try again.
![en-us_image_0000001221356692](figures/en-us_image_0000001221356692.png) ![en-us_image_0000001221356692](figures/en-us_image_0000001221356692.png)
......
en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
浏览文件 @ 3893e225
# Burning # Burning
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> In this document, the DevEco Device Tool 3.0 Release version is used as an example. The UI and usage of DevEco Device Tool vary by version. If you are using the latest version of DevEco Device Tool, perform instructions in [Burning an Image](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-ide-3568-burn.md).
1. [Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) **DriverInstall.exe**. Double-click **DriverInstall.exe** to open the installer. Then click the install button to install the USB driver as prompted. 1. [Download](https://gitee.com/hihope_iot/docs/blob/master/HiHope_DAYU200/%E7%83%A7%E5%86%99%E5%B7%A5%E5%85%B7%E5%8F%8A%E6%8C%87%E5%8D%97/windows/DriverAssitant_v5.1.1.zip) **DriverInstall.exe**. Double-click **DriverInstall.exe** to open the installer. Then click the install button to install the USB driver as prompted.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the burning tool of an earlier version has been installed, uninstall it first. > If the burning tool of an earlier version has been installed, uninstall it first.
2. Connect the computer to the target development board through the USB port. 2. Connect the computer to the target development board through the USB port.
...@@ -15,7 +19,8 @@ ...@@ -15,7 +19,8 @@
![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png) ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png)
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![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. > 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. 4. In DevEco Device Tool, choose QUICK ACCESS > DevEco Home > Projects, and then click Settings.
...@@ -37,7 +42,8 @@ ...@@ -37,7 +42,8 @@
2. In **Partition Options**, modify the items selected in the preceding step. 2. In **Partition Options**, modify the items selected in the preceding step.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap. > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
![en-us_image_0000001268653461](figures/en-us_image_0000001268653461.png) ![en-us_image_0000001268653461](figures/en-us_image_0000001268653461.png)
...@@ -52,9 +58,10 @@ ...@@ -52,9 +58,10 @@
9. If the message "Operation paused, Please press Enter key to continue" is displayed, press **Enter**. 9. If the message "Operation paused, Please press Enter key to continue" is displayed, press **Enter**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
>
> If the message "The boad is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key. > If the message "The boad is not in Loader mode. Please Hold on the VOL+key..." is displayed, place the development board in Loader mode as follows: Press and hold the Volume+ key for 3 seconds, press the RESET key, wait for 3 seconds, and then release the Volume+ key.
10. Wait until the burning is complete. If the following message is displayed, the burning is successful. 10. Wait until the burning is complete. If the following message is displayed, the burning is successful.
![en-us_image_0000001194984912](figures/en-us_image_0000001194984912.png) ![en-us_image_0000001194984912](figures/en-us_image_0000001194984912.png)
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或