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.

Link Problems , with .s and asm files

Hi,
 
Dear team, I am getting the an error. I am unable to resolve/ understand the message '
Deprecated use of PSR; flag bits not specified, "cf" assumed'




Also, I have a project, say TILinkAll, which has many othere projects dependencies, say P1,P2.. I am able to build each iof these P1, P2 successfully. Howver when I try to build through TILinkALL, some donot build. On building a .s file, I got the below error. Please help me resolve this also:

'
has a Tag_ABI attribute value of "2" that is different than one previously seen ("1"); combining incompatible files
I am unable to understand 'Tag_ABI attribute value'
Please help me. Is this a linker problem?

Regards,
Aadishri
  • Aadishri G S said:
    Deprecated use of PSR; flag bits not specified, "cf" assumed'



    I would suggest taking a look at the ARM Architecture Reference Manual for the correct syntax of the instruction this error is reported for. This The Reference manuals should be accesible from ARM's web site. This post might also be of help.

    Aadishri G S said:
    has a Tag_ABI attribute value of "2" that is different than one previously seen ("1"); combining incompatible files



    This means that you are trying to link together object files or libraries with different ABIs. Each ABI has a tag (1 for TI ARM7 ABI, 2 for TI ARM9 ABI and 3 for EABI). So it seems that one or more of your object files has been built for ARM7 ABI while others have been built for ARM9 ABI. You need to ensure that they are all built for the same ABI. Please see the TMS470 Compiler Users Guide, section 5.11 and 2.13 for explanations of the ABIs and how to link together files built for TIABI and TI ARM9 ABI.

  • Dear AartiG,

    I was able to resolve that error

    AartiG said:
    This means that you are trying to link together object files or libraries with different ABIs

    Below are my linker and compiler options in ccs3.3 but there were no such issues there. Is the ccsv5 stricter or am I missing out something?

    Regards,

    Aadishri

  • Aadishri G S said:

    Below are my linker and compiler options in ccs3.3 but there were no such issues there. Is the ccsv5 stricter or am I missing out something?

    You are using the --abi=tiabi option with CCS 3.3. Check the build options in your CCSv5 project and see if they are the same. My guess is that it is set to --abi=ti_arm9_abi.

    More related info is in my reply in your other thread.