STM32F4 BSP usage

Steven Grunza steven.grunza at gmail.com
Thu Apr 18 13:44:29 UTC 2013


Ok.  I didn't want to re-invent the wheel.  The libraries provided by ST are probably not usable due to the licensing restrictions.  

Would it be acceptable to not include the ST libraries in RTEMS but require the end-user of the BSP to acquire them?  There are many examples of how to configure the STM32 hardware but these examples assume the ST libraries are being used.  Simply re-creating the libraries might not be possible without using the source code of the libraries since the source code is the only documentation in most cases.

Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:

>Hello,
>
>in RTEMS we are in general very sloppy with hardware access.  Most systems have 
>memory mapped registers and we simply use structs to access the hardware. 
>RTEMS has not bus space API like in BSD or the inb() etc. macros from Linux.
>
>One of the first steps of a new driver is normally to write a header file for 
>the registers, e.g.
>
>http://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/stm32f4/include/stm32f4.h
>
>Fell free to add more defines and send patches.
>
>-- 
>Sebastian Huber, embedded brains GmbH
>
>Address : Dornierstr. 4, D-82178 Puchheim, Germany
>Phone   : +49 89 189 47 41-16
>Fax     : +49 89 189 47 41-09
>E-Mail  : sebastian.huber at embedded-brains.de
>PGP     : Public key available on request.
>
>Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>_______________________________________________
>rtems-users mailing list
>rtems-users at rtems.org
>http://www.rtems.org/mailman/listinfo/rtems-users




More information about the users mailing list