"I loaded the 710k hex file, and it said the firmware was 252950 bytes. It loaded successfully and appears to be working. If anyone knows how to tell the size of the firmware based on the .hex file size, I'd still like to know.
"I upgraded all of the above packages to the "testing" versions in the Debian package repository and tried again. It compiles to around 710k. I'm fairly certain I'm doing something wrong."
I'm trying to compile the ArduCopter code for an APM2 on Debian linux 7. I followed the instructions on the DIYDrones page, but the resulting ArduCopter.hex file is around 730k (found in /tmp/ArduCopter.build), which is almost double what it should…
"Ok, that makes sense, but I'm still hung up. In a typical C program, you'd start out with some include files, defines, and variable declarations. Then you'd see the function declarations, with a function "main" at the end which gets executed first.…"
So, I've been digging into the ArduPilotMega (Beta 1.0) code to get a better understanding of how it works. I figure that it will help out in troubleshooting any problems I might have, but the real reason is that I'd like to modify the code to suit…
What is the frame rate of the ArduPilot Mega?Are there any timing diagrams that show the order and timing of the different tasks during each frame? (I.E. feedback/PWM input measurement, control law calculations, PWM output generation, etc...)Thanks.