• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 676 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.

Support Keystone I with CCS 6.1 and MCSDK 3

Yoyo Lee
Intellectual 695 points

We are transferring from Keystone I to Keystone II.   We use CCS 6.1 and MCSDK 3 to support Keystone II.  During the past, maintain two version of CCS on one computer has given us problem.  We also know we should not have two version of MCSDK inside one CCS.  Our idea is that using Keystone II with MCSDK 3 to support both old Keystone I code and new Keystone II code. Could this goal reachable?  

  • 0
    TI__Guru**** 171639 points

    Hi,

    If I understood your question correctly:

    - As mentioned in their pages, MCSDK releases 3.x do not support Keystone I devices (check here for 3.0 and here for 3.1). You will need to have two MCSDKs installed (2.x for Keystone I and 3.x for Keystone II)

    - I haven't had a problem having two MCSDKs installed in my system and recognized by the same CCS version. In order to do this I simply installed them in different parent directories (C:\ti\MCSDK_02_01_02_06, C>\ti\MCSDK_03_01_04_07) and add each MCSDK subdirectory using the procedure shown in section 4.11 of this wiki page.

    - Similarly, I haven't had problems in maintaining two CCS versions in my PC - I have at least five versions installed side-by-side all the time. The trick to achieve this is to install CCS in different directories (C:\CCSv5_5_0, C:\CCSv6_0_1, C:\CCS_v6_1_2, etc.) and use different workspaces for each.

    Hope this helps,

    Rafael