Specification of ECU State Manager, No.78, AUTOSAR R21-11(255) CP

Specification of ECU State Manager, No.78, 2021-11

https://www.autosar.org/fileadmin/user_upload/standards/classic/21-11/AUTOSAR_SWS_ECUStateManager.pdf


AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11,160文書読んだ。2022年5月中に全部読み。

https://qiita.com/kaizen_nagoya/items/9935c9e58bf82e1e63d2

AUTOSAR 21-11, 62文書読んだ。2022年5月中に半分到達予定。

https://qiita.com/kaizen_nagoya/items/648b32867635993410c8

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 用語(terms)
|Term|Description|
|:--|:--|
|Callback| Refer to the Glossary [5]
|Callout|’Callouts’ are function stubs that the system designer can replace　with code, usually at configuration time, to add functionality to the　ECU Manager module. Callouts are separated into two classes.　One class provides mandatory ECU Manager module functionality and serves as a hardware abstraction layer. The other class　provides optional functionality.
|Integration Code |Refer to the Glossary [5]
|Mode|A Mode is a certain set of states of the various state machines　(not only of the ECU Manager) that are running in the vehicle　and are relevant to a particular entity, an application or the whole　vehicle
|Passive Wakeup |A wakeup caused from an attached bus rather than an internal　event like a timer or sensor activity.
|Phase|A logical or temporal assembly of ECU Manager’s actions and　events, e.g. STARTUP, UP, SHUTDOWN, SLEEP, ... Phases　can consist of Sub-Phases which are often called Sequences if　they above all exist to group sequences of executed actions into　logical units. Phases in this context are not the phases of the　AUTOSAR Methodology.
|Shutdown Target|The ECU must be shut down before it is put to sleep, before it is　powered off or before it is reset. SLEEP, OFF, and RESET are　therefore valid shutdown targets. By selecting a shutdown target,　an application can communicate its wishes for the ECU behavior　after the next shutdown to the ECU Manager module.
|State|States are internal to their respective BSW component and thus　not visible to the application. So they are only used by the BSW’s　internal state machine. The States inside the ECU Manager build　the phases and therefore handle the modes.
|Wakeup Event|A physical event which causes a wakeup. A CAN message or a　toggling IO line can be wakeup events. Similarly, the internal SW　representation, e.g. an interrupt, may also be called a wakeup　event.
|Wakeup Reason |The wakeup reason is the wakeup event that is the actual cause　of the last wakeup.
|Wakeup Source|The peripheral or ECU component which deals with wakeup　events is called a wakeup source.
|BswM |Basic Software Mode Manager
|Dem| Diagnostic Event Manager
|Det| Default Error Tracer
|EcuM |ECU Manager
|Gpt |General Purpose Timer
|Icu| Input Capture Unit
|ISR |Interrupt Service Routine
|Mcu |Microcontroller Unit
|NVRAM |Non-volatile random access memory
|Os |Operating System
|Rte |Runtime Environment
|VFB| Virtual Function Bus

## 英日
日本語は仮訳

T.B.D.

# 参考(reference)

[1] List of Basic Software Modules
AUTOSAR_TR_BSWModuleList
[2] Specification of RTE Software
AUTOSAR_SWS_RTE
[3] Specification of Basic Software Mode Manager
AUTOSAR_SWS_BSWModeManager
[4] Guide to Mode Management
AUTOSAR_EXP_ModeManagementGuide
[5] Glossary
AUTOSAR_TR_Glossary
[6] General Specification of Basic Software Modules
AUTOSAR_SWS_BSWGeneral
[7] Virtual Functional Bus
AUTOSAR_EXP_VFB
[8] General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral
[9] Requirements on Mode Management
AUTOSAR_SRS_ModeManagement
[10] Specification of ECU State Manager
AUTOSAR_SWS_ECUStateManager
[11] Specification of MCU Driver
AUTOSAR_SWS_MCUDriver
[12] Specification of CAN Transceiver Driver
AUTOSAR_SWS_CANTransceiverDriver