Hardware Interrupt

R2026b

Trigger function-call subsystems in response to hardware interrupt events

Since R2026a

• 

Hardware Interrupt block

To add a block to a model, double-click the canvas and start typing the block name. Then, select the block from the list.

Libraries:
Embedded Coder Support Package for Renesas RH850 Microcontrollers / Renesas RH850 U2A Based
Embedded Coder Support Package for Renesas RH850 Microcontrollers / Renesas RH850 U2B Based

Description

The Hardware Interrupt block triggers a downstream function-call subsystem from an interrupt service routine. When the selected interrupt occurs, the block outputs a signal that activates the connected function-call subsystem.

You can select the appropriate interrupt service routine and define which events to handle, as well as the order in which they are executed. Additionally, you can assign a priority level to the downstream function-call subsystem to control its execution precedence. You can also configure the block to run the interrupt service routine as an atomic unit, blocking other interrupts during its execution.

Examples

Using MCAL ADC and Hardware Interrupt Blocks with Renesas RH850 Microcontrollers

Acquire analog signals using the MCAL ADC block in a Simulink model and process the results using the Hardware Interrupt block on a Renesas RH850/U2A16 starter kit. You can use this approach to generate software-triggered ADC conversions, handle end-of-conversion interrupts, and read multiple ADC channels in real time.

• Open Live Script

Ports

Output

Port_1 — Function-call output

scalar

The block outputs a function-call signal when the selected interrupt and event occur.

Parameters

Interrupt group — Select interrupt group

Microcontroller Abstraction Layer (MCAL) Callbacks (default)

Select the peripheral or abstraction layer whose interrupt to use. The available options depend on the Renesas RH850 device and configuration.

Programmatic Use

Block Parameter: ISRNumber

Callback name — Specify callback name

mcal_driver_callback (default)

Specify the name of the callback function associated with the selected interrupt group.

Programmatic Use

Block Parameter: DerivedISRName

Simulink task priority — Option to add a new derived callback name

30 (default)

Specify the priority of the downstream function-call subsystem. Lower values indicate higher priority. This controls the execution precedence of the function-call subsystem triggered by the interrupt.

Programmatic Use

Block Parameter: TaskPriority

Run interrupt service routine as atomic unit — Block all other interrupts during execution

off (default) | on

Select to enable atomic execution of the interrupt service routine. When enabled, all other interrupts are blocked while the selected interrupt service routine is running.

Programmatic Use

Block Parameter: DisablePreemption

Programmatic Use: Add Block

To add the block programmatically, use the add_block function with one of these library block paths as the source.

"rh850u2axblockslib/Hardware Interrupt"

"rh850u2bxblockslib/Hardware Interrupt"

Example: add_block("rh850u2axblockslib/Hardware Interrupt","myModel/myBlock",MakeNameUnique="on")

Version History

Introduced in R2026a