Do you think the next release of the pro version will be free?
The other big question is what will happen to TrueStudio's support for other platforms. I can't see ST putting any more effort into that, which would be a shame.
The other big question is what will happen to TrueStudio's support for other platforms. I can't see ST putting any more effort into that, which would be a shame.
Yes, that's what usually happens afterwards. Support for other platform will be gone for good.
One example: There's a company named Yogitech, making functional safety support libraries for a variety of platforms (thrown in all well known uC vendors here), including STM32. Yogitech was acquired by Intel, just after Intel acquired Altera (which was one of the platforms Yogitech supported). Guess what happened to all platforms but Altera?
Yep, they weren't allowed to support them anymore ... For a giant like Intel, that's a simple way to hinder competitors, as they'll all have to find new ways to support functional safety for their products.
I guess STM was in the need to provide a decent free IDE / debug platform now, since most of their competitors have such stuff (some better, some worse). The Cube SW alone isn't enough, and the
http://www.openstm32.org/HomePage IDE - nice try, but below usual standards.
The other big question is what will happen to TrueStudio's support for other platforms. I can't see ST putting any more effort into that, which would be a shame.
They won't, same for other vendors also...
Honestly ? Just give me a gcc toolchain I can drive from code::blocks, makefiles or whatever other system I want
Just give me a gcc toolchain I can drive from code::blocks, makefiles or whatever other system I want
That's my usual way, too. In the past I spent some effort to make the CubeMX output usable with my Makefiles ... breaks every time they update CubeMX.
I recently designed a project using a couple STM32's and used Eclipse and the free GNU MCU plugins from
https://gnu-mcu-eclipse.github.io/. The setup took a long time but after getting it figured out it worked well, although that's the only dev environment I've used for the STM32 so I can't compare it to other solutions.
this totally sucks...
I've been using atollic on and off (and pretty consistently since it came out with the free lite version) for years. I'm currently using atollic with STM32 on one project but the whole point of using atollic is it just works for LOTS of processors.
Now ST have come along with their moneybag and ruined things for everyone else using atollic for any other processor manufacturer.
funnily enough, the details just showed up in my atollic truestudio IDE while I was using it...
http://blog.atollic.com/early-holiday-gift-from-stmicroelectronicsAs far as I'm concerned this is a reason to NOT use STM32 in future projects.
also, given ST micro's crappy track record of supporting their hardware with developer tools, I'll be surprised if they keep all of atollic's developers in work. So on top of becoming a locked down crippleware version of its former self, it's also going to become abandonware and rot away soon enough, till it's as garbage as cubeMX and sw4stm32.
So even STM32 developers are going to be losing a well maintained and tuned professional eclipse/gcc solution in the not so distant future...
PS, they have said that all support for other processors is being dropped for their next release... Maybe a good idea to save a copy of the 8.10 installer for future use if you have any existing non-STM32 projects you need to support in future!
Anyway, looks like I'm moving my general arm cortex m development back out of windows, and back to a linux VM...
Or maybe I'll see what that hacky little plugin for VS is like nowdays.... It's been a year, maybe that's improved to the point of being properly useful now.
PS, all support for other processors is being dropped for their next release...
I was wondering if that would happen.
The cynical might say that STM don't need to acquire an IDE and this is simply a cheap way for STM to eliminate quality tools used for competitor MCUs.
US companies are sitting on big piles of cash, after they have finished snapping up the big fish, I guess they are turning their attention to the small fry, Eagle, FreeRTOS, Atollic. On the hand, I suspect a business plan for some small companies is to create products that fill a niche for particular vendors, and hope to be bought out.
Non-US companies may also be sitting on big piles of cash. Use your brain, FFS.
Honestly ? Just give me a gcc toolchain I can drive from code::blocks, makefiles or whatever other system I want
That's what I would ultimately suggest as well.
Learn how to do without IDEs.
make and
gcc are not going to be abandoned any time soon. As long as your target is supported by gcc, you'll probably be fine for maybe decades.
A lot of IDEs actually use a gcc toolchain and makefiles behind the scenes. You can take a look at the generated makefiles to get you started rolling your own.
ARM GNU toolchains can be found here:
https://developer.arm.com/open-source/gnu-toolchain
I agree the "learn without IDE" approach...
Also you can have a look at
http://platformio.org/ which is a great development environment for embedded and microcontrollers based applications. Based on solid CLI tools, it also provide some IDE-like stuff based on atom or vscode.
David
Envoyé de mon GT-N7105 en utilisant Tapatalk
sorry, but it's not the 70s anymore.
a proper IDE allows you to easily refactor code, dig into structure, chase down objects through the codebase, it allows you to interact with the debugger, and with the advanced features of atollic, to profile execution, to debug your application in awareness of freeRTOS, to communicate with the running application via a terminal over segger RTT, and it allows you to do all of this via a single consistent interface..... All of this doesn't need to be configured manually for every single person in the project who needs to work on it, they just install a single exe file and from there it all just works.
Sure you can replace all this with a bunch of separate things.... and manual configuration of toolchains is possible (yes i can do it) but for a single engineer it's a waste of time, and when you add in a team it becomes worse - you end up with a whole bunch of steps where someone can stuff up and get a non-compliant toolchain. so with a team that means you also need to check everything, not just at setup time to make sure everyone is using all the right things, but regularly in case someone updates something for some reason or some system level config (like say $PATH) just got stomped by something unrelated...... You also have to train everyone on the way each individual tool needs to work, and how to make them work together and then constantly be debugging and verifying everyone's setup... what a waste of time that could just be spent developing a solution!
Given that Atollic is mostly a nicely-wrapped Eclipse+embedded tools package (at least the free version is, the pro version has some pretty extensive debugging and profiling tools), it seems like a good opportunity for an open source project to go after the same niche. There are numerous projects around embedded toolchains, but I don't think I've seen any take that extra step of going "here's a ready-made installer for Windows, one for Mac, and [whatever makes sense for Linux]". That's a big deal when trying to get takeup among people who don't care to muck around with toolchains and just want to start building their projects. I was just looking at one where the Windows setup instruction start with "install make. . ."-- nope, you've already lost right there. It's two thousand fucking seventeen, nobody wants to build your software from source just to see if it sucks or not.
That is great news, but I see a huge overlap with systemworkbench. Also, it would be nice if their example code was more useful.
sorry, but it's not the 70s anymore.
a proper IDE allows you to easily refactor code, dig into structure, chase down objects through the codebase, it allows you to interact with the debugger, and with the advanced features of atollic, to profile execution, to debug your application in awareness of freeRTOS, to communicate with the running application via a terminal over segger RTT, and it allows you to do all of this via a single consistent interface..... All of this doesn't need to be configured manually for every single person in the project who needs to work on it, they just install a single exe file and from there it all just works.
Sure you can replace all this with a bunch of separate things.... and manual configuration of toolchains is possible (yes i can do it) but for a single engineer it's a waste of time, and when you add in a team it becomes worse - you end up with a whole bunch of steps where someone can stuff up and get a non-compliant toolchain. so with a team that means you also need to check everything, not just at setup time to make sure everyone is using all the right things, but regularly in case someone updates something for some reason or some system level config (like say $PATH) just got stomped by something unrelated...... You also have to train everyone on the way each individual tool needs to work, and how to make them work together and then constantly be debugging and verifying everyone's setup... what a waste of time that could just be spent developing a solution!
I have been on both sides of the fence. I started with ARM and windows and a developed tool chain, then I went to a company that was Linux and everything was in the command line. At the end of the day, it is about what your company is wiling to support (and the pride that the software people have). For me, the best option is what would appease everyone. Just because you use an IDE does not mean you cannot do it without an IDE, also. That is how it eventually went at my last company. You had to make minor changes, but we were able to make everything work whether you use an IDE or if you preferred the command line and some notepad editor.
I agree the "learn without IDE" approach...
Also you can have a look at http://platformio.org/ which is a great development environment for embedded and microcontrollers based applications. Based on solid CLI tools, it also provide some IDE-like stuff based on atom or vscode.
David
Envoyé de mon GT-N7105 en utilisant Tapatalk
I was sold until i realized you have to pay for the debugger.
