cubeMX MDMA bugs on cubeIDE 1.12

[SeyyedMohammad]

1. After selecting transfers MDMA request, the tab will lock to the selected request and will be no longer changable.
2. We can't change order of channels.

Big bug:

I've changed mdma channel number:

But code generator force sw request channel as channel 2 (ioc included):

DMA_HandleTypeDef hdma_dma_generator0;
DMA_HandleTypeDef hdma_dma_generator1;
MDMA_HandleTypeDef hmdma_mdma_channel40_dma1_stream0_tc_0;
MDMA_LinkNodeTypeDef node_mdma_channel40_dma1_stream0_tc_1;
MDMA_HandleTypeDef hmdma_mdma_channel41_dma1_stream3_tc_0;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_1;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_2;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_3;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_4;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_5;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_6;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_7;
MDMA_LinkNodeTypeDef node_mdma_channel41_dma1_stream3_tc_8;
MDMA_HandleTypeDef hmdma_mdma_channel42_sw_0;
MDMA_LinkNodeTypeDef node_mdma_channel42_sw_1;
MDMA_HandleTypeDef hmdma_mdma_channel43_dma1_stream6_tc_0;
MDMA_LinkNodeTypeDef node_mdma_channel43_dma1_stream6_tc_1;
MDMA_LinkNodeTypeDef node_mdma_channel43_dma1_stream6_tc_2;
MDMA_HandleTypeDef hmdma_mdma_channel44_dma1_stream6_tc_0;
MDMA_LinkNodeTypeDef node_mdma_channel44_dma1_stream6_tc_1;
MDMA_LinkNodeTypeDef node_mdma_channel44_dma1_stream6_tc_2;

 After some manipulation of Channel number now the actual channel numbers differ from what I've set in cube MX and that really pain.  :wheelchair_symbol:�?

Also it seems in a generated code we have bug, the number 4 is redundant, doesn't it?

Major bug is MDMA link nodes variable declaration need to be attributed on align(8). But cube will not generate it and we need to change codes after every code generation on stm32cubeIDE 1.12 

Hi @Semer CHERNI​ 

If you could inspecting it I will thank you.

Best regards.

[Ghofrane GSOURI · Accepted solution]

Hello @SeyyedMohammad​ 

Thank you for your contributions and for your detailed explanations,

I confirm the issue on my side, it has been reported to STM32CubeMX development team .

Internal ticket number: 150288(This is an internal tracking number and is not accessible or usable by customers).

I will keep you posted with updates.

Thx

Ghofrane