DevGuide/SampleAp - Revision history

Esden at 00:47, 10 March 2011

2011-03-10T00:47:03Z

← Older revision		Revision as of 18:47, 9 March 2011
Line 15:		Line 15:

	== Using the uart on stm32 ==		== Using the uart on stm32 ==

			[[Category:Software]] [[Category:Developer_Documentation]]

Esden: DevGuideSampleAp moved to DevGuide/SampleAp: Conform to naming conventions

2011-03-10T00:46:43Z

DevGuideSampleAp moved to DevGuide/SampleAp: Conform to naming conventions

← Older revision	Revision as of 18:46, 9 March 2011
(No difference)

Poine at 15:08, 16 June 2010

2010-06-16T15:08:39Z

← Older revision		Revision as of 09:08, 16 June 2010
Line 5:		Line 5:
	Paparazzi build system is pretty flexible, but can seem complex at a first glance.		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 able to build software for different vehicles. 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 ( var/my_vehicle/airframe.h and var/my_vehicle/Makefile.ac ).

	~~- 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 ( var/my_vehicle/airframe.h and var/my_vehicle/Makefile.ac ).~~		The file conf/conf.xml holds the list of available vehicles. The name of the vehicle is used

	The ~~list of available vehicles~~ is in conf/~~conf~~.~~xml~~		- 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\|...]

	- For each vehicle, it is able to build a number of "targets" ( aka programs), like for example an autopilot and a number of test programs, or in the case of our multiprocessor board Lisa/L, a program for the STM32 and a program for the Overo.		- For each vehicle, it is able to build a number of "targets" ( aka programs), like for example an autopilot and a number of test programs, or in the case of our multiprocessor board Lisa/L, a program for the STM32 and a program for the Overo.

Poine at 14:36, 16 June 2010

2010-06-16T14:36:02Z

← Older revision		Revision as of 08:36, 16 June 2010
Line 1:		Line 1:
	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		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, the use of peripheral drivers and the communications with the ground segment.

	== 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\|...]		Paparazzi build system is pretty flexible, but can seem complex at a first glance.

	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.		- 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 ( var/my_vehicle/airframe.h and var/my_vehicle/Makefile.ac ).

	The list of available vehicles is in conf/conf.xml		The list of available vehicles is in conf/conf.xml

			- For each vehicle, it is able to build a number of "targets" ( aka programs), like for example an autopilot and a number of test programs, or in the case of our multiprocessor board Lisa/L, a program for the STM32 and a program for the Overo.


	== Using the uart on stm32 ==		== Using the uart on stm32 ==

Poine at 20:04, 15 June 2010

2010-06-15T20:04:40Z

← Older revision		Revision as of 14:04, 15 June 2010
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\|...]

	== ~~using~~ the uart on 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 ==

Poine at 19:47, 15 June 2010

2010-06-15T19:47:41Z

← Older revision		Revision as of 13:47, 15 June 2010
Line 1:		Line 1:
	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		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 ==


			== using the uart on stm32 ==

Poine at 18:28, 15 June 2010

2010-06-15T18:28:31Z

New page

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