Invalid setting of ADC_ETC(XBAR) trigger group that occurs in RT1010

[YutakaN]

Hello,
I found a strange point that occurs only when selecting RT1010 of MCUXpresso Config Tools (ADC_ETC).

Trigger group is selected as follows.

(Trigger source) → (Trigger group)
XBAR1_TRIG, 0 → 4
XBAR1_TRIG, 1 → 5
XBAR1_TRIG, 2 → 6
XBAR1_TRIG, 3 → 7

But this doesn't work.
The operation is stopped by the following assertions.

Here, ADC_ETC_TRIGn_CTRL_COUNT is defined in MIMXRT1011.h as follows.

#define ADC_ETC_TRIGn_CTRL_COUNT (4U)

So Trigger Group seems to be correct at 0,1,2,3.

Actually, in the sample project "evkmimxrt1010_adc_etc_software_trigger_conv", the following is written.

ADC_ETC_SetTriggerConfig(DEMO_ADC_ETC_BASE, 0U, &adcEtcTriggerConfig);

(That is, 0 is used instead of 4.)

It occurred in the following versions.
-------------------------------
Config Tools - Peripherals Tool
Version: 8.0.0.202007071544
-------------------------------

Kind regards,
YutakaN

[YutakaN]

Dear Felipe,
Thank you for your reply.

My main issue is the number of "Trigger group" created by the Config Tools.

I have confirmed the RM by your reply and found out.

The "Config Tools" ought to generate the value as follows:

//Current (MIMXRT1011)
(Trigger source) → (Trigger group)
XBAR1_TRIG, 0 → 4
XBAR1_TRIG, 1 → 5
XBAR1_TRIG, 2 → 6
XBAR1_TRIG, 3 → 7

//Modify
(Trigger source) → (Trigger group)
XBAR1_TRIG, 0 → 0
XBAR1_TRIG, 1 → 1
XBAR1_TRIG, 2 → 2
XBAR1_TRIG, 3 → 3

Please check it.

Best regards,
YutakaN

[FelipeGarcia]

Dear YutakaN,

I think I see what you mean now. I am going to report this issue to the Config Tools development team to see if we can fix this in future releases.

Thanks for bringing this to our attention.

Best regards,

Felipe

[FelipeGarcia]

Hi Yutaka,

This assert is because i.MX RT1010 devices only have 4 trigger groups (0 to 3). You can confirm this if you check the reference manual in ADC_ETC Memory map section you will see only ETC_TRIG0 to ETC_TRIG3.

On the other hand, RT1050 families contains up to 8 trigger groups. That's why the asserted is needed to prevent Config Tools to set a trigger group that is only available in larger devices.

I hope this clarifies.

Best regards,

Felipe