Functional description emb6 Network Stack

#Functional description emb6 Network Stack ##Event handling The event driver engine functioned as a lib between the contiki-based timer management and the emb6 architecture without protothreads. The event handling is done in the evproc sources and headers. In the evproc.h all used event types are defined and the API functions are described for an easy use of the event handling. For each event a callback function is registered and invoked in the emb6 main function.

##Timer management The emb6 timer management is derived from the contiki sources and just adapted with small changes to fit in the emb6 stack. The API of the different timers is described in the related header files. More detailed information can be found under [?]

##Packet buffer A packet buffer is a structure that is used to create an outbound packet or store an inbound packet. A packet buffer is also used to operate on a packet and it can store only one packet at a time. More detailed information can be found under [?].

##Board Support Package (BSP) The BSP depicts a sublayer between network stack and hardware abstraction layer 3.6.5. With the BSP it is possible to use hardware functionality in a hardware independent way. On the one hand the BSP just acts as a wrapper of the HAL and one the other hat the BSP provides some added value with extra features e.g. to toggle a LED. These functions are constructed with the help of the utils section (cf. ch. 2.4.6) The platform independent Board Support Package (BSP) provides its API description in the bsp.h, located in the bsp folder including the related source file.

##Hardware Abstraction Layer The hardware abstraction layer represents the hardware dependent functions for every target. The API of the HAL is described in the target.h, located in the target folder. The target-specific sources are implemented in the target.c which can be found in the related MCU folder.