• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Development Tools » TI C/C++ Compiler » TI C/C++ Compiler - Forum » Asm errors after migrating from ccs3.3 to ccs5.1
Share
TI C/C++ Compiler
  • Forum
Options
  • Subscribe via RSS

Forums

Asm errors after migrating from ccs3.3 to ccs5.1

This question is answered
Aadishri G S
Posted by Aadishri G S
on Jan 20 2012 06:03 AM
Intellectual505 points
Hi,
I have migrated my project from ccs3.3 to ccs5.1. I am particularly unable to build some asm files. Below is one such error. 
I*********************************************************************************

"D:/ROM/source/fpu/FS_MUL.asm", ERROR! at line 50:
[E0002]
Instruction is only available in V5 and higher
CDP p5,#F_MUL,ResultReg0,SP_OP2,SP_OP1 ; Perform the Single Precision Multiplication
*********************************************************************************
I went through the instruction set in Reference manuals(thumb instruction set) which says 
*********************************************************************************
Assembler syntax
CDP{2}<c><q> <coproc>, #<opc1>, <CRd>, <CRn>, <CRm> {,#<opc2>}
where:
2 If specified, selects the C == 1 form of the encoding. If omitted, selects the C == 0 form.
<c><q> See Standard assembler syntax fields on page 4-6.
<coproc> Specifies the name of the coprocessor, and causes the corresponding coprocessor number to
be placed in the cp_num field of the instruction. The standard generic coprocessor names
are p0, p1, ..., p15.
<opc1> Is a coprocessor-specific opcode, in the range 0 to 15.
<CRd> Specifies the destination coprocessor register for the instruction.
<CRn> Specifies the coprocessor register that contains the first operand.
<CRm> Specifies the coprocessor register that contains the second operand.
<opc2> Is a coprocessor-specific opcode in the range 0 to 7. If it is omitted, <opc2> is assumed to
be 0.
*********************************************************************************
The usage does not seem to violate this.

I would like to know how to resolve this issue and what is meant by V5 in the message
 'Instruction is only available in V5 and higher'
Also, has the ARM syntax changed from ccs3.3 to ccs5.1 in some cases?
 Is there no compatibility module which can compile the ccs3.3 code itself in ccs5.1.

