درباره ما
NASA-LLIS-1483
Lessons Learned – MER Spirit Flash Memory Anomaly (2004)
Year: 2004
Abstract: Abstract:
Shortly after the commencement of science activities on Mars, an MER rover lost the ability to execute any task that requested memory from the flight computer. The cause was incorrect configuration parameters in two operating system software modules that control the storage of files in system memory and flash memory. Seven recommendations cover enforcing design guidelines for COTS software, verifying assumptions about software behavior, maintaining a list of lower priority action items, testing flight software internal functions, creating a comprehensive suite of tests and automated analysis tools, providing downlinked data on system resources, and avoiding the problematic file system and complex directory structure.
Shortly after the commencement of science activities on Mars, an MER rover lost the ability to execute any task that requested memory from the flight computer. The cause was incorrect configuration parameters in two operating system software modules that control the storage of files in system memory and flash memory. Seven recommendations cover enforcing design guidelines for COTS software, verifying assumptions about software behavior, maintaining a list of lower priority action items, testing flight software internal functions, creating a comprehensive suite of tests and automated analysis tools, providing downlinked data on system resources, and avoiding the problematic file system and complex directory structure.
Subject: autonomous shutdown
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T16:30:45Z | |
| date available | 2017-09-04T16:30:45Z | |
| date copyright | 08/23/2004 | |
| date issued | 2004 | |
| identifier other | UMWEQCAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/94175 | |
| description abstract | Abstract: Shortly after the commencement of science activities on Mars, an MER rover lost the ability to execute any task that requested memory from the flight computer. The cause was incorrect configuration parameters in two operating system software modules that control the storage of files in system memory and flash memory. Seven recommendations cover enforcing design guidelines for COTS software, verifying assumptions about software behavior, maintaining a list of lower priority action items, testing flight software internal functions, creating a comprehensive suite of tests and automated analysis tools, providing downlinked data on system resources, and avoiding the problematic file system and complex directory structure. | |
| language | English | |
| title | NASA-LLIS-1483 | num |
| title | Lessons Learned – MER Spirit Flash Memory Anomaly (2004) | en |
| type | standard | |
| page | 4 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;2004 | |
| contenttype | fulltext | |
| subject keywords | autonomous shutdown | |
| subject keywords | avionics | |
| subject keywords | Computers | |
| subject keywords | file system corruption | |
| subject keywords | Flight Equipment | |
| subject keywords | Flight Operations | |
| subject keywords | flight software architecture | |
| subject keywords | flight software design | |
| subject keywords | flight software requirements | |
| subject keywords | Ground Operations | |
| subject keywords | Hardware | |
| subject keywords | Independent Verification and Validation | |
| subject keywords | Information Technology/Systems | |
| subject keywords | Payloads | |
| subject keywords | repetitive resets | |
| subject keywords | Risk Management/Assessment | |
| subject keywords | Safety & Mission Assurance | |
| subject keywords | shutdown failure | |
| subject keywords | Software | |
| subject keywords | Spacecraft | |
| subject keywords | system memory space | |
| subject keywords | system reboot | |
| subject keywords | Test & Verification |