- This topic has 3 replies, 3 voices, and was last updated 8 years ago by
.
-
Posts
-
Hi,
I’m using the ‘ac6 system workbench’ from openstm and it seems to be pretty much identical to the tool chain setup described in the book.I wanted to ask if there are any differences between the two, and what advantages are provided by making my own tool chain as in the book?
If no differences are there, then do kindly add this as a topic in the book, mentioning this open-source and free toolchain.
Hi,
I’m not familiar with the SW4STM32 (aka AC6) toolchain, due to the fact that the support to MacOS was introduced recently. Moreover, it supports only latest MacOS releases, while I’m an happy owner of several Macs with the 10.9 release (aka Mavericks).Looking to its features, it seems that it still has less features compared to the GNU ARM Eclipse plug-ins suite. For example, it doesn’t support the SEGGER J-LINK debugger (unless we don’t use the OpenOCD support to this debugger, but it’s really slow compared to the original SEGGER GDB server). SEGGER has recently released a replacement firmware for the ST-LINK debugger, which allows to use its debugging suite with all development board from ST. KEIL Packs seems to be another missed feature in SW4STM32, and it’s really useful especially during the debug.
On the contrary, SW4STM32 directly supports the import of CubeMX projects, which is an interesting feature (even if my CubeMXImporter plug-in allows to import a CubeMX project easily).
I don’t exclude the possibility to switch to the SW4STM32 tool-chain before I finish the book. But I want to wait for the future evolutions of this toolchain. We have seen other “promising” toolchains in the past for the STM32 platform (for example, the Coocox) that have become abandoned or have become no longer free. The GNU ARM Eclipse plug-in from Liviu is a mature and well-supported project. Finally, the AC6 is just another Eclipse/GCC based toolchain. So I think that the majority of instructions contained in my book are perfectly adaptable to other similar tool-chains.
Carmine,
I purchased your book since the beginning.
But I still find AC6 a better solution due to the integration with cubemx. Did you tried it now?
What is your opinion?Hi,
AC6 is constantly evolving, but I think that the current release still lacks of several features already implemented in the GNU ARM Eclipse toolchain, especially regarding debug. Moreover, the author of the GNU ARM Eclipse toolchain is currently working on a CubeMX integration. So I think that I’ll keep the GNU ARM Eclipse in my book. Maybe, I’ll evaluate AC6 for a next release of the book (if any).
- You must be logged in to reply to this topic.