Introduction to AUTOSAR/OSEK RTOS II

Bind alarms to counters and trigger actions when the counter, incremented by the tick source, reaches the alarm preset defined in the oil description; presets can change at runtime.

Configure each alarm statically in the oil description with a single action—task activation, event setting, or callback, and cannot be changed at runtime. Include relative, absolute, one-shot, and periodic types.

Explore the absolute alarm API (ABS) and how an alarm time and optional cycle time produce first fires, one-shot or periodic actions, auto-start, and active task activation per the oil description.

Demonstrates implementing a periodic task that toggles a led, with an initialization task auto-starting at power-up and an absolute alarm firing every 50 ticks, first at 300 ticks.

Explore an autosar os alarm example that triggers a led blink every 500 ms after a 3-second power-up, with simulation and real-time measurements validating timing.

Understand relative alarms in AUTOSAR OSEK RTOS: the RL service fires first relative to the current counter, using id, alarm time, and cycle time.

Autosar/osek rtos ii explains one shot alarms: a set relative alarm fires once after invocation, with zero cyclic time, activating a task, and must be re-invoked for another fire.

Explore alarm management in AUTOSAR/OSEK RTOS II using absolute and one-shot relative alarms to drive periodic and non-periodic tasks; observe expiry-based activations and tick-based timing with a base counter.

Demonstrates alarm management with a periodic alarm triggering a periodic task every 50 ticks after a 200-tick startup, and a relative activation aperiodic alarm activating the second task.

Build a simple state machine on the launchpad using left and right switches to set the onboard LED color through states 0 to 3, with alarm management and periodic tasks.

Explore alarm-driven multitasking in Autosar/OSEK RTOS II, with initialization, switch handling, and led control tasks activated by five-second alarms to drive a red-green-blue-white led state machine via gpio port f.

Explore the Osek alarm APIs in AUTOSAR/OSEK RTOS II, including set absolute and relative alarms, with alarm ID, start, cycle, plus cancel, get alarm base, and get alarm current value.

Learn alarm management for pwm-based led brightness using a fixed period and duty cycle. Use left and right switches to change color and duty cycle via alarms.

Explains alarm driven execution in autosar/osek rtos ii using a cortex-m4 system with millisecond ticks, multiple tasks, and three alarms to control a pulse width modulated led.

Explore configuring alarm callbacks in AUTOSAR/OSEK RTOS II with two alarms that trigger short callbacks to toggle variables A and B every 50 and 20 ticks after a three-second start.

Explore the event control technique in this os-based rtos, where event objects act as binary flags to synchronize tasks and manage private and public masks.

Explore how event usage in AUTOSAR/OSEK RTOS II enables task synchronization through owner task events, wait and set operations, and how event masks map to bits for clearing by owner.

Explore an Autosar/OSEK RTOS II event control example where a basic periodic task is activated by a 50-tick alarm and an auto-started extended task awaits and toggles a periodic event.

Explore event-driven scheduling in Autosar/OSEK RTOS II, detailing periodic extended and periodic basic tasks, alarms, and event masks, and observe preemption and task toggling in simulation.

Describe how event setting and waiting affect task management and scheduling in preemptive and non-preemptive systems, using set and wait event services and priority-driven state transitions.

demonstrates non-preemptive system behavior with event setting, showing that set event is not a preemption point, and detailing state changes between running, waiting, and ready for basic and extended tasks.

Learn how a server task uses conditional events, set by another task, to wait for A, B, and C, execute event-specific code, and then re-wait for new events.

Observe two tasks: a periodic basic task activated by a ten-tick absolute alarm and an extended auto-started task that responds to events A, B, and C by toggling signals.

Explore AUTOSAR/OSEK RTOS II event example: events A, B, C managed by a server task and a periodic basic task activated by ten-tick alarm, showing event toggling and priority order.

Explore a four-state finite state machine driven by left and right switches, outputting red, green, blue, or white leds and handling inputs and transitions via events.

Convert a state machine from diagrams to a state transition table, showing color outputs and next states by input, then map to a C structure with a state pointer.

Explore an autosar os ek rt os ii event driven finite state machine example with initialization and server tasks, plus an input task driving gpio colors red, green, blue, white.

Explore how an alarm sets an event for an extended task on expiry, with static task and event IDs guiding wait, ready, and run transitions.

Demonstrates a single auto-start task coordinated by three alarms that set five, ten, and thirty-five tick events to generate pwm signals, illustrating event-driven scheduling and runtime behavior.

Configure hook routines in the osek os to execute actions within the os context using fixed startup interfaces, while observing kernel restrictions and oil descriptions that shape generated code.

startup hook routine in autosar/osek rtos ii initializes os objects during startup and is implemented by the application designer; the scheduler runs, selecting the highest priority ready task after startup.

Utilize the startup hook to initialize hardware during startup, eliminating the init task to save memory. Manage PWM with a single auto-started task, two alarms, and two events.

Drive led brightness with a startup hook during system startup, using cycle start and pulse width alarms to sweep a counter from 1 to 99 and back.

Configure pre-task and post-task hooks to run at scheduling points, enabling runtime measurements, task state checks, and debugging of task order and cpu load in autosar/osek rtos ii.

Explore hook routines in AUTOSAR/OSEK RTOS II by using pre and post task hooks and startup hooks to measure a periodic task’s execution time and illustrate array multiplication performance.