Models can include blocks for generating code that handles asynchronous events, such as:
Asynchronous read and write operations
Asynchronous tasks spawned by a real-time operating system (RTOS)
For simulation, you can import asynchronous event data into a function-call subsystem.
|Asynchronous Task Specification||Specify priority of asynchronous task represented by referenced model triggered by asynchronous interrupt|
|Async Interrupt||Generate Versa Module Eurocard (VME) interrupt service routines (ISRs) that execute downstream subsystems or Task Sync blocks|
|Idle Task||Create free-running task|
|Task Sync||Run code of downstream function-call subsystem or Stateflow chart by spawning an example RTOS (VxWorks) task|
Design models that support execution of blocks in response to events that occur asynchronously to the periodic timing source of the system.
Use Rate Transition blocks to handle data transfers to and from asynchronous blocks.
Generate an interrupt service routine (ISR) that is associated with a specific VME interrupt level.
Simulate and generate code for asynchronous events on a multitasking, real-time operating system (VxWorks®).
Generate code for a model that triggers asynchronous events that get passed as input to a referenced model.
Maintain absolute and elapsed timing data for blocks that execute in the context of an asynchronous task with the code generator.
Create custom blocks that support handling of asynchronous events with vxlib1 library blocks as templates.
Import asynchronous event data into a function-call subsystem.
Limitations of asynchronous event support.