Regards,
Aadishri
assembler
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • AartiG
    Posted by AartiG
    on Jan 20 2012 10:28 AM
    Guru69005 points

    Aadishri G S
     'Instruction is only available in V5 and higher'



    This message is saying that the instruction syntax is supported only in ARM v5 architecture and higher. Please take a look at slide 3 of this presentation for  correlating architecture versions with processors.

    Over time, the ARM codegen tools have evolved to add support for the different ABIs and ARM architectures, Starting with codegen tools 4.1.x the default ABI also changed from the older TIABI to TI ARM9 ABI. If you have the latest version of CCS 3.3, you will find ARM codegen tools v4.1.4 in it. You can review the CGTNew.txt file within the C:\CCStudio_v3.3\tms470\docs folder to understand the ABI changes that came starting with that veraion. If you are migrating code from an older version of compiler tools (that came with CCS 3.3) to a newer version (that comes with CCS v5) these are some of the factors to consider.

    Which version of compiler tools did you use when building with CCS 3.3? You can check by going to the Component Manager, Build Tools and check the version of TMS470 code generation tools. To perform the migration in a more step-by-step approach you could first start off by setting CCSv5 to use the same version of compiler tools as you did with CCS 3.3. This page describes how to do that: http://processors.wiki.ti.com/index.php/Compiler_Installation_and_Selection#CCStudio_5.1 
    Verify that the project builds and works as expected. Then modify the project to use the newer version of compiler tools. You may need to set/keep some compiler options to maintain backward compatibility and/or modify code to make it compatible with the newer tools.

     


    If a post answers your question please mark it with the "Verify Answer" button

    Search the wikis for common questions: CGT, BIOS,  CCSv3, CCSv4
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Jan 25 2012 06:38 AM
    Intellectual505 points

    Dear AartiG,

    As per your suggestion, I compiled with earlier ccd 3.3 cgtools(4.1.4). The files compiled. Thank you.

    But if I change to compile with cg tools 4.9.0(Project->Properties->CCS General->Code-generation tools),

    the abi option((Project->Properties->CCS Build->TMS470 Compiler->Runtime Model Options->abi) automatically changes to ti_arm9_abi.

    Even if I change to tiabi, I get the same error,

    **********************************************************************************************************************
    Instruction is only available in V5 and higher
    CDP p5,#F_SUB,ResultReg0,SP_OP2,SP_OP1 ; Perform the Single Precision Substraction
    **********************************************************************************************************************

    I checked this presentation. Here, in slide, 'ARM Processors Overview', it says 

    ARM7  |       ARMv4T  |      -mv4 
    ARM9 | ARMv5TE | -mv5e
    
    
    I am using '-mv4' option itself.
    I am unable to understand whether I have to change some other compile option or make the change in the instruction. 
    I am skeptical about the latter as I am still using '-mv4' option and the same instruction ran with '-mv4 -tiabi ' options in cgtools 4.1.4 and it compiles.
    Please help me resolve this.
    
    
    Regards,
    Aadishri
    assembler CCSv5.1 cgtools4.9.0
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • AartiG
    Posted by AartiG
    on Jan 25 2012 11:21 AM
    Guru69005 points

    It may be that the instruction may need to be changed. Could you attach the assembly file which generates this error and the full list of compiler options you are using?


    If a post answers your question please mark it with the "Verify Answer" button

    Search the wikis for common questions: CGT, BIOS,  CCSv3, CCSv4
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Jan 27 2012 01:03 AM
    Intellectual505 points

    Hi AartiG,

    Please find the compile options I am using:

    "-mv4 -g --define="_DEBUG" --include_path="C:/ccs/ccsv5/tools/compiler/tms470/include" --include_path="/packages/ti/xdais" --diag_warning=225 -me --abi=tiabi --code_state=16 --std_lib_func_redefined --obj_directory="C:/GNSS_45nm/Private/source/product/ti/GPS_ROM/projectfiles/fpu/Build_45NM""

    I have attached one of the asm files(renamed as .txt) which throws this error. The CDP instruction is used in line 47 and 61.

    Below are the ccs 3.3 compiler options that I used:

    -g -pdsw225 -ol0 -fr"C:\GNSS_45nm\Private\source\product\ti\GPS_ROM\projectfiles\fpu\Build_45NM" -d"_DEBUG" -me -mt -mv4 --abi=tiabi

    Regards,

    Aadishri

    5516.PRI_SUB.asm.txt

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • AartiG
    Posted by AartiG
    on Jan 27 2012 09:26 AM
    Guru69005 points

    I am missing the include file pri.h hence cannot compile the file successfully. However, even with all the other assembler errors generated I don't see the "Instruction is only available in V5 and higher " error with CGT 4.9.0. If you can include the pri.h and any other files that file may include so I can get a successful compile, I can confirm if I can reproduce the error or not.


    If a post answers your question please mark it with the "Verify Answer" button

    Search the wikis for common questions: CGT, BIOS,  CCSv3, CCSv4
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Jan 31 2012 07:44 AM
    Intellectual505 points

    Dear AartiG,

    Please find the header file attached.

    Regards,

    Aadishri

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • AartiG
    Posted by AartiG
    on Jan 31 2012 09:38 AM
    Guru69005 points

    Sorry, but there was no file attached.


    If a post answers your question please mark it with the "Verify Answer" button

    Search the wikis for common questions: CGT, BIOS,  CCSv3, CCSv4
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Feb 01 2012 00:09 AM
    Intellectual505 points

    Hi AarthiG,

    Sorry too! Please find the same attached

    2627.PRI.h.txt.

    Regards,

    Aadishri

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • AartiG
    Posted by AartiG
    on Feb 01 2012 11:14 AM
    Guru69005 points

    Thanks for providing the file. I can reproduce the error you mentioned. I see that there is no error with CGT 4.1.x but starting with 4.4.0, all the later compiler versions generate the error. I will see if I can get someone else to comment on the reason for this.


    If a post answers your question please mark it with the "Verify Answer" button

    Search the wikis for common questions: CGT, BIOS,  CCSv3, CCSv4
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Feb 03 2012 07:20 AM
    Intellectual505 points

    can you please update me...

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • ThomasS
    Posted by ThomasS
    on Feb 03 2012 14:45 PM
    Expert6430 points

    The CDP and CDP2 instructions are only available for Thumb-2 devices.  I read the thread too quickly. This appears to be a bug. It looks like we took the warning for the CDP2 instruction (available for v5 and higher) and applied it to CDP.

    -----------------------------------------------------------------------------------------------------------------------------

    TI Compiler Resources: MediaWiki (detailed info, tutorials...) FAQ

    Track an issue with SDOWP enter your bug id in the "Find Record ID" box.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • ThomasS
    Posted by ThomasS
    on Feb 03 2012 15:01 PM
    Verified Answer
    Verified by JohnS
    Expert6430 points

    This issue is now in our bug tracking system as SDSCM00043069. The only workaround would be to assemble with version v5e or higher.

    -----------------------------------------------------------------------------------------------------------------------------

    TI Compiler Resources: MediaWiki (detailed info, tutorials...) FAQ

    Track an issue with SDOWP enter your bug id in the "Find Record ID" box.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Apr 16 2012 08:06 AM
    Intellectual505 points

    How can I check if the issue SDSCM00043069 is resolved?

    Regards,

    Aadishri

    bug
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Archaeologist
    Posted by Archaeologist
    on Apr 16 2012 08:25 AM
    Verified Answer
    Verified by Aadishri G S
    Mastermind40800 points

    As indicated in the signatures of both Aarti and Thomas, you can track the status of known bugs by using SDOWP

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Aadishri G S
    Posted by Aadishri G S
    on Jun 01 2012 06:25 AM
    Intellectual505 points

    Team,

    Thank you for thr resolution.

    Please let me know if I have to re-install CCSv5 or a version update will suffice to get the bug-free version.

    Regards,

    Aadishri

    CCSv5
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
12
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use