It’s been fairly quiet as the Mars Science Laboratory (MSL) rover Curiosity continues driving towards the point at which it is hoped the rover can traverse between a line of low-lying sand dunes and start exploring the lower slopes of Aeolis Mons, which NASA has dubbed “Mount Sharp”.
However, Thursday November 7th saw an unexpected hiccup in proceedings as Curiosity unexpectedly performed a “warm reset” (software reboot). This occurred around four and a half hours after the new flight software uploaded to the rover (see my last mission report) had been temporarily loaded into memory as a part of the uploading and commissioning of the software, and while the rover was also transmitting data to the Mars Reconnaissance Orbiter (MRO) for later transmission to Earth.
A warm reset is executed when the flight software identifies a problem with one of the operations it is executing which may adversely affect the rover’s operations, and is a standard fault protection mode on all automated craft operated by NASA. It resets the software to its initial state, preventing further issues occurring. While there have previously been problems with Curiosity’s on-board computers, this was actually the first time since the rover’s arrival on Mars 16 months ago that a fault-related software warm reset had been executed.

Following the reset, the rover resumed communications, but the mission team initiated a root cause analysis for the reset using the ground testbed unit (essentially, Curiosity’s Earthside “twin”). This revealed an error in a catalogue file for the existing onboard software was triggered when the catalogue file was executed by the newly uploaded flight software, causing the reset. As a result of this analysis, the flight software team were able to determine the steps required to recover the rover to its operating state prior to the reboot. These were successfully uploaded to Curiosity, and on Sunday November 10th, the rover set confirmation to mission controllers that it has successfully transitioned back to a nominal surface operations mode.
“We returned to normal engineering operations,” software and systems engineer Rajeev Joshi from the Curiosity team at JPL reported following the transition. “We are well into planning the next several days of surface operations and expect to resume our drive to Mount Sharp this week.”
Following the successful reinstatement of normal operations for the rover, the mission science team resumed planning for the next stage of Curiosity’s surface activities, which were due to restart on Thursday November 14th.
Continue reading “Resets, safe modes, and the journey so far”












