mjb/altos/src, branch 1.3.2.3

altos: Switch TeleGPS to GPS logging format

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

It's customized for TeleGPS uses Signed-off-by: Keith Packard

altos: Update other CONFIG_EEPROM users to set LOG_ERASE_MARK

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

All products placing config and erase marks in on-CPU EEPROM needs to configure the erase code correctly. 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: Write current flight state to GPS data from GPS drivers

2014-06-07T18:39:10+00:00

This will be useful with TeleGPS which has no other packet containing flight state. 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/telemega-v1.0: Adjust config params to make flight erase work

2014-06-07T18:01:14+00:00

Flight erase records are supposed to be written after the ao_config to eeprom in telemega. They were getting written in the middle of one of the pyro channel config blocks. Put a bunch of space between the two by making the config max 1024 bytes instead of 128 bytes. Set the log erase marker to 0x55 -- eeprom comes from the factory as 0x00, so we use any value other than 0x55 to indicate 'unused' erase slots. Save space for more flight erase blocks; we've got plenty. 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