• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 2887 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cortex-M3 - Compiler

Felipe Bortolon

Hello everyone,

I working on a Cortex-M3 and I would like to know if it is possible to change the ARM-C compiler to MentorGraphics ARM-NONE-EABI on µVision(information below)?

Thank you very much.
Best Regards,
Felipe

---------------------------------------------------------------------------
IDE-Version:
µVision V4.72.10.0
Copyright (C) 2013 ARM Ltd and ARM Germany GmbH. All rights reserved.

Tool Version Numbers:
Toolchain:        MDK-Lite  Version: 4.72.1.0
Toolchain Path:     C:\Keil\ARM\ARMCC\bin\ 
C Compiler:         Armcc.Exe        V5.03.0.76 [Evaluation]
Assembler:          Armasm.Exe       V5.03.0.76 [Evaluation]
Linker/Locator:     ArmLink.Exe      V5.03.0.76 [Evaluation]
Librarian:          ArmAr.Exe        V5.03.0.76 [Evaluation]
Hex Converter:      FromElf.Exe      V5.03.0.76 [Evaluation]
CPU DLL:            SARMCM3.DLL      V4.72.1.0
Dialog DLL:         DARMSTM.DLL      V1.64.0.0
Target DLL:         UL2CM3.DLL       V1.150.11.0
Dialog DLL:         TARMSTM.DLL      V1.64.0.0
---------------------------------------------------------------------------

Parents
  • 0 in reply to Felipe Bortolon

    Changing compiler tool chain need not be so hard.

    But changing compiler when using it from an IDE can really be quite hard. How hard depends a bit on the similarities between old and new compiler tool chain.

    You need to make all command-line invocations of the individual tools (assembler, compiler, linker, librarian) match.
    You need to make sure that you supply assembler startup files of a proper format for the assembler.
    You need to make sure that you supply the relevant paths for suitable header files and libraries.
    You need to make sure that the projects includes the use of the relevant libraries for all libraries the linker doesn't have some auto-method to include in the linking step.
    ...

Reply
  • 0 in reply to Felipe Bortolon

    Changing compiler tool chain need not be so hard.

    But changing compiler when using it from an IDE can really be quite hard. How hard depends a bit on the similarities between old and new compiler tool chain.

    You need to make all command-line invocations of the individual tools (assembler, compiler, linker, librarian) match.
    You need to make sure that you supply assembler startup files of a proper format for the assembler.
    You need to make sure that you supply the relevant paths for suitable header files and libraries.
    You need to make sure that the projects includes the use of the relevant libraries for all libraries the linker doesn't have some auto-method to include in the linking step.
    ...

Children