SNIP_CLASSIC_DLT_SECTION_7_1_6_Startup_behavior

7.1.6 Startup behavior The Dlt module specifies several configuration parameters, which can be reconfigured during runtime via API calls or via Dlt control messages. This means, that those configuration parameters respectively data structures, which are based on them, have to be loaded into runtime variables during the startup of the Dlt module. In addition, it might happen that SW-Cs and/or BSW modules are already generating log and trace data even though the Dlt module itself has not been initialized yet. For this scenario, the Dlt module offers the possibility to buffer even this data until the Dlt module is initialized. The described functionalities result in the requirements below: [SWS_Dlt_00003] Upstream requirements: RS_LT_00036 ⌈The Dlt module shall be able to buffer data coming from calls to Dlt_SendLogMessage and/or Dlt_SendTraceMessage even if the Dlt module has not been initialized yet.⌋ [SWS_Dlt_00648] ⌈When the Dlt_Init is called, the optional timer DltGeneralStartUpDelayTimer shall be started if configured.⌋ [SWS_Dlt_00649] ⌈If the parameter DltGeneralNvRAMSupport is disabled, static Dlt module configuration shall be used for initialization.⌋ [SWS_Dlt_00005] ⌈As soon as the Dlt module is initialized by Dlt_Init and the optional timer DltGeneralStartUpDelayTimer has expired, all the log and trace data, which has been buffered meanwhile, shall be processed according to [SWS_Dlt_00651], using the configured filter settings.⌋