We get lots of questions from developers who are using "home-made" Eclipse / GCC development tools. They want to know if there is a simple way to migrate their legacy code into Atollic TrueSTUDIO. The answer is, 'Yes,' but there are several factors to consider.
This article highlights the major reasons to why many engineers eventually moves towards a commercial tool. It also suggest an easy migration path from an "home-made" Eclipse / GCC development tool to Atollic TrueSTUDIO.
What's the problem with homemade tools?
Before suggesting a solution to this problem it may be interesting to understand why this question arises in the first place. Why wouldn't everyone simply use homemade tools?
Here are the most common reasons why developers decide to move to TrueSTUDIO from something homemade or free:
- Technical support - who helps me out when there is a problem with my tool?
- Quality uncertainties - not everything works the way it should
- Cost-effectiveness - how much time does it take to build and configure my own tool?
- Work efficiency - is my tool simple and efficient to use?
- Target support - how do I get my tool to work with my development board?
- Feature set - does my tool have what you need to support my development efforts?
- Software upgrades, bug fixes and target support - who will maintain my tool?
Making the migration easy
Since the Atollic IDE is built on the Eclipse framework and based on ARM-GCC, it is as simple as it gets to perform this migration. This also mean that if you decide later to go back to using vanilla Eclipse/GCC or another Eclipse/GCC development tool you don't need worry about being locked in to a proprietary compiler, and your legacy code remains easy to port.
- An Eclipse-to-Eclipse IDE migration requires minimum of GUI re-training
- GNU-to-GNU command line tool migration removes need to rewrite the source code files
- No change to the assembler file syntax
- No change to the linker file syntax
- No change to the makefile syntax
- No change to the compiler #pragmas
- No change to the inline assembly syntax
- No change to the command line options (for script builds, etc.)
- No change to compiler specific behavior (such as structure packing, bitfields, etc.)
- No change to the compiler warnings
Here are the basic steps
- Create a new Atollic TrueSTUDIO wizard C Project selecting the right target MCU.
- Delete unnecessary resources (files) in the new project
- Copy resources across from your legacy project to the new project
- Modify build settings
- Build the project
- Setup a debug configuration
We have written an application note describing the above steps in more detail. You can read it here:
Feel free to post comments or questions about migrating to TrueSTUDIO.