• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 522 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

EABI greyed out CCSv4 for C6000

Kaan Dogan
Prodigy 140 points
Other Parts Discussed in Thread: CCSTUDIO

Hi
I am using  OMAP L137 evm boards with  CCS v 4.1.2.00027 and code generation tools 7.0.1 . I need to obtain EABI formatted output file, but the project settings for output format type is greyed out. I remember  to change it to EABI two months ago, with different ccs version and same cgt. In my project settings, the processor type is I need to know what causes this bug / problem .I believe if I can find  which eclipse plugin file is responsible for greying out that field, the cgt will generate EABI.


Thanks :).

  • 0
    TI__Guru**** 162325 points

    Kaan,

    In the latest releases of 4.1.x we have disabled by default the ability to select EABI on C6000.  The reason for this is that the move to EABI is a big one.  All of your software has to be EABI (ELF) and most people are not ready for that and longs are no longer 40bits.  There is more information here: http://processors.wiki.ti.com/index.php/EABI_Support_in_C6000_Compiler

    If you are aware of these concerns and still want to use EABI what you can do is manually add the build option.  Right click on your project, select build options, click on the C6000 Compiler node in the tree, in the command line pattern box you can insert extra build options, the same is true if you click on C6000 Linker.  Insert the extra option after the ${flags} macro.

    Regards,

    John

     

  • 0 in reply to JohnS
    Prodigy 140 points

    Thanks John.

    Honestly, I prefer you should let the users make the decision, rather then disabling that setting altogether and contradicting with the web page. Elf support is one of the reasons that we work with this processor. 

    After your post , I twiddled with the setting, and it should be added before the ${flags}  macro. (" ${command} --abi=eabi ${flags}${inputs} " for compiler and "${command} --abi=eabi ${flags} ${output_flag} ${output} ${inputs}" for linker).

    If you disabled it from an eclipse jar file, can you tell which one is that? If not, then I'll stick with manual manipulation, which I do not like. 

    Thanks again.

  • 0 in reply to Kaan Dogan
    TI__Guru**** 162325 points

    Kaan,

    The option would have been disabled in com.ti.ccstudio.buildDefinitions.C6000_7.0_xxxxxxxxxxxx  where xxxxxxxxxxxxxx is the version # of the plug-in.  If the option was exposed and then disappeared then there should be multiple versions of that plug-in in your \eclipse\plugins folder

     

    John