|
 |
|
POSIX-compliant real-time operating system |
|
|
|
| eT-Kernel/POSIX, developed exclusively by eSOL based on eT-Kernel/Extended, is an enhanced POSIX-compliant real-time OS providing full support for pthread, signal, and IPC (Inter Process Communication) on the system level.
eT-Kernel/POSIX implements standard UNIX-based interface specifications, including Linux. UNIX-based OSs are widely used overseas and support a variety of commercial/open source software. It is broadly incorporated not only with embedded systems, but also with other systems such as infrastructure systems. Therefore there is a rich resource of UNIX engineers available both domestically and internationally.
eT-Kernel/POSIX enables you to utilize these resources in deployment with eT-Kernel's superior realtime capability.
eT-Kernel/POSIX produces a more efficient development cycle for embedded systems, which are becoming larger-scaled with more features. |
|
|
| POSIX-compliant enhanced real-time OS |
|
eT-Kernel/POSIX complies with the IEEE Std 1003.1, 2004 Edition The Open Group Technical Standard Base Specifications, Issue 6, and supports most POSIX APIs that are prescribed in it.
eT-Kernel/POSIX is not a mere wrapper library, but is able to achieve total POSIX functionality by tuning the eT-Kernel core. eT-Kernel/POSIX:
| * |
Supports XBD (Base Definitions volume) and XSH (System Interfaces volume) |
| * |
Supports pthread as a thread-managing function in/between processes |
|
*
|
Completely supports IPC (Inter Process Communication) |
|
*
|
Supports programming using signals which is often used in UNIX systems |
|
|
|
|
| Reusability in UNIX-based OS software and engineering resources |
|
| eT-Kernel/POSIX was purposely designed and developed to reuse UNIX-based OS software. Therefore you can construct systems incorporating the superior real-time functions of eT-Kernel while you are reusing existing UNIX-based OS software, including Linux and other commercial/open source software. You can also utilize domestic and international engineers who have UNIX application development experience. |
|
|
|
| Co-existence of POSIX and T-Kernel applications |
|
| In addition to being able to construct systems using only POSIX functions, POSIX-based applications and T-Kernel based applications can co-exist in one system.
It is especially beneficial for you when you want to add a new function to an existing T-Kernel-based system, because you can directly reuse any POSIX-based commercial/open-source software, such as network middleware, on eT-Kernel/POSIX without going to the trouble of implementing the function in T-Kernel. |
|
|
|
| Basic functions of eT-Kernel/POSIX |
|
eT-Kernel/POSIX has the following basic functions:
| * |
Process/task management |
| * |
Thread management |
|
*
|
Timer management |
|
*
|
Synchronization/communication between tasks:
Signal/Barrier/Rwlock/Condition Variable/Semaphore/Mutex/Message Queue |
|
*
|
Pipe/FIFO |
|
*
|
Asymmetric I/O |
|
*
|
Socket |
|
|
|
|
| eBinder — the development environment |
|
A user process/system process, system program, shared library, and DLL may all be developed using eBinder. eBinder assists in debugging a process, tasks within a process or even device drivers.
|
|
|
|
eT-Kernel/POSIX structure
|
|
|
|
| eT-Kernel/POSIX was developed based on eT-Kernel/Extended. POSIX functions were implemented as subsystems and libraries of eT-Kernel/Extended. |
|
| On eT-Kernel/POSIX, while you can implement applications using only the POSIX API, POSIX-based applications and T-Kernel-based applications can co-exist in one system, because there is a transmitting method between these two applications. |
eT-Kernel/POSIX structure
|
| The following graphic expresses how POSIX and T-Kernel programming relate to each other.
The center portion, where two oval shapes are overlapped, is jointly used by both POSIX applications and T-Kernel applications. |
POSIX programming
| * |
Partial service from device drivers, T-Kernel, and T-Kernel Standard Extensions that are implemented as T-Kernel applications is applied when you use the device management function. |
| * |
You can use T-Kernel, T-Kernel Standard Extensions, and T-Kernel-based subsystem/DLLs. |
|
*
|
You can implement subsystems, shared libraries, and DLLs, which deploy POSIX services.
|
|
T-Kernel programming
| * |
Only T-Kernel-based programs are available from T-Kernel applications. POSIX or POSIX-based-services, subsystems, shared libraries, and DLLs are not applicable. |
|
|
| Item |
Description |
| CPU |
eT-Kernel/POSIX supports the following CPU:
| - |
CPU with ARM/MPCore architecture |
| - |
MIPS architecture |
| ** |
Support for SH series will be available soon |
|
|
|
 |
Click here for more information. |
|
Click here for information on customization or contract development. |
|
|
|
