Re: [Paparazzi-devel] Errors on updated version

[Árni Þorvaldsson]

Thanks alot for your help Felix

I tried peripherals_imu_refactor branch and it didn't work (I am using sen10121 
IMU from sparkfun). I then reinstalled paparazzi and got an error about yaml 
missing so I installed python-yaml. Not sure what that does but it worked 
afterwards and the IMU started working again on  <subsystem name="imu" 
type="ppzuav"/>
so it is all good now :)

regards Arni
________________________________
Frá: address@hidden address@hidden fyrir hönd Felix Ruess address@hidden
Sent: 17. janúar 2013 12:55
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

Hi Arni,

  git branch
will show you your local branches with the one you are currently on highlighted 
(probably master in your case).

To checkout the peripherals_imu_refactor branch (assuming you have a recent git 
version this this will be sufficient):
  git checkout peripherals_imu_refactor
This should create a new local branch peripherals_imu_refactor based on the 
upstream branch.
If you have an older version or prefer the more explicit way:
  git checkout -b peripherals_imu_refactor origin/peripherals_imu_refactor
Where origin is the name for the remote to fetch from (origin is the default if 
you directly cloned the paparazzi repo).

With git pull you basically fetch+merge the changes from the upstream branch 
you are tracking (e.g. in the normal case your local branch master will track 
the paparazzi master branch).
If you checkout the new branch like above it will automatically set the 
upstream tracking branch, so if you are on the peripherals_imu_refactor branch 
and do a git pull you will fetch+merge the latest changes from that branch...

You can always switch between branches with git checkout branch_name

Cheers, Felix



On Thu, Jan 17, 2013 at 12:25 PM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden>> wrote:
Hi Felix
I am currently on Paparazzi version v4.9_devel-398-g7016820 and I am not sure 
how to get the version  v4.9_devel-413-g17dbd8f, What is the best way to get 
updates, I use git pull and then make, do I only get masters that way? I am 
trying to find out how to do this on the wiki.

Regards Arni
________________________________
Frá: address@hidden<mailto:address@hidden> 
address@hidden<mailto:address@hidden>] fyrir hönd Felix Ruess 
address@hidden<mailto:address@hidden>]
Sent: 17. janúar 2013 00:52
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

This is not merged into master yet, but on the peripherals_imu_refactor 
branch....


On Wed, Jan 16, 2013 at 10:38 PM, David Conger 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
 wrote:
Hello,

Great. I'll test. I'm building a new Ubuntu server ATM. Will install latest 
master and test with a ppz9dom.

Regards,

-- David

On Jan 16, 2013, at 10:00 AM, Felix Ruess 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
 wrote:

Hi again,

with v4.9_devel-413-g17dbd8f there should now also be a cleaned up imu ppzuav 
driver in the peripherals_imu_refactor branch.
You should now also be able to omit the GYRO_x and ACCEL_x defines in the IMU 
section to use the correct datasheet defaults for the PPZUAV 9dof imu.

Would be really great if you could test that one and report if everything is 
working correctly and the axes are correct...

thx, Felix


On Wed, Jan 16, 2013 at 4:56 PM, Felix Ruess 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
 wrote:
Hi Arni,

did you checkout the peripherals_imu_refactor branch first? The cleaned up imu 
aspirin_i2c_v1.0 subsystem is only available there so far...
git checkout peripherals_imu_refactor

There is some more refactoring and testing (e.g. default mag signs/channels 
probably changed for aspirin there) before it will be merged to master.

Best just report your paparazzi version (should be reported in blue at the 
beginning of the airframe build), so I can see which commit you are on ;-)

Cheers, Felix


On Wed, Jan 16, 2013 at 4:42 PM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
 wrote:
Hi Felix
Thanks for your reply and I am more than willing to help out with testing if I 
can:)

I tried aspirin_i2c_v1.0 and got an error

BUILD Belgingur, TARGET ap
make[1]: Entering directory `/home/notandi/paparazzi'
/home/notandi/paparazzi/var/Belgingur/Makefile.ac:103: 
/home/notandi/paparazzi/conf/firmwares/subsystems/shared/imu_aspirin_i2c_v1.0.makefile:
 No such file or directory
make[1]: *** No rule to make target 
`/home/notandi/paparazzi/conf/firmwares/subsystems/shared/imu_aspirin_i2c_v1.0.makefile'.
  Stop.
make[1]: Leaving directory `/home/notandi/paparazzi'
make: *** [ap.ac_h] Error 2
make: Leaving directory `/home/notandi/paparazzi'

Then I tried also aspirin2_i2c according to wiki and that build but and 
datalinked did not show error. But like with the type"ppzuav" I did not get any 
message from the tiny and the GCS did not load up.

regards Arni
________________________________
Frá: 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>
 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>]
 fyrir hönd Felix Ruess 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>]
Sent: 16. janúar 2013 13:26
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

Hi Arni,

