diff --git a/en/OpenHarmony-Overview.md b/en/OpenHarmony-Overview.md index 75dc8b66607121be43c3bcfa13398ecee5b76401..31fcc72313e04883f23d9feef50dd7671b118004 100644 --- a/en/OpenHarmony-Overview.md +++ b/en/OpenHarmony-Overview.md @@ -156,7 +156,7 @@ Currently, the OpenHarmony community supports 17 types of development boards, wh ## Getting Started -- [Getting Started for Device Development](device-dev/quick-start/quickstart-ide-lite-overview.md) +- [Getting Started for Device Development](device-dev/quick-start/quickstart-overview.md) - [Getting Started for Application Development](application-dev/quick-start/start-overview.md) diff --git a/en/device-dev/kernel/kernel-overview.md b/en/device-dev/kernel/kernel-overview.md index ffcf8d171b3a05a88a08a0c2a8d9c70b86653aec..873d8b0a6c09eabbaaee70005e8eda10793045dd 100644 --- a/en/device-dev/kernel/kernel-overview.md +++ b/en/device-dev/kernel/kernel-overview.md @@ -108,7 +108,7 @@ To keep pace with the rapid development of the IoT industry, the OpenHarmony lig **Figure 4** LiteOS-A kernel architecture - ![](figures/architecture-of-the-openharmony-liteos-a-kernel.png "architecture-of-the-openharmony-liteos-a-kernel") + ![](figures/Liteos-a-architecture.png "Liteos-a-architecture.png") ### How to Use diff --git a/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md b/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md index 0070fc5fd80a26c7d2611af75272011357b5727a..8ca304d90e087c9e8864fcb0fa8e5dc91e2b92b6 100644 --- a/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md +++ b/en/release-notes/api-change/v3.2-beta3/changelog-v3.2-beta3.md @@ -56,7 +56,7 @@ In earlier versions, these privileges are configured in the **config.json** or * **Change Impacts** -JS and native APIs are not involved. If your application needs to use any of these privileges, apply for it. For details about how to apply for and configure the privileges, see [Application Privilege Configuration](../device-dev/subsystems/subsys-app-privilege-config-guide.md). +JS and native APIs are not involved. If your application needs to use any of these privileges, apply for it. For details about how to apply for and configure the privileges, see [Application Privilege Configuration](../../../device-dev/subsystems/subsys-app-privilege-config-guide.md). **Key API/Component Changes** @@ -64,7 +64,7 @@ N/A **Adaptation Guide** -See [Application Privilege Configuration](../device-dev/subsystems/subsys-app-privilege-config-guide.md). +See [Application Privilege Configuration](../../../device-dev/subsystems/subsys-app-privilege-config-guide.md). ```json { @@ -95,7 +95,7 @@ In earlier versions, these privileges are configured in the **config.json** or * **Change Impacts** -JS and native APIs are not involved. If your application needs to use any of these privileges, apply for it. For details, see [Configuration Mode](../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-mode). +JS and native APIs are not involved. If your application needs to use any of these privileges, apply for it. For details, see [Configuration Mode](../../../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-mode). **Key API/Component Changes** @@ -103,7 +103,7 @@ N/A **Adaptation Guide** -See [Configuration Mode](../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-mode). +See [Configuration Mode](../../../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-mode). ```json { diff --git a/zh-cn/device-dev/device-test/xts.md b/zh-cn/device-dev/device-test/xts.md index dbe852a1830d6def4f1630d31d12f6689a568b79..77dba25a137504ae7a19c2edcc3248bea4f7da60 100644 --- a/zh-cn/device-dev/device-test/xts.md +++ b/zh-cn/device-dev/device-test/xts.md @@ -191,7 +191,7 @@ XTS子系统当前包括acts与tools软件包: 5. 测试套件编译命令。 随版本编译,debug版本编译时会同步编译acts测试套件。 - > ![icon-note.gif](public_sys-resources/icon-note.gif) **说明:** + > ![icon-note.gif](../public_sys-resources/icon-note.gif) **说明:** > acts测试套件编译中间件为静态库,最终链接到版本镜像中 。 ### C语言用例执行指导(适用于轻量系统产品用例开发) @@ -324,7 +324,7 @@ XTS子系统当前包括acts与tools软件包: 5. 测试套件编译命令。 随版本编译,debug版本编译时会同步编译acts测试套件 - > ![icon-note.gif](public_sys-resources/icon-note.gif) **说明:** + > ![icon-note.gif](../public_sys-resources/icon-note.gif) **说明:** > 小型系统acts独立编译成可执行文件(bin格式), 在编译产物的suites\acts目录下归档。 diff --git a/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md b/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md index c645347cdbb2a7de6d162e3fd2e62371378fc048..045a09c28d618d7b84963820dfdd08db709dd182 100644 --- a/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md +++ b/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md @@ -9,7 +9,7 @@ | Ability | 应用的重要组成部分,是应用所具备能力的抽象。Ability是系统调度应用的最小单元,是能够完成一个独立功能的组件,一个应用可以包含一个或多个Ability。 | | FA | Feature Ability,是FA模型的Ability框架下具有UI界面的Ability类型,用于与用户进行交互。Feature Ability唯一对应一种模板,即Page模板(Page Ability)。 | | PA | Particle Ability,是在FA模型的Ability框架下无界面的Ability,主要为Feature Ability提供服务与支持,例如作为后台服务提供计算能力,或作为数据仓库提供数据访问能力。Particle Ability有三种模板,分别为Service模板(Service Ability)、Data模板(Data Ability)、以及Form模板(Form Ability)。 | -| FA模型 | 两种Ability框架模型结构的其中一种。是Ability框架在API 8及更早版本采用FA模型。FA模型将Ability分为FA(Feature Ability)和PA(Particle Ability)两种类型,其中FA支持Page Ability模板,PA支持Service ability、Data ability、以及Form ability模板。详情可参考[FA模型综述](../../application-dev/ability/fa-brief.md)。 | +| FA模型 | 两种Ability框架模型结构的其中一种。是Ability框架在API 8及更早版本采用FA模型。FA模型将Ability分为FA(Feature Ability)和PA(Particle Ability)两种类型,其中FA支持Page Ability模板,PA支持Service ability、Data ability、以及Form ability模板。详情可参考[FA模型综述](../../application-dev/ability-deprecated/fa-brief.md)。 | | Stage模型 | 两种Ability框架模型结构的其中一种。从API 9开始支持。Stage模型将Ability分为Ability和ExtensionAbility两大类,其中ExtensionAbility又被扩展为ServiceExtensionAbility、FormExtensionAbility、DataShareExtensionAbility等等一系列ExtensionAbility。 | ### 功能简介 diff --git a/zh-cn/device-dev/website.md b/zh-cn/device-dev/website.md index 7c60895c2a5446bffda63bb7fca41cc13cd2c270..897e3e7550dcd897fa94c62fd29cf63525c724f5 100644 --- a/zh-cn/device-dev/website.md +++ b/zh-cn/device-dev/website.md @@ -149,6 +149,8 @@ - 标准系统芯片移植案例 - [标准系统方案之瑞芯微RK3568移植案例](porting/porting-dayu200-on_standard-demo.md) + - [标准系统方案之瑞芯微RK3566移植案例](https://gitee.com/openharmony/vendor_kaihong/blob/master/khdvk_3566b/porting-khdvk_3566b-on_standard-demo.md) + - [标准系统方案之扬帆移植案例](porting/porting-yangfan-on_standard-demo.md) - 子系统开发 @@ -217,6 +219,7 @@ - [虚拟文件系统](kernel/kernel-small-bundles-fs-virtual.md) - [支持的文件系统](kernel/kernel-small-bundles-fs-support.md) - [适配新的文件系统](kernel/kernel-small-bundles-fs-new.md) + - [Plimitsfs文件系统](kernel/kernel-small-plimits.md) - 调测与工具 - Shell - [Shell介绍](kernel/kernel-small-debug-shell-overview.md) @@ -383,6 +386,7 @@ - [产品配置规则](subsystems/subsys-build-product.md) - [子系统配置规则](subsystems/subsys-build-subsystem.md) - [部件配置规则](subsystems/subsys-build-component.md) + - [部件编译构建规范](subsystems/subsys-build-component-building-rules.md) - [模块配置规则](subsystems/subsys-build-module.md) - [芯片解决方案配置规则](subsystems/subsys-build-chip_solution.md) - [特性配置规则](subsystems/subsys-build-feature.md) @@ -393,6 +397,7 @@ - [查看NinjaTrace](subsystems/subsys-build-reference.md) - [HAP编译构建指导](subsystems/subsys-build-gn-hap-compilation-guide.md) - [常见问题](subsystems/subsys-build-FAQ.md) + - [ArkCompiler](subsystems/subsys-arkcompiler-guide.md) - [分布式远程启动](subsystems/subsys-remote-start.md) - 图形图像 - [图形图像概述](subsystems/subsys-graphics-overview.md) @@ -457,6 +462,8 @@ - [系统参数](subsystems/subsys-boot-init-sysparam.md) - [沙盒管理](subsystems/subsys-boot-init-sandbox.md) - [插件](subsystems/subsys-boot-init-plugin.md) + - [组件化启动](subsystems/subsys-boot-init-sub-unit.md) + - [init运行日志规范化](subsystems/subsys-boot-init-log.md) - [appspawn应用孵化组件](subsystems/subsys-boot-appspawn.md) - [bootstrap服务启动组件](subsystems/subsys-boot-bootstrap.md) - [常见问题](subsystems/subsys-boot-faqs.md) diff --git "a/zh-cn/readme/\346\265\213\350\257\225\345\255\220\347\263\273\347\273\237.md" "b/zh-cn/readme/\346\265\213\350\257\225\345\255\220\347\263\273\347\273\237.md" index cfef586c836ade2118dd84dd4f999a4f8674f873..3e9fdbaf2b34b1b7de740aedd90dd990b20d34b4 100755 --- "a/zh-cn/readme/\346\265\213\350\257\225\345\255\220\347\263\273\347\273\237.md" +++ "b/zh-cn/readme/\346\265\213\350\257\225\345\255\220\347\263\273\347\273\237.md" @@ -4,7 +4,7 @@ OpenHarmony为开发者提供了一套全面的自测试框架,开发者可根 本文从基础环境构建,用例开发,编译以及执行等方面介绍OpenHarmony测试框架如何运行和使用。 ## 基础环境构建 测试框架依赖于python运行环境,在使用测试框架之前可参阅以下方式进行配置。 - - [环境配置](../device-dev/subsystems/subsys-testguide-envbuild.md) + - [环境配置](../device-dev/device-test/xdevice.md) - [源码获取](../device-dev/get-code/sourcecode-acquire.md)