Hi David,
the default airframes should be up to date. They are in
conf.xml.example. But they only get copied to conf.xml if you don't
already have one. Meaning it will work if you just made a new checkout
and hence don't have your own conf.xml with old airframes.
So you should update your conf.xml and through out the old ones and
replace them with the up-to-date examples. Or just delete your
conf.xml, let it be created again and then add your own airframes
again...
Maybe we could change it so that the conf.xml.example is included
automatically and you only put your own airframes in conf.xml which is
not under version control. Then the examples would always be up to
date.
Cheers, Felix
On Thu, Oct 7, 2010 at 4:32 PM, David Conger<address@hidden> wrote:
Hello,
This is interesting. I was using the commands I always use and that are on the
WIki for programming the u-blox using the tunnel. I run make at the command
line but used the MJ5 airframe which is one of the default ones. I guess the
fault is in the MJ5 airframe file?
It would be nice to have a default airframe files and custom airframe files.
The defaults always being updated when the code changes. Although I'm not new
and will make the changes required for someone new we should make an experience
where following the commands on the Wiki or choosing defaults in the menu just
work. I suppose it means when changes like this are made someone also changes
the defaults as well. With so many airframe files now that's not practical
hence my suggestion to limit or separate them into default and custom or other
or ?
Thank you Felix for helping. I will make the changes. To quickly solve my issue
I just reverted SVN using: svn update -r 5920
-David
On Oct 7, 2010, at 3:58 AM, Felix Ruess wrote:
Hi David,
the Makefile.arm7 is obsolete, we now have the more consistent
Makefile.lpc21 for the tiny.
are you still using the old makefile section or did you switch to the
new firmware/subsystems already?
That sounds like you still use the old way and then you would have to
adapt your makefile section.
If you use firmware/subsystems you should have something like this in
your airframe file:
<firmware name="setup">
<target name="tunnel" board="tiny_2.11"/>
</firmware>
When you set the board it will automatically call the right Makefile
for that architecture.
(In this case $(TARGET).ARCHDIR is set to lpc21 in the
tiny_2.11.makefile and then the correct Makefile.lpc21 will be called)
Cheers, Felix
On Thu, Oct 7, 2010 at 6:30 AM, David Conger<address@hidden> wrote:
I tried to program the tunnel into a Tiny2.11 tonight and get:
make[1]: Entering directory `/home/dconger/paparazzi3/sw/airborne'
Makefile:38: ../../conf/Makefile.arm7: No such file or direct
Sure enough the file isn't found anywhere. I did see it in a backup SVN and a change 2
weeks ago from flixr saying "moved arm7 directory to arch/lpc21 and set most
makefiles accordingly" ...
Do I need to fix a Makefile somewhere?
-David
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel