SNIP_CLASSIC_COMM_SECTION_7_4_4_3_Jump_from_Bootloader_ECUReset

7.4.4.3 Jump from Bootloader / ECUReset [SWS_Dcm_00536] Upstream requirements: RS_Diag_04098 ⌈At Dcm initialization, the Dcm shall call Dcm_GetProgConditions to know if the initialization is the consequence of a jump from the bootloader / ECUReset.⌋ Note: It is the responsibility of the software integrator to ensure that the data contained in Dcm_ProgConditionsType is valid when Dcm_Init is called. E.g. if this data is stored in non-volatile memory, it may take some time to make it available after an ECU reset. This has to be taken into account when designing the ECU’s startup process. [SWS_Dcm_00537] ⌈If the initialization of the Dcm is the consequence of a jump from the bootloader / ECUReset (see [SWS_Dcm_00536], the Dcm shall call ComM_DCM_ActiveDiagnostic(NetworkId) to request the ComManager for the full communication mode.⌋ [SWS_Dcm_00767] Upstream requirements: RS_Diag_04098 ⌈When the ComM reports full communication to the Dcm, the Dcm shall send the Response to the Service Id passed in the Dcm_ProgConditionsType.⌋ [SWS_Dcm_00768] ⌈If the initialization of the Dcm is the consequence of a jump from the bootloader (see [SWS_Dcm_00536] and the application is updated by an FLASH download (Dcm_ProgConditionsType.ApplUpdated == True), the Dcm shall call BswM_Dcm_ApplicationUpdated() to notify the BswM that the application was updated.⌋