Replies to This Discussion

Permalink Reply by Lewis W on May 29, 2012 at 9:25am

Have you followed the instructions here?

The first things that come to mind are to a) ensure that you're using the right version of Arduino (there's an arduplane-specific version mentioned in the link above), and b) check that the arduplane folder and the libraries folder are in the folder that you're using for your arduino "sketches".

Hope that helps.

Permalink Reply by Curt Olson on May 29, 2012 at 9:57am

Hi Lewis,

Thanks for the tip.  It's often a challenge when starting cold on something new to find where the right information is located. :-)

So I have arduino-1.0.1 (for linux 64 bit) installed.  Supposedly (?) this has relax patch included so I don't have to worry about that ???

I'm trying to build ArduPlane-2.34.

The compile runs through and appears to go cleanly until the final link where I get this message:

/usr/local/Arduino/arduino-1.0.1/hardware/tools/avr/bin/../lib/gcc/avr/4.3.2/../../../avr/bin/ld: region text is full (ArduPlane.cpp.elf section .text)
/usr/local/Arduino/arduino-1.0.1/hardware/tools/avr/bin/../lib/gcc/avr/4.3.2/../../../avr/bin/ld: region text is full (ArduPlane.cpp.elf section .text)
/usr/local/Arduino/arduino-1.0.1/hardware/tools/avr/bin/../lib/gcc/avr/4.3.2/../../../avr/bin/ld: region text is full (ArduPlane.cpp.elf section .text)

Anyone have any ideas?  Did the relax patch not go into the linux version of arduino?  Please don't tell me I have to limp around a windows system to build the arduplane code. :-)

Thanks,

Curt.

Permalink Reply by david.collett on June 5, 2012 at 5:03am

The changelog says that relax is there, so it should be.

I suspect the problem could be that the code is simply too big (despite relax patch) for the 1280 board. I believe the 2560 is the main target for the devs these days, and you may have to disable a few things to get a build that fits into the 2560. I suggest asking the question over in the Arduplane 2.x forum.

Dave

Permalink Reply by Curt Olson on June 6, 2012 at 6:36am

Ok, yes, when I compile for the 2560 then all is good, except my board here is a 1280.  I have a 2560 v2.0 kit on order so my plan is to move forward and not spend too much time trying to make the older stuff work.

Ultimately, my plan is to turn the ardupilot-mega into a "mega" sensor head.  In other words, the ardupilot hardware spends all it's time reading sensors and running the RC system and handing the data up a layer to a higher end CPU.  All the high level stuff: kalman filtering, autopilot PID, navigation, guidance, control, ground station communication, payload communication, etc. will live one layer up.  This will allow me to use higher level coding constructs, posix/linux api's, hardware floating point operations, a real file system, etc.  The ardupilot is growing by leaps and bounds in capabilities, so asking why I want to do this is a legitimate question, and there are some shades of gray here, but ultimately I like the portability of higher level code and I like the idea of keeping the bare metal stuff as contained as possible.