[battor agent] Fix the init sequence so it retries inits instead of resets.

tools/battor_agent/battor_error.h

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef TOOLS_BATTOR_AGENT_BATTOR_ERROR_H_
 #define TOOLS_BATTOR_AGENT_BATTOR_ERROR_H_
 
 #include <string>
 
 namespace battor {
 
 // A BattOrError is an error that occurs when communicating with a BattOr.
 enum BattOrError {
   BATTOR_ERROR_NONE,
   BATTOR_ERROR_CONNECTION_FAILED,
   BATTOR_ERROR_TIMEOUT,
   BATTOR_ERROR_SEND_ERROR,
   BATTOR_ERROR_RECEIVE_ERROR,
   BATTOR_ERROR_UNEXPECTED_MESSAGE,
+  BATTOR_ERROR_INIT_ERROR,

[charliea (OOO until 10-5), 2016/05/23 14:08:52]

How about BATTOR_ERROR_INIT_TIMEOUT? This seems like just a special case of a
timeout where the last command attempted is an init.

I think eventually we probably want to get rid of this error and instead have
each BattOr error be some tuple of (error code, last command attempted).
However, until we have that, I agree that it makes sense to have some obvious
way to detect that this is the stage that failed.

[aschulman, 2016/06/10 07:22:59]

I went with BATTOR_ERROR_INIT_MAX_RETRIES since I think that best matches what
caused this error to fire.

 };
 
 std::string BattOrErrorToString(BattOrError error);
 
 }
 
 #endif  // TOOLS_BATTOR_AGENT_BATTOR_ERROR_H_