7 years, 3 months ago.

Stefano -

I think the problem you may be having is that you are using the default usart, USART2, which is not capable of operating at a target baud rate of 3686400 without making additional changes to the mbed default uart configuration for the nuclei f411re (e.g. reducing the default mbed oversampling from 16 to 8).

The f411re’s USART1 and USART6 should be capable of operating at a target baud rate of 3686400 since they run off of the APB2 bus. The APB2 bus has an f_pclk of 100MHz when the MCU is clocked at 100 MHz. USART2 runs off of the APB1 bus, which only has an f_pclk of 50 MHz. USART2 therefore can only operate at half the maximum baud rate of USART1 and USART6.

General information on setting the f411re usart baud rate can be found in Section 19.3.4 of the MCU reference manual RM0383. That section describes how to configure the BRR register for the baud rate closest to the desired target and the associated baud rate error.

The mbed api sets the baud rate using the init_uart function in serial_api.c, using oversampling by 16 (OVER8 = 0). This function calculates the BRR register DIV_Mantissa and DIV_Fraction values using the macro USART_BRR(_PCLK_, _BAUD_) which you can find in "stm32f4xx_hal_usart.h".

The APB2 f_pclk is 100 MHz for the nucleo f411re board clocked at 100 Mhz. For a target baud rate of 3686400 with 16x oversampling, the desired USARTDIV value is 1.695. The closest available USARTDIV value is 1.6875 (DIV_Mantissa = 1, DIV_Fraction = 11). This gives an actual baud rate of 3703703.7, or an error of 0.4672 percent.

If you switch to USART1 or USART6 and still have problems, you can check that the USART baud rate is being correctly configured by reading out the values in the BRR register after you have initialized the uart. Note that you are trying to run the usart at the maximum specified value for the f411re, so other factors may come into play that could effect its performance at this rate.