Skip to content

D
Docs

OpenHarmony / Docs
接近 2 年 前同步成功

通知 159
Star 292
Fork 28
D
Docs
提交 3b2df328 编写于 作者: E ester.zhou
浏览文件
操作

update quick-start folder 

Signed-off-by: Nester.zhou <ester.zhou@huawei.com>
上级 d57fcbc5
隐藏空白更改
内联 并排
Showing with 258 addition and 590 deletion
en/device-dev/quick-start/Readme-EN.md
浏览文件 @ 3b2df328
...@@ -7,14 +7,14 @@ ...@@ -7,14 +7,14 @@
- [Creating a Source Code Project](quickstart-ide-lite-create-project.md) - [Creating a Source Code Project](quickstart-ide-lite-create-project.md)
- Running a Hello World Program - Running a Hello World Program
- Hi3861 Development Board - Hi3861 Development Board
- [Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-application-framework.md) - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-helloworld.md)
- [Building](quickstart-ide-lite-steps-hi3861-building.md) - [Building](quickstart-ide-lite-steps-hi3861-building.md)
- [Burning](quickstart-ide-lite-steps-hi3861-burn.md) - [Burning](quickstart-ide-lite-steps-hi3861-burn.md)
- [Networking](quickstart-ide-lite-steps-hi3861-netconfig.md) - [Networking](quickstart-ide-lite-steps-hi3861-netconfig.md)
- [Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md) - [Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md)
- [Running](quickstart-ide-lite-steps-hi3861-running.md) - [Running](quickstart-ide-lite-steps-hi3861-running.md)
- Hi3516 Development Board - Hi3516 Development Board
- [Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-application-framework.md) - [Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-helloworld.md)
- [Building](quickstart-ide-lite-steps-hi3516-building.md) - [Building](quickstart-ide-lite-steps-hi3516-building.md)
- [Burning](quickstart-ide-lite-steps-hi3516-burn.md) - [Burning](quickstart-ide-lite-steps-hi3516-burn.md)
- [Running](quickstart-ide-lite-steps-hi3516-running.md) - [Running](quickstart-ide-lite-steps-hi3516-running.md)
...@@ -28,7 +28,7 @@ ...@@ -28,7 +28,7 @@
- Running a Hello World Program - Running a Hello World Program
- Hi3861 Development Board - Hi3861 Development Board
- [Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md) - [Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)
- [Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md) - [Writing a Hello World Program](quickstart-lite-steps-hi3861-helloworld.md)
- [Building](quickstart-lite-steps-hi3861-building.md) - [Building](quickstart-lite-steps-hi3861-building.md)
- [Burning](quickstart-lite-steps-hi3861-burn.md) - [Burning](quickstart-lite-steps-hi3861-burn.md)
- [Networking](quickstart-lite-steps-hi3861-netconfig.md) - [Networking](quickstart-lite-steps-hi3861-netconfig.md)
...@@ -36,7 +36,7 @@ ...@@ -36,7 +36,7 @@
- [Running](quickstart-lite-steps-hi3861-running.md) - [Running](quickstart-lite-steps-hi3861-running.md)
- Hi3516 Development Board - Hi3516 Development Board
- [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md) - [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)
- [Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md) - [Writing a Hello World Program](quickstart-lite-steps-hi3516-helloworld.md)
- [Building](quickstart-lite-steps-hi3516-building.md) - [Building](quickstart-lite-steps-hi3516-building.md)
- [Burning](quickstart-lite-steps-hi3516-burn.md) - [Burning](quickstart-lite-steps-hi3516-burn.md)
- [Running](quickstart-lite-steps-hi3516-running.md) - [Running](quickstart-lite-steps-hi3516-running.md)
...@@ -75,7 +75,7 @@ ...@@ -75,7 +75,7 @@
- [Setting Up Environments for Standard System](quickstart-standard-env-setup.md) - [Setting Up Environments for Standard System](quickstart-standard-env-setup.md)
- Running a Hello World Program - Running a Hello World Program
- Hi3516 Development Board - Hi3516 Development Board
- [Writing a Hello World Program](quickstart-standard-running-hi3516-create.md) - [Writing a Hello World Program](quickstart-std-3516-create.md)
- [Building](quickstart-standard-running-hi3516-build.md) - [Building](quickstart-standard-running-hi3516-build.md)
- [Burning](quickstart-standard-running-hi3516-burning.md) - [Burning](quickstart-standard-running-hi3516-burning.md)
- [Running](quickstart-standard-running-hi3516-running.md) - [Running](quickstart-standard-running-hi3516-running.md)
......
en/device-dev/quick-start/quickstart-docker-lite.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Getting Started with Mini and Small Systems (Installation Package Mode)
- **[Mini and Small System Overview](quickstart-lite-overview.md)**
- **[Setting Up Environments for the Mini and Small Systems](quickstart-lite-env-setup.md)**
- **[Running a Hello World Program](quickstart-lite-steps.md)**
- **[FAQs](quickstart-lite-env-setup-faqs.md)**
- **[Appendix](quickstart-lite-appendix.md)**
en/device-dev/quick-start/quickstart-ide-lite-appendix.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Appendix
- **[Introduction to Development Boards](quickstart-ide-lite-board-introduction.md)**
en/device-dev/quick-start/quickstart-ide-lite-board-introduction.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Introduction to Development Boards
- **[Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md)**
- **[Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md)**
en/device-dev/quick-start/quickstart-ide-lite-create-project.md
浏览文件 @ 3b2df328
# Creating a Source Code Project # Importing a Source Code Project
After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-lite-sourcecode-acquire.md), perform the following steps to create a source code project in Windows: After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-lite-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:
...@@ -15,7 +15,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st ...@@ -15,7 +15,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st
![en-us_image_0000001271477045](figures/en-us_image_0000001271477045.png) ![en-us_image_0000001271477045](figures/en-us_image_0000001271477045.png)
3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue. 3. If this is the first time you import a project, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
![en-us_image_0000001135394334](figures/en-us_image_0000001135394334.png) ![en-us_image_0000001135394334](figures/en-us_image_0000001135394334.png)
......
en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md
浏览文件 @ 3b2df328
...@@ -11,15 +11,18 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -11,15 +11,18 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
- Windows: Windows 10 (64-bit) - Windows: Windows 10 (64-bit)
- Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher. - Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher
- User name: cannot contain Chinese characters - User name (Ubuntu): cannot contain Chinese characters
- DevEco Device Tool: 3.0 Release - DevEco Device Tool: 3.0 Release
## Setting Up the Ubuntu Development Environment ## Setting Up the Ubuntu Development Environment
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> If the Ubuntu system has not been set up yet, set it up on a virtual machine running Windows. Then, configure the Ubuntu basic environment.
1. Make sure the Ubuntu shell environment is **bash**. 1. Make sure the Ubuntu shell environment is **bash**.
1. Run the following command and check whether the command output is **bash**. If the command output is not **bash**, go to step 2. 1. Run the following command and check whether the command output is **bash**. If the command output is not **bash**, go to step 2.
...@@ -55,14 +58,15 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits ...@@ -55,14 +58,15 @@ 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>
> 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
``` ```
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> 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 page for agreeing to the user agreement and privacy statement is displayed. Read and agree to the user agreement and privacy statement.
>
> If this page is not displayed and the installation exits, run the apt-get install whiptail command, then the installation command.
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)
...@@ -76,7 +80,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -76,7 +80,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
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 to a path that does not contain any Chinese characters, and then 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.
...@@ -101,11 +105,14 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -101,11 +105,14 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
![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**.
![en-us_image_0000001239634067](figures/en-us_image_0000001239634067.png) ![en-us_image_0000001239634067](figures/en-us_image_0000001239634067.png)
6. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard. 6. Read the user agreement and privacy statement carefully, select I accept the licenses, and click **Next**.
![en-us_image_0000001307019009](figures/en-us_image_0000001307019009.png)
7. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard.
![en-us_image_0000001239650137](figures/en-us_image_0000001239650137.png) ![en-us_image_0000001239650137](figures/en-us_image_0000001239650137.png)
...@@ -174,29 +181,9 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits ...@@ -174,29 +181,9 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
![en-us_image_0000001215720398](figures/en-us_image_0000001215720398.png) ![en-us_image_0000001215720398](figures/en-us_image_0000001215720398.png)
5. In the displayed dialog box, select **Linux**, select **Continue**, and enter the password for logging in to the remote computer. 5. In the displayed dialog box, select **Linux**, select **Continue**, and enter the password for logging in to the remote computer.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
> To eliminate the need for frequently entering the password for logging in to the remote computer, set an SSH public key.
![en-us_image_0000001215897530](figures/en-us_image_0000001215897530.png) ![en-us_image_0000001215897530](figures/en-us_image_0000001215897530.png)
After the connection is successful, the plug-in is automatically installed in the .vscode-server folder on the remote computer. After the installation is complete, reload Visual Studio Code in Windows as prompted. Then you can develop, compile, and burn source code in DevEco Device Tool on Windows. After the connection is successful, the plug-in is automatically installed in the .vscode-server folder on the remote computer. After the installation is complete, reload Visual Studio Code in Windows as prompted. Then you can develop, compile, and burn source code in DevEco Device Tool on Windows.
### Registering the Public Key for Accessing the Ubuntu Environment
After the preceding operations are complete, you can remotely connect to the Ubuntu environment through Windows for development. However, you need to frequently enter the remote connection password. To eliminate this need, you can use the SSH public key.
1. Open the Git bash CLI and run the following command to generate an SSH public key. During command execution, perform operations as prompted. Set **username** and **ip** to the user name and IP address you use for connecting to the Ubuntu system.
```
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub username@ip
```
![en-us_image_0000001271532317](figures/en-us_image_0000001271532317.png)
2. In Visual Studio Code, click the remote connection setting button and open the **config** file.
![en-us_image_0000001226034634](figures/en-us_image_0000001226034634.png)
3. In the **config** file, add the SSK key file information, as shown below. Then save the file.
![en-us_image_0000001270356233](figures/en-us_image_0000001270356233.png)
en/device-dev/quick-start/quickstart-ide-lite-env-setup.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Environment Preparation
- **[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)**
en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md
浏览文件 @ 3b2df328
...@@ -7,7 +7,7 @@ Hi3861 is a 2 x 5 cm development board. It is a 2.4 GHz WLAN SoC chip that highl ...@@ -7,7 +7,7 @@ Hi3861 is a 2 x 5 cm development board. It is a 2.4 GHz WLAN SoC chip that highl
**Figure 1** Hi3861 development board **Figure 1** Hi3861 development board
![en-us_image_0000001226634692](figures/en-us_image_0000001226634692.png) ![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. 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.
......
en/device-dev/quick-start/quickstart-ide-lite-overview.md
浏览文件 @ 3b2df328
...@@ -10,7 +10,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge ...@@ -10,7 +10,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
- IDE mode: DevEco Device Tool is used for one-stop development, covering dependency installation, building, burning, and running. - IDE mode: DevEco Device Tool is used for one-stop development, covering dependency installation, building, burning, and running.
- Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool. - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool.
OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode. OpenHarmony also provides the [Docker environment](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.
This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-overview.md). This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-overview.md).
......
en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md
浏览文件 @ 3b2df328
...@@ -10,7 +10,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -10,7 +10,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
2. Register an SSH public key for access to Gitee. 2. Register an SSH public key for access to Gitee.
3. Install the git client and git-lfs. 3. Install the git client and git-lfs if they are unavailable.
Update the software source: Update the software source:
...@@ -18,7 +18,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -18,7 +18,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
sudo apt-get update sudo apt-get update
``` ```
Run the following command to install the tools: Run the following command to install the tools:
``` ```
sudo apt-get install git git-lfs sudo apt-get install git git-lfs
...@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
``` ```
## Procedure ## 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. > 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.
...@@ -70,7 +70,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -70,7 +70,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
For details about how to obtain the source code of an OpenHarmony release, see the [Release-Notes](../../release-notes/Readme.md). For details about how to obtain the source code of an OpenHarmony release, see the [Release-Notes](../../release-notes/Readme.md).
## Running prebuilts ### 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:
......
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
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.
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).
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
>
> - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
>
> - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
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). 2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
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).
- 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_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. - 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) ![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 build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. 4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
![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** 5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
> 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**.
![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png) ![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png)
5. On the **hi3516dv300** tab page, set the burning options. 6. On the **hi3516dv300** tab page, set the burning options.
- **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time. - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained. - **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**. - **upload_protocol**: Select the burning protocol **hiburn-usb**.
![en-us_image_0000001223190441](figures/en-us_image_0000001223190441.png) ![en-us_image_0000001223190441](figures/en-us_image_0000001223190441.png)
6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**. 7. In **Partitions**, check the preset burning settings of the files to be burnt.
1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
![en-us_image_0000001198889702](figures/en-us_image_0000001198889702.png)
2. In **Partition Options**, modify the items selected in the preceding step.
> ![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.
![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png) ![en-us_image_0000001312778829](figures/en-us_image_0000001312778829.png)
3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files. To modify the burning settings for a specific file, click ![en-us_image_0000001312898911](figures/en-us_image_0000001312898911.png) next to the file.
> ![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.
7. When you finish modifying, click **Save** on the top. ![en-us_image_0000001312780249](figures/en-us_image_0000001312780249.png)
8. Go to **hi3516dv300** > **Upload** to start burning. 8. When you finish modifying, click **Save** on the top.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE** 9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning.
> 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_0000001266887264](figures/en-us_image_0000001266887264.png)
9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning. 10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning.
![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png) ![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png)
If the following message is displayed, it indicates that the burning is successful. If the following message is displayed, it indicates that the burning is successful.
![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png) ![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png)
10. When the burning is successful, perform the operations in Running an Image to start the system. 11. When the burning is successful, perform the operations in Running to start the system.
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md
浏览文件 @ 3b2df328
...@@ -30,13 +30,13 @@ After burning is completed, you need to configure the bootloader to run the Open ...@@ -30,13 +30,13 @@ After burning is completed, you need to configure the bootloader to run the Open
After the system is started, perform the following steps to run the Hello World program: After the system is started, perform the following steps to run the Hello World program:
1. Go to the **bin** directory on the startup page. 1. Go to the **bin** directory on the startup page.
``` ```
cd bin cd bin
``` ```
2. Run the following command to run the **helloworld** program: 2. Run the following command to run the **helloworld** program:
``` ```
./helloworld ./helloworld
``` ```
...@@ -48,4 +48,4 @@ After the system is started, perform the following steps to run the Hello World ...@@ -48,4 +48,4 @@ After the system is started, perform the following steps to run the Hello World
## Next ## Next
Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](https://gitee.com/openharmony/docs/blob/master/en/device-dev/guide/device-camera.md) to better familiarize yourself with OpenHarmony development. Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](../guide/device-camera-control-overview.md) to better familiarize yourself with OpenHarmony development.
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3516 Development Board
- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-application-framework.md)**
- **[Building](quickstart-ide-lite-steps-hi3516-building.md)**
- **[Burning](quickstart-ide-lite-steps-hi3516-burn.md)**
- **[Running](quickstart-ide-lite-steps-hi3516-running.md)**
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
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:
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).
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). 2. If your computer does not have the USB-to-serial driver, install it by following the instructions in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
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_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. - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon.
...@@ -16,18 +19,17 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug ...@@ -16,18 +19,17 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
> ![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. 4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
![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**
> 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**. 5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
![en-us_image_0000001198943768](figures/en-us_image_0000001198943768.png) ![en-us_image_0000001198943768](figures/en-us_image_0000001198943768.png)
5. On the **hi3861** tab page, set the burning options. 6. On the **hi3861** tab page, set the burning options.
- **upload_port**: Select the serial port number obtained. - **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-serial**. - **upload_protocol**: Select the burning protocol **hiburn-serial**.
...@@ -35,22 +37,24 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug ...@@ -35,22 +37,24 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
![en-us_image_0000001243704061](figures/en-us_image_0000001243704061.png) ![en-us_image_0000001243704061](figures/en-us_image_0000001243704061.png)
6. Check the preset information of the files to be burnt and modify them when necessary. 7. In **Partitions**, check the preset burning settings of the files to be burnt.
![en-us_image_000000131299335](figures/en-us_image_000000131299335.png)
On the **hi3861_app** tab page, select **partition_bin** from **New Option**, and set the path of the file to be burnt. To modify the burning settings for a specific file, click ![en-us_image_0000001312898911](figures/en-us_image_0000001312898911.png) next to the file.
![en-us_image_0000001260919759](figures/en-us_image_0000001260919759.png) ![en-us_image_0000001312912501](figures/en-us_image_0000001312912501.png)
7. When you finish modifying, click **Save** on the top. 8. When you finish modifying, click **Save** on the top.
8. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning. 9. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning.
![en-us_image_0000001216440138](figures/en-us_image_0000001216440138.png) ![en-us_image_0000001216440138](figures/en-us_image_0000001216440138.png)
9. When the following information is displayed, press the RST button on the development board to restart it. 10. When the following information is displayed, press the RST button on the development board within 15 seconds to restart it.
![en-us_image_0000001198466090](figures/en-us_image_0000001198466090.png) ![en-us_image_0000001198466090](figures/en-us_image_0000001198466090.png)
10. Wait until the burning is complete. When the following message is displayed, the burning is successful. When the following message is displayed, the burning is successful.
![en-us_image_0000001216761476](figures/en-us_image_0000001216761476.png) ![en-us_image_0000001216761476](figures/en-us_image_0000001216761476.png)
\ No newline at end of file \ No newline at end of file
en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3861 Development Board
- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-application-framework.md)**
- **[Building](quickstart-ide-lite-steps-hi3861-building.md)**
- **[Burning](quickstart-ide-lite-steps-hi3861-burn.md)**
- **[Networking](quickstart-ide-lite-steps-hi3861-netconfig.md)**
- **[Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md)**
- **[Running](quickstart-ide-lite-steps-hi3861-running.md)**
en/device-dev/quick-start/quickstart-ide-lite-steps.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Running a Hello World Program
- **[Hi3861 Development Board](quickstart-ide-lite-steps-hi3861.md)**
- **[Hi3516 Development Board](quickstart-ide-lite-steps-hi3516.md)**
en/device-dev/quick-start/quickstart-ide-lite.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Getting Started with Mini and Small Systems (IDE Mode)
- **[Mini and Small System Overview](quickstart-ide-lite-overview.md)**
- **[Environment Preparation](quickstart-ide-lite-env-setup.md)**
- **[Creating a Source Code Project](quickstart-ide-lite-create-project.md)**
- **[Running a Hello World Program](quickstart-ide-lite-steps.md)**
- **[Appendix](quickstart-ide-lite-appendix.md)**
en/device-dev/quick-start/quickstart-ide-standard-appendix.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Appendix
- **[Introduction to Development Boards](quickstart-ide-standard-board-introduction.md)**
en/device-dev/quick-start/quickstart-ide-standard-board-introduction.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Introduction to Development Boards
- **[Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)**
- **[Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)**
en/device-dev/quick-start/quickstart-ide-standard-create-project.md
浏览文件 @ 3b2df328
# Creating a Source Code Project # Importing a Source Code Project
After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-standard-sourcecode-acquire.md), perform the following steps to create a source code project in Windows: After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-standard-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:
...@@ -23,7 +23,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st ...@@ -23,7 +23,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st
![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png) ![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png)
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 **Ohos Ver**. The following figure uses **Hi3516DV300** as an example. 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**<br/> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>
> - Set **Product** to **Hi3516DV300** for the Hi3516D V300 development board. > - Set **Product** to **Hi3516DV300** for the Hi3516D V300 development board.
......
en/device-dev/quick-start/quickstart-ide-standard-env-setup.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Environment Preparation
- **[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)**
en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**<br>
> - If you are using source code from the master branch released since May 9, 2022, use HiTool for burning.
>
> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
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**
> This feature is available in DevEco Device Tool 2.2 Beta2 and later versions.
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).
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE** 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 you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
>
> - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
>
> - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
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).
- 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_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. - 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) ![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 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.
4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool. ![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png)
![en-us_image_0000001267932252](figures/en-us_image_0000001267932252.png) > ![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).
5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**. 4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png) ![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png)
6. On the **hi3516dv300** tab page, set the burning options. 5. On the **hi3516dv300** tab page, set the burning options.
- **upload_partitions**: Select the files to be burnt. By default, **fastboot**, **boot**, **updater**, **misc**, **system**, **vendor**, and **userdata** are burnt at the same time. - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained. - **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**. - **upload_protocol**: Select the burning protocol **hiburn-usb**.
![en-us_image_0000001177478136](figures/en-us_image_0000001177478136.png) ![en-us_image_0000001223190441](figures/en-us_image_0000001223190441.png)
6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
![en-us_image_0000001198889702](figures/en-us_image_0000001198889702.png)
7. In **Partitions**, check the preset burning settings of the files to be burnt. 2. In **Partition Options**, modify the items selected in the preceding step.
![en-us_image_0000001312541849](figures/en-us_image_0000001312541849.png) > ![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.
To modify the burning settings for a specific file, click ![en-us_image_0000001265361888](figures/en-us_image_0000001265361888.png) next to the file. ![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png)
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**<br> 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
>
> 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_0000001264982466](figures/en-us_image_0000001264982466.png) 7. When you finish modifying, click **Save** on the top.
8. When you finish modifying, click **Save** on the top. 8. Go to **hi3516dv300** > **Upload** to start burning.
9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning. > ![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.
![en-us_image_0000001267532292](figures/en-us_image_0000001267532292.png) ![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png)
10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning. 9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png) ![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png)
If the following message is displayed, it indicates that the burning is successful. If the following message is displayed, it indicates that the burning is successful.
![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png) ![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png)
11. When the burning is successful, perform the operations in Running to start the system. 10. When the burning is successful, perform the operations in Running an Image to start the system.
en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-create.md
浏览文件 @ 3b2df328
...@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board. ...@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board.
The complete code directory is as follows: The complete code directory is as follows:
``` ```
applications/sample/hello applications/sample/hello
│── BUILD.gn │── BUILD.gn
...@@ -34,7 +34,7 @@ Perform the steps below in the source code directory: ...@@ -34,7 +34,7 @@ Perform the steps below in the source code directory:
Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program. Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program.
``` ```
#include <stdio.h> #include <stdio.h>
#include "helloworld.h" #include "helloworld.h"
...@@ -55,7 +55,7 @@ Perform the steps below in the source code directory: ...@@ -55,7 +55,7 @@ Perform the steps below in the source code directory:
Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows: Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows:
``` ```
#ifndef HELLOWORLD_H #ifndef HELLOWORLD_H
#define HELLOWORLD_H #define HELLOWORLD_H
...@@ -78,7 +78,7 @@ Perform the steps below in the source code directory: ...@@ -78,7 +78,7 @@ Perform the steps below in the source code directory:
2. Create a build file. 2. Create a build file.
1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows: 1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows:
``` ```
import("//build/ohos.gni") # Import the build template. import("//build/ohos.gni") # Import the build template.
ohos_executable("helloworld") {# Executable module. ohos_executable("helloworld") {# Executable module.
...@@ -99,7 +99,7 @@ Perform the steps below in the source code directory: ...@@ -99,7 +99,7 @@ Perform the steps below in the source code directory:
} }
``` ```
2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows: 2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows:
``` ```
{ {
"name": "@ohos/hello", "name": "@ohos/hello",
...@@ -141,7 +141,7 @@ Perform the steps below in the source code directory: ...@@ -141,7 +141,7 @@ Perform the steps below in the source code directory:
Add the configuration of the new subsystem to the **build/subsystem_config.json** file. Add the configuration of the new subsystem to the **build/subsystem_config.json** file.
``` ```
"sample": { "sample": {
"path": "applications/sample/hello", "path": "applications/sample/hello",
...@@ -151,9 +151,9 @@ Perform the steps below in the source code directory: ...@@ -151,9 +151,9 @@ Perform the steps below in the source code directory:
4. Modify the product configuration file. 4. Modify the product configuration file.
In the **vendor\hisilicon\Hi3516DV300\config.json** file, add the **hello** part after the existing part. In the vendor\hisilicon\Hi3516DV300\config.json file, add the hello part after the existing part.
``` ```
"usb:usb_manager_native":{}, "usb:usb_manager_native":{},
"applications:prebuilt_hap":{}, "applications:prebuilt_hap":{},
......
en/device-dev/quick-start/quickstart-ide-standard-running-hi3516.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3516 Development Board
- **[Writing a Hello World Program](quickstart-ide-standard-running-hi3516-create.md)**
- **[Building](quickstart-ide-standard-running-hi3516-build.md)**
- **[Burning](quickstart-ide-standard-running-hi3516-burning.md)**
- **[Running](quickstart-ide-standard-running-hi3516-running.md)**
en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-burning.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> - If you are using source code from the master branch released since May 9, 2022, use RKDevTool for burning.
>
> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
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**<br>
> 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.
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**<br>If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host: 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).
>
> - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
>
> - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
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).
- 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_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. - 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) ![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**<br>
> 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. Open 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.
![en-us_image_0000001239661509](figures/en-us_image_0000001239661509.png) ![en-us_image_0000001239661509](figures/en-us_image_0000001239661509.png)
...@@ -44,28 +29,32 @@ Burning is the process of downloading compiled program files to a development bo ...@@ -44,28 +29,32 @@ Burning is the process of downloading compiled program files to a development bo
![en-us_image_0000001194504874](figures/en-us_image_0000001194504874.png) ![en-us_image_0000001194504874](figures/en-us_image_0000001194504874.png)
6. In **Partitions**, check the preset burning settings of the files to be burnt. 6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **loader**, **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata**.
![en-us_image_0000001265041892](figures/en-us_image_0000001265041892.png) 1. On the **hh_scdy200_loader** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
To modify the burning settings for a specific file, click ![en-us_image_0000001265361888](figures/en-us_image_0000001265361888.png) next to the file. ![en-us_image_0000001224173270](figures/en-us_image_0000001224173270.png)
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**<br>
>
> 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_0000001265201928](figures/en-us_image_0000001265201928.png) 2. In **Partition Options**, modify the items selected in the preceding step.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> 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)
3. Follow the same procedure to modify the information about the **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata** files.
7. When you finish modifying, click **Save** on the top. 7. When you finish modifying, click **Save** on the top.
8. Choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning. 8. Click **Open** to open the project file. Click ![en-us_image_0000001239221905](figures/en-us_image_0000001239221905.png) to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
![en-us_image_0000001194821710](figures/en-us_image_0000001194821710.png) ![en-us_image_0000001194821710](figures/en-us_image_0000001194821710.png)
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>If the message "The board 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. > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> > 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.
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)
en/device-dev/quick-start/quickstart-ide-standard-running-rk3568-create.md
浏览文件 @ 3b2df328
...@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board. ...@@ -8,7 +8,7 @@ The following exemplifies how to run the first program on the development board.
The complete code directory is as follows: The complete code directory is as follows:
``` ```
applications/sample/hello applications/sample/hello
│── BUILD.gn │── BUILD.gn
...@@ -33,7 +33,7 @@ Perform the steps below in the source code directory: ...@@ -33,7 +33,7 @@ Perform the steps below in the source code directory:
Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program. Create the **applications/sample/hello/src/helloworld.c** directory and file whose code is shown in the following example. You can customize the content to be printed. For example, you can change **World** to **OHOS**. Declare the string printing function **HelloPrint** in the **helloworld.h** file. You can use either C or C++ to develop a program.
``` ```
#include <stdio.h> #include <stdio.h>
#include "helloworld.h" #include "helloworld.h"
...@@ -54,7 +54,7 @@ Perform the steps below in the source code directory: ...@@ -54,7 +54,7 @@ Perform the steps below in the source code directory:
Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows: Add the header file **applications/sample/hello/include/helloworld.h**. The sample code is as follows:
``` ```
#ifndef HELLOWORLD_H #ifndef HELLOWORLD_H
#define HELLOWORLD_H #define HELLOWORLD_H
...@@ -77,7 +77,7 @@ Perform the steps below in the source code directory: ...@@ -77,7 +77,7 @@ Perform the steps below in the source code directory:
2. Create a build file. 2. Create a build file.
1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows: 1. Create the **applications/sample/hello/BUILD.gn** file. The file content is as follows:
``` ```
import("//build/ohos.gni") # Import the build template. import("//build/ohos.gni") # Import the build template.
ohos_executable("helloworld") {# Executable module. ohos_executable("helloworld") {# Executable module.
...@@ -98,7 +98,7 @@ Perform the steps below in the source code directory: ...@@ -98,7 +98,7 @@ Perform the steps below in the source code directory:
} }
``` ```
2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows: 2. Create the **applications/sample/hello/bundle.json** file and add the description of the **sample** component. The content is as follows:
``` ```
{ {
"name": "@ohos/hello", "name": "@ohos/hello",
...@@ -140,7 +140,7 @@ Perform the steps below in the source code directory: ...@@ -140,7 +140,7 @@ Perform the steps below in the source code directory:
Add the configuration of the new subsystem to the **build/subsystem_config.json** file. Add the configuration of the new subsystem to the **build/subsystem_config.json** file.
``` ```
"sample": { "sample": {
"path": "applications/sample/hello", "path": "applications/sample/hello",
...@@ -150,7 +150,7 @@ Perform the steps below in the source code directory: ...@@ -150,7 +150,7 @@ Perform the steps below in the source code directory:
4. Modify the product configuration file. 4. Modify the product configuration file.
In the **vendor\hihope\rk3568\config.json** file, add the **hello** part after the existing part. In the vendor\hihope\rk3568\config.json file, add the hello part after the existing part.
``` ```
"usb:usb_manager_native":{}, "usb:usb_manager_native":{},
......
en/device-dev/quick-start/quickstart-ide-standard-running-rk3568.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# RK3568 Development Board
- **[Writing a Hello World Program](quickstart-ide-standard-running-rk3568-create.md)**
- **[Building](quickstart-ide-standard-running-rk3568-build.md)**
- **[Burning](quickstart-ide-standard-running-rk3568-burning.md)**
- **[Running](quickstart-ide-standard-running-rk3568-running.md)**
en/device-dev/quick-start/quickstart-ide-standard-running.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Running a Hello World Program
- **[Hi3516 Development Board](quickstart-ide-standard-running-hi3516.md)**
- **[RK3568 Development Board](quickstart-ide-standard-running-rk3568.md)**
en/device-dev/quick-start/quickstart-ide-standard-sourcecode-acquire.md
浏览文件 @ 3b2df328
...@@ -4,7 +4,7 @@ ...@@ -4,7 +4,7 @@
In the Ubuntu environment, perform the following steps to obtain the OpenHarmony source code: In the Ubuntu environment, perform the following steps to obtain the OpenHarmony source code:
## Preparations ## Before You Start
1. Register your account with Gitee. 1. Register your account with Gitee.
...@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -41,7 +41,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
``` ```
## Procedure ## Obtaining Source Code
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>
> 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. > 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.
......
en/device-dev/quick-start/quickstart-lite-appendix.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Appendix
- **[Introduction to Development Boards](quickstart-lite-board-introduction.md)**
- **[Reference](quickstart-lite-reference.md)**
en/device-dev/quick-start/quickstart-lite-board-introduction.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Introduction to Development Boards
- **[Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md)**
- **[Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md)**
en/device-dev/quick-start/quickstart-lite-env-setup-faqs.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# FAQs
- **[Fixing hb Installation Issues](quickstart-lite-faq-hb.md)**
- **[Fixing Compilation Issues](quickstart-lite-faq-compose.md)**
- **[Fixing Burning Issues](quickstart-lite-faq-burning.md)**
en/device-dev/quick-start/quickstart-lite-env-setup.md
浏览文件 @ 3b2df328
...@@ -278,7 +278,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -278,7 +278,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
``` ```
### Procedure ### Obtaining Source Code
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> 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. > 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.
...@@ -309,7 +309,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -309,7 +309,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
### Running prebuilts ### 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 bash build/prebuilts_download.sh
......
en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md
浏览文件 @ 3b2df328
# 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. Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
### Importing Source Code ### Importing Source Code
...@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu ...@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu
![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png) ![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png)
5. On the **Import Project** page, select **ipcamera_hispark_taurus** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**. 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**. Select **ipcamera_hispark_taurus**.
![en-us_image_0000001227711014](figures/en-us_image_0000001227711014.png) ![en-us_image_0000001227711014](figures/en-us_image_0000001227711014.png)
......
en/device-dev/quick-start/quickstart-lite-steps-hi3516.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3516 Development Board
- **[Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)**
- **[Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)**
- **[Building](quickstart-lite-steps-hi3516-building.md)**
- **[Burning](quickstart-lite-steps-hi3516-burn.md)**
- **[Running](quickstart-lite-steps-hi3516-running.md)**
en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md
浏览文件 @ 3b2df328
...@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu ...@@ -27,7 +27,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu
![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png) ![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png)
5. On the **Import Project** page, select **wifiiot_hispark_pegasus** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **ohosVersion**. 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**. Select **wifiiot_hispark_pegasus**.
![en-us_image_0000001272109325](figures/en-us_image_0000001272109325.png) ![en-us_image_0000001272109325](figures/en-us_image_0000001272109325.png)
......
en/device-dev/quick-start/quickstart-lite-steps-hi3861.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3861 Development Board
- **[Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)**
- **[Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md)**
- **[Building](quickstart-lite-steps-hi3861-building.md)**
- **[Burning](quickstart-lite-steps-hi3861-burn.md)**
- **[Networking](quickstart-lite-steps-hi3861-netconfig.md)**
- **[Debugging and Verification](quickstart-lite-steps-hi3861-debug.md)**
- **[Running](quickstart-lite-steps-hi3861-running.md)**
en/device-dev/quick-start/quickstart-lite-steps.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Running a Hello World Program
- **[Hi3861 Development Board](quickstart-lite-steps-hi3861.md)**
- **[Hi3516 Development Board](quickstart-lite-steps-hi3516.md)**
en/device-dev/quick-start/quickstart-standard-appendix.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Appendix
- **[Introduction to Development Boards](quickstart-standard-board-introduction.md)**
- **[Reference](quickstart-standard-reference.md)**
en/device-dev/quick-start/quickstart-standard-board-introduction.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Introduction to Development Boards
- **[Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)**
- **[Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)**
en/device-dev/quick-start/quickstart-standard-docker.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Getting Started with Standard System (Using the Installation Package)
- **[Standard System Overview](quickstart-standard-overview.md)**
- **[Setting Up Environments for Standard System](quickstart-standard-env-setup.md)**
- **[Running a Hello World Project](quickstart-standard-running.md)**
- **[FAQs](quickstart-standard-faqs.md)**
- **[Appendix](quickstart-standard-appendix.md)**
en/device-dev/quick-start/quickstart-standard-env-setup.md
浏览文件 @ 3b2df328
...@@ -32,14 +32,13 @@ In Ubuntu: ...@@ -32,14 +32,13 @@ In Ubuntu:
> - Java 8 or later is required. This section uses Java 8 as an example. > - Java 8 or later is required. This section uses Java 8 as an example.
2. Set Python 3.8 as the default Python version. 2. Set Python 3.8 as the default Python version.
Check the location of Python 3.8:
Check the location of Python 3.8:
``` ```
which python3.8 which python3.8
``` ```
Change python and python3 to python3.8. Change python and python3 to python3.8.
``` ```
...@@ -268,7 +267,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -268,7 +267,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
``` ```
### Procedure ### Obtaining Source Code
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> 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. > 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.
...@@ -299,7 +298,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony ...@@ -299,7 +298,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
### Running prebuilts ### 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 bash build/prebuilts_download.sh
......
en/device-dev/quick-start/quickstart-standard-faqs.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# FAQs
- **[Fixing hb Installation Issues](quickstart-standard-faq-hb.md)**
- **[Fixing Compilation Issues](quickstart-standard-faq-compose.md)**
- **[Fixing Burning Issues](quickstart-standard-faq-burning.md)**
en/device-dev/quick-start/quickstart-standard-ide.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Getting Started with Standard System (IDE Mode)
- **[Standard System Overview](quickstart-ide-standard-overview.md)**
- **[Environment Preparation](quickstart-ide-standard-env-setup.md)**
- **[Creating a Source Code Project](quickstart-ide-standard-create-project.md)**
- **[Running a Hello World Program](quickstart-ide-standard-running.md)**
- **[Appendix](quickstart-ide-standard-appendix.md)**
en/device-dev/quick-start/quickstart-standard-running-hi3516-build.md
浏览文件 @ 3b2df328
...@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor ...@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
1. Set the build path. 1. Set the build path.
``` ```
hb set hb set
``` ```
2. Select the current path. 2. Select the current path.
``` ```
. .
``` ```
3. Select **hispark_taurus_standard** under **hisilicon** and press **Enter**. 3. Select **Hi3516D V300** under **built-in** and press **Enter**.
4. Start building. 4. Start building.
...@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor ...@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
> >
> This example builds a product from the scratch. > This example builds a product from the scratch.
``` ```
hb build -f hb build -f
``` ```
**Figure 1** Hi3516 build settings **Figure 1** Hi3516 build settings
![en-us_image_0000001271562433](figures/en-us_image_0000001271562433.png) ![en-us_image_0000001271562433](figures/en-us_image_0000001271562433.png)
......
en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> - If you are using source code from the master branch released since May 9, 2022, use HiTool for burning.
>
> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
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.
## Importing Source Code ### Importing Source Code
[Ensure that the Windows system can remotely access the Ubuntu environment](../quick-start/quickstart-standard-env-setup.md), and then perform the following steps to import source code: After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-standard-env-setup.md). Then, perform the following steps to import the source code before burning:
1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code. 1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code.
![en-us_image_0000001278358765](figures/en-us_image_0000001278358765.png) ![en-us_image_0000001171426014](figures/en-us_image_0000001171426014.png)
2. Select the target directory (in the Ubuntu environment) and click **Import**. 2. Select the target directory (in the Ubuntu environment) and click **Import**.
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> Make sure the selected directory does not contain Chinese characters or spaces.
![en-us_image_0000001235266636](figures/en-us_image_0000001235266636.png) > ![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_0000001227711882](figures/en-us_image_0000001227711882.png)
3. If this is the first time you import the source code, the following dialog box will be displayed. Click **Import** when prompted. 3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
![en-us_image_0000001314076609](figures/en-us_image_0000001314076609.png) ![en-us_image_0000001135394334](figures/en-us_image_0000001135394334.png)
4. On the **Select Project type** page, select **Import from OpenHarmony Source**. 4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png) ![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png)
5. On the **Import Project** page, select **Hi3516DV300** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**. 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**. In the figure below, **Hi3516DV300** is used as an example.
![en-us_image_0000001279426717](figures/en-us_image_0000001279426717.png) ![en-us_image_0000001271912277](figures/en-us_image_0000001271912277.png)
6. Click **Open** to open the project or source code. 6. Click **Open** to open the project or source code.
## Burning ### Burning
After the source code is imported, perform the following steps: After the source code is imported, perform the following steps:
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> This feature is available in DevEco Device Tool 2.2 Beta2 and later versions.
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).
> ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
> If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
>
> - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
>
> - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver. 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).
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).
- 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_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. - 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) ![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 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. 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.
![en-us_image_0000001315910101](figures/en-us_image_0000001315910101.png) ![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png)
5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**. > ![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).
4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png) ![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png)
6. On the **hi3516dv300** tab page, set the burning options. 5. On the **hi3516dv300** tab page, set the burning options.
- **upload_partitions**: Select the files to be burnt. By default, **fastboot**, **boot**, **updater**, **misc**, **system**, **vendor**, and **userdata** are burnt at the same time.
- **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
- **upload_port**: Select the serial port number obtained. - **upload_port**: Select the serial port number obtained.
- **upload_protocol**: Select the burning protocol **hiburn-usb**. - **upload_protocol**: Select the burning protocol **hiburn-usb**.
![en-us_image_0000001177478136](figures/en-us_image_0000001177478136.png) ![en-us_image_0000001223190441](figures/en-us_image_0000001223190441.png)
6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
![en-us_image_0000001198889702](figures/en-us_image_0000001198889702.png)
2. In **Partition Options**, modify the items selected in the preceding step.
7. In **Partitions**, check the preset burning settings of the files to be burnt. > ![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.
![en-us_image_0000001312541849](figures/en-us_image_0000001312541849.png) ![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png)
To modify the burning settings for a specific file, click ![en-us_image_0000001265361888](figures/en-us_image_0000001265361888.png) next to the file. 3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
> ![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.
![en-us_image_0000001264982466](figures/en-us_image_0000001264982466.png) 7. When you finish modifying, click **Save** on the top.
8. When you finish modifying, click **Save** on the top. 8. Go to **hi3516dv300** > **Upload** to start burning.
9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning. > ![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.
![en-us_image_0000001315932049](figures/en-us_image_0000001315932049.png) ![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png)
10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning. 9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png) ![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png)
If the following message is displayed, it indicates that the burning is successful. If the following message is displayed, it indicates that the burning is successful.
![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png) ![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png)
11. When the burning is successful, perform the operations in Running to start the system. 10. When the burning is successful, perform the operations in Running an Image to start the system.
en/device-dev/quick-start/quickstart-standard-running-hi3516.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Hi3516 Development Board
- **[Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)**
- **[Building](quickstart-standard-running-hi3516-build.md)**
- **[Burning](quickstart-standard-running-hi3516-burning.md)**
- **[Running](quickstart-standard-running-hi3516-running.md)**
en/device-dev/quick-start/quickstart-standard-running-rk3568-build.md
浏览文件 @ 3b2df328
...@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor ...@@ -8,18 +8,18 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
1. Set the build path. 1. Set the build path.
``` ```
hb set hb set
``` ```
2. Select the current path. 2. Select the current path.
``` ```
. .
``` ```
3. Select **rk3568** under **hihope** and press **Enter**. 3. Select **rk3568** under **built-in** and press **Enter**.
4. Start building. 4. Start building.
...@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor ...@@ -32,12 +32,12 @@ Go to the root directory of the source code in the Ubuntu environment and perfor
> >
> This example builds a product from the scratch. > This example builds a product from the scratch.
``` ```
hb build -f hb build -f
``` ```
**Figure 1** RK3568 build settings **Figure 1** RK3568 build settings
![en-us_image_0000001226922302](figures/en-us_image_0000001226922302.png) ![en-us_image_0000001226922302](figures/en-us_image_0000001226922302.png)
......
en/device-dev/quick-start/quickstart-standard-running-rk3568-burning.md
浏览文件 @ 3b2df328
# Burning # Burning
Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>
> - If you are using source code from the master branch released since May 9, 2022, use RKDevTool for burning.
>
> - DevEco Device Tool currently does not support burning of source code released before May 9, 2022. This feature will be introduced in the coming version.
To burn source code to RK3568 on Windows, perform the following steps: To burn source code to RK3568 on Windows, perform the following steps:
## Importing Source Code ### Importing Source Code
[Ensure that the Windows system can remotely access the Ubuntu environment](../quick-start/quickstart-standard-env-setup.md), and then perform the following steps to import source code: After the building is complete, ensure that you can [remotely access the Ubuntu environment from Windows](../quick-start/quickstart-standard-env-setup.md). Then, perform the following steps to import the source code before burning:
1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code. 1. Open DevEco Device Tool, go to the home page, and click **Import Project** to open your project or source code.
![en-us_image_0000001278358765](figures/en-us_image_0000001278358765.png) ![en-us_image_0000001171426014](figures/en-us_image_0000001171426014.png)
2. Select the target directory (in the Ubuntu environment) and click **Import**. 2. Select the target directory (in the Ubuntu environment) and click **Import**.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/> > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> Make sure the selected directory does not contain Chinese characters or spaces. > Make sure the selected directory does not contain Chinese characters or spaces. Otherwise, the building may fail.
![en-us_image_0000001271791385](figures/en-us_image_0000001271791385.png) ![en-us_image_0000001272032361](figures/en-us_image_0000001272032361.png)
3. If this is the first time you import the source code, the following dialog box will be displayed. Click **Import** when prompted. 3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
![en-us_image_0000001314076609](figures/en-us_image_0000001314076609.png) ![en-us_image_0000001135394334](figures/en-us_image_0000001135394334.png)
4. On the **Select Project type** page, select **Import from OpenHarmony Source**. 4. On the **Select Project type** page, select **Import from OpenHarmony Source**.
![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png) ![en-us_image_0000001215743910](figures/en-us_image_0000001215743910.png)
5. On the **Import Project** page, select **rk3568** for **Product**, and the MCU, board, company, and kernel fields will be automatically populated. Then, select the OpenHarmony source code version for **Ohos Ver**. 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**. Select **rk3568**.
![en-us_image_000000127958708](figures/en-us_image_000000127958708.png) ![en-us_image_0000001227712350](figures/en-us_image_0000001227712350.png)
6. Click **Open** to open the project or source code. 6. Click **Open** to open the project or source code.
## Burning ### Burning
After the source code is imported, perform the following steps: After the source code is imported, perform the following steps:
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**<br/>
> 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.
> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/> 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 you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
>
> - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
>
> - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
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). - 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_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. - 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) ![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**<br>
> 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. Open 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.
![en-us_image_0000001239661509](figures/en-us_image_0000001239661509.png) ![en-us_image_0000001239661509](figures/en-us_image_0000001239661509.png)
...@@ -83,29 +65,32 @@ After the source code is imported, perform the following steps: ...@@ -83,29 +65,32 @@ After the source code is imported, perform the following steps:
![en-us_image_0000001194504874](figures/en-us_image_0000001194504874.png) ![en-us_image_0000001194504874](figures/en-us_image_0000001194504874.png)
6. In **Partitions**, check the preset burning settings of the files to be burnt. 6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **loader**, **parameter**, **uboot**, **boot_linux**, **system**, **vendor**, and **userdata**.
1. On the **hh_scdy200_loader** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
![en-us_image_0000001265041892](figures/en-us_image_0000001265041892.png) ![en-us_image_0000001224173270](figures/en-us_image_0000001224173270.png)
To modify the burning settings for a specific file, click ![en-us_image_0000001265361888](figures/en-us_image_0000001265361888.png) next to the file. 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**<br>
> 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_0000001265201928](figures/en-us_image_0000001265201928.png) ![en-us_image_0000001268653461](figures/en-us_image_0000001268653461.png)
3. Follow the same procedure to modify the information about the **parameter**, **uboot**, **boot_linuxv, **system**, **vendor**, and **userdata** files.
7. When you finish modifying, click **Save** on the top. 7. When you finish modifying, click **Save** on the top.
8. Choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning. 8. Click **Open** to open the project file. Click ![en-us_image_0000001239221905](figures/en-us_image_0000001239221905.png) to open DevEco Device Tool. Then, choose **PROJECT TASKS** > **hh_scdy200** > **Upload** to start burning.
![en-us_image_0000001194821710](figures/en-us_image_0000001194821710.png) ![en-us_image_0000001194821710](figures/en-us_image_0000001194821710.png)
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/>If the message "The board 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. > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
> > 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.
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)
en/device-dev/quick-start/quickstart-standard-running-rk3568.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# RK3568 Development Board
- **[Writing a Hello World Program](quickstart-standard-running-rk3568-create.md)**
- **[Building](quickstart-standard-running-rk3568-build.md)**
- **[Burning](quickstart-standard-running-rk3568-burning.md)**
- **[Running](quickstart-standard-running-rk3568-running.md)**
en/device-dev/quick-start/quickstart-standard-running.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Running a Hello World Program
- **[Hi3516 Development Board](quickstart-standard-running-hi3516.md)**
- **[RK3568 Development Board](quickstart-standard-running-rk3568.md)**
en/device-dev/quick-start/quickstart.md 已删除 100644 → 0
浏览文件 @ d57fcbc5
# Getting Started
- **[Getting Started with Mini and Small Systems](quickstart-lite.md)**
- **[Getting Started with Standard System](quickstart-standard.md)**
en/device-dev/website.md
浏览文件 @ 3b2df328
...@@ -76,7 +76,7 @@ ...@@ -76,7 +76,7 @@
- [Setting Up Environments for Standard System](quick-start/quickstart-standard-env-setup.md) - [Setting Up Environments for Standard System](quick-start/quickstart-standard-env-setup.md)
- Running a Hello World Program - Running a Hello World Program
- Hi3516 Development Board - Hi3516 Development Board
- [Writing a Hello World Program](quick-start/quickstart-standard-running-hi3516-create.md) - [Writing a Hello World Program](quick-start/quickstart-std-3516-create.md)
- [Building](quick-start/quickstart-standard-running-hi3516-build.md) - [Building](quick-start/quickstart-standard-running-hi3516-build.md)
- [Burning](quick-start/quickstart-standard-running-hi3516-burning.md) - [Burning](quick-start/quickstart-standard-running-hi3516-burning.md)
- [Running](quick-start/quickstart-standard-running-hi3516-running.md) - [Running](quick-start/quickstart-standard-running-hi3516-running.md)
......
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或