Policy & Caution
Kernel & System
File System
Network
Audio
Confirmation of Porting
-
Driver Implementation Recommendation
Instead of hooking the default driver interface code (which is a part of SoC package) to the platform,
it is advisable to include the drivers according the TizenRT platform driver model. -
New Application Inclusion
It is a good practise to add the Kconfig entry. All application configurations and dependencies should be included properly. -
Use driver, framework and system call APIs
Don't call architecture codes from application directly. When protected build enables, it will be blocked.
Application must call TizenRT driver interface to talk to underlying driver. -
Maintain TizenRT Code Structure
It is not advised if addition of peripherals, new interfaces, new open source code etc are done by aligning to default board package structure.
Understanding the TizenRT code structure and adhering to the structure helps in better architecture desgin and portability.
- How to add new board
- How to use peripheral
- How to add static library
- How to configure memory
- How to use MPU
- How to use LWIP (will be updated)
- How to port TizenRT on new WiFi chipset
Will be updated
Will be updated