2020-03-15 01:51 AM
I reporte a bug of STM32G4xx LL library, the Definition of DMAMUX_LL_EC_REQUEST Transfer request in header file "stm32g4xx_ll_dmamux.h" as shown below.
#define LL_DMAMUX_REQ_FMAC_WRITE 0x0000006EU /*!< DMAMUX FMAC WRITE request */
#define LL_DMAMUX_REQ_FMAC_READ 0x0000006FU /*!< DMAMUX FMAC READ request */
#define LL_DMAMUX_REQ_CORDIC_WRITE 0x00000070U /*!< DMAMUX CORDIC WRITE request*/
#define LL_DMAMUX_REQ_CORDIC_READ 0x00000071U /*!< DMAMUX CORDIC READ request */
But the STM32G4 Series reference manual is defined as below.
110 FMAC_Read
111 FMAC_Write
112 Cordic_Read
113 Cordic_Write
The HAL library is defined as follows.(stm32g4xx_hal_dma.h)
#define DMA_REQUEST_FMAC_READ 110U
#define DMA_REQUEST_FMAC_WRITE 111U
#define DMA_REQUEST_CORDIC_READ 112U
#define DMA_REQUEST_CORDIC_WRITE 113U
So it looks like that read and write are defined as the exact opposite in the LL library,include FMAC and CORDIC module.
Not only that, but a compilation error will be generated after generating the project, because there are no two macro definitions.
"LL_DMAMUX_REQ_MATRIX_READ"
"LL_DMAMUX_REQ_MATRIX_WRITE"
After the following modifications, can pass the compilation.
// LL_DMA_SetPeriphRequest(DMA1, LL_DMA_CHANNEL_3, LL_DMAMUX_REQ_MATRIX_READ);
LL_DMA_SetPeriphRequest(DMA1, LL_DMA_CHANNEL_3, LL_DMAMUX_REQ_FMAC_READ);
// LL_DMA_SetPeriphRequest(DMA1, LL_DMA_CHANNEL_4, LL_DMAMUX_REQ_MATRIX_WRITE);
LL_DMA_SetPeriphRequest(DMA1, LL_DMA_CHANNEL_4, LL_DMAMUX_REQ_FMAC_WRITE);
Expecting official feedback.
Thanks.
Solved! Go to Solution.
2020-03-19 05:32 AM
Hello all,
Thanks for the feedback,
It will be fixed next STM32CubeMX version.
Best regards,
Nesrine
2020-03-15 01:53 AM
Losing screenshots is frustrating.
2020-03-16 06:50 AM
I will check this issue and come back to you.
Which cube firmware version are you using ?
Can you please use the latest STM32CubeMx (V5.6.0)
2020-03-16 05:05 PM
Hi Imen DAHMEN
The firmware version STM32Cube_FW_G4_V1.1.0. I think the MCU package version is lastest.
The CubeMX current version is 5.5.0.
Anyway, I try use the latest STM32CubeMx (V5.6.0).
2020-03-16 05:44 PM
Hi Imen DAHMEN
I have used the latest STM32CubeMX (V5.6.0) regenerate this project, and the MCU package version also upgraded to the latest version "STM32Cube_FW_G4_V1.2.0."
But the bug is still not fixed.
2020-03-17 05:49 AM
Thank your for your contribution and reported issue.
After check, I confirm this issue and raise this internally for correction.
Best Regards,
Imen
2020-03-17 05:39 PM
Hi Imen DAHMEN
Thank you for your quick reply and looking forward to your confirmation.
Best Regards,
Peng
2020-03-18 02:10 AM
Hello,
The reported problem will be reviewed by our STM32CubeMX team, we will come back to you if there is any update.
Best regards,
Nesrine
2020-03-19 05:32 AM
Hello all,
Thanks for the feedback,
It will be fixed next STM32CubeMX version.
Best regards,
Nesrine
2020-03-19 07:55 PM
Hi Nesrine
Thank you for your reply.
Best Regards,
Peng