See issue #345
Refactored so far:
- hmc58xx magnetometer refactoring #105
- itg3200 gyro (also imu3000) refactoring
- adxl345 i2c peripheral
- adxl345 spi peripheral
- imu_navgo driver
- imu_umarim driver
- imu_aspirin (via spi) refactoring (only polling, no interrupt handling)
- imu aspirin (i2c)
- imu_ppzuav refactoring #192
* peripherals_imu_refactor: (23 commits)
[stm32][ppm] compile time config info
[ms2100] removed superflous var
[ms2100] fix input buffer reading order
[stm32][spi] attempt to fix issue #348 - added extra status flags and interrupt to handle different transaction input and output lengths - added support for before_cb, made the callbacks happen while slave is still selected - added support for 0 output_length case
[peripherals] first shot at refactoring ms2100, not quite nice yet...
[imu] signs for mag in aspirin imu should be correct again, still needs checking though
[subsystems][imu] cleaned up imu_ppzuav driver no modules for imu_ppzuav and imu_aspirin_i2c anymore
[imu] minor config name change for aspirin
[peripherals] max1168: set spi transaction status to SPITransDone in init
[subsystems][imu] add aspirin_i2c_v1.[0|5] subsystems, should replace imu_ppzuav closes#192
[peripherals][itg3200] enable data ready interrupt by default is this really needed to read the RAW_DATA_RDY flag in the status register??
[peripherals][imu] add adxl345_spi; update adxl345_i2c, itg3200, hmc58xx; update imu_aspirin, imu_b2 and imu_navgo drivers
aspirin driver seems to work without arch depedent eoc/irq handling, ready for next step
some more refactoring for hmc58xx and itg3200
renamed some asprin config options
[conf][i2c] changed all FOO_I2C_DEVICE defines to FOO_I2C_DEV to be consistent While FOO_I2C_DEVICE is less ambiguous, FOO_I2C_DEV was choosen since most modules already use that. Since this is a user facing config, rather keep existing configs working...
aspirin1 cleanup, seems to work fine so far...
working on aspirin1 driver
macros to print vars with values during compile time
[peripherals] started reworking the itg3200 peripheral driver - update imu_navgo driver
...
The bit shifts are reduced by 5 (increasing the gain by factor 32), GUIDANCE_V_GAIN_SCALER (48) removed
So to get the same gains as before, multiply them by 1.5
Maybe also adjust the GUIDANCE_V_MAX_SUM_ERR, which should really have a sensible default anyway!!!!
On the other hand the max sum error was not adjusted in any airframe file when the GAIN_SCALER was added by Bart 2012-04-03.
So now it's nearly back to the same level as we had then, which was probably good?
Default is always true
It is required on some receivers that are still produicing valid frames
after RC lost (futaba R617FS). It is still possible to get the lost
flag from an rssi reading or at least with a GPIO (usually possible when
the receiver has a led to indicate the RC lost state).
It doesn't accecpt a "Black Sphere Technologies" manufacturer device anmyore,
this should prevent you from accidentally uploading ap firmware to your BMP.
Should close#349
- added extra status flags and interrupt to handle different transaction input and output lengths
- added support for before_cb, made the callbacks happen while slave is still selected
- added support for 0 output_length case
Doesn't work as intended (yet).
The sorting e.g. splits up `pkg-config glib-2.0 --cflags` into
--cflags` glib-2.0 `pkg-config
so it doesn't work anymore...
One way could be to make sure to resolve these first before sorting.
This reverts commit 70168207ab.
Felix Ruess
Christophe De Wagter
Gautier Hattenberger
podhrmic
Stephen Dwyer
Ewoud Smeur