[kekkoian]

ok i fixed with HAL_GPIO_WritePin(GPIOA, GPIO_PIN_5, GPIO_PIN_SET);

in MX_GPIO_Init function

but really is not clear why i need to SET the GPIO in the init function to have it OFF.

• This reply was modified 3 years, 8 months ago by kekkoian.

[kekkoian]

hahhaha, the reason is explained in question and suggestions.

Many thanks, but really i already see this in HAL_UART_Receive_DMA:

/* Enable the UART Parity Error Interrupt */
SET_BIT(huart->Instance->CR1, USART_CR1_PEIE);
/* Enable the UART Error Interrupt: (Frame error, noise error, overrun error) */
SET_BIT(huart->Instance->CR3, USART_CR3_EIE);

[kekkoian]

Read Carefully
In STM32F2/F4/F7/L1/L4 families, only the DMA2 has full access to the Bus Matrix. This
means that only timers whose requests are bound to this DMA controller can be used to
perform transfers involving other peripheral (except for the internal and external volatile
memories). For this reasons, this example for Nucleo boards based on F2/F4/L1/L4 MCUs
use TIM1 as base generator.
In STM32F103R8, STM32F302RB and STM32F334R8, STM32L053R8 and STM32L073RZ
MCUs TIMx_UP request does not allow to trigger transfer between memory and
GPIO peripheral. So this example is not available for the corresponding Nucleo
boards.

[kekkoian]

ok it works with advanced timer. Thanks!!!

[kekkoian]

ok i understand why….

i think its becouse HAL_UART_RxCpltCallback

[Author]

Posts