The strict software team likes Linux and command line, the EE side likes the Attolic or Workbench. Where I work, we have used cubeMX as our starter, and then you do whatever you'd like. Gone are the days of having to pay for a toolchain.
Even CubeMX is pleading a case to all the haters. I am not sure why anyone would use anything other than Attolic or Workbench for STM32 stuff when starting out. For example, a command like: :~$ platformio lib search max7219 spits out a list of 13 different libraries. It also has a search engine for browsing and installing thousands of software libraries and this makes it fast to find and try out support code for a lot of supported chips. It can grab complete tool chains from the 'net and install them on your PC. You can configure projects from Arduino, to Mbed, CMSIS, and a bunch of other frameworks, and it makes the setup of an unfamiliar uC architecture pretty trivial. Platformio does have an enourmous amount of options. I was still content with Qt Creator, so I only fiddled a bit with the command line scripts of Platformio. A year or so ago they used Atom as IDE, and that seems to be a quite capable IDE, but it seems they have switched to another lately. In it's basic form it is a collection of python scripts based around scons, but you can also install it with a full IDE. I have been using Qt Creator with a makefile as IDE for my AVR uC projects for some time as it seems to have the right balance between funcionality and complexity for me. I think CubeMx can spit out makefiles for projects, and then you're free to use any IDE you happen to fancy. Choosing an IDE can be a pretty personal choice if you're picky.
0 kommentar(er)
