paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] solved many problams with my lisa/m


From: Felix Ruess
Subject: Re: [Paparazzi-devel] solved many problams with my lisa/m
Date: Thu, 14 Feb 2013 02:07:02 +0100

Hi Michal,

Minor update:
If you have a Lia board, use that as your target board (lia_1.1)!
It defaults to BARO_MS5611_SPI, so assumes you have an aspirin on it...
To use BARO_MS5611_I2C instead, in your firmware section:
<configure name="LIA_BARO" value="BARO_MS5611_SPI"/>

Cheers, Felix


On Thu, Feb 14, 2013 at 1:09 AM, Felix Ruess <address@hidden> wrote:
Hi,

a proposed minor "compatibility fix" is in the v4.2_aspirin2.2_compat branch on github.
Please test it.... but keep in mind that proper support for aspirin_v2.2 is only available in master and will be part of the next stable release.

Regarding baro on aspirin in master:
Michal... just noticed that you removed the support for the onboard bmp085 baro in your pull request.
I resurrected that and this is the default again.
There are three baro drivers to choose:
    - BARO_BOARD_BMP085 (default)
    - BARO_MS5611_SPI
    - BARO_MS5611_I2C
To use the MS5611 on the Aspirin IMU, configure it in your firmware section, e.g.:
    <configure name="LISA_M_BARO" value="BARO_MS5611_SPI"/>

Cheers, Felix


On Wed, Feb 13, 2013 at 12:52 PM, Felix Ruess <address@hidden> wrote:
Hi Christophe,

the poposed fix pulls PC13 high in arch specific part for the aspirin v1.x driver.
The aspirin2 driver you wrote is currently totally arch independent and does not initialize they GPIOs anywhere...

Cheers, Felix


On Wed, Feb 13, 2013 at 11:23 AM, Christophe De Wagter <address@hidden> wrote:
Dear Michael,

Thank you for your debugging efforts and finding the important issue: the current release (v4.2) is not compatible with the new aspirin v2.2 (yet). Indeed if the SPI-Baro-Chip-Select is left floating, the the baro and the mpu6000 will fight each other every time the baro-chip-select is getting low (e.g. with your finger), so software MUST pull PC13 high.

While full support for the aspirin2.2 will only be given in the next paparazzi release (current master), v4.2 should be at least fixed.

Constraints:

-Lisa-m/2 with aspirin <= 2.1 -> PC13 soldered to ground
-Lisa-m/2 with aspirin >= 2.2 -> PC13 should be high

Can anyone verify/validate this?

-Christophe 


On Wed, Feb 13, 2013 at 12:53 AM, Felix Ruess <address@hidden> wrote:
Hi,

Btw, editing the makefile is annoying, just changed this in master so you can configure it from the airframe file, e.g.
<configure name="LISA_M_BARO" value="BARO_SPI"/>
default is BARO_I2C and another option would be BARO_ASPIRIN

Cheers, Felix


On Wed, Feb 13, 2013 at 12:40 AM, Piotr Esden-Tempski <address@hidden> wrote:
Hi,

If I understand you correctly you pulled up the CS pin permanently making communication to the barometer permanently impossible.

Am I right in the assumption you were not using master branch of paparazzi for your tests? To my knowledge only master branch has support for the MS5611 connected to SPI.

If you use master you need to edit conf/firmware/rotorcraft.makefile replacing:
BARO = BARO_ASPIRIN
with
BARO = BARO_SPI

then the barometer should be read out correctly as well as all other IMU sensors with no hardware modifications necessary.

I hope this helps.

Cheers Esden

On Feb 12, 2013, at 11:23 AM, michael matkov <address@hidden> wrote:

> hey everyone !
>
> didn't touched paparazzi for a long time until :
> i've got from TR , x3 lisa/m v2.0 with aspirin 2.2-r0
>
> had alot of problams with IMU sensors, hanged start up of the STM32 ,super touch sensitive around the soldered aspirin
> and troubled upload firmware with the paparazzi-center (random hangs and errors), i tried to contact with esden and TR but no replay
> from both of them... even tough the fast shipping ,i tought all the three lisa DOA ...
>
> then i decided to check by my self :
> done some research and the new barometer hangs the SPI bus + garbeging the MPU6... values
> removed the trace of that GYRO_SS pin as described at the wiki but no good.
> BTW :when i've got the boards shipment ,i quickly soldered the aspirin include the pin that didn't need to be soldered ( see: http://paparazzi.enac.fr/wiki/address@hidden@warning )
>
> all the problems got cleared until i've soldered jumper from the CS of the Barometer to 3.3v
>
> now i feel like i've got new boards ;) fast upload ,fast start up ,and fast PFD lock !
>
> maybe it will help somebody with the same problems
> i don't know how or how to start :) can some one add :
> if using the hardware setup above ,to pull high stm32 pin PC13 to high trough the c code -> its CS of the new barometer.
> i think a future driver for that barometer will do that by the way ,but need to change the wiki to not remove that pad from the aspirin ?
>
> sorry about my english ...
>
> best regards
>     matkov michael
>
> _______________________________________________
> 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


_______________________________________________
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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]