MCUXpresso generates invalid eDMA code when "Submit transfer" is enabled (MCXN547 )

[tjo_dk]

Hi,

I am using MCUXpresso Config Tools v26.x with an MCXN547 project and configuring an ADC -> eDMA transfer using the eDMA peripheral component.

Configuration:

• eDMA Channel API mode: Transactional (transfer configuration)
• eDMA request: ADC1 FIFO A request
• Submit transfer: Enabled
• Auto stop request: Enabled
• Peripheral request: Enabled

The generated code in peripherals.c contains:

status = EDMA_SubmitTransfer(&DMA0_CH0_Handle,
                             DMA0_CH0_Transfers_config,
                             1U);
assert(status == kStatus_Success);

However, no declaration for status is generated. As a result, the project fails to compile with:

error: 'status' undeclared (first use in this function)

Expected generated code would be either:

status_t status;
status = EDMA_SubmitTransfer(...);

or:

assert(kStatus_Success ==
       EDMA_SubmitTransfer(...));

Has anyone seen this issue before?

Is this a known code-generation bug in Config Tools, or is there an additional configuration option required when using "Submit transfer"?

I can provide the generated peripherals.c and .mex configuration if needed.

Thanks.

[carlos_o]

Hi @tjo_dk 

Thank you for your post!

Could you please share the which package of MCXN547 are you using?

Which version of Config tools are you using? is it 26.03?

Which SDK version do you have installed? 

Please share this information to replicate the setup on my end.

[tjo_dk]

Hi

Thnaks for the fast responds.

Yes, I have v26.03 of the tool

Processors:
MCXN547 (26.03.20) - MCX MCXN

MCUXpresso SDK version 25.13.00

Package: mcuxsdk-core
Version: 2.0.0

The 'Loop all transfeer' in the DMA0- Transfeer Configuration ad this code to DMA0_init()

/* DMA0 loop transfer submit */
status = EDMA_SubmitLoopTransfer(&DMA0_CH0_Handle, DMA0_CH0_Transfers_config, 1U);
assert(status == kStatus_Success);

Where 'status' is not declared anywhere.

[carlos_o]

Hi @tjo_dk,

I tried to replicate the issue using the same configuration you are using. However, on my side, the code preview already includes the declaration of the status variable in the DMA0_init function.