<?xml version="1.0" encoding="UTF-8"?><item><title>More rover stuff.</title><description>&lt;DIV&gt;More data (from listening to a replay of the briefing): The rover has 3 kinds of memory: RAM, Flash, EEPROM.&amp;nbsp;There's a file system on the flash memory.&amp;nbsp; When in cripple mode, the OS uses a ram disk instead of working with flash.&lt;/DIV&gt;&#13;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&#13;
&lt;DIV&gt;The 9:30am MARS time communications window was not there, meaning the vehicle was in low power mode; which meant the vehicle should come up at 11am.&amp;nbsp; Just before 11am, they asked the rover to go into cripple mode and then asked it to reboot.&amp;nbsp; It did this.&amp;nbsp; Once it came up, everything that they attempted worked fine.&lt;/DIV&gt;&#13;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&#13;
&lt;DIV&gt;When the rover OS boots, sounds like it has to mount the flash file system, and it's that process that's messing up.&amp;nbsp; Sounds like they need to run an fsck on the Flash.&amp;nbsp; :)&lt;/DIV&gt;&#13;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&#13;
&lt;DIV&gt;The Rover is stable in power and thermal; the fault protection mechanisms are working fine, the cripple mode will let them figure out what's going on.&amp;nbsp; It's low data rate, with limited functionality, but they seem confident that they can recover from this.&lt;/DIV&gt;&#13;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&#13;
&lt;DIV&gt;&#13;
&lt;DIV&gt;What was happening when it failed was &amp;#8220;sequence 2502&amp;#8221;, operating the elevation motor in the mast.&lt;/DIV&gt;&#13;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description><pubDate>Thu, 01 Sep 2005 19:17:05 GMT</pubDate></item>