undefined reference to `HAL_NVIC_SetPriority'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-13 3:15 AM
Hello,
I create new STM32 project for STM32MP131AAG3 with baremetal.
I encounter the following errors when to build the codes of DMA generated by STM32CubeMX.
- undefined reference to `HAL_NVIC_SetPriority'
- undefined reference to `HAL_NVIC_EnableIRQ'
static void MX_DMA_Init(void)
{
/* DMA controller clock enable */
__HAL_RCC_DMAMUX1_CLK_ENABLE();
__HAL_RCC_DMA2_CLK_ENABLE();
/* DMA interrupt init */
/* DMA2_Stream1_IRQn interrupt configuration */
HAL_NVIC_SetPriority(DMA2_Stream1_IRQn, 0, 0);
HAL_NVIC_EnableIRQ(DMA2_Stream1_IRQn);
}
I fixed the code as follows.
static void MX_DMA_Init(void)
{
/* DMA controller clock enable */
__HAL_RCC_DMAMUX1_CLK_ENABLE();
__HAL_RCC_DMA2_CLK_ENABLE();
/* DMA interrupt init */
/* DMA2_Stream1_IRQn interrupt configuration */
IRQ_SetPriority(DMA2_Stream1_IRQn, 0);
IRQ_Enable(DMA2_Stream1_IRQn);
}
Is this bug? Or is there possibility that I took mistake MX settings or else?
If it is bug, is there a plan to apply this bug fix to the STM32CubeMP13 codebase?
I am in trouble since the code reverts when I change MX settings.
Solved! Go to Solution.
- Labels:
-
Bug-report
-
Generate-Code
-
STM32MP13 Lines
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-18 3:29 AM
Hello @it3
First let me thank you for posting.
You are right about the proposed solution for this misbehavior.
In fact, this is a known issue and it's the subject of investigation. It should be fixed permanently in future release.
BR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-06-18 3:29 AM
Hello @it3
First let me thank you for posting.
You are right about the proposed solution for this misbehavior.
In fact, this is a known issue and it's the subject of investigation. It should be fixed permanently in future release.
BR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
