Setting Up Hook Routines
Note |
|---|
This instruction applies only to the ASCET‑RP targets. To use the RTPRO-PC target, you must also use an external INTECRIO V4.7.2 or lower as hardware configurator; see Selecting an External Hardware Configurator. |
You can specify the generation of hook routines for debugging purposes for each task.
- Make sure that the Enable Monitoring option is activated.
From the pre/post hooks combo box, select one of the following options.
none
no debug functions
monitoring
Complete debug functions, i.e. the monitoring variables for the task (see Monitoring Option) are generated during the next code generation. You can show them in the measure windows or write them to the data logger.
Depending on the settings, suitable data structures are created during code generation, and the appropriate OS libraries are included. For this purpose, ASCET generates the make variable E_HOOKS. The following table shows the correlations between the settings in the OS editor and the E_HOOKS variable:
Enable Monitoring | Pre/post hooks | Generated value for E_HOOKS | dT available in the Code |
activated | monitoring for at least one task | MONITORING | yes, additional debug information |
deactivated | monitoring for at least one task | DTONLY | yes |
any | none for all tasks | DTONLY | no |
For simulations with experimental targets, only the monitoring option is important. It controls the generation of monitoring variables (see The Monitoring Option).
See also
Defining the Scheduling (RTA-OSEK + Generic OSEK)
Defining the Scheduling (Generic OS)
Selecting a Trigger (ISR Source)