FPGA image checksum mismatch and cRio image checksum mismatch

[JacobGH]

We had a practice competition yesterday and immediately encountered a fatal error that we couldn't overcome. Our robot runs Java. We placed our robot onto the field, connected to the robot to the Field Management System (FMS) and plugged our driver station laptop into the ethernet. The match started and our robot ran the autonomous routine, but as soon as the game entered teleop mode, the robot wouldn't respond. We checked the output on the netbeans console later, and found two error statements printed. They were something about an "FPGA image checksum mismatch" and a "cRio image checksum mismatch." Prior to these error statements, we saw debugging print statements from autonomous mode, but no more print statements after, suggesting the that the cRio had frozen up.

Here are the pertinent facts:

• This behavior occurred in multiple matches. We power cycled and reload the code.
• We had previously tested our code extensively off the field with no issues.
• After returning to home base, we set up an FMS Lite system to fully emulate the environment that was used at the competition. We put the robot into the same configuration as it was in the competition but it successfully operated in autonomous and teleop mode. We could not reproduce the error.

We're totally stumped, the robot works just fine at home. We have no way of knowing if this problem will arise again at the official competition. Does anyone have any idea what would be causing this?

[Mark McLeod]

Sounds like a corrupted cRIO/FPGA image.
Did you reimage the cRIO? Where the results the same?

[JacobGH]

We suspected that, but we tried several things in the code and hardware settings before getting to that. But by then, it was the end of the day and the matches were over. We'll try reimaging it, but since the error can't be reproduced anywhere else, we won't know if that fixed the problem.