![]() Getting started with any microcontroller will need a programming IDE like we have Arduino IDE for Arduino boards, Atmel Studio for AVR microcontroller, MP Lab for PIC, etc. Selecting and Downloading the Required Development Platforms for Nucleo64 Boards Even, if you have a different version, most things discussed in the tutorial will suffice for you to get started. We have selected this board mainly because of its low cost. Note: There are many versions of STM32 Nucleo64 Development Boards, the particular board used in this tutorial is NUCLEO-F030R8. The video also demonstrates how to program STM32 using ARM Mbed Platform but for this tutorial, we will use another free to use platform from ST Microelectronics called TrueSTUDIO. If you are completely new to the STM32 Nucleo64 Development Boards, do check out this Nucleo64 Review video to understand the basics of this board before you proceed further. Nucleo64 Development Boards are low cost and easy to use platform for professional developers as well as for hobbyist. Similarly, starting with this article, we will also plan a sequence of STM32 Nucleo64 Development Board Tutorials which can help absolute beginners to learn and develop using the STM32 Platform. We have already covered a sequence of PIC Microcontroller tutorials, which guides beginners for learning PIC microcontrollers. In fact, for most people, Arduino would have been their first development board, but as we dig deep and begin professional designs, we will soon realize the limitations of Arduino (like cost, versatility, stability, speed, etc.) and understand the need to shift into a more native Microcontroller platform like PIC, STM, Renesas, etc. The whole use the most generic IDE thing does not really matter because both of those IDEs are just eclipse anyways and most hardcore firmware jobs use IDEs that cost money.Many of us should be familiar with the popular microcontrollers and development boards like Arduino, Raspberry Pi, ESP8266, NoduMCU, 8051, etc. The much more important thing is to learn how to read the tech sheet and APIs. At the end of the day, you are gonna be forced to use what your job tells you to use (unless you are the one that gets to pick). Which ever one you like better and find easier is what you should use. In the end, the best thing to do would be to acquire a board from each and see how long it takes you to do a simple task on each (like blink and LED). ![]() It took me an hour to do the same task (without cubemx) with ST. Without using the any code generation programs, it took me about 10 minutes to figure out how to blink an LED. However, as I mentioned, the API Freescale was much more accessible. In therms of silicon bugs, not sure I agree with that, but I have only used these micros for 5 years, so I am still kind of immature with them. With Freescale/NXP, I really had to go digging to find someone. Also, when it comes to me having to outsource work, it seems that more people come forward when it is the ST platform. The other added bonus is the cheap JTAG that you can buy from ST. The cubemx software is not bad (last I tried, the Freescale version that was integrated in the IDE did not work well, but this was 3 years ago). In fact, all the nucleo boards of the same line are the same exact board, just with the chip replaced and maybe one or two resistors. They even tell you in their manuals how to design your board with upgrading or downgrading across chip lines. Different lines of different chips have the same or similar pin outs. Yes, I like the NXP/Freescale libraries better, but ST has kind of made everything generic, even down to the hardware. Because of that, I have to give the edge to ST for beginners. One thing that ST is doing now is developing there own eco system instead of just relying on MBED, which is sort facing an identity crisis at the moment. However, ST bought Atollic and now this is not an issue (previously, you could get Atollic, but you had no debugger). The IDE from Freescale was bug not free, but it still was better than what ST had to offer. Freescale had them beat in that regard (and not too mention that the API was much better than ST's). The one thing that ST was lacking years a go was a nice free non stripped down IDE. Both ST and NXP/Freescale are pretty good to start with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |