将工程从CWE和CCW移植到S32DS说明

1 Introduction

This application note aims to teach the reader how to migrate

projects from CodeWarrior v10.6 (CW Eclipse or CWE) and

CodeWarrior for MPC55xx, MPC56xx 2.10 (Classic CW or

CCW) embedded software development tools to S32 Design

Studio (S32DS). There are code examples included in this

application note which support KEAZ128 for the ARM

®

portion and MPC5604B and MPC5644C for the Power

integrates various open-source software components, such as

the GNU Compiler Collection (GCC) and GNU Debugger

(GDB), as well as NXP proprietary device initialization tools.

The latter provides a layer of abstraction so that a user needs

only call device registers by name, rather than having to

specify their memory locations as well. NXP’s goal with this

tool is to provide customers with an easy-to-use IDE that gives

the look and feel of CWE at no cost and provides customers

with faster development cycle time than previously available.

NXP Semiconductors

by: David Chung

1 Introduction.............................. .............................. 1

2 How to Migrate an ARM project from

CodeWarrior to S32DS...........................................3

3 CodeWarrior Eclipse and S32DS

Comparison for Power Architecture........................6

4 Project Migration from CodeWarrior

Eclipse for Power Architecture................ .............26

10 Revision History................................................... 58

1.2 Why migrate?

There are no plans to discontinue CodeWarrior in the near-future, but software enablement for future automotive and ultra-

reliable industrial releases from NXP will be supported through S32DS. CodeWarrior support for existing products will

remain available. Products released in between tool transition, including the Kinetis EA (KEA), MPC57xx series, and

MPC56xx, will be supported by both CodeWarrior and S32DS. However, migrating code to S32DS where available will

allow for maximum software reusability for future NXP products. The table below summarizes tool support for selected

product lines.

S32DS features a CodeWarrior project importer for KEA MCUs that allows a user to migrate a CodeWarrior KEA MCU

project to S32DS with a click of a button, because CodeWarrior projects for KEA MCUs and S32DS both use the GCC

Compiler. Power Architecture Processor projects are not so lucky: CodeWarrior project for Power Architecture products use

a propriety NXP compiler. CWE and S32DS may share the same Eclipse tools framework, but differences such as compiler

and project structure schemes prohibit a straight one-to-one migration of CodeWarrior Power Architecture projects to S32DS.

An owner of a CodeWarrior Power Architecture project that wishes to migrate to S32DS will have to start a new project. This

application note seeks to help the user streamline the migration process, covering the items that must be migrated over, what

needs to stay, and what has to be modified in order for the new S32DS project to work the same as its CodeWarrior

There are separate versions of S32DS for ARM and Power Architecture. The ARM tool is called S32 Design Studio for

ARM.

KEA is the only ARM device that is supported by both CodeWarrior and S32DS. Importing a KEA project from CWE to

S32DS requires the CodeWarrior project importer. Go to File>Import as shown in the following figure.

Figure 1. S32DS import option

The CodeWarrior project importer option is located within the S32DS Design Studio folder. Expand it, as shown in the figure

below.

Select CW Project Importer and click Next. Configure the importer options to your liking and browse for your CWE project.

You can also give your imported project a new name. If you choose not to, the wizard will give your imported project the

configures it for S32DS, and stores it in your S32DS workspace directory. Since CWE ARM projects use the GCC compiler

just like S32DS, migration is straightforward enough, compared to Power Architecture, for the process to be automated. The

project importer adjusts the sysroot, which specifies the path to compiler libraries, to link to the S32DS libraries. The

importer then modifies the toolchain selection in the debug configurations of the CWE project. If you simply import a CWE

project using the Existing Projects into Workspace option, these steps would not be performed and the project would be

unable to compile in S32DS.