BswM - Mode Management & Rules - AUTOSAR Classic BSW

BswM Rule Anatomy

XMLBswM_SleepRule.arxml

<BSWM-RULE>
  <SHORT-NAME>Sleep_Entry_Rule</SHORT-NAME>
  <CONDITION>
    <BSWM-LOGICAL-EXPRESSION>
      <BSWM-LOGICAL-OPERATOR>AND</BSWM-LOGICAL-OPERATOR>
      <BSWM-CONDITION>
        <BSWM-MODE-VALUE>COMM_NO_COM</BSWM-MODE-VALUE>
        <BSWM-MODE-REQUEST-SOURCE-REF>/BswM/ModeConditions/ComM_CAN0
        </BSWM-MODE-REQUEST-SOURCE-REF>
      </BSWM-CONDITION>
      <BSWM-CONDITION>
        <BSWM-MODE-VALUE>NVM_REQ_OK</BSWM-MODE-VALUE>
        <BSWM-MODE-REQUEST-SOURCE-REF>/BswM/ModeConditions/NvM_WriteAll
        </BSWM-MODE-REQUEST-SOURCE-REF>
      </BSWM-CONDITION>
    </BSWM-LOGICAL-EXPRESSION>
  </CONDITION>
  <TRUE-ACTION-LIST-REF>/BswM/ActionLists/GoSleep_ActionList</TRUE-ACTION-LIST-REF>
</BSWM-RULE>

Mode Request Sources

Source	API	Example Condition
ComM	BswM_ComM_CurrentMode(channel, mode)	COMM_NO_COM → start sleep sequence
DcmCommunicationControl	BswM_Dcm_CommunicationMode_CurrentState()	Disable COM PDU groups in diagnostic session
EcuM wakeup	BswM_EcuM_CurrentWakeup()	Trigger FULL_COM on CAN wakeup
NvM multi-block	BswM_NvM_CurrentJobMode()	Gate RUN mode until ReadAll complete
SWC mode switch	BswM_RequestMode(userId, mode)	App requests ECU mode change

Action List Evaluation Types

Type	Behaviour	Use Case
TRIGGER_ON_REQUEST	Executed every time condition becomes TRUE	COM PDU group enable/disable on mode change
IMMEDIATE	Executed once when condition becomes TRUE	EcuM_GoDown, NvM_WriteAll — single-shot actions

⚠️ Rule Never Fires

Most common BswM bug: a rule condition that never becomes TRUE. Check: (1) mode request source reference path exact match; (2) ComM/NvM/EcuM notification is actually being sent; (3) BswM_MainFunction is called often enough (every 10 ms minimum).

BswM Use Cases

Use Case	Trigger Condition	Action List
PDU group switch at wakeup	EcuM wakeup validated + ComM FULL_COM	Enable COM Rx/Tx PDU groups
Sleep entry	ComM NO_COM AND NvM WriteAll OK	Com_DeInit → CanIf sleep → EcuM_GoSleep
RUN mode at startup	NvM ReadAll complete	Enable application SWC task alarms
Diag silent mode	Dcm CommunicationControl = silentMode	Disable non-diagnostic Tx PDU groups

Summary

BswM is the centralised mode coordinator for the entire BSW. Every mode-dependent BSW action should be implemented as a BswM rule — not hardcoded in SWC runnables or scattered across callouts. This centralisation makes mode logic auditable and testable.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.