Re: [Paparazzi-devel] how to compile and upload sw/airborne/main_demo#.c to a Tiny v2?

[antoine . drouin]

Hi Miles

if you look at conf/airframes/demo.xml you'll see something like
demo1.CFLAGS += -DCONFIG=\"conf_demo.h\"

this files is located in conf/autopilot and is the header describing the
peripherals on the olimex development board ( really only one led )

If you want to compile this code for a tiny, just replace the above line with

demo1.CFLAGS += -DCONFIG=\"tiny_2_1.h"

( the led is not connected on the same pin - so even the blink led example would
not work with the above configuration )

I am in the process of transfering the "demo" code to sw/airborne/example
directory. I already added a gps demo in there.
We talked about using a CONFIG variable in the makefile to be able to overide it
on the command line, but I'm not sure how useful that is.

hth

Poine



Quoting Miles Colman <address@hidden>:

> Thanks Gautier, I was able to compile the demos.
>
> uploading is:
>  ~/paparazzi3/sw/ground_segment/lpc21iap/lpc21iap
> ~/paparazzi3/var/demo/demo#/demo#.elf
>
> Now my question is, why am I not seeing any results?
>
> There's no blinking led, and no uptime on either serial (usart1 or
> usart0). ublox GPS strings come down serial 0, but if I ground
> GPS_reset then there's nothing.
> I think I need to #define LED_#_BANK or something, based on looking at led.h
> Also, any advice on seeing the debug messages on serial?
>
> I promise to make a wiki page about this bottom-up stuff if someone
> could give me a clue.
>
> Thanks,
> Miles
>
> On Thu, Apr 17, 2008 at 4:21 PM, Gautier Hattenberger
> <address@hidden> wrote:
> > Hello,
> >
> >  You can try with demo#.compile and demo#.upload instead of ap.upload
> >
> >  Gautier
> >
> >  Miles Colman a écrit :
> >
> > >
> > >
> > >
> > > Hello,
> > >
> > > I'm trying to compile the demos in /paparazzi3/sw/airborne
> > > Can someone help me with this please?
> > > (I'm hoping to upload the blinking LED demos to the Tiny v2, starting
> > > with main_demo2.c)
> > >
> > > here's what happens:
> > > address@hidden:~/paparazzi3$ make AIRCRAFT=demo ap.upload TARGET=TINY
> > > [...]
> > > cd sw/airborne; make PAPARAZZI_SRC=/home/mcolman/paparazzi3
> > > PAPARAZZI_HOME=/home/mcolman/paparazzi3 TARGET=ap all
> > > Makefile:40: ../../conf/Makefile.: No such file or directory
> > > make[1]: *** No rule to make target `../../conf/Makefile.'.  Stop.
> > > make: *** [ap.compile] Error 2
> > >
> > >
> > > I'm not sure how to do the compile. So far I tried adding a section to
> > > conf/conf.xml:
> > >
> > >  <aircraft
> > >   name="demo"
> > >   ac_id="1"
> > >   airframe="airframes/demo.xml"
> > >   radio="radios/cockpitSX.xml"
> > >   telemetry="telemetry/booz.xml"
> > >   settings="settings/booz.xml"
> > >   flight_plan="flight_plans/booz_test_1.xml"
> > >  />
> > >
> > >
> > > _______________________________________________
> > > 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
>