mjb/altos/src/kernel, branch 1.3.2.4

altos: Encode TeleGPS battery voltage in configuration packet

2014-06-08T05:30:26+00:00

TeleGPS doesn't need apogee delay, so re-purpose it for the battery voltage Signed-off-by: Keith Packard

altos: Reduce tracker GPS buffer to 4 samples

2014-06-08T04:11:33+00:00

We just don't have enough RAM for 8 samples. Signed-off-by: Keith Packard

altos: Define lat/lon sum variables as 64-bit instead of 16

2014-06-08T04:05:01+00:00

Oops. 16 bits won't hold position information... Signed-off-by: Keith Packard

altos: Use 0x80 to indicate valid state value in the GPS location packet

2014-06-08T04:02:26+00:00

And only set this for tracker products; other products place state in separate state packets Signed-off-by: Keith Packard

altos: Write tracker logging from tracker thread directly

2014-06-07T19:34:14+00:00

Also, logs 8 pre-launch GPS packets so we can get the ground position. Signed-off-by: Keith Packard

altos: Add TeleGPS logging format

2014-06-07T18:34:29+00:00

This is mostly like the mega format, but places the flight state in a spare byte of the GPS data and writes the gps starting location to the flight packet. Log data is written by the main tracker thread; there's no reason for a separate thread given the GPS update rate and the lack of flight controls. This means ao_log_gps has an API to be called from there, rather than a thread to run. Signed-off-by: Keith Packard

altos: Clear out eeprom erase records when writing entry 0

2014-06-07T17:54:14+00:00

When writing config/erase to eeprom, there's no 'erase' operation as on-chip eeprom is writable at a byte level. As such, we can't tell when the erase blocks get reset when the config gets written. When this happens, erase block 0 gets written explicitly, so just use that call to trigger explicit erasing of the data. Signed-off-by: Keith Packard

altos: Allow value other than 0 for marking erased flights

2014-06-07T17:09:51+00:00

on-chip eeprom doesn't erase to 0xff, so let TeleMega use a different value. Signed-off-by: Keith Packard

altos: Allow AO_CONFIG_MAX_SIZE to be configured. Validate it.

2014-06-07T17:05:21+00:00

TeleMega config is 200 bytes. AO_CONFIG_MAX_SIZE was 128. That didn't work out well when logging erased flight information. Allow TeleMega to use a larger value (1k), and then do a compiler hack to make sure the defined value is at least as large as the ao_config structure. Signed-off-by: Keith Packard

altos: Move ao_tracker.c to kernel

2014-06-07T14:41:11+00:00

Doesn't make sense to be in product Signed-off-by: Keith Packard