Problems with Hardware Triggers on S32K358

simon98 — Mon, 24 Nov 2025 11:06:02 GMT

Hi NXP,

I'm having problems with Hw trigger functionality in a S32K358 custom board.

I'm using MBDT v1.5 in matlab 2024.

I've configured 3 cahnnels of EMIOS_1 (ch_9, ch_11, ch_19) in order to have 3 pwm signals and i've configured them as EMIOS_PWM_IP_MODE_OPWMT to enable trigger generation.

In AdcHwTrigger i've configured 3 Hardware Triggers with the correspondig BTCU sources and 3 ADC_1 groups with one injected channel each.
These cahnnels are latched on with the corresonding Hw Trigger as well. The ADC_1 works with interrupt method.

I've configured also the Platform ISR and MCU Clock correctly.

In the simulink model i enabled the Notifications and Hw Triggers in a subsystem called every 50ms by a stateflow chart. Once the adc channel is converted the application calls the
Interrupt Hw callback in which disables the Notification and the relative Hw Trigger for that group.
This is done for each of the 3 groups.

In this way i have 3 pwm signals that starts at the same time with the same periodicity (200Hz in my case), so based on what i've read on RM (64.3.1.9 Priority of simultaneous triggers)
i expect that the BCTU receives 3 triggers at the same time and perform the conversion of the adc channel attached to the highest priority trigger (BCTU_EMIOS_1_9 in my case)
while the others (BCTU_EMIOS_1_11 and BCTU_EMIOS_1_19) stay pending waiting for their turn to access ADC_1 and perform conversion as well.
When the conversion related to BCTU_EMIOS_1_9 trigger is performed i expect that his trigger would be disabled in the interrupt callback and the second pending trigger (BCTU_EMIOS_1_11 in my case)
starts the conversion...

Unfortunately i couldn't see this behavior… I only see that it performs the convertion of the adc attached to the highest priority trigger (BCTU_EMIOS_1_9 in my case),
ignoring the others.

Am i doing something wrong or misunderstanding something? How could i do to have the behavior descripted above?

I attach the mex file

Thanks,
Simon

Model-Based Design Toolbox (MBDT)のトピックProblems with Hardware Triggers on S32K358

Problems with Hardware Triggers on S32K358