SNIP_CLASSIC_OS_SECTION_7_4_2_2_1_Startup

7.4.2.2.1 Startup There are two options for starting an explicitly synchronized ScheduleTable: 1. Asynchronous start: Start the ScheduleTable at an arbitrary value of the synchronization Counter. 2. Synchronous start: Start the ScheduleTable at absolute value zero of the synchronization Counter only after a synchronization count has been provided. This may mean waiting for first synchronization indefinitely. Asynchronous start is provided by the existing absolute and relative ScheduleTable start services. Both of these services set the point at which the initial expiry point is processed with respect to the driver Counter not the synchronization Counter. This allows the ScheduleTable to start running before the value of the synchronization Counter is known. Synchronous start requires an additional service that starts the ScheduleTable only after the Operating System module is told the value of the synchronization Counter. The Operating System module provides the service StartScheduleTableSynchron (see [SWS_Os_00201]) to start an explicitly synchronized ScheduleTable synchronously. The Initial Expiry Point will be processed after (Duration - Value) + Initial Offset ticks of the driver Counter have elapsed where Value is the absolute value of the synchronization Counter provided to the ScheduleTable. [SWS_Os_00435] ⌈If an explicitly synchronized ScheduleTable was started synchronously, then the Operating System module shall guarantee that it has state "waiting" when the call of service StartScheduleTableSynchron returns.⌋()