ArduPlane, ArduCopter, ArduRover, ArduSub source
Go to file
Lucas De Marchi 84f399ec3c APMrover2: Start using new Functor implementation
It both reduces flash size and move symbols to read-only sections.
The scheduler_tasks table is one known not to be in read-only section before due
to the FastDelegate implementation. Before and after this patch:

	APMrover2 $ size APMrover2.elf{.old,}
	   text	   data	    bss	    dec	    hex	filename
	 611406	   4832	  40920	 657158	  a0706	APMrover2.elf.old
	 609686	   4824	  38936	 653446	  9f886	APMrover2.elf

	APMrover2 $ nm -C APMrover2.elf{.old,} |grep tasks
	0000000000696f80 B Rover::scheduler_tasks
	000000000047c440 R Rover::scheduler_tasks

As can be seen above, now the scheduler_tasks symbol is in a read-only data
section and in all of them we decreased the total size.

For APM2 we have a similar situation, but the table was already in text section
because it was using plain C pointers:

	APMrover2 $ size APMrover2.elf{.old,}
	   text	   data	    bss	    dec	    hex	filename
	 189518	   1038	   3494	 194050	  2f602	APMrover2.elf.old
	 189216	   1038	   3480	 193734	  2f4c6	APMrover2.elf

	APMrover2 $ nm -C APMrover2.elf{.old,} |grep tasks
	00001f92 T Rover::scheduler_tasks
	00001f8a T Rover::scheduler_tasks
2015-05-26 13:46:55 +10:00
APMrover2 APMrover2: use functor macros 2015-05-26 13:46:54 +10:00
AntennaTracker AntennaTracker: removed NOINLINE define 2015-05-21 09:35:47 +10:00
ArduCopter Copter: remove unnecessary bracket 2015-05-25 22:13:51 +09:00
ArduPlane ArduPlane: use functor macros 2015-05-26 13:46:54 +10:00
Tools autotest: make sim_vehicle.sh work better on windows 2015-05-25 16:50:27 +10:00
docs docs: allow docs build to output to another directory 2013-08-15 09:04:58 +10:00
libraries APMrover2: Start using new Functor implementation 2015-05-26 13:46:55 +10:00
mk build: switch to c++11 2015-05-26 13:46:48 +10:00
.editorconfig all: Change the editorconfig so that it won't want to reformat 2014-07-09 19:03:18 -07:00
.gitattributes Revert ".gitattributes: automatically clean up newlines in source files" 2015-04-20 11:04:59 +09:00
.gitignore ardupilot: revise gitignore to reflect jsb_sim folder rename 2015-05-08 12:03:27 +09:00
.pydevproject AP_Relay: add -1:Disabled to list of param values 2014-05-15 17:13:37 +09:00
.travis.yml Travis: require sudo so not to run on a container 2015-04-14 09:07:31 +10:00
CONTRIBUTING.md Update CONTRIBUTING.md 2014-10-12 00:11:30 -07:00
COPYING.txt cmake overhaul, cleaned up readme, added license 2011-09-30 17:32:51 -04:00
Doxyfile.in Working on doxygen support. 2011-11-25 21:35:20 -05:00
MAINTAINERS.md documentation: Add a contributing & maintainers file 2014-07-09 18:59:26 -07:00
README.md Added Gitter badge 2014-12-23 05:38:32 +00:00
Vagrantfile Support building of Pixhawk firmware under Vagrant/VirtualBox. 2015-04-06 15:44:01 -07:00
reformat.sh better commit message for uncrustify 2012-08-17 11:36:07 -07:00
uncrustify_cpp.cfg fixes to preprocessor retab settings 2012-08-17 11:36:07 -07:00
uncrustify_headers.cfg small changes to uncrustify_headers.cft 2012-08-21 18:59:13 -07:00

README.md

#ArduPilot Project#

Gitter

The ArduPilot project is made up of:

ArduCopter (or APM:Copter) : code, wiki

ArduPlane (or APM:Plane) : code, wiki

ArduRover (or APMrover2) : code, wiki

Antenna Tracker : code, wiki

User Support & Discussion Forums

APM Forum: http://ardupilot.com/forum/index.php

Community Site: http://diydrones.com

Developer Information

Github repository: https://github.com/diydrones/ardupilot

Main developer wiki: http://dev.ardupilot.com

Developer email group: drones-discuss@googlegroups.com

Contributors

Github statistics

How To Get Involved

The ArduPilot project is open source and we encourage participation and code contributions: guidelines for contributors to the ardupilot codebase

We have an active group of Beta Testers especially for ArduCopter to help us find bugs: release procedures

Desired Enhancements and Bugs can be posted to the issues list.

Helping other users with log analysis on diydrones.com and the APM forums is always appreciated:

There is a group of wiki editors as well in case documentation is your thing: ardu-wiki-editors@googlegroups.com

Developer discussions occur on drones-discuss@google-groups.com

License

Overview of license

Full Text