• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 953 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.

CCS: RTSC-project from CCSv6 to CCSv7

Dmit Rach
Intellectual 420 points

Tool/software: Code Composer Studio

Hi everyone,

The problem is as follows:

Worked on ccsv6.2, decided to upgrade to ccsv7.4.

Open project (created on ccsv6.2 as other ...->Empty RTSC-Configuration Project) on ccsv7. After that it does not open on v6.

Composer v6 writes:

"An error has occurred. See error log for more details.
assertion failed: "

on my actions on project files

The processor for creating is TCI6614.

  • 0
    TI__Guru**** 173310 points

    There was one bug that we fixed for CCS 7.1 (see this link), but that was an "assertion failed" message when importing a RTSC static library project into CCSv7 not CCSv6. 

    Could you provide some additional details so I can try to reproduce this?

    - Was the RTSC library project first created with CCS 6.2, then imported into CCS 7.4? 
    - Did you open the 6.2 created workspace in CCS 7.4, or did you create a new workspace with 7.4 and import the project into it?
    - When you tried opening it again with 6.2, did you simply open the previous workspace or import it into a new workspace?

  • 0 in reply to AartiG
    Intellectual 420 points
    Hi AartiG,

    - Was the RTSC library project first created with CCS 6.2, then imported into CCS 7.4?
    Yes, it was first created with CCS 6.2, then imported into CCS 7.4.
    - Did you open the 6.2 created workspace in CCS 7.4, or did you create a new workspace with 7.4 and import the project into it?
    No, I create a new workspace with 7.4 and import the project into it.
    - When you tried opening it again with 6.2, did you simply open the previous workspace or import it into a new workspace?
    No, I open previous workspace.
  • 0 in reply to Dmit Rach
    TI__Guru**** 173310 points
    Hi Dmit,

    I have not been able to reproduce this so far. Would you be able to share a project that demonstrates the issue? Ideally a CCS 6.2 created library project that is still good (prior to whatever conditions may be triggering the "assertion failed" message) so I can go through the above steps to reproduce the error.
  • 0 in reply to AartiG
    Intellectual 420 points

    Hi Aartig,

    can you try this one?

    Bios 6.42.3.35

    XDC 3.32.2.25_core

    IPC 3.42.0.02

    TestPlatform_6.2.tar.gz

  • 0 in reply to Dmit Rach
    TI__Guru**** 173310 points

    Thank you for bringing this issue to our attention. I was able to reproduce the issue and have filed bug # CCSIDE-3269 to track this issue. Feel free to track it using the SDOWP link in my signature.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    Dmit,

    The CCS engineers looked at this issue and clarified that this is not a supported configuration. When a project created with an older version of CCS is imported into a newer CCS, it usually needs to be migrated, and that may render it unusable again in older CCS versions. Instead, a good way to test out older projects in newer CCS is to copy it into the CCSv7 workspace (enable the "copy to workspace" option during import) so as to keep two different copies of the project.
  • 0 in reply to AartiG
    Intellectual 420 points

    AartiG,

    Ok. Thanks.