Go to file
arvinzzz 6f6dc4f24c fix: 修复内核c库的makefile中被优化函数替换的高频函数依然参与了编译的问题
1. 更正makefile过滤时被替换函数的不正确路径
2. 防止LOCAL_SRCS再直接+= /*/*.c添加回来

close: #I3XGM8

Signed-off-by: arvinzzz <zhaotianyu9@huawei.com>
Change-Id: I3aff2a60c5a48f2d6c174afa04d30fa6f5514d7e
2021-06-28 17:34:08 +08:00
.gitee add issue and pr template 2021-04-07 14:49:32 +08:00
apps fix: avoid compile warning ignored 2021-06-15 19:56:21 +08:00
arch !302 fix: Codex告警清零 2021-06-08 08:48:48 +08:00
bsd fix: remove redundant headfile 2021-06-19 17:32:47 +08:00
compat/posix !322 文件系统冗余代码和依赖删除 2021-06-19 20:40:14 +08:00
drivers fix: 设置qemu默认userfs大小/修改qemu驱动目录 2021-06-26 15:38:19 +08:00
figures update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
fs !362 修复在Liteos-a在FATFS中创建的文件夹在Ubuntu中不可见的BUG 2021-06-25 07:20:10 +00:00
kernel fix: 设置qemu默认userfs大小/修改qemu驱动目录 2021-06-26 15:38:19 +08:00
lib fix: 修复内核c库的makefile中被优化函数替换的高频函数依然参与了编译的问题 2021-06-28 17:34:08 +08:00
net fix: SIOCGIFCONF ioctl malloc size error in kernel 2021-06-26 10:26:40 +08:00
platform refactor: Refactored the kernel boot process and added a init framework 2021-05-20 16:45:43 +08:00
security remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
shell refactor: Refactored the kernel boot process and added a init framework 2021-05-20 16:45:43 +08:00
syscall fix: remove redundant headfile 2021-06-19 17:32:47 +08:00
testsuites test: 信号管道用例ItPosixPipe005由于偶现性问题暂时下线 2021-06-26 15:27:31 +08:00
tools feat: L1支持低功耗投票框架 2021-06-24 14:27:23 +08:00
.gitignore fix: Show conflicting files for git apply or patch -p command 2021-04-22 16:44:46 +08:00
BUILD.gn fix: add product_path parameter for driver build 2021-06-22 15:18:54 +08:00
Kconfig !263 fix(build): 去除冗余单板相关的宏配置 2021-06-09 14:02:52 +08:00
LICENSE update openharmony 1.0.1 2021-03-11 18:43:57 +08:00
Makefile chore: add a mini config for qemu arm virt 2021-06-05 17:40:22 +08:00
README.md TicketNo:DTS2021012805GXU8P0H00 2021-03-16 16:54:09 +08:00
README_zh-HK.md fix(doc): 修复README_zh-HK.md的链接错误 2021-06-25 14:13:32 +08:00
README_zh.md README_zh.md: update the correct links 2021-06-03 09:24:50 +08:00
TODOList.md update TODOList.md. 2021-05-21 15:01:20 +08:00
build.sh fix: avoid compile warning ignored 2021-06-15 19:56:21 +08:00
config.mk remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00
kernel_test.sources remove __cplusplus guards in .c files 2021-04-19 18:28:25 +08:00

README.md

LiteOS Cortex-A

Introduction

The OpenHarmony LiteOS Cortex-A is a new-generation kernel developed based on the Huawei LiteOS kernel. Huawei LiteOS is a lightweight operating system OS built for the Internet of Things IoT field. With the rapid development of the IoT industry, OpenHarmony LiteOS Cortex-A brings small-sized, low-power, and high-performance experience and builds a unified and open ecosystem for developers. In addition, it provides rich kernel mechanisms, more comprehensive Portable Operating System Interface POSIX, and a unified driver framework, Hardware Driver Foundation HDF, which offers unified access for device developers and friendly development experience for application developers. Figure 1 shows the architecture of the OpenHarmony LiteOS Cortex-A kernel.

Figure 1 Architecture of the OpenHarmony LiteOS Cortex-A kernel

Directory Structure

/kernel/liteos_a
├── apps                   # User-space init and shell application programs
├── arch                   # System architecture, such as ARM
│   └── arm                # Code for ARM architecture
├── bsd                    # Code of the driver and adaptation layer module related to the FreeBSD, such as the USB module
├── compat                 # Kernel API compatibility
│   └── posix              # POSIX APIs
├── drivers                # Kernel drivers
│   └── char               # Character device
│       ├── mem            # Driver for accessing physical input/output (I/O) devices
│       ├── quickstart     # APIs for quick start of the system
│       ├── random         # Driver for random number generators
│       └── video          # Framework of the framebuffer driver
├── fs                     # File system module, which mainly derives from the NuttX open-source project
│   ├── fat                # FAT file system
│   ├── jffs2              # JFFS2 file system
│   ├── include            # Header files exposed externally
│   ├── nfs                # NFS file system
│   ├── proc               # proc file system
│   ├── ramfs              # RAMFS file system
│   └── vfs                # VFS layer
├── kernel                 # Kernel modules including the process, memory, and IPC modules
│   ├── base               # Basic kernel modules including the scheduling and memory modules
│   ├── common             # Common components used by the kernel
│   ├── extended           # Extended kernel modules including the dynamic loading, vDSO, and LiteIPC modules
│   ├── include            # Header files exposed externally
│   └── user               # Init process loading
├── lib                    # Kernel library
├── net                    # Network module, which mainly derives from the lwIP open-source project
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
│   ├── hw                 # Logic code related to clocks and interrupts
│   ├── include            # Header files exposed externally
│   └── uart               # Logic code related to the serial port
├── platform               # Code for supporting different systems on a chip (SOCs), such as Hi3516D V300
├── security               # Code related to security features, including process permission management and virtual ID mapping management
├── syscall                # System calling
└── tools                  # Building tools as well as related configuration and code

Constraints

  • Programming languages: C and C++
  • Applicable development boards: Hi3518E V300 and Hi3516D V300
  • Hi3518E V300 uses the JFFS2 file system by default, and Hi3516D V300 uses the FAT file system by default.

Usage

OpenHarmony LiteOS Cortex-A supports the Hi3518E V300 and Hi3516D V300. You can develop and run your applications based on both development boards.

Preparations

You need to set up the compilation environment on Linux.

Source Code Acquisition

Download and decompress a set of source code on a Linux server to acquire the source code. For more acquisition methods, see Source Code Acquisition.

Compilation and Building

For details about how to develop the first application, see:

Repositories Involved

Kernel subsystem

drivers_liteos

kernel_liteos_a