STM32F4 discovery makefile
sarraciro
sarraciro at yahoo.it
Sat Oct 26 17:39:26 UTC 2013
Yes, Later I noticed that I've already saw it... (in git repository...
in fact.. :) ).
I've created the directories structure in the home directory!
First I want to learn to build a RTEMS application.
Regards
--
SC
Il giorno sab, 26/10/2013 alle 15.49 +0200, Sebastian Huber ha scritto:
> On 10/25/2013 09:21 PM, sarraciro wrote:
> > Hi, I've built with success a template for the stm32f4-discovery.
> > Now I want integrate the GPIO support (for starting) .
> > I've noticed :
> > http://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/stm32f4
>
> This is the BSP source directory for the STM32 Cortex-M controllers.
>
> >
> > Then I made this structure: two directories inc & src
> > |-- init.c
> > |-- lib
> > | |-- inc
> > | | |-- bsp.h
> > | | |-- bspopts.h
> > | | |-- i2c.h
> > | | |-- io.h
> > | | |-- irq.h
> > | | |-- rcc.h
> > | | |-- stm32f4.h
> > | | |-- stm32f4xxxx_gpio.h
> > | | |-- stm32f4xxxx_rcc.h
> > | | |-- stm32_i2c.h
> > | | |-- stm32_usart.h
> > | | `-- usart.h
> > | |-- Makefile
> > | `-- src
> > | |-- console-config.c
> > | |-- i2c.c
> > | |-- i2c-config.c
> > | `-- usart.c
> > |-- Makefile
> > |-- pmacros.h
> > |-- system.h
> > |-- init.c
> > |-- lib
> > | |-- inc
> > | | |-- bsp.h
> > | | |-- bspopts.h
> > | | |-- i2c.h
> > | | |-- io.h
> > | | |-- irq.h
> > | | |-- rcc.h
> > | | |-- stm32f4.h
> > | | |-- stm32f4xxxx_gpio.h
> > | | |-- stm32f4xxxx_rcc.h
> > | | |-- stm32_i2c.h
> > | | |-- stm32_usart.h
> > | | `-- usart.h
> > | |-- Makefile
> > | `-- src
> > | |-- console-config.c
> > | |-- i2c.c
> > | |-- i2c-config.c
> > | `-- usart.c
> > |-- Makefile
> > |-- pmacros.h
> > |-- system.h
> >
> > but how to the control of building-process can flow through from the
> > first makefile to the second one (lib/) for build the library? there 're
> > any recommendations to build & include a library?
>
> Where do you have this directory layout? Do you want to develop a RTEMS
> application or do you want to enhance the BSP?
>
More information about the users
mailing list