| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
In case the companion is delayed while booting, retry the setup 10
times with a 1s delay between tries.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
Lets the companion log them for later matching with TeleMetrum log
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
Get the companion board starting its data logging as soon as possible
after boost starts.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
Was using board_id == ~board_id instead of board_id ==
~board_id_inverse.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
This prints out whether there is a board connected, along with the
various values fetched from it.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
| |
The AVR CPU on the other side just can't go very fast. This reduces
the SPI clock by a factor of 16, just under 200kHz. As the companion
commands are reasonably short, this shouldn't have a huge effect on
overall SPI utilization.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
This sends current flight state information and retrieves companion
data to include in telemetry.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
