Source code migration

The majority of application code is usually written in a high level language (C or C++), in fact using common compiler extensions such as support for interrupt service routines in C, and it is possible to write nearly all of an application without using Assembly.

Even Assembly modules can be converted relatively simply as most cross-assemblers support similar functionality, differing only slightly in syntax (for example the way that some addressing modes are indicated, or that macros and other high level features are implemented), a simple search and replace or perhaps writing a file to map one symbol to another may suffice.

If the original source code was written using Standard C or Standard C++, it is likely that you are good to go.

Tip

When migrating sources that use non-portable code (i.e. compiler-specific extensions), a developer needs to review and migrate such code manually. Device-specific startup files are, in many cases, bundled with the IAR Embedded Workbench example projects found in the IDE's main menu: Help → Information Center → Example projects. Example projects targeting a similar device provide a compendium of starting points which you can immediately use as references for your own project.

Migrating from GCC to IAR

This section provides additional articles that might be useful for when migrating from GCC to the IAR Embedded Workbench.

• Language extensions
• Compiler internal symbols
• Interrupt handling
• Migrating from LD to IAR ILINK

Additional information

For more information, refer to the User Guides found at the IAR Support Page. If you have the product already installed on your workstation, its User Guides are found in the IDE's main menu: Help → Information Center → User guides.