This topic provides a panorama of all documents for you to obtain helpful information quickly. These documents are classified based on your learning progress and development scenarios of OpenHarmony.
...
...
@@ -12,161 +12,46 @@ To make the integration simple and easy on different hardware, OpenHarmony defin
- Mini system
A mini system runs on the devices whose memory is greater than or equal to 128 KiB and that are equipped with MCU processors such as Arm Cortex-M and 32-bit RISC-V. This system provides multiple lightweight network protocols and graphics frameworks, and a wide range of read/write components for the IoT bus. Typical products include connection modules, sensors, and wearables for smart home.
A mini system fits into the devices that come with Micro Controller Units (MCUs), such as Arm Cortex-M and 32-bit RISC-V processors, and memory greater than or equal to 128 KiB. This system provides multiple lightweight network protocols, a graphics framework, and a wide range of read/write components with the IoT bus. Typical products include connection modules, sensors, and wearables for smart home.
- Small system
A small system runs on the devices whose memory is greater than or equal to 1 MiB and that are equipped with application processors such as Arm Cortex-A. This system provides higher security capabilities, standard graphics frameworks, and video encoding and decoding capabilities. Typical products include smart home IP cameras, electronic cat eyes, and routers, and event data recorders \(EDRs\) for smart travel.
A small system fits into the devices that come with application processors, such as Arm Cortex-A, and memory greater than or equal to 1 MiB. This system provides higher security capabilities, standard graphics frameworks, and video encoding and decoding capabilities. Typical products include smart home IP cameras, electronic cat eyes, and routers, and event data recorders (EDRs) for easy travel.
- Standard system
A standard system runs on the devices whose memory is greater than or equal to 128 MiB and that are equipped with application processors such as Arm Cortex-A. This system provides a complete application framework supporting the enhanced interaction, 3D GPU, hardware composer, diverse components, and rich animations. This system applies to high-end refrigerator displays.
A standard system fits into the devices that come with application processors, such as Arm Cortex-A, and memory greater than or equal to 128 MiB. This system provides a complete application framework supporting enhanced interactions, 3D GPU, hardware composer, diverse components, and various animations. Typical products include high-end refrigerator displays.
In addition, OpenHarmony provides a series of optional system components that can be configured as required to support feature extension and customization. These system components are combined to form a series of system capabilities that, for better understanding, are described as features or functions for you to choose.
In addition, OpenHarmony provides a wide array of system components that can be configured as required to support feature extension and customization. These system components are combined to form a series of system capabilities that, for better understanding, are described as features or functions for you to choose.
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p14987151715312"><aname="p14987151715312"></a><aname="p14987151715312"></a>Getting familiar with <spanid="text9808161615252"><aname="text9808161615252"></a><aname="text9808161615252"></a>OpenHarmony</span></p>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p39871917185313"><aname="p39871917185313"></a><aname="p39871917185313"></a>Preparing for your development</p>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p55771237111517"><aname="p55771237111517"></a><aname="p55771237111517"></a>Getting started with setup, build, burning, debugging, and running of <spanid="text203751321355"><aname="text203751321355"></a><aname="text203751321355"></a>OpenHarmony</span></p>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><pid="p10832159115410"><aname="p10832159115410"></a><aname="p10832159115410"></a><ahref="quick-start/quickstart-lite.md">Mini and Small Systems</a></p>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p857711379158"><aname="p857711379158"></a><aname="p857711379158"></a>Using basic capabilities of <spanid="text8928941123820"><aname="text8928941123820"></a><aname="text8928941123820"></a>OpenHarmony</span></p>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><aname="ul1577103716159"></a><aname="ul1577103716159"></a><ulid="ul1577103716159"><li><ahref="kernel/kernel-mini.md">Kernel for Mini Systems</a></li><li><ahref="kernel/kernel-small.md">Kernel for Small Systems</a></li><li><ahref="driver/Readme-EN.md">Drivers</a></li><li><ahref="subsystems/Readme-EN.md">Subsystems</a></li><li><ahref="security/security-guidelines-overall.md">Security Guidelines</a></li><li><ahref="security/security-privacy-protection.md">Privacy Protection</a></li></ul>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p155782037201518"><aname="p155782037201518"></a><aname="p155782037201518"></a>Developing smart devices based on system capabilities</p>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><aname="ul257883731519"></a><aname="ul257883731519"></a><ulid="ul257883731519"><li><ahref="guide/device-wlan.md">WLAN-connected Products</a></li><li><ahref="guide/device-iotcamera-control.md">Cameras Without a Screen</a></li><li><ahref="guide/device-camera.md">Cameras with a Screen</a></li></ul>
</td>
</tr>
<trid="row360273716155"><tdclass="cellrowborder"valign="top"width="28.472847284728473%"headers="mcps1.2.4.1.1 "><pid="p12579163711513"><aname="p12579163711513"></a><aname="p12579163711513"></a>Porting and adaptation</p>
</td>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><aname="ul12579137121512"></a><aname="ul12579137121512"></a><ulid="ul12579137121512"><li>Porting and adapting the <spanid="text1415622205014"><aname="text1415622205014"></a><aname="text1415622205014"></a>OpenHarmony</span> to an SoC</li><li>Porting and adapting the <spanid="text82061719165013"><aname="text82061719165013"></a><aname="text82061719165013"></a>OpenHarmony</span> to a third-party library</li></ul>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><aname="ul157903731520"></a><aname="ul157903731520"></a><ulid="ul157903731520"><li><ahref="porting/porting-minichip.md">Mini System SoC Porting Guide</a></li><li><ahref="porting/porting-smallchip.md">Small System SoC Porting Guide</a></li><li><ahref="porting/porting-thirdparty.md">Third-Party Library Porting Guide for Mini and Small Systems</a></li></ul>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p45798376158"><aname="p45798376158"></a><aname="p45798376158"></a>Contributing components to <spanid="text207913212498"><aname="text207913212498"></a><aname="text207913212498"></a>OpenHarmony</span></p>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><aname="ul957919379156"></a><aname="ul957919379156"></a><ulid="ul957919379156"><li><ahref="hpm-part/hpm-part-about.md">HPM Part Overview</a></li><li><ahref="hpm-part/hpm-part-development.md">HPM Part Development</a></li><li><ahref="hpm-part/hpm-part-reference.md">HPM Part Reference</a></li></ul>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p458073721519"><aname="p458073721519"></a><aname="p458073721519"></a>Referring to development specifications</p>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p16673531512"><aname="p16673531512"></a><aname="p16673531512"></a>Getting familiar with <spanid="text897788591"><aname="text897788591"></a><aname="text897788591"></a>OpenHarmony</span></p>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p0671053115115"><aname="p0671053115115"></a><aname="p0671053115115"></a>Preparing for your development</p>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p1167135345112"><aname="p1167135345112"></a><aname="p1167135345112"></a>Getting started with setup, build, burning, debugging, and running of <spanid="text687119202170"><aname="text687119202170"></a><aname="text687119202170"></a>OpenHarmony</span></p>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p136812535511"><aname="p136812535511"></a><aname="p136812535511"></a>Using basic capabilities of <spanid="text1468659507"><aname="text1468659507"></a><aname="text1468659507"></a>OpenHarmony</span></p>
</td>
<tdclass="cellrowborder"valign="top"width="36.07360736073608%"headers="mcps1.2.4.1.3 "><aname="ul1954915235272"></a><aname="ul1954915235272"></a><ulid="ul1954915235272"><li><ahref="kernel/kernel-standard.md">Kernel for Standard Systems</a></li><li><ahref="driver/Readme-EN.md">Drivers</a></li><li><ahref="subsystems/Readme-EN.md">Subsystems</a></li><li><ahref="security/security-guidelines-overall.md">Security Guidelines</a></li><li><ahref="security/security-privacy-protection.md">Privacy Protection</a></li></ul>
<tdclass="cellrowborder"valign="top"width="35.61356135613561%"headers="mcps1.2.4.1.2 "><pid="p155782037201518"><aname="p155782037201518"></a><aname="p155782037201518"></a>Developing smart devices based on system capabilities</p>
</td>
<tdclass="cellrowborder"valign="top"width="35.91359135913591%"headers="mcps1.2.4.1.3 "><aname="ul257883731519"></a><aname="ul257883731519"></a><ulid="ul257883731519"><li><ahref="guide/device-clock-guide.md">Development Guidelines on Clock Apps</a></li><li><ahref="guide/device-driver-demo.md">Development Example for Platform Drivers</a></li><li><ahref="guide/device-outerdriver-demo.md">Development Example for Peripheral Drivers</a></li></ul>
</td>
</tr>
<trid="row66915375119"><tdclass="cellrowborder"valign="top"width="27.872787278727873%"headers="mcps1.2.4.1.1 "><pid="p4696535512"><aname="p4696535512"></a><aname="p4696535512"></a>Porting and adaptation</p>
</td>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p185185615284"><aname="p185185615284"></a><aname="p185185615284"></a>Porting and adapting the <spanid="text1434016533511"><aname="text1434016533511"></a><aname="text1434016533511"></a>OpenHarmony</span> to a third-party library</p>
</td>
<tdclass="cellrowborder"valign="top"width="36.07360736073608%"headers="mcps1.2.4.1.3 "><aname="ul14724164204819"></a><aname="ul14724164204819"></a><ulid="ul14724164204819"><li><ahref="porting/standard-system-porting-guide.md">Standard System Porting Guide</a></li><li><ahref="porting/porting-linux-kernel.md">A Method for Rapidly Porting the OpenHarmony Linux Kernel </a></li></ul>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p1469115335113"><aname="p1469115335113"></a><aname="p1469115335113"></a>Contributing components to <spanid="text1180831622"><aname="text1180831622"></a><aname="text1180831622"></a>OpenHarmony</span></p>
</td>
<tdclass="cellrowborder"valign="top"width="36.07360736073608%"headers="mcps1.2.4.1.3 "><aname="ul44949625110"></a><aname="ul44949625110"></a><ulid="ul44949625110"><ahref="hpm-part/hpm-part-about.md">HPM Part Overview</a></li><li><ahref="hpm-part/hpm-part-development.md">HPM Part Development</a></li><li><ahref="hpm-part/hpm-part-reference.md">HPM Part Reference</a></li></ul>
<tdclass="cellrowborder"valign="top"width="36.053605360536054%"headers="mcps1.2.4.1.2 "><pid="p670135335116"><aname="p670135335116"></a><aname="p670135335116"></a>Referring to development specifications</p>
**Table 1** Mini and small system development guidelines (reference memory < 128 MB)
| Topic| Development Scenario| Related Documentation|
| -------- | -------- | -------- |
| About OpenHarmony| Getting familiar with OpenHarmony| - [About OpenHarmony](https://gitee.com/openharmony)<br>- [Glossary](../glossary.md) |
| Development resources| Preparing for your development| - [Obtaining Source Code](get-code/sourcecode-acquire.md)<br>- [Obtaining Tools](get-code/gettools-acquire.md) |
| Getting started| Getting started with setup, build, burning, debugging, and running of OpenHarmony| [Mini and Small Systems](quickstart/quickstart-lite.md)|
| Basic capabilities| Using basic capabilities of OpenHarmony| - [Kernel for Mini System](kernel/kernel-mini-overview.md)<br>- [Kernel for Small System](kernel/kernel-small-overview.md)<br>- [HDF](driver/driver-hdf-overview.md)<br>- [Subsystems](subsystems/subsys-build-mini-lite.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md)|
| Advanced development| Developing smart devices based on system capabilities| - [WLAN-connected Products](guide/device-wlan-led-control.md)<br>- [Cameras Without a Screen](guide/device-iotcamera-control-overview.md)<br>- [Cameras with a Screen](guide/device-camera-control-overview.md) |
| Porting and adaptation| - Porting and adapting OpenHarmony to an SoC<br>- Porting and adapting OpenHarmony to a third-party library| - [Mini System SoC Porting](porting/oem_transplant_chip_prepare_knows.md)<br>- [Small System SoC Porting](porting/porting-smallchip-prepare-needs.md)<br>- [Third-Party Library Porting for Mini and Small Systems](porting/porting-thirdparty-overview.md) |
| Contributing components| Contributing components to OpenHarmony| - [HPM Part Overview](hpm-part/hpm-part-about.md)<br>- [HPM Part Development](hpm-part/hpm-part-development.md)<br>- [HPM Part Reference](hpm-part/hpm-part-reference.md) |
| Reference| Referring to development specifications| - [API References](https://gitee.com/link?target=https%3A%2F%2Fdevice.harmonyos.com%2Fen%2Fdocs%2Fdevelop%2Fapiref%2Fjs-framework-file-0000000000616658)<br>- [FAQs](faqs/faqs-overview.md) |
**Table 2** Standard system development guidelines (reference memory ≥ 128 MB)
| Topic| Development Scenario| Related Documentation|
| -------- | -------- | -------- |
| About OpenHarmony| Getting familiar with OpenHarmony| - [About OpenHarmony](https://gitee.com/openharmony)<br>- [Glossary](../glossary.md) |
| Development resources| Preparing for your development| - [Obtaining Source Code](get-code/sourcecode-acquire.md)<br>- [Obtaining Tools](get-code/gettools-acquire.md) |
| Getting started| Getting started with setup, build, burning, debugging, and running of OpenHarmony| [Standard System](quick-start/)|
| Basic capabilities| Using basic capabilities of OpenHarmony| - [Kernel Development](kernel/kernel-standard.md)<br>- [HDF](driver/driver-hdf-overview.md)<br>- [Subsystems](subsystems/subsys-build-standard-large.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md)|
| Advanced development| Developing smart devices based on system capabilities| - [Development Guidelines on Clock Apps](guide/device-clock-guide.md)<br>- [Development Example for Platform Drivers](guide/device-driver-demo.md)<br>- [Development Example for Peripheral Drivers](guide/device-outerdriver-demo.md) |
| Porting and adaptation| Porting and adapting OpenHarmony to a third-party library| - [Standard System Porting Guide](porting/standard-system-porting-guide.md)<br>- [A Method for Rapidly Porting the OpenHarmony Linux Kernel](porting/porting-linux-kernel.md) |
| Contributing components| Contributing components to OpenHarmony| - [HPM Part Overview](hpm-part/hpm-part-about.md)<br>- [HPM Part Development](hpm-part/hpm-part-development.md)<br>- [HPM Part Reference](hpm-part/hpm-part-reference.md) |
| Reference| Referring to development specifications| - [API References](https://gitee.com/link?target=https%3A%2F%2Fdevice.harmonyos.com%2Fen%2Fdocs%2Fdevelop%2Fapiref%2Fjs-framework-file-0000000000616658)<br>- [FAQs](faqs/faqs-overview.md) |
