Electronic – STM32F303 STM32CubeMX __HAL_TIM_SetCompare macro does not exist

nucleopwmstm32stm32cubemx

I am using CubeMX to generate code for my NucleoF303. I am a bit confused how to set the pulse width of a timer in PWM mode.

Previously (using an F4) there has been a __HAL_TIM_SetCompare macro in the stm32fxxx_hal_tim.h file.

But that does not exist. Am I supposed to set the duty cycle in some other manner?

Of course I can just directly set the CCRx registers. That works. But if I am going to use a HAL with lots of abstraction like cube seems to be, I would at least like to know how they intend me to use it. Even if I don't.

Not really any code to go with this question.. But here is my current commit in case it is useful:
https://github.com/c-herring/Sumo2017_NucleoF303/tree/221dc57a305ccd64a4b98726df3cce02720b280b

Cheers!

Best Answer

Previously (using an F4) there has been a __HAL_TIM_SetCompare macro in the stm32fxxx_hal_tim.h file.

That was indeed some time ago. I've found a copy of STM32CubeF4 V1.6.0 (released 28-May-2015) lying around in an old project directory, and it already has the following alias definition

Inc/Legacy/stm32_hal_legacy.h:#define __HAL_TIM_SetCompare            __HAL_TIM_SET_COMPARE

Digging even deeper, the description of 1.4.0 says

STM32CubeF4 Firmware Package V1.4.0 / December 26, 2014

Main Changes

Maintenance release to fix known defects and several enhancements implementation

HAL Macros and literals renaming to ensure compatibles across STM32 series, backward compatibility maintained thanks to new added file stm32_hal_legacy.h under /Inc/Legacy

So, it must be the time when __HAL_TIM_SetCompare got deprecated in favor of __HAL_TIM_SET_COMPARE.

You should still get the alias definition though, because all HAL headers include stm32_hal_legacy.h.

Related Solutions

Electrical – STM32 interrupt does not fire

Do the steps from my comment, Here is the sample code. I had a different hardware connections so I used a different pins.

int main(void) {
    RCC->APB2ENR = RCC_APB2ENR_IOPBEN | RCC_APB2ENR_IOPCEN | RCC_APB2ENR_AFIOEN;


    //confure PB2  PC13 as inputs, PB0 output

    AFIO->EXTICR[0] = AFIO_EXTICR1_EXTI2_PB;
    AFIO->EXTICR[3] = AFIO_EXTICR4_EXTI13_PC;
    EXTI->IMR = EXTI_IMR_MR2 | EXTI_IMR_MR13;
    EXTI->RTSR = EXTI_RTSR_TR2;
    EXTI->FTSR = EXTI_FTSR_TR13;
    NVIC_EnableIRQ(EXTI2_IRQn);
    NVIC_EnableIRQ(EXTI15_10_IRQn);
    while (1);
} 
void EXTI2_IRQHandler(void) {
    if (EXTI->PR & EXTI_PR_PR2) {
        EXTI->PR = EXTI_PR_PR2;
        GPIOB -> ODR |= GPIO_ODR_0;
    }
}

void EXTI15_10_IRQHandler(void) {
    if (EXTI->PR & EXTI_PR_PR13) {
        EXTI->PR = EXTI_PR_PR13;
        GPIOB -> ODR &= ~GPIO_ODR_0;            
    }
}

one pin turns led on another turns off

Electronic – STM32F303 Readout Protection Level 1 – programs do not start at all

Silly thing. After setting the protection level Power On Reset is needed. No other reset type resets the micro. After the power on reset everything works fine. (only one POR needed of course after the protection level change).

It is in the RM - I have not noticed it

If the read protection is set while the debugger is still connected through JTAG/SWD, apply a POR (power-on reset) instead of a system reset.

Best Answer

Related Solutions

Electrical – STM32 interrupt does not fire

Electronic – STM32F303 Readout Protection Level 1 – programs do not start at all

Related Topic