Difference between revisions of "DevGuide/SampleAp"
| Line 3: | Line 3: | ||
== Airframe file and brief presentation of the build system == | == Airframe file and brief presentation of the build system == | ||
Paparazzi build system is pretty flexible, but can seem complex at a first glance. It is able to cross compile code for different architectures ( avr, lpc21, stm32, geode, omap3 for the moment ). The makefile responsible for a particular architecture is conf/Makefile.[avr|arm7|stm32|...] | |||
== | It is also able to build software for different vehicles. So for a given vehicle, everything starts with a xml file, stored in conf/airframes/my_vehicle.xml. This file is processed by the build system to generate one header and one makefile. | ||
The list of available vehicles is in conf/conf.xml | |||
== Using the uart on stm32 == | |||
Revision as of 13:04, 15 June 2010
This page is intended as a HOWTO for paparazzi developer. Instead of presenting the build system in a formal way, we will walk you through the creation of a sample application in Paparazzi. This application is targeted to run on a Lisa/L board. It will consist in receiving data from an IMU connected to the STM32, pass it to the overo which will downlink them to the ground segment for displaying. This will allow us to cover the build system
Airframe file and brief presentation of the build system
Paparazzi build system is pretty flexible, but can seem complex at a first glance. It is able to cross compile code for different architectures ( avr, lpc21, stm32, geode, omap3 for the moment ). The makefile responsible for a particular architecture is conf/Makefile.[avr|arm7|stm32|...]
It is also able to build software for different vehicles. So for a given vehicle, everything starts with a xml file, stored in conf/airframes/my_vehicle.xml. This file is processed by the build system to generate one header and one makefile.
The list of available vehicles is in conf/conf.xml