mjb/altos/src/drivers, branch master

altos: Use fast timer for buttons instead of edge-triggered ISR

2019-08-13T00:30:48+00:00

If the button bounces between the triggering interrupt and the button state check, we could lose the final state change of the button and send an incorrect event to the application. In the worst case, the button would end up in exactly the wrong state, toggling in the wrong direction. Use the fast timer to poll all buttons instead so that there is only one check of each button at each poll interval (instead of the interrupt and the state check). This makes buttons reliably debounced. Signed-off-by: Keith Packard

altos: Record all failed sensors and report status at power up

2019-07-16T18:12:49+00:00

Use DATA bits to mark which sensors have failed, then report that in beeps at startup time to help diagnose hardware failures while still allowing the board to be used over USB. Signed-off-by: Keith Packard

altos: Allow ms5607 driver to either set ao_sensor_errors or panic

2019-07-15T20:26:30+00:00

Products that want to remain usable (over USB) after a sensor failure don't want to panic when the ms5607 fails, but products with limited ROM space don't want to have extra code to check for the sensor failure and panic. Change the MS5607 driver to allow either option, and then make the micropeak based devices use it. Signed-off-by: Keith Packard

altos: Don't dump MS5607 eeprom in 'B' command

2019-06-19T06:14:54+00:00

MicroPeak v2 now has config stuff where these values get shown Signed-off-by: Keith Packard

altos/micropeak-v2.0: expose log and config commands over USB

2019-06-18T21:50:53+00:00

This lets AltosUI handle the eeprom data Signed-off-by: Keith Packard

altos: Support ao_ms5607_dump when no ms5607 task

2019-06-18T06:43:02+00:00

MicroPeak v2.0 has tasking support, but doesn't have a separate ms5607 task. That means the device isn't getting initialized when not running the flight code, so in cmd mode we need to make sure it's initialized, and we also need to actually fetch a value to display. Signed-off-by: Keith Packard

altos: Add preliminary TeleStatic v3.0 code

2019-04-22T01:30:43+00:00

This adds the pin definitions and all of the code except for the ads131a04 driver. Signed-off-by: Keith Packard

altos: Change MAX6691 driver to run its own thread

2019-04-22T01:18:55+00:00

This just captures temp data continuously; it takes 100ms to get the temp data from the sensor, so the maximum rate is around 10 samples/sec. Signed-off-by: Keith Packard

altos: get ao_max6691 driver working

2019-04-21T23:54:54+00:00

The driver uses a timer connected to a DMA engine to measure pulse widths from the chip. We get 11 pulses for 4 channels; the first pulse is caused by the timer starting up, the next two are the marker pulse and then 8 more indicating the end of the high and low periods for each channel. The driver API returns the 8 pulse widths; the caller is expected to know what to do with those values as using them requires knowing the value of the configuration resistor and the characteristics of the thermistors. The test code assumes a 1k configuration resistor, using that it computes the resistance of the four thermistors. Signed-off-by: Keith Packard

altos: Work on MAX6691 driver

2019-04-21T23:54:54+00:00