 |
Life with dooroos |
|
|
|
|
|
dooroos.realtime > MACRO-KERNEL |
|
| |
 |
MACRO KERNEL | |
| |
 |
Profile |
 |
The macro kernel is run on the micro-kernel and the nano-kernel. The micro-kernel and the nano-kernel is the core of the real-time operating system,
but the macro-kernel is the expansion of the operating system to support the various OS functions needed to design the products.
The following supported functions are the standard servers. But The dooroos.realtime has no restriction to develope the user-defined server (expanded function).
So, the user can insert the user-specific function servers. This architecture provides the freedom to the solution to design the best user-products.
|
|
Loader Server |
|
Loader server of the dooroos.realtime provides the load / the unload of the DLL files, the DRV(driver) files and the EXE(executable) files.
The loader server can automatically link the loaded symbol's symbols with the DLL and the dooroos.realtime kernel symbols.
|
 |
DLL, DRV, EXE files loading/unloading functions. |
|
Automatic symbol link. |
|
Device (Driver) Server |
|
Device server of the dooroos.realtime provides the attachment / detachment of the device driver.
The device driver can be attached or detached to the dooroos.realtime freely without re-boot.
The device server manages the access handle. All other parts can acquire the access handle from the device server.
All device driver should be registered to the device driver to be accessed.
|
|
Device Driver attach/detach function. |
|
Access handle management to device driver. |
|
Filesystem Server |
|
The filesystem server provides the data access service to the file on the block device.
The application can use the various services of filesystem server to access the file.
Some filesytems are provided, but the other filesystem can be plug-ined easily to the filesystem server without any restriction.
The filesystem server uses the device server to access the block device, so block device driver should use standard device driver model.
|
|
The file access on block device. |
|
The small memory requirement. |
|
The access to various media(NOR filesystem, NAND filesystem, MMC, SD card,...) |
|
The various media management support. |
|
The simultaneous access to the various filesystem and the mounting function support. |
|
The standard filesystem API support to the many filesystem. |
|
FAT12/16/32 filesystem support. |
|
ROM filesystem support |
|
RAM filesystem support |
|
Window Server |
|
The window server manages the window on the display device. The application can use the window server to make the GUI and graphical interface.
All the window is consist of the widget units. The widget is managed by the widget procedure supported by window server and is displayed on
the screen by using the widget drawing fuctions and graphic library.
|
|
Window management support. |
|
Standard window API support. |
|
Drawing function call to display device. |
|
The input device is connected to the thread |
|
The graphic library and the window server is seperated. |
|
User defined graphic library can be added. |
|
The hardware dependent part is implemented in SDI (screen device drvier). |
|
Network Server |
|
The network server supports the TCP/IP network service. The application can use the network server to access the network.
The socket interface is provided and TCP/UDP, IP, ICMP, ARP, RARP etc. is supported, but the not supported protocols can be implemented by using network server.
The network device driver looks like the general device driver model, but some special network API is given.
|
|
The memory usage is defined to control the network throughput. |
|
Provide the high speed and the high throughput network. |
|
The stable network protocol is supported. |
|
The network device driver regitration/deregistration. |
|
Raw, TCP, UDP protocol. |
|
IP, ICMP, ARP, RARP protocol. |
|
|
|
is
