From 5fb46b0e11845dc82e1c3fa79078ad708b5a1c75 Mon Sep 17 00:00:00 2001
From: Peter Barker <pbarker@barker.dropbear.id.au>
Date: Mon, 8 Jun 2015 22:55:22 +1000
Subject: [PATCH] Replay: fix dataflash overflow on timestamp-poor (older)
 logfiles

---
 Tools/Replay/MsgHandler.cpp | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Tools/Replay/MsgHandler.cpp b/Tools/Replay/MsgHandler.cpp
index a004034a71..6245bae573 100644
--- a/Tools/Replay/MsgHandler.cpp
+++ b/Tools/Replay/MsgHandler.cpp
@@ -580,6 +580,18 @@ void MsgHandler_PARM::process_message(uint8_t *msg)
 {
     const uint8_t parameter_name_len = AP_MAX_NAME_SIZE + 1; // null-term
     char parameter_name[parameter_name_len];
+    uint64_t time_us;
+
+    if (field_value(msg, "TimeUS", time_us)) {
+        wait_timestamp_usec(time_us);
+    } else {
+        // older logs can have a lot of FMT and PARM messages up the
+        // front which don't have timestamps.  Since in Replay we run
+        // DataFlash's IO only when stop_clock is called, we can
+        // overflow DataFlash's ringbuffer.  This should force us to
+        // do IO:
+        hal.scheduler->stop_clock(last_timestamp_usec);
+    }
 
     require_field(msg, "Name", parameter_name, parameter_name_len);