Found that the STM32 development board is not good

ddllxxrr

Found that the STM32 development board is not good [Copy link]

The standard library of STM32 is a very convenient solution for porting. However, I have recently looked at the routines of several STM32 development boards, and they all have a BSP, which is so annoying. You have a BSP, and he has a BSP, which makes the very convenient porting of the industry go back to the pre-liberation era. This restricts STM32 again. For example, if I want to copy a piece of USART code. I have to include a BSP.h. Isn't it annoying? ? ? ? ? This content was originally created by EEWORLD forum user ddllxxrr. If you want to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source

littleshrimp

Using STM32CubeMX

dcexpert

The current development method is too complicated. In order to promote their own products, each manufacturer has more and more restrictions on the software. Mbed can make the software more universal, but it has not been popular for so many years.