

Remove redundant directivesĭelete all source lines that start with MODULE or RTMODEL as these are not required and have no equivalent in CrossWorks. We'll set aside calling conventions for the moment and focus on simply getting EW source code to compile and link under CrossStudio. The format of CrossWorks assembler source code is mostly compatible with EW, but there are differences in naming conventions and directives. Making assembly language source files assemble

After stage three, everything should work. Make changes to assembly language source files to account for calling convention changes.Īfter step two, you should have something that compiles and links but possibly does not work.Convert C source files to compile under CrossWorks.Convert assembly language source files to assemble under CrossWorks.There are three distinct steps to getting an EW project to work under CrossWorks: So we recommend that you start converting an IAR EW project rather than a CCE project and we don't consider CCE further.

In fact, TI have been making Code Composer Essentials compatible with Embedded Workbench at the source level too. I'm working on it as I help a customer through this process so might as well share with the world.ĬrossWorks is mostly compatible with IAR's Embedded Workbench at the source level. This article is work in progress and is draft form at present.
