diff --git a/Readme-CN.md b/Readme-CN.md index 79e01a45041928659dc02a82a4893145401c6ea6..7405516a982a4d744139f6da517d5585a7e5e225 100755 --- a/Readme-CN.md +++ b/Readme-CN.md @@ -6,18 +6,18 @@ ## 文档目录结构 -- quick-start:[快速入门](quick-start/Readme-CN.md) -- get-code:[获取源码/获取工具](get-code/Readme-CN.md) -- driver:[驱动](driver/Readme-CN.md) -- kernel:[内核](kernel/Readme-CN.md) -- subsystems:[子系统](subsystems/Readme-CN.md) -- bundles:[组件开发](bundles/Readme-CN.md) -- guide:[设备开发](guide/Readme-CN.md) -- security:[安全](security/Readme-CN.md) -- api-LinkIoT:[联接类模组API](api/api-LinkIoT/Readme-CN.md) -- api-SmartVision-Devices:[智慧视觉设备API](api/api-SmartVision-Devices/Readme-CN.md) -- contribute:[贡献](contribute/参与贡献.md) -- term:[术语](term/术语.md) +- quick-start:[快速入门](quick-start/Readme-CN.md) +- get-code:[获取源码/获取工具](get-code/Readme-CN.md) +- driver:[驱动](driver/Readme-CN.md) +- kernel:[内核](kernel/Readme-CN.md) +- subsystems:[子系统](subsystems/Readme-CN.md) +- bundles:[组件开发](bundles/Readme-CN.md) +- guide:[设备开发](guide/Readme-CN.md) +- security:[安全](security/Readme-CN.md) +- api-LinkIoT:[联接类模组API](api/api-LinkIoT/Readme-CN.md) +- api-SmartVision-Devices:[智慧视觉设备API](api/api-SmartVision-Devices/Readme-CN.md) +- contribute:[贡献](contribute/参与贡献.md) +- term:[术语](term/术语.md) ## 贡献 @@ -26,4 +26,3 @@ 您可以对现有文档进行评价、简单更改、反馈文档质量问题、贡献您的原创内容,详细请参考[贡献文档](contribute/贡献文档.md)。 卓越贡献者将会在开发者社区文档贡献专栏表彰公示。 - diff --git a/api/api-LinkIoT/Broadcast.md b/api/api-LinkIoT/Broadcast.md index c7f2897538dbbe7d5d5e1d7d42bc7cc9fea65864..dc33012242f117f67128f3c14885ef63b885b0da 100755 --- a/api/api-LinkIoT/Broadcast.md +++ b/api/api-LinkIoT/Broadcast.md @@ -37,7 +37,7 @@ With this module, the [Service](Service.md), [Feature](Feature.md), or other m
Defines the subscriber for external interfaces to subsribe to events and data of a topic.
+Defines the subscriber for external interfaces to subscribe to events and data of a topic.
64a518b50422b6f1ba8f6f56a5e303fb8448a311211ba10c385ad307a1d2546f
614ee086ead1a4fd7384332b85dd62707801f323de60dfdb61503f473d470a24
50a5a5ba5877dd0ec8afcb23d3dd4d966a16403c29cd80a4002230241d32ef34
b4a4ba21e94ff77634e1f88697a00b6f498fdbc0b40d7649df1b246b285874f9
fcfee489371947a464fe41a4b45a897b9a44155891a957f15bad2e157c750162
|
@@ -453,7 +456,7 @@ Compile and burn images by referring to [Compiling Code](developing-the-first-e
rootaddr=10 M, rootsize=15 M rw indicates the start address and size of the rootfs.img file to be burnt, respectively. The file size must be the same as that of the compiled file in the IDE. saveenv means to save the current configuration. reset means to reset the board. -(Optional) go 0x80000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-Boot startup to interrupt the automatic startup. +(Optional) go 0x80000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-boot startup to interrupt the automatic startup. |
|---|
|
@@ -148,7 +151,7 @@ This method applies only to development boards that have network ports, for exam
rootaddr=10 M, rootsize=15 M rw indicates the start address and size of the rootfs.img file to be burnt, respectively. The file size must be the same as that of the compiled file in the IDE. saveenv means to save the current configuration. reset means to reset the board. -(Optional) go 0x80000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-Boot startup to interrupt the automatic startup. +(Optional) go 0x80000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-boot startup to interrupt the automatic startup. |
|---|
| @@ -92,7 +92,7 @@ Burn images to the Hi3518EV300 board over the serial port. | setenv bootcmd "sf probe 0;sf read 0x40000000 0x100000 0x600000;go 0x40000000"; Run this command to set the content of bootcmd. Select the flash whose number is 0, and read content that has a size of 0x600000 and a start address of 0x100000 to memory address 0x40000000. -(Optional) go 0x40000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-Boot startup to interrupt the automatic startup. +(Optional) go 0x40000000 indicates that the command is fixed in the startup parameters by default and the board automatically starts after it is reset. If you want to manually start the board, press Enter in the countdown phase of the U-boot startup to interrupt the automatic startup. setenv bootargs "console=ttyAMA0,115200n8 root=flash fstype=jffs2 rw rootaddr=7 M rootsize=8 M"; In this command, bootargs is set to the serial port output, the baud rate is 115200, the data bit is 8, and the rootfs is mounted to the flash memory. The file system type is set to jffs2 rw, which provides the read-write attribute for the JFFS2 file system. rootaddr=7 M rootsize=8 M indicates the actual start address and length of the rootfs.img file to be burnt. The size must be the same as that of the compiled files in the HiTool. @@ -115,5 +115,5 @@ Burn images to the Hi3518EV300 board over the serial port. ## Follow-up Learning -Congratulations! You have finished all steps! You are advised to go on learning how to develop [Cameras with a Screen](en-us_topic_0000001055366100.md). +Congratulations! You have finished all steps! You are advised to go on learning how to develop [Cameras with a Screen](../guide/camera-control.md). diff --git a/docs-en/quick-start/developing-the-first-example-program-running-on-hi3861.md b/docs-en/quick-start/developing-the-first-example-program-running-on-hi3861.md index 88734f1912abde6108a7ec38fb6738811a6973b2..2093cee18a07929ea7b2ff0480e6f880d4db9c76 100755 --- a/docs-en/quick-start/developing-the-first-example-program-running-on-hi3861.md +++ b/docs-en/quick-start/developing-the-first-example-program-running-on-hi3861.md @@ -4,7 +4,7 @@ This example shows how to use attention \(AT\) commands to complete WLAN module ## Acquiring Source Code -You need to acquire [Hi3861 source code](http://tools.harmonyos.com/mirrors/os/1.0/code-1.0.tar.gz) and download it on a Linux server. For more obtaining methods, see [Source Code Acquisition](../get-code/source-code-acquisition.md). +You need to acquire [Hi3861 source code](https://repo.huaweicloud.com/harmonyos/os/1.0/code-1.0.tar.gz) and download it on a Linux server. For more obtaining methods, see [Source Code Acquisition](en-us_topic_0000001050769927.md). ## Compiling Source Code diff --git a/docs-en/quick-start/developing-the-second-example-program-running-on-hi3861.md b/docs-en/quick-start/developing-the-second-example-program-running-on-hi3861.md index e8358ef045cd3c8fb9ba289fd5f28d2c743edcdc..31f1b5d87dba44252b069875b76c262dd1e7f5c3 100755 --- a/docs-en/quick-start/developing-the-second-example-program-running-on-hi3861.md +++ b/docs-en/quick-start/developing-the-second-example-program-running-on-hi3861.md @@ -144,5 +144,5 @@ wifi init success! ## Follow-up Learning -Congratulations! You have finished all steps! You are advised to go on learning how to develop [WLAN-connected products](../guide/overview.md). +Congratulations! You have finished all steps! You are advised to go on learning how to develop [WLAN-connected products](en-us_topic_0000001054530966.md). diff --git a/docs-en/quick-start/faqs-0.md b/docs-en/quick-start/faqs-0.md index f29b798342873d20273b181bff09caf8b2db0292..12610762aaa2b6fdc3817b3ee45220e1a65e6f91 100755 --- a/docs-en/quick-start/faqs-0.md +++ b/docs-en/quick-start/faqs-0.md @@ -117,3 +117,57 @@  +**Problem 5:** **What should I do when no command output is displayed?** + +- **Symptom** + + The serial port shows that the connection has been established. After the board is restarted, nothing is displayed when you press **Enter**. + +- **Possible Causes** + - The serial port is connected incorrectly. + - The U-boot of the board is damaged. + +- **Solutions** + + **Solution 1: Change the serial port number.** + + Start **Device Manager** to check whether the serial port connected to the board is the same as that connected to the terminal device. If not, perform the following steps to change the serial port number. + + **Figure 10** Procedure for changing the serial port number +  + + +1. Disconnect from the current serial port. +2. Click **Settings**. +3. Change the serial port number in the dialog box and click **OK**. +4. Press **Enter** in the dialog box to check whether any command output is displayed after the connection is established. + +**Solution 2: Burn the U-boot.** + +If the fault persists after you perform the preceding operations, the U-boot of the board may be damaged. You can burn the U-boot by performing the following steps: + +1. Obtain the U-boot file. + + > **NOTICE:** + >The U-boot file of the board can be obtained from **vendor\\hisi\\hi35xx\\hi3516dv300\\uboot\\out\\boot\\u-boot-hi3516dv300.bin** in the open-source package. + +2. Use HiTool to burn the U-boot. + + **Figure 11** Procedure for burning the U-boot using HiTool + + +  + + 1. Select the COM7 serial port. + 2. Select **Serial** for **Transfer Mode**. + 3. Select **Burn Fastboot**. + 4. Select **spi nor** for **Flash Type**. + 5. Click **Browse** and select the corresponding U-boot file. + 6. Click **Burn** to start burning. + +3. Power off the board and then power it on. Connect the serial port after the burning is complete. Serial ports shown in the following figure are displayed after the U-boot is burnt. + + **Figure 12** Serial port displayed after the U-boot is burnt +  + + diff --git a/docs-en/quick-start/faqs-2.md b/docs-en/quick-start/faqs-2.md index ffc8060fc952ba6597b823b3074bac12e9e774ad..feb6b39d5cd0b5b64fa2ca606ae2921b739b9879 100755 --- a/docs-en/quick-start/faqs-2.md +++ b/docs-en/quick-start/faqs-2.md @@ -8,14 +8,16 @@ - **Possible Causes** - The serial port is connected incorrectly. - - The U-Boot of the board is damaged. + - The U-boot of the board is damaged. - **Solutions** + **Solution 1: Change the serial port number.** + Start **Device Manager** to check whether the serial port connected to the board is the same as that connected to the terminal device. If not, perform the following steps to change the serial port number. **Figure 1** Procedure for changing the serial port number -  +  1. Disconnect from the current serial port. @@ -23,32 +25,34 @@ 3. Change the serial port number in the dialog box and click **OK**. 4. Press **Enter** in the dialog box to check whether any command output is displayed after the connection is established. -If the fault persists after you perform the preceding operations, the U-Boot of the board may be damaged. You can burn the U-Boot by performing the following steps: +**Solution 2: Burn the U-boot.** + +If the fault persists after you perform the preceding operations, the U-boot of the board may be damaged. You can burn the U-boot by performing the following steps: -1. Obtain the U-Boot file. +1. Obtain the U-boot file. > **NOTICE:** - >The U-Boot file of the board can be obtained from **vendor\\hisi\\hi35xx\\hi3518ev300\\uboot\\out\\boot\\u-boot-hi3518ev300.bin** in the open-source package. + >The U-boot file of the board can be obtained from **vendor\\hisi\\hi35xx\\hi3518ev300\\uboot\\out\\boot\\u-boot-hi3518ev300.bin** in the open-source package. -2. Use HiTool to burn the U-Boot. +2. Use HiTool to burn the U-boot. - **Figure 2** Procedure for burning the U-Boot using HiTool + **Figure 2** Procedure for burning the U-boot using HiTool  1. Select the COM7 serial port. 2. Select **Serial** for **Transfer Mode**. 3. Select **Burn Fastboot**. 4. Select **spi nor** for **Flash Type**. - 5. Click **Browse** and select the corresponding U-Boot file. + 5. Click **Browse** and select the corresponding U-boot file. 6. Click **Burn** to start burning. -3. Power off the board and then power it on. Connect the serial port after the burning is complete. Serial ports shown in the following figure are displayed after the U-Boot is burnt. +3. Power off the board and then power it on. Connect the serial port after the burning is complete. Serial ports shown in the following figure are displayed after the U-boot is burnt. - **Figure 3** Serial port displayed after the U-Boot is burnt -  + **Figure 3** Serial port displayed after the U-boot is burnt +  -**Problem 2: What should I do when an error is reported when the U-Boot is burnt using HiTool?** +**Problem 2: What should I do when an error is reported when the U-boot is burnt using HiTool?** - **Symptom** diff --git a/docs-en/quick-start/figures/adding-the-hi3516dv300-board.png b/docs-en/quick-start/figures/adding-the-hi3516dv300-board.png index 81a2b496aacb056d6003d0fe440e9d1dfe8f96e8..2d807c348ffdb802b239e295abb7b7e079e213e5 100755 Binary files a/docs-en/quick-start/figures/adding-the-hi3516dv300-board.png and b/docs-en/quick-start/figures/adding-the-hi3516dv300-board.png differ diff --git a/docs-en/quick-start/figures/appearance-of-hi3861-wlan-module.png b/docs-en/quick-start/figures/appearance-of-hi3861-wlan-module.png index df3f85daabb08e137bafd8a098c6f882f1a5776b..ccc714eadc965fc4b29703c3156e730f84c97596 100755 Binary files a/docs-en/quick-start/figures/appearance-of-hi3861-wlan-module.png and b/docs-en/quick-start/figures/appearance-of-hi3861-wlan-module.png differ diff --git a/docs-en/quick-start/figures/procedure-for-changing-the-serial-port-number-4.png b/docs-en/quick-start/figures/procedure-for-changing-the-serial-port-number-4.png new file mode 100644 index 0000000000000000000000000000000000000000..f699204d10d39eb088c0ecc7aa08ba134ec4b6b6 Binary files /dev/null and b/docs-en/quick-start/figures/procedure-for-changing-the-serial-port-number-4.png differ diff --git a/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt-5.png b/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt-5.png new file mode 100644 index 0000000000000000000000000000000000000000..4e2a2794e63f64341e448313968b6f82d237543d Binary files /dev/null and b/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt-5.png differ diff --git a/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt.png b/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt.png index 4e2a2794e63f64341e448313968b6f82d237543d..ad4fd618860ca9f79e9bdc39436c3b2f9cdb72de 100755 Binary files a/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt.png and b/docs-en/quick-start/figures/serial-port-displayed-after-the-u-boot-is-burnt.png differ diff --git "a/docs-en/quick-start/figures/\346\234\252\345\221\275\345\220\215\345\233\276\347\211\20711111.png" "b/docs-en/quick-start/figures/\346\234\252\345\221\275\345\220\215\345\233\276\347\211\20711111.png" new file mode 100644 index 0000000000000000000000000000000000000000..4b8caa20e71b5a592b82a625d9f022a29667427d Binary files /dev/null and "b/docs-en/quick-start/figures/\346\234\252\345\221\275\345\220\215\345\233\276\347\211\20711111.png" differ diff --git a/docs-en/quick-start/introduction-to-the-hi3861-development-board.md b/docs-en/quick-start/introduction-to-the-hi3861-development-board.md index 0cbcbe583033866e300b75bd797b708e8b8a231c..8fb93d867301459da72cecec565d434d12411515 100755 --- a/docs-en/quick-start/introduction-to-the-hi3861-development-board.md +++ b/docs-en/quick-start/introduction-to-the-hi3861-development-board.md @@ -43,9 +43,9 @@ As the Hi3861 only offers 2 MB Flash and 352 KB RAM, use them efficiently when c | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
+
|
-http://tools.harmonyos.com/mirrors/gn/1523/linux/gn.1523.tar +https://repo.huaweicloud.com/harmonyos/compiler/gn/1523/linux/gn.1523.tar
|
|
-http://tools.harmonyos.com/mirrors/ninja/1.9.0/linux/ninja.1.9.0.tar +https://repo.huaweicloud.com/harmonyos/compiler/ninja/1.9.0/linux/ninja.1.9.0.tar
|
|
-http://tools.harmonyos.com/mirrors/clang/9.0.0-34042/linux/llvm-linux-9.0.0-34042.tar +https://repo.huaweicloud.com/harmonyos/compiler/clang/9.0.0-34042/linux/llvm-linux-9.0.0-34042.tar
|
|
-http://tools.harmonyos.com/mirrors/hc-gen/0.65/linux/hc-gen-0.65-linux.tar +https://repo.huaweicloud.com/harmonyos/compiler/hc-gen/0.65/linux/hc-gen-0.65-linux.tar
@@ -175,7 +175,7 @@ Linux服务器通用环境配置需要的工具及其获取途径如下表所示
查看shell是否为bash,在终端运行如下命令
-```
+```bash
ls -l /bin/sh
```
@@ -183,13 +183,13 @@ ls -l /bin/sh
**方法一**:在终端运行如下命令,然后选择 no。
-```
+```bash
sudo dpkg-reconfigure dash
```
**方法二**:先删除sh,再创建软链接。
-```
+```bash
rm -rf /bin/sh
sudo ln -s /bin/bash /bin/sh
```
@@ -207,7 +207,7 @@ sudo ln -s /bin/bash /bin/sh
2. 获取[python3.8.5安装包](https://www.python.org/ftp/python/3.8.5/Python-3.8.5.tgz),将其放至linux服务器中,运行 :
- "tar -xvzf Python-3.8.5.tgz && cd Python-3.8.5 && sudo ./configure && make && sudo make install"
+ "tar -xvzf Python-3.8.5.tgz && cd Python-3.8.5 && sudo ./configure && sudo make && sudo make install"
3. 确定Python-3.8.5安装好后,运行"which python3.8",将回显路径链接到"/usr/bin/python",示例:
@@ -215,7 +215,7 @@ sudo ln -s /bin/bash /bin/sh
- 安装Python包管理工具,运行“sudo apt-get install python3-setuptools python3-pip -y”命令。(需root/sudo权限安装),升级pip3运行"sudo pip3 install --upgrade pip"。
-
+
或按官网方式安装Python包管理工具:下载"curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py"后,再执行"python get-pip.py"
@@ -249,7 +249,7 @@ sudo ln -s /bin/bash /bin/sh
## 安装gn
1. 打开Linux编译服务器终端。
-2. [下载gn工具](http://tools.harmonyos.com/mirrors/gn/1523/linux/gn.1523.tar)。
+2. [下载gn工具](https://repo.huaweicloud.com/harmonyos/compiler/gn/1523/linux/gn.1523.tar)。
3. 解压gn安装包至\~/gn路径下:"tar -xvf gn.1523.tar -C \~/"。
4. 设置环境变量:"vim \~/.bashrc", 新增:"export PATH=\~/gn:$PATH"。
5. 生效环境变量:"source \~/.bashrc"。
@@ -257,7 +257,7 @@ sudo ln -s /bin/bash /bin/sh
## 安装ninja
1. 打开Linux编译服务器终端
-2. [下载ninja工具](http://tools.harmonyos.com/mirrors/ninja/1.9.0/linux/ninja.1.9.0.tar)。
+2. [下载ninja工具](https://repo.huaweicloud.com/harmonyos/compiler/ninja/1.9.0/linux/ninja.1.9.0.tar)。
3. 解压ninja安装包至\~/ninja路径下:"tar -xvf ninja.1.9.0.tar -C \~/"。
4. 设置环境变量:"vim \~/.bashrc", 新增:"export PATH=\~/ninja:$PATH"。
5. 生效环境变量:"source \~/.bashrc"。
@@ -265,7 +265,7 @@ sudo ln -s /bin/bash /bin/sh
## 安装LLVM编译工具链
1. 打开Linux编译服务器终端。
-2. [下载LLVM工具](http://tools.harmonyos.com/mirrors/clang/9.0.0-34042/linux/llvm-linux-9.0.0-34042.tar)。
+2. [下载LLVM工具](https://repo.huaweicloud.com/harmonyos/compiler/clang/9.0.0-34042/linux/llvm-linux-9.0.0-34042.tar)。
3. 解压LLVM安装包至\~/llvm路径下:"tar -xvf llvm-linux-9.0.0-34042.tar -C \~/"。
4. 设置环境变量:"vim \~/.bashrc", 新增:export PATH=\~/llvm/bin:$PATH。
5. 生效环境变量:"source \~/.bashrc"。
@@ -273,8 +273,8 @@ sudo ln -s /bin/bash /bin/sh
## 安装hc-gen
1. 打开Linux编译服务器终端。
-2. [下载hc-gen工具](http://tools.harmonyos.com/mirrors/hc-gen/0.65/linux/hc-gen-0.65-linux.tar)。
-3. 解压hc-gen安装包到Linux服务器\~/hc-gen路径下。
+2. [下载hc-gen工具](https://repo.huaweicloud.com/harmonyos/compiler/hc-gen/0.65/linux/hc-gen-0.65-linux.tar)。
+3. 解压hc-gen安装包到Linux服务器\~/hc-gen路径下:"tar -xvf hc-gen-0.65-linux.tar -C \~/"。
4. 设置环境变量:"vim \~/.bashrc", 新增:export PATH=\~/hc-gen:$PATH。
5. 生效环境变量:"source \~/.bashrc"。
diff --git "a/quick-start/\346\220\255\345\273\272\347\216\257\345\242\203.md" "b/quick-start/\346\220\255\345\273\272\347\216\257\345\242\203.md"
index 675c8dc1ec1b17a3cad90597dbc9d27209c452d0..08c0856803c506d1cb568994cc1796217866a322 100755
--- "a/quick-start/\346\220\255\345\273\272\347\216\257\345\242\203.md"
+++ "b/quick-start/\346\220\255\345\273\272\347\216\257\345\242\203.md"
@@ -67,7 +67,7 @@ Linux服务器通用环境配置需要的工具及其获取途径如下表所示
|
|
-http://tools.harmonyos.com/mirrors/gcc_riscv32/7.3.0/linux/gcc_riscv32-linux-7.3.0.tar.gz +https://repo.huaweicloud.com/harmonyos/compiler/gcc_riscv32/7.3.0/linux/gcc_riscv32-linux-7.3.0.tar.gz
@@ -102,14 +102,14 @@ Linux服务器通用环境配置需要的工具及其获取途径如下表所示
|
|
-http://tools.harmonyos.com/mirrors/gn/1523/linux/gn.1523.tar +https://repo.huaweicloud.com/harmonyos/compiler/gn/1523/linux/gn.1523.tar
|
|
-http://tools.harmonyos.com/mirrors/ninja/1.9.0/linux/ninja.1.9.0.tar +https://repo.huaweicloud.com/harmonyos/compiler/ninja/1.9.0/linux/ninja.1.9.0.tar
|
-
+ |
|
@@ -94,7 +93,7 @@
|
|
-
+ |
|
|
|---|