• 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 » Code Composer Studio » Code Composer Forum » CCSv5.1 DM6437
Share
Code Composer Studio
  • Forum
  • Announcements
Options
  • Subscribe via RSS
Common Questions
  • Code Composer Studio Forum Usage Guidelines

  • Resources
  • Code Composer Studio (CCStudio) Product Folder
  • Troubleshooting CCS
  • CCS Wiki
  • Download CCS
  • Order CCS
  • Tools Insider Blog
  • Bug Tracking
  • CCSv5.1 DM6437

    CCSv5.1 DM6437

    This question is answered
    Junqing Zhao
    Posted by Junqing Zhao
    on Apr 12 2012 01:56 AM
    Intellectual735 points
     Hey everybody
           I try to convert my old DM6437 projects (done with CCSV3.3, bios support) to CCSV5.1.I  have add all relevant library,but still  some unresolved symbol erros:
    As follows: 
     

    Regards,

    JunQing  Zhao

    ,
    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 Apr 12 2012 13:14 PM
      Guru68915 points

      Junqing Zhao
       I try to convert my old DM6437 projects (done with CCSV3.3, bios support) to CCSV5.1.I  have add all relevant library

      Did you import the CCS 3..3 project into 5.1 using the import wizard, or did you recreate a new project in CCS 5.1? Typically the DVSDK projects designed for CCS 3.3 require some work after importing into CCS 5.1 to get it to build. In some cases it might be easier to create a new project in CCS 5.1 rather than try an import.

      The linker errors you are seeing are because the BIOS libraries are missing. Check your project view in CCS and see if the .tcf file is being excluded from the build. If it is, go to its Properties and uncheck the setting which "excludes it from build". I have seen this happen with other DVSDK projects that I have tried importing (for a different device though). If the .tcf is not built, it will not generate the linker command file which in turn will link in the BIOS libraries. You may give this a try, or try creating the project from scratch.


      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.
    • Junqing Zhao
      Posted by Junqing Zhao
      on Apr 12 2012 23:51 PM
      Intellectual735 points

      Thx,Sir.

              I have used the import wizard. Some projects can be successfully converted,while others have a lot errors. One big problem is that head file (.h) and library file(.lib). Some of these files have many versions,which are located in CCSV5  is the new ,that is different with what I have used. Which I can use correctly?

            In CCSV5.1,the CGTOOLS version is 7.3 and the BIOS is 5.4.31 as default.which is different with what I used in CCS3.3.  Then how can I solve this to migrate the projection successfully?

      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 Apr 13 2012 09:42 AM
      Verified Answer
      Verified by AartiG
      Guru68915 points

      Depending on how the original project was created and its complexity, the import wizard may or may not be able to "convert" it to CCSv5 in a clean manner, which is why some additional work would be needed to get the project working after import.

      Junqing Zhao
      One big problem is that head file (.h) and library file(.lib). Some of these files have many versions,which are located in CCSV5  is the new ,that is different with what I have used. Which I can use correctly?

      In general, using the latest versions should be ok, but this may really be dependent on the project. You can try setting it to use your older version and see if that works better.

      Junqing Zhao
      In CCSV5.1,the CGTOOLS version is 7.3 and the BIOS is 5.4.31 as default.which is different with what I used in CCS3.3.  Then how can I solve this to migrate the projection successfully?

      You can set CCSv5 to use a different version of CGT and BIOS than the default. This page tells you how to do it.
      For CGT you should be fine using the older version that you used with CCS 3.3. For BIOS, although you can still use BIOS 5.3.x it is advisable and recommended to use 5.4.x and higher with CCSv5 to avail of the BIOS debug tooling. http://processors.wiki.ti.com/index.php/DSP/BIOS_Support_in_CCSv4


      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.
    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