![]() ![]() Likewise, it's still simple to flash the boards with your code in a single command line. The thing I like with ST is that their STM32Cube development tools are pretty straight forward and multiplatform (I use Linux). You can also physically remove, or simply disable, the ST-Link also, which is good if you're wanting to use the board in a project and don't need the ST-Link and its accompanying power consumption. The Nucleo boards have an onboard ST-Link programmer / debugger, which is nice to have when getting started. However, if you're a hobbyist this doesn't matter too much, and within a given series the variations won't matter much unless you've very specific needs. Starting on STM32 boards, the big thing is overcoming information overload from the almost endless versions of microcontrollers that ST offer. I've got a few STM32 boards on my desk at the moment, including a Nucleo-L073RZ and STM32F0Discovery both very affordable when purchased from one of the big suppliers like Mouser or Digikey etc. I mean ~$3 for a robust M4 development and prototyping system is a pretty good buy. This is all true with the Discovery and Nucleo boards too, but they aren't $1-3 each. Like MicroPython instead, you can get it running in a few minutes and be good to go. Yes, CubeMX is easy, the others are just other ways that people like to work, and they are all available using the Blue or Black Pill boards. I personally tend to just rock across the buttons to get into DFU mode and program them, and find it easier than the ST-LINK, either stand alone or on the Discovery boards. On the new STM32F411 boards, the DFU is built into ROM, and they come with buttons instead of jumpers. So if you prefer that method, it is easy and cheap to just grab a USB ST-LINK device. What I am saying is if you get an st-link, a blue pill will behave as the discovery, as all ST did was add a STM32F103 on a part of the board and programmed it to be an ST-LINK. ![]()
0 Comments
Leave a Reply. |