• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 3061 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

migration from CCS V3.3 to V4.0

steven149
Prodigy 135 points

I am just noticing the difference in migrating projects from V3.3 to V4. Please correct my understanding if I am wrong.

There are two procedures migrating from V3.3 to V4, depending on what the legacy applications are about:

1. If the legacy project is simply a .prj without, I can just follow this link with some manual tweaks:

http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4#Example

ideally it should work.

2. If the legacy project includes DSP/BIOS5 on V3.3, (of course V4 can also use DSP/BIOS5 but we're talking about migration here), then I have to use the procedure specified in App note "Migrating a DSP/BIOS 5 Application to DSP/BIOS 6" (it is in document coming with CCSv4 installation). This procedure is much more complex, at least on paper.

I also want to make sure if there is a "combined" migration procedure so that I don't need to differentiate the legacy application before I start.

Thanks.

  • 0
    TI__Mastermind 18130 points

    steven149 said:
    1. If the legacy project is simply a .prj without, I can just follow this link with some manual tweaks: http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4#Example ideally it should work.

    Agreed. Porting a simple project should be very straightforward. You may need to tweak some include paths and the like, but from my experience you should not run into any significant hurdles.

    steven149 said:
    2. If the legacy project includes DSP/BIOS5 on V3.3, (of course V4 can also use DSP/BIOS5 but we're talking about migration here), then I have to use the procedure specified in App note "Migrating a DSP/BIOS 5 Application to DSP/BIOS 6" (it is in document coming with CCSv4 installation). This procedure is much more complex, at least on paper.

    I also want to make sure if there is a "combined" migration procedure so that I don't need to differentiate the legacy application before I start.
    I have not seen any combined migration documents, but then again you need to complete step 1 before you can really convert from BIOS5 to BIOS6.

  • 0
    TI__Guru*** 125430 points

    steven149 said:
    2. If the legacy project includes DSP/BIOS5 on V3.3, (of course V4 can also use DSP/BIOS5 but we're talking about migration here), then I have to use the procedure specified in App note "Migrating a DSP/BIOS 5 Application to DSP/BIOS 6" (it is in document coming with CCSv4 installation). This procedure is much more complex, at least on paper.

    I recommend taking these steps one at a time.  These are 2 independent steps so doing them altogether will make it more difficult to determine what has gone wrong when you have an issue.  Stick to BIOS 5 for now....  Once you have migrated to CCS 4 then I recommend looking at BIOS 6 and deciding whether you want to move at all.  Personally I would just stick with BIOS 5.