MW Build Tools

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MW Build Tools

1,389 Views
patrickfoley
Contributor I

Hi, I am using a Kinetis S9KEAZN64.  Using the mw build tools (mwasmarm.exe, mwccarm.exe, mwldarm.exe) I am getting a linker script error.  The error comes back as "expecting: identifier" line 63.  I am following AN4498 and chapter 13 of the CodeWarrior Development Studio for Microcontroller V10.x Kinetis Freescale Build Tools Reference Manual, Rev 10.6, 02/2014 for reference.  Any help with the script would be appreciated.

 

 

attached is my LCF

Original Attachment has been moved to: 8093_Rev_AA_1.lcf.zip

Labels (1)
0 Kudos
4 Replies

1,050 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hello Patrick:

Those tools are the Freescale build tools for Kinetis, but that compiler does not support Cortex M0+ processor, as in KEA series. The correct tools are GCC compiler/linker.

Is this a project you created with CodeWarrior? or can you provide more details on what you are trying to achieve?

Regards!

Jorge Gonzalez

0 Kudos

1,050 Views
patrickfoley
Contributor I

Hello Jorge,

I am wondering if there are any environment variables that need to be set

when using the gcc compiler. While using the mw toolset I had set

variables such as MWCIncludes and MWLibraries, are these paths used by

GCC?

Thank You,

Patrick Foley

Software Engineer

Magna Mirrors

Kraft Engineering Center

5085 Kraft Avenue, S.E.

Kentwood, MI 49512

Phone: (616) 786-7104

Fax: (616) 656-8594

Patrick.Foley@magnamirrors.com

0 Kudos

1,050 Views
Jorge_Gonzalez
NXP Employee
NXP Employee

Hi Patrick:

- I think the executables with/without "arm-none-eabi" are basically the same, but from your makefile you should call the "arm-none-eabi..." ones with the corresponding options. A brief explanation about this here.

- MWCIncludes and MWLibraries are for Freescale Kinetis build tools. For GCC tools in case you want to use CodeWarrior EWL libraries you can specify include paths in the makefile, and use such paths as options when invoking GCC compiler/linker.

- AN4498 covers the Linker Command File format for Freescale compiler. For GCC linker you should not read this. The counterpart document for GCC tools is in the next path here in the community:

Relocating Code and Data Using the CW GCC Linker File for Kinetis

I hope this helps.

Regards!

Jorge Gonzalez

0 Kudos

1,050 Views
patrickfoley
Contributor I

I am trying to implement a build platform utilizing a makefile that will

be tied to our 3rd party ide that we use (CodeWright). So am I to call

arm-none-eabi-gcc.exe with the compile/link options or should I call

gcc.exe/ld.exe/objcopy.exe directly? Is there a difference?

Thank You,

Patrick Foley

Software Engineer

Magna Mirrors

Kraft Engineering Center

5085 Kraft Avenue, S.E.

Kentwood, MI 49512

Phone: (616) 786-7104

Fax: (616) 656-8594

Patrick.Foley@magnamirrors.com

0 Kudos