|
 |
|
Compact RTOS with the smallest footprint |
|
|
|
| eT-Kernel/Compact is a compact real-time operating system (RTOS) with the smallest footprint to provide the fastest performance. |
eT-Kernel/Compact has the following features.
| eT-Kernel/Compact Functions |
T-Kernel/OS
(Operating System) |
T-Kernel/SM
(System Manager) |
T-Kernel/DS
(Debugger Support) |
| * |
Task control |
| * |
Task synchronization & communication |
| * |
Memory management |
| * |
Exception/interrupt control |
| * |
Time management |
| * |
Subsystem management |
|
| * |
System memory management |
| * |
Address space management |
| * |
Device management |
| * |
Interrupt management |
| * |
I/O port access support |
| * |
Power management |
| * |
System configuration & information management |
|
| * |
Kernel internal status reference |
| * |
Execution trace |
|
|
|
|
| The basic design and implementation of eT-Kernel/Compact is very similar to that of µITRON in terms of the flat memory space, no MMU, service calls, and the scheduling method, making it very easy to migrate from the µITRON environment. The migration from eT-Kernel/Compact to eT-Kernel/Extended is also very easy. Therefore, it makes the most engineering sense for those using a simple design to start with µITRON-level functions and later migrate to a larger eT-Kernel based system when higher OS functions are necessary.
|
|
|
|
| Migration from PrKERNELv4 |
|
| Migration from PrKERNELv4 is easy because the hardware-dependent code of eT-Kernel/Compact and PrKERNELv4 is shared. There is no need to re-implement firmware around hardware. |
|
|
|
| Make system calls directly |
|
| eT-Kernel/Compact has a configuration switch that selects direct function calling for kernel APIs in the same fashion as µITRON, not the software exception model defined by the T-Kernel specification. Selecting direct function calling can accelerate eT-Kernel performance.
|
|
|
|
| T-Kernel/SM and unused kernel objects can be removed |
|
| Using eT-Kernel/Compact, T-Kernel/SM or unused kernel objects can be removed to minimize memory usage. For example, eT-Kernel/Compact can be configured to exclude T-Kernel/SM if the system does not require functions provided by T-Kernel/SM, such as input/output management of I/O ports. Removing T-Kernel/SM reduces the memory footprint and eliminates T-Kernel/SM initialization so that system startup becomes faster. |
|
|
|
| eBinder: optimal development environment for T-Kernel |
|
| eSOL offers the eBinder development environment for T-Kernel-based embedded system development. |
|
| Item |
Summary |
| CPU |
eT-Kernel/Compact operates on the following CPUs:
|
| * |
ARM920T |
| * |
SH7727, SH7751R, SH7780 |
| * |
VR5500, VR5701, TX49 |
|
|
|
 |
Click here for more information. |
|
Click here for information on customization or contract development. |
|
|
|
