|
From: | Helge Walle |
Subject: | Re: [Paparazzi-devel] PPM and Lisa/M v2.0 |
Date: | Thu, 14 Jan 2016 11:23:14 +0100 |
Would be great if you could confirm that this fixes it for you.Cheers, FelixOn Tue, Jan 5, 2016 at 12:21 AM, Felix Ruess <address@hidden> wrote:FelixCheers,We shouldn't really have any configure options that are used more than once (where you would want to change them between subsystems...@gautierhattenberger, what do you think about changing the generator to put _all_ configure (makefile variables) at the beginning of a target and not only the ones that are nested directly under firmware or target?In the generated var/aircrafts/ACNAME/Makefile.ac you can see that the board makefile is included before the makefile variable is set.Hi Helge,ugh, that is an annoying side effect that I hadn't considered... sorry.On Fri, Jan 1, 2016 at 6:15 PM, Helge Walle <address@hidden> wrote:_______________________________________________Helge.Thanks,Maybe the wiki needs to be updated a little, but I am not sure how to put this correctly.I have just moved directly from v5.4 to v5.8. Using Lisa/M v2.0 in one of my fixedwings, I had to do some changes to my airframe file.Hi,And happy new year to the Paparazzi community!
In v5.4 I had:
<subsystem name="radio_control" type="ppm">
<configure name="RADIO_CONTROL_PPM_PIN" value="UART1_RX"/>
</subsystem>Now, RADIO_CONTROL_PPM_PIN has moved to the board makefile, and I needed to move the configure line outside of the subsystem lines. so now I have:
<subsystem name="radio_control" type="ppm"/>and separately:
<configure name="RADIO_CONTROL_PPM_PIN" value="UART1_RX"/>
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
[Prev in Thread] | Current Thread | [Next in Thread] |