/*!
<!--

This document is automatically processed by Doxygen (http://www.doxygen.org/).
Don't remove special formatting tags.
This section won't be processed unless enabled.

Doxygen supports a LaTeX-like syntax to write documentation; use that syntax to make changes to this file.
You can find a reference here: http://www.stack.nl/~dimitri/doxygen/manual.html, inside the section 'Special commands'.

For tables, use ONLY the html formatting tags that you can find in the previous page in the section 'HTML commands'. This way
we'll always be able to generate valid documentation for every language supported by Doxygen.

Remember to use Doxygen tags sparingly inside source code.
-->






 
\page dev_status BeRTOS Development Status

If you are looking for the list of BeRTOS ports or a detailed overview of all modules completeness and stability this is the right place.

BeRTOS is stable and it's used in production environments but it is also a very large project, so all of its parts may not be at the same level.

Table of contents:

 \li \ref kernel
 \li \ref core_drivers
 \li \ref internal_peripherals
 \li \ref independant_drivers
 \li \ref storage
 \li \ref graphics
 \li \ref algorithms
 \li \ref networking
 \li \ref data_structures
 \li \ref mware

\section kernel Kernel
BeRTOS features a cooperative kernel with synchronization primitives.

Embedded systems are mostly I/O bound systems. In these systems the microprocessor/microcontroller spends the most part of its computing power doing... absolutely nothing :-)

Since the system simply waits for external events to happen we decided to implement a strong and robust cooperative kernel with very low memory footprint and high modularity. This allows the kernel to be used on a variety of different CPUs, even the smaller ones.
Currently the kernel code is very stable.

<b> Kernel features </b>:
  \li \link preempt.c Cooperative and preemptive \endlink round-robin scheduling.
  \li \link monitor.h Stack process monitor \endlink, useful to prevent stack overflows.
  \li \link msg.h Inter-process messaging system \endlink (with very low overhead).
  \li \link sem.h Binary semaphores \endlink.
  \li \link signal.c Signals \endlink.

The kernel has a port layer (a single assembly function) that needs to be reimplemented each time a new CPU is added.
Here is a list of currently available CPU family ports:

<table>
  <tr> <td> <b> CPU Family </b> </td> <td> <b> Port status </b> </td></tr>
  <tr> <td>  ARM7TDMI </td> <td> Atmel AT91SAM7, NXP LPC2XXX </td> </tr>
  <tr> <td>  Cortex-M3</td> <td> Luminary Stellaris LM3S, ST Microelectronics STM32 </td> </tr> 
  <tr> <td>  Atmel AVR</td>  <td> Most cpu supported (including Arduino) </td> </tr>  
  <tr> <td>  PowerPC </td>  <td> emulator </td> </tr>
  <tr> <td>  Intel/AMD x86    </td>  <td>emulator </td> </tr>
  <tr> <td>  Intel/AMD x86-64 </td>  <td> emulator </td> </tr>
</table>

\section core_drivers Core Drivers
BeRTOS is not only a kernel, it aims to supply full operating system services.
To achieve this we need at least some core drivers for every CPU port.

These drivers are: <b> system timer </b>, <b> debug system </b> and <b> serial comm driver </b>.

Adding CPU support for an already present CPU family is quite simple since hardware manufacturers share peripherals design between the same CPU cores.

Core drivers are completely supported on all platforms.

\section internal_peripherals MCU Internal peripheral drivers 
Since BeRTOS aims to supply full operating system services, for every CPU port we try to implement as much drivers as possible. This section covers the current development status for MCU Internal peripheral drivers.
<table>
	<tr>
            <td>Driver / <br>MCU family</td>
            <td>ADC</td>
            <td>UART</td>
            <td>FLASH</td>
            <td>I2C</td>
            <td>PWM</td>
            <td>SPI</td>
	</tr>
        <tr><td><strong>Atmel AVR</strong></td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
        </tr>
        <tr><td><strong>Atmel AT91SAM7 ARM</strong></td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
        </tr>
        <tr><td><strong>Atmel AT91SAM3N ARM</strong></td>
            <td>-</td>
            <td>Yes</td>
            <td>-</td>
            <td>-</td>
            <td>-</td>
            <td>-
        </tr>
        <tr><td><strong>STmicro STM32F103xx ARM</strong></td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>-</td>
            <td>-</td>
        </tr>
        <tr><td><strong>Philips LPC23XX ARM</strong></td>
            <td>-</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>-</td>
            <td>-</td>
        </tr>
        <tr><td><strong>Stellaris LM3S ARM</strong></td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>Yes</td>
            <td>-</td>
            <td>Yes</td>
        </tr>
</table>

\section independant_drivers Generic CPU independent drivers 
BeRTOS supplies a full set of CPU independent generic hardware drivers. To achieve this all drivers are structured to have an hardware abstraction layer (HAL) that isolate CPU specific code and makes porting to new CPU easy.
Current driver list:
<table>
<tr> <td> <b> Driver </b> </td> <td> <b> Status </b> </td> </tr>
<tr> <td> \link adc.h ADC API \endlink</td>                                <td>stable</td> </tr>
<tr> <td> \link buzzer.h Buzzer \endlink</td>                              <td>stable</td> </tr>
<tr> <td> \link dataflash.h Atmel Dataflash \endlink</td>                  <td>stable</td> </tr>
<tr> <td> \link eeprom.h I2C EEPROM \endlink</td>                          <td>stable</td> </tr>
<tr> <td> \link flash25.h AT25Fxxx Atmel flash memories \endlink</td>      <td>beta</td> </tr>
<tr> <td> \link ft245rl.h FT245RL USB to parallel converter \endlink</td>  <td>beta</td> </tr>
<tr> <td> \link kbd.h Keyboard \endlink</td>                               <td>stable</td> </tr>
<tr> <td> \link i2c.h I2C \endlink with bitbang support</td>               <td>stable</td> </tr>
<tr> <td> Displaytech 32122A Graphic LCD</td>                              <td>stable</td> </tr>
<tr> <td> \link dc_motor.h DC Motor with PID \endlink</td>                 <td>stable</td> </tr>
<tr> <td> \link lcd_text.h Alphanumeric LCD \endlink</td>                  <td>stable</td> </tr>
<tr> <td> \link lm75.h LM75 temperature sensor \endlink</td>               <td>stable</td> </tr>
<tr> <td> \link mcp41.h MPC41 digital potentiometer \endlink</td>          <td>stable</td> </tr>
<tr> <td> \link mpxx6115a.h MPxx6115A pressure sensor \endlink</td>          <td>stable</td> </tr>
<tr> <td> \link ntc.h NTC \endlink</td>                                    <td>stable</td> </tr>
<tr> <td> \link phase.h TRIAC phase partialization \endlink</td>           <td>stable</td> </tr>
<tr> <td> \link pwm.h PWM API \endlink</td>                                <td>beta</td> </tr>
<tr> <td> \link pcf8574.h PCF85974 I2C port expander \endlink</td>         <td>beta</td> </tr>
<tr> <td> \link sd.h Secure Digital card API \endlink</td>                 <td>stable</td> </tr>
<tr> <td> \link ser.h Serial API \endlink</td>                             <td>stable</td> </tr>
<tr> <td> \link spi_bitbang.h Bitbanged SPI \endlink</td>                  <td>stable</td> </tr>
<tr> <td> \link tas5706a.h TAS5706A \endlink digital audio DSP</td>        <td>stable</td> </tr>
<tr> <td> \link tc520.h TC520 ADC \endlink</td>                            <td>obsolete</td> </tr>
<tr> <td> \link thermo.h Thermostat \endlink</td>                          <td>stable</td> </tr>
<tr> <td> \link timer.h System timer API \endlink</td>                     <td>stable</td> </tr>
<tr> <td> \link tmp123.h TMP123 temperature sensor \endlink</td>           <td>stable</td> </tr>
<tr> <td> \link stepper.h Stepper motor with ramps \endlink</td>           <td>stable</td> </tr>
<tr> <td> Watchdog</td>                                                    <td>beta</td> </tr>
</table>

To get up to date informations look at the <A href="http://dev.bertos.org/browser/trunk/bertos/drv">drivers source code</A>.

\section storage File system 
BeRTOS supports two file systems. The first one is the mainstream \link fat.h FAT \endlink filesystem, using the <A href="http://elm-chan.org/fsw/ff/00index_e.html">FatFs</A>  library. The module is highly configurable, for example it can be compiled in read-only mode for some space saving.

The second is \link battfs.h BattFs\endlink, a file system specifically planned for embedded platforms. The goal is to have a filesystem suitable for little flash and eeprom memories (like dataflash), reliable, robust and capable of wear-levelling the memory pages to increase its life.
The code is in beta stage. Currently you can create files, append data to them but file deletion is still not supported. Wear-levelling is achieved by rotating a page every time it is written. Plans are to add even transactions (a whole write can be performed atomically).

File system development takes place in the <A href="http://dev.bertos.org/browser/trunk/bertos/fs">fs directory</A>.

\subsection fat File System: FAT
 
 <p>The <strong>FAT</strong> file system is the de-facto standard for removable devices such as SD cards or Memory cards. BeRTOS supports read and write operations on all existing FAT file systems, ranging from FAT12 to FAT32, with support to long file names. This file system is light and fast and allows to easily exchange data through external memory devices.</p>
 
 <p>FAT module is highly configurable, for example it can be compiled in read-only mode for some space saving.</p>
 
\subsection battfs File System: BattFS
 
 <p><strong>BattFS</strong> (Batt File System), has been developed to solve problems specific to embedded systems; BattFS is a file system that can <strong>be used on any physical media</strong> and it's optimized to reduce RAM and ROM usage to meet the strict design guidelines we have used with all the others BeRTOS components.</p>
 
 <p>The goal is to have a filesystem suitable for little flash and eeprom memories (like dataflash), reliable, robust and capable of wear-levelling the memory pages to increase its life.</p>
 
 <p>The code is in beta stage. Currently you can create files, append data to them but file deletion is still not supported. Wear-levelling is achieved by rotating a page every time it is written. Plans are to add even transactions (a whole write can be performed atomically).</p>


\section graphics Graphic subsystem 
BeRTOS also features a complete graphic subsystem, suitable for generating compact yet powerful GUI.
This system is composed of several modules ranging from simple graphic primitives to complex menu management functions.

<table>
<tr> <td> <b> Module </b> </td> <td> <b> Status </b> </td> </tr>
<tr> <td> \link bitmap.c Bitmaps manipulation \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link line.c Lines drawing \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link line.c Rectangles drawing \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link win.h Simple windowing system \endlink</td>  <td>stable</td> </tr>
<tr> <td> Proportional and fixed size fonts</td>  <td>stable</td> </tr>
<tr> <td> \link text.h Text rendering \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link charts.h Simple Charts \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link menu.h Menus \endlink</td>  <td>stable</td> </tr>
</table>

To get up to date informations look at <A href="http://dev.bertos.org/browser/trunk/bertos/">the source code</A> in the directories \b gfx, \b gui or \b fonts.


\section algorithms Algorithms 
In embedded programming sometimes you have to cope with protocols, security systems and things like that.
BeRTOS comes in help with a set of optimized portable algorithms:
<table>
<tr> <td> <b> Algorithm </b> </td> <td> <b> Status </b> </td> </tr>
<tr> <td> \link crc.h CRC16 \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link md2.c MD2 \endlink</td>  <td>beta</td> </tr>
<tr> <td> \link randpool.c Cryptographically secure Random Pool \endlink</td>  <td>beta</td> </tr>
<tr> <td> \link rotating_hash.h Rotating hash checksum \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link tea.h TEA (Tiny Encryption Algorithm) \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link ramp.h Stepper motor ramp generator \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link pid_control.h PID Controller \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link rle.c RLE (Run lenght en/decondig) \endlink</td>  <td>stable</td> </tr>
</table>

To get up to date informations look at the <A href="http://dev.bertos.org/browser/trunk/bertos/algo">algorithms source code</A>.

\section networking Network protocols 
Since BeRTOS can also be used in very tiny systems, some simple communication protocols has been developed.

This is the current status:
<table>
<tr> <td> <b> Protocol </b> </td> <td> <b> Status </b> </td> </tr>
<tr> <td> \link pocketbus.c PocketBus \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link keytag.c Keytag (for 125KHz transponders) \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link xmodem.c XModem protocol \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link nmea.c NMEA GPS protocol parser \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link afsk.c AFSK1200 modem \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link ax25.h AX25 data link layer protocol \endlink</td>  <td>beta</td> </tr>
</table>

For more information take a look at <A href="http://dev.bertos.org/browser/trunk/bertos/net/">network directory</A>.

\section data_structures Data Structures 
BeRTOS supplies common data structures, implemented and optimized for low memory footprint and speed.

<table>
<tr> <td> <b> Module </b></td> <td> <b> Status </b></td></tr>
<tr> <td> \link fifobuf.h FIFO \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link hashtable.h Hash table \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link heap.h Embedded-optimized dynamic memory allocator \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link list.h Lists \endlink</td>  <td>stable</td> </tr>
</table>

\section mware Middleware 
This section covers all BeRTOS modules that provide general purpose utility functions. Most of them should be moved to \ref algorithms directory.

In the meanwhile, here is the list:
<table>
<tr> <td> <b> Module </b> </td> <td> <b> Status </b> </td></tr>
<tr> <td> \link cpu/byteorder.h Integers to/from host byte-order conversion \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link event.h Events \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link except.h C++ like exception handling in C \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link formatwr.c Embedded-optimized printf \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link readline.h Command shell with history \endlink</td>  <td>stable</td> </tr>
<tr> <td> \link ini_reader.h Ini file reader \endlink</td>  <td>stable</td> </tr>
</table>

As usual, check <A href="http://dev.bertos.org/browser/trunk/bertos/mware">source code</A> for detailed reference.
*/