removing the imu was just a test to see if that is the issue...
Sorry that this isn't working in master right now, but then this is the 
development branch and testing/feedback is very welcome here!

I started refactoring the peripherals and imu drivers in the 
peripherals_imu_refactor branch.
Could you try to use that branch with <subsystem name="imu" 
type="aspirin_i2c_v1.0"/>? (as that uses the same sensors as imu ppzuav)

Cheers, Felix


On Wed, Jan 16, 2013 at 12:03 PM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>
 wrote:
Hi Felix

It worked when I removed the imu ppzuav subsystem
How can I then use the IMU?

Other problem I am still trying to fix:
I am using Baro MS5611 just to get the data from it,
I am using baro_ms6511_i2c module and SENSOR_SYNC_SEND but data from the sensor 
is still not coming up in the messages tool. I am also using ETS airspeed 
sensor and it works every time. Is there anything I am missing?

Regards Arni
________________________________
Frá: 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>]
 fyrir hönd Felix Ruess 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>]
Sent: 15. janúar 2013 13:49
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

Hi Arni,

the tiny_2.11 does not have the SYS_TIME_LED enabled by default: 
http://paparazzi.enac.fr/wiki/Tiny/v2.11#LEDs
You can configure that: 
http://paparazzi.enac.fr/wiki/Airframe_Configuration#LEDs
At least the SYS_TIME_LED should blink with 1Hz when you have it enabled.

I don't have your hardware config, so I can't test this.
Could you try to disable/comment out all the optional modules and try again.
And maybe try to remove the imu ppzuav subsystem (leave the infrared module and 
change the ahrs to infrared).

Cheers, Felix


On Tue, Jan 15, 2013 at 2:28 PM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>
 wrote:
Hi and thanks for the reply
I am not getting any errors now but the problem is that I am not receiving any 
data  from the Tiny.

Here is the firmware section:

<!DOCTYPE airframe SYSTEM "airframe.dtd">

<!-- Funjet Multiplex (http://www.multiplex-rc.de/)
     Tiny 2.11 board (http://paparazzi.enac.fr/wiki/Tiny_v2.11)
     XBee modem with AT firmware
     LEA 5H GPS
-->

<airframe name="Funjet Tiny 2.11">

  <firmware name="fixedwing">
    <define name="AGR_CLIMB"/>
    <define name="USE_AIRSPEED"/>
    <define name="SENSOR_SYNC_SEND"/>
    <define name="USE_BARO_MS5611"/>
    <define name="LOITER_TRIM"/>
    <define name="ALT_KALMAN"/>

    <target name="sim"             board="pc"/>

    <target name="ap"             board="tiny_2.11">
    </target>

    <subsystem name="radio_control" type="ppm"/>
    <subsystem name="joystick"/>

    <!-- Communication -->
    <subsystem name="telemetry" type="transparent"/>
    <subsystem name="imu" type="ppzuav"/>


    <!-- Actuators are automatically chosen according to board-->
    <subsystem name="control"/>
    <!-- Sensors -->
    <subsystem name="ahrs"     type="float_dcm"/>
    <subsystem name="gps"      type="ublox"/>
    <subsystem name="ins"      type="alt_float"/>
    <subsystem name="navigation"/>


  </firmware>

  <modules>
    <load name="infrared_adc.xml"/>
    <load name="humid_sht.xml"/>
    <load name="airspeed_ets.xml"/>
    <load name="temp_temod.xml"/>
    <load name="baro_ms5611_i2c.xml"/>
  </modules>

  <firmware name="setup">
    <target name="tunnel"             board="tiny_2.11"/>
    <target name="setup_actuators"     board="tiny_2.11"/>
  </firmware>


Regards Arni
________________________________
Frá: 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>
 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>]
 fyrir hönd Felix Ruess 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>]
Sent: 14. janúar 2013 12:57
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

Hi Arni,

Could you please post at least the firmware section so we know what 
architecture/board/firmware/subsystems you are using?
Most boards have some leds enabled by default (e.g. the SYS_TIME_LED that 
should blink with 1Hz).

Regarding the conf.xml: as the message says you can either update the outdated 
config or remove them if you don't want/need these other airframes.
You could also copy conf.xml.example and then just add your ariframe again to 
get up-to-date examples.

Cheers, Felix


On Mon, Jan 14, 2013 at 12:38 PM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>>
 wrote:
Thanks Felix that worked for me and it builds.
I upload without errors the leds are not blinking after the upload. ( is that 
okay?)

Current size:
/home/notandi/paparazzi/var/Belgingur/ap/ap.elf  :
section             size         addr
.text             145740        16384
.data              14236   1073741824
.bss                5700   1073756064
.stack              4096   1073761792
.comment              60            0
.ARM.attributes       46            0
.debug_aranges      2336            0
.debug_info        35314            0
.debug_abbrev      13041            0
.debug_line        26893            0
.debug_frame        2668            0
.debug_str          7217            0
.debug_loc         26048            0
.debug_ranges        824            0
Total             284219


make[1]: Leaving directory `/home/notandi/paparazzi/sw/airborne'
cd sw/airborne; make TARGET=ap upload
make[1]: Entering directory `/home/notandi/paparazzi/sw/airborne'
/home/notandi/paparazzi/sw/ground_segment/lpc21iap/lpc21iap  
/home/notandi/paparazzi/var/Belgingur/ap/ap.elf
lpc21iap v1.3
.
Found USB device
BootROM code: 2.12
Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)
BootLoader version: 1.3
#########################################
Starting software at 0x00004000
make[1]: Leaving directory `/home/notandi/paparazzi/sw/airborne'
make: Leaving directory `/home/notandi/paparazzi'

DONE (exec make -C /home/notandi/paparazzi -f Makefile.ac AIRCRAFT=Belgingur 
ap.upload  2>&1)


when I excecute session I get some errors. Is it okay to just erase from 
conf.xml?
I am not getting messages from the autopilot so it is not working right.

Run '/home/notandi/paparazzi/sw/ground_segment/tmtc/link  -d /dev/ttyUSB0 -s 
57600'
Run '/home/notandi/paparazzi/sw/ground_segment/tmtc/server '
Run '/home/notandi/paparazzi/sw/ground_segment/cockpit/gcs '
A failure occurred while processing aircraft 'BOOZ2_A1'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_booz2.xml
 - 'BOOZ2_A1' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'BOOZ2_A7'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_booz2.xml
 - 'BOOZ2_A7' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'BOOZ2_A8'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_test_passthrough.xml
 - 'BOOZ2_A8' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'EasyStar_ETS'
 - Fail with : File not found: /home/notandi/paparazzi/conf/settings/tuning.xml
 - 'EasyStar_ETS' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'Hexa_LisaL'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_booz2.xml
 - 'Hexa_LisaL' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'LISA_ASCTEC_PIOTR'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_booz2.xml
 - 'LISA_ASCTEC_PIOTR' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'LisaM_Heli'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/settings_booz2_ahrs_cmpl.xml
 - 'LisaM_Heli' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'Microjet'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/basic_infrared.xml
 - 'Microjet' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'Tiny_IMU'
 - Fail with : File not found: 
/home/notandi/paparazzi/conf/settings/tuning_ins.xml
 - 'Tiny_IMU' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
A failure occurred while processing aircraft 'Twinjet'
 - Fail with : File not found: /home/notandi/paparazzi/conf/settings/tuning.xml
 - 'Twinjet' will be ignored by the server
 - Please remove it from 'conf.xml' or fix its parameter(s)
Broadcasting on network 127.255.255.255, port 2010

DONE (exec /home/notandi/paparazzi/sw/ground_segment/cockpit/gcs  2>&1)

Best regards Arni

________________________________
Frá: 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>
 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>]
 fyrir hönd Felix Ruess 
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>]
Sent: 14. janúar 2013 11:10
To: Paparazzi devel list
Efni: Re: [Paparazzi-devel] Errors on updated version

Hi Arni,

in the development branch the ins subsystem is mandatory.
To use altitude filtering add
<subsystem name="ins" type="alt_float"/>
or to just use a "fake" ins that passes gps values along as is:
<subsystem name="ins" type="gps_passthrough"/>

Cheers, Felix


On Mon, Jan 14, 2013 at 11:27 AM, Árni Þorvaldsson 
<address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>>>
 wrote:
Hi ,
I just updated my paparazzi to v4.9_devel-377-gba37ac6
but got a lot of errors while building my files.

CC /home/notandi/paparazzi/var/Belgingur/ap/modules/sensors/baro_ms5611_i2c.o
LD /home/notandi/paparazzi/var/Belgingur/ap/ap.elf
/home/notandi/paparazzi/var/Belgingur/ap/firmwares/fixedwing/main_ap.o: In 
function `init_ap':
main_ap.c:(.text.init_ap+0x18): undefined reference to `ins_init'
/home/notandi/paparazzi/var/Belgingur/ap/firmwares/fixedwing/main_ap.o: In 
function `sensors_task':
main_ap.c:(.text.sensors_task+0x24): undefined reference to `ins_periodic'
/home/notandi/paparazzi/var/Belgingur/ap/firmwares/fixedwing/main_ap.o: In 
function `event_task_ap':
main_ap.c:(.text.event_task_ap+0x2cc): undefined reference to `ins_update_gps'
collect2: ld returned 1 exit status
make[1]: *** [/home/notandi/paparazzi/var/Belgingur/ap/ap.elf] Error 1
make[1]: Leaving directory `/home/notandi/paparazzi/sw/airborne'
make: *** [ap.compile] Error 2
make: Leaving directory `/home/notandi/paparazzi'


regards Arni





_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>><mailto:address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel


_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden><mailto:address@hidden<mailto:address@hidden>>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



_______________________________________________
Paparazzi-devel mailing list
address@hidden<mailto:address@hidden>
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel