MansOS Architecture - Revision history

Girts at 09:01, 14 November 2011

2011-11-14T09:01:25Z

Girts at 08:59, 14 November 2011

2011-11-14T08:59:40Z

Girts at 08:58, 14 November 2011

2011-11-14T08:58:31Z

Girts at 14:19, 26 October 2011

2011-10-26T14:19:13Z

Girts at 14:18, 26 October 2011

2011-10-26T14:18:04Z

Leo: /* Related publications and papers */

2010-11-10T09:43:05Z

‎Related publications and papers

Leo: New page: Mansos architecture is tailored for ease of portability to different hardware platforms. The OS is structured in three main layers: * HIL - Hardware Interface layer is hardware independa...

2008-11-12T16:50:12Z

New page: Mansos architecture is tailored for ease of portability to different hardware platforms. The OS is structured in three main layers: * HIL - Hardware Interface layer is hardware independa...

New page

Mansos architecture is tailored for ease of portability to different hardware platforms.

The OS is structured in three main layers:

* HIL - Hardware Interface layer is hardware independant services that almost any hardware should support or at least emulate.

* HAL - Hardware abstraction layer provides services speciffic to hardware platforms - collections of modules and chips

* HPL - Hardware presentation layer defines the services by the lowest level of hardware - usually chips or certain low level services that do not keep state. HPL is talking directly to hardware.

On top of the structure atre defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.

Another interface between the user applications and the OS are the system calls, such as sleep(milliseconds) or yield().

as a result an application can be developed witout the specifics of the hardware. In fact, one of the platforms provided is PC that allows for immediate application debugging and simulation at a high level.

The OS also provides tools such as PRINT that let the developers debug their embedded systems over the serial, radio, or any other supported link.

=== Related publications and papers ===

* [http://www.polastre.com/papers/ewsn05-fha.pdf Flexible Hardware abstraction] describing the HPL - HAL - HIL notion
* [http://www.liteos.net/docs/IPSN_2008.pdf LiteOS paper], the original OS from which MansOS branched

@@ Line 13: / Line 13: @@
 On top of the structure are defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.
-Another interface between the user applications and the OS are the system calls, such as sleep(milliseconds) or yield().
+Another interface between the user applications and the OS are the system calls, such as msleep(milliseconds).
 As a result an application can be developed without the specifics of the hardware. In fact, one of the platforms provided is PC that allows for immediate application debugging and simulation at a high level.

@@ Line 9: / Line 9: @@
 * HPL - Hardware presentation layer defines the services by the lowest level of hardware - usually chips or certain low level services that do not keep state. HPL is talking directly to hardware.
-[[Image:MansOS-arch-2011-sensys.png | MansOS Architecture]]
+[[Image:MansOS-arch-2011-sensys.png | 600px | MansOS Architecture]]
 On top of the structure are defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.

@@ Line 9: / Line 9: @@
 * HPL - Hardware presentation layer defines the services by the lowest level of hardware - usually chips or certain low level services that do not keep state. HPL is talking directly to hardware.
+[[Image:MansOS-arch-2011-sensys.png | MansOS Architecture]]
 On top of the structure are defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.

← Older revision		Revision as of 14:18, 26 October 2011
Line 10:		Line 10:


	On top of the structure ~~atre~~ defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.		On top of the structure are defined device drivers and device manager, allowing for a unified and arbitrated access to the resources by all applications.

	Another interface between the user applications and the OS are the system calls, such as sleep(milliseconds) or yield().		Another interface between the user applications and the OS are the system calls, such as sleep(milliseconds) or yield().

@@ Line 14: / Line 14: @@
 Another interface between the user applications and the OS are the system calls, such as sleep(milliseconds) or yield().
-as a result an application can be developed witout the specifics of the hardware. In fact, one of the platforms provided is PC that allows for immediate application debugging and simulation at a high level.
+As a result an application can be developed without the specifics of the hardware. In fact, one of the platforms provided is PC that allows for immediate application debugging and simulation at a high level.
 The OS also provides tools such as PRINT that let the developers debug their embedded systems over the serial, radio, or any other supported link.

@@ Line 21: / Line 21: @@
 === Related publications and papers ===
-* [http://www.polastre.com/papers/ewsn05-fha.pdf Flexible Hardware abstraction] describing the HPL - HAL - HIL notion
+* [http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1462006 Flexible Hardware abstraction] describing the HPL - HAL - HIL approach
 * [http://www.liteos.net/docs/IPSN_2008.pdf LiteOS paper], the original OS from which MansOS branched