AUTOSAR

AUTOSAR

Posts 1-4 of 4
  • MD Najmuddin Siddique
    MD Najmuddin Siddique
    The company name is only visible to registered members.
    ECU StateManager and BSW Mode Manager - AUTOSAR 4.0
    ....Mode Switch indications (always issued by BSW modules) go through the BswM for further propagation to the SW-Cs,

    ....eg1: If DCM (Requests Mode) ----> Disable Normal Communication goes thru COM ----> It would then goto BswM (Mode control / actions) for enable or disable ---> then initiate an action to COM ---> to turn off the corresponding I-PDU groups and NM PDU:s.

    ....eg2: SW-C (Requests which communication mode) -----> BswM ----> ComM (provides an indication) to SW-C

    ....eg3: Shutdown request from SW-C ---> goes to EcuM ---> indicates BswM about the request ---> then sends the control back to EcuM to resume shutdown process


    Query?? >>

    1. Are the above examples flow is correct? Else Please correct me if I was wrong anywhere in my understanding... Also does AUTOSAR suggest alternate Use-Case to implement the above examples? Please explain..

    2. SW-C can makes direct calls(thru RTE) to EcuM or BswM or ComM, ?

    3. If BswM wants to change the EcuM state, it has communicate to EcuM only thru RTE switch calls or BswM can directly interact with EcuM

    4. Does EcuM has to indicate BswM about all the request or it is not mandatory?

    Please help me to correct the above use-cases and queries.


    Thank you,
    Md Najmuddin Siddique.
    This post was modified on 20 May 2010 at 07:45 pm.
    • 20 May 2010, 7:42 pm
  • Oliver Meili
    Oliver Meili
    The company name is only visible to registered members.
    Re: ECU StateManager and BSW Mode Manager - AUTOSAR 4.0
    Hello,

    ....Mode Switch indications (always issued by BSW modules) go through the BswM for further propagation to the SW-Cs,
    Not necessarily. E.g. the ComM has a user mode indication for each user individually, which can directly be read by an SW-C.

    Topic here is that the AUTOSAR 4.0 approach (only using modes and the BswM) collides with the legacy approach of AUTOSAR 3.1 and before where all requests were made to ComM, EcuM.

    ....eg1: If DCM (Requests Mode) ----> Disable Normal Communication goes thru COM ----> It would then goto BswM (Mode control / actions) for enable or disable ---> then initiate an action to COM ---> to turn off the corresponding I-PDU groups and NM PDU:s.
    The path is as follows: Dcm -> BswM -> Com/BusSM and finally BswM -> Dcm (for mode switch confirmation)

    ....eg2: SW-C (Requests which communication mode) -----> BswM ----> ComM (provides an indication) to SW-C
    Typically the use-case would be that an SW-C switches to an application mode, which the BswM detects as a necessity to activate communication and therefore requests communication with the ComM. The SW-C does not get a confirmation for the mode switch, unless it uses the BswM_RequestMode API and checks whether the BswM actually switched the mode.

    ....eg3: Shutdown request from SW-C ---> goes to EcuM ---> indicates BswM about the request ---> then sends the control back to EcuM to resume shutdown process
    This corresponds to the AUTOSAR 3.1 (and prior) method to do this. In AUTOSAR 4.0 you would enter an application mode or request an application with the BswM which leads to the release of an EcuM user or (as for example in the diagnostics request EcuReset) calls EcuM_KillAllRUNRequests.

    Query?? >>
    1. Are the above examples flow is correct? Else Please correct me if I was wrong anywhere in my understanding... Also does AUTOSAR suggest alternate Use-Case to implement the above examples? Please explain..
    See above.

    2. SW-C can makes direct calls(thru RTE) to EcuM or BswM or ComM, ?
    If you are developping SW-C for AUTOSAR 4.0, the preferred method is to use the BswM only and avoid any direct interfaces to the EcuM or the ComM. The BswM is supposed to arbitrate any mode requests and either accept or reject them.

    3. If BswM wants to change the EcuM state, it has communicate to EcuM only thru RTE switch calls or BswM can directly interact with EcuM
    The BswM may use a direct interface to the EcuM without using the RTE.

    4. Does EcuM has to indicate BswM about all the request or it is not mandatory?
    The EcuM indicates all state changes to the BswM by means of the API BswM_EcuM_CurrentState. Note that this does not mean that all requests are indicated, only the state changes.

    Note that AUTOSAR 4.0 specifies two different variants of the EcuM, the EcuMfixed (corresponding to the EcuM in AUTOSAR 3.1 and prior) and the EcuM (which is just a very basic EcuM managing startup and shutdown). In the latter case, you will have to configure the different run mode with the BswM, particulary useful for ECUs which have to perform some actions in a semi-sleep mode and go to sleep again (think of BCMs).

    Hope this helps

    Oliver
    • 21 May 2010, 5:00 pm
  • MD Najmuddin Siddique
    MD Najmuddin Siddique
    The company name is only visible to registered members.
    Re^2: ECU StateManager and BSW Mode Manager - AUTOSAR 4.0
    Thank you Oliver !! It was good info ...
    This post was modified on 24 May 2010 at 01:54 pm.
    • 24 May 2010, 1:50 pm
  • User photo
    Balu Chriss
    (not a XING member)
    Re^2: ECU StateManager and BSW Mode Manager - AUTOSAR 4.0
    Hello Oliver,

    i have some more doubts regarding the communication between ECUM-FIXED and BSWM.

    EcuM-Fixed module indicating current wakeup source to Bswm by using following interface "BswM_EcuM_CurrentWakeup".

    Que1. what are the actions BswM has to perform based on this indication?

    Thanks in advance,

    BR,
    Balu
    • 14 Jul 2011, 4:01 pm