|
 |
|
Standard T-Kernel with device drivers |
|
|
|
eT-Kernel/Standard is a real-time OS that includes eT-Kernel/Compact with T-Engine standard device drivers. Higher-level development may begin right away without having to develop device drivers from scratch. It is easy to reuse device drivers and software which relies on the drivers. Otherwise, the features and benefits are similar to eT-Kernel/Compact.
|
|
|
| eT-Kernel/Standard comes with T-Engine standard device drivers |
|
The following is the list of T-Engine device drivers included in eT-Kernel/Standard.
|
| Available T-Engine standard device drivers: |
| PCMCIA bus driver, clock (RTC), console (serial), system disk, KB/PD (keyboard, touch panel, mouse), monitor (LCD), USB bus driver (USB host function) |
|
|
|
| Features of eT-Kernel/Standard |
|
eT-Kernel/Standard has the following features.
| Functions of eT-Kernel/Standard |
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 |
|
|
|
|
| eT-Kernel/Standard is similar to µITRON in terms of the flat memory space, no MMU, service calls, and the internal configuration of OS. Therefore, it is perfect for migrating from µITRON. And, because of the ease of migration to eT-Kernel/Extended, it makes sense when µITRON-level functions are sufficient for an immediate purpose but higher OS functions will be necessary in future.
|
|
|
|
| Migration from PrKERNELv4 |
|
| Migration from PrKERNELv4 is easy because the hardware-dependent code of eT-Kernel/Standard and PrKERNELv4 is shared. There is no need to re-implement firmware around hardware. |
|
|
|
| Make system calls directly |
|
| eT-Kernel/Standard has a configuration switch that lets you select direct kernel API function calling in the same fashion as µITRON, not the software exception model as defined by the T-Kernel specification. Selecting direct calling can accelerate eT-Kernel performance.
|
|
|
|
| T-Kernel/SM and unused kernel objects can be removed |
|
Using eT-Kernel/Standard, T-Kernel/SM or unused kernel objects may 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.
* T-Kernel/SM cannot be removed when using T-Engine standard device drivers. |
|
|
|
| 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/Standard 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. |
|
|
|
