Layered Software Architecture, No.53, 2021-11
AUTOSAR R21-11記事一覧はこちら。
AUTOSAR 21-11,200文書読んだ。2022年5月に全部到達。
AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成
用語(terms)
| Term | Description |
|---|---|
| Hardware errors / failures | Root cause: Damage, failure or ‚value out of range‘, detected by software- Example 1: EEPROM cell is not writable any more - Example 2: Output voltage of sensor out of specified range |
| Software errors | Root cause: Wrong software or system design, because software itself can never fail. - Example 1: wrong API parameter (EEPROM target address out of range) - Example 2: Using not initialized data |
| System errors | -Example 1: CAN receive buffer overflow - Example 2: time-out for receive messages |
| Development Errors | Development errors are software errors. They shall be detected like assertions and fixed during development phase. The detection of errors that shall only occur during development can be switched off per module for production code (by static configuration namely preprocessor switches). The according API is specified within AUTOSAR, but the functionality can be chosen/implemented by the developer according to specific needs. |
| Runtime Errors | Runtime errors are systematic software errors. They indicate severe exceptions that hinder correct execution of the code. The monitors may stay in code even for a deployed systems. Synchronous handling of these errors can be done optionally in integrator code. |
| Transient Faults | Transient faults occur in hardware e. g. by passage of particles or thermal noise. Synchronous handling of these faults can be done optionally in integrator code. The detecting module may offer behavioral alternatives selectable by this integrator code. |
| Production Errors / Extended Production Errors | Those errors are stored in fault memory for repair actions in garages. Their occurrence can be anticipatedand cannot be avoided in production code. Production errors have a detection and a healing condition. |
英日
日本語は仮訳
T.B.D.
参考(reference)
no