Electronic – STM32: Difference between HAL_xxx_Init() and HAL_xxx_MspInit()

hal-librarymicrocontrollerprogrammingstm32stm32f3

When using the HAL (Hardware Abstraction Library) for any of the STM32 micro controllers:

For a given peripheral, why do you have to call an HAL_…init() , as well as a HAL…_MspInit() – why are several 'inits' separated?

Best Answer

The ST User Manual UM1725 - Description of STM32F4 HAL and LL drivers, see pages 61 - 63, gives an explanation:

The peripheral initialization is done through HAL_PPP_Init() while
the hardware resources initialization used by a peripheral (PPP) is performed during this initialization by calling MSP callback function HAL_PPP_MspInit().
The MspInit callback performs the low-level initialization related to the different additional hardware resources: RCC, GPIO, NVIC and DMA.

(MSP: MCU Support Package)

and

2.12.2 HAL global initialization:

HAL_Init(): this function must be called at application startup to
- initialize data/instruction cache and pre-fetch queue
- set SysTick timer to generate an interrupt each 1ms (based on HSI clock) with the lowest priority
- set priority grouping to 4 preemption bits
- call HAL_MspInit() user callback function to perform system level initializations (Clock, GPIOs, DMA, interrupts). HAL_MspInit() is defined as “weak” empty function in the HAL drivers.

Related Solutions

Electronic – STM32 ADC conversion using HAL

In your original code, set the End of Conversion Selection to disabled.

 hadc1.Init.EOCSelection = DISABLE;

It turned out that #define ADC_EOC_SEQ_CONV ((uint32_t)0x00000000) value is equal to DISABLE. So actually the EOCSelection should be configured as:
to be able to poll the ADC multiple times.

Then you can read the ADC continously without stopping and starting the ADC:

int main(void)
{
    HAL_Init();
    SystemClock_Config();
    ConfigureADC();

    HAL_ADC_Start(&hadc1);
    while(1)
    {
        if (HAL_ADC_PollForConversion(&hadc1, 1000000) == HAL_OK)
        {
            ADCValue = HAL_ADC_GetValue(&hadc1);
        }
    }
}

This way it worked fine for me.

Since HAL is a quite new library there are not a lot of resources to be find but not impossible. I learned a lot from this tutorial, it demonstrates all possible ADC useage step by step; from simple polling, to using interrupts and DMA.

Electronic – HAL + DMA + UART = STM32 crash

I finally found the problem :)

The startup script file (startup_stm32.s) was not good, the declaration of each handler and interrupt was missing. Added it and now the DMA + UART triggers the HAL_UART_RxCpltCallback as expected.

For example:

.weak   DMA1_Channelx_IRQHandler
.thumb_set DMA1_Channelx_IRQHandler,Default_Handler

Best Answer

Related Solutions

Electronic – STM32 ADC conversion using HAL

Electronic – HAL + DMA + UART = STM32 crash

Related Topic