S32K312 BCTU FIFO/loop switch (non AUTOSAR prj)

Drifter22 — Fri, 13 Feb 2026 10:27:45 GMT

Hello,

I've read so many posts regarding BCTU topic and examples too, but I'm a bit confused about best configuration for my purpose.

Into my project I have 2 system statuses:

1- (DC brushed motor PWM active) ADC acquisitions triggered by Emios_1_12 PWM in order to read motor current and other channels synchronized with PWM frequency (and duty)

2- (no actuation) I'd like to acquire same channels from ADC continously without interruptions and then I'll read via SW only the channel that I need for a particular task.

My analysis:

Mode 1: BCTU HW triggered and list with all needed channels

Mode 2: BCTU triggered started once via SW and with loop mode active, in order to let conversions run continously.

I need to switch between these two modes (by disabling HW trigger or stopping loop mode), so I'd like to know which is the best solution and maybe alternatives.

My question is related also to which destination to use for results: for mode 2 I'd use ADC registers and then read with Adc_Sar_Ip_GetConvResultsToArray() API. For mode 1 I haven't found a way to specify an interrupt callback when all acquisistions of the channel list is done (independently from ADC instance) because I noted that it is possible to specify a "List last conversion notification" into "Bctu ADC Notifications" (NXP Configuration tool - MEX file) but I'll have an interrupt for each ADC (2 in my case), instead I'd like to have a single interrupt for all conversions of the list finished: for this reason I'm thinking to use FIFO and watermark.

For internal policy, I can't share my entire project at the moment.
Channels added into screenshots are both on ADC1 just for testing, but then I'll have to add other channels from ADC0.

Thanks

Re: S32K312 BCTU FIFO/loop switch (non AUTOSAR prj)

Julián_AragónM — Tue, 17 Feb 2026 18:18:40 GMT

Hi @Drifter22,

I think both modes are fairly common applications, and I see no issue with applying them to your routine.

For Mode 1, I recommend configuring FIFO + Watermark, as this would enable you to raise an interrupt for a completed "set" of ADC channels. Just keep in mind that notifications are done in a N + 1 logic, meaning that if you have watermark set to 3, notification is called when there are 4 entries in the FIFO and you can do 4 readings of FIFO.

For Mode 2, I think you have two choices. Either SW-triggered BCTU as you've mentioned or continuous ADC scanning (if you do not need various ADC instances). You can use either Adc_Sar_Ip_GetConvData or Adc_Sar_Ip_GetConvResultsToArray to extract the channel result,

There are various BCTU + ADC examples in our community, which may prove useful:

Best regards,
Julián

topic Re: S32K312 BCTU FIFO/loop switch (non AUTOSAR prj) in S32K

S32K312 BCTU FIFO/loop switch (non AUTOSAR prj)

Re: S32K312 BCTU FIFO/loop switch (non AUTOSAR prj)