• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 231 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.

TMS320F2812: Project Import

Michael Stach
Prodigy 10 points

Part Number: TMS320F2812

I have a new computer, have the same CCS setup (V10.4) and compiler installed, however it is not possible to import a project from the old computer to the new computer. 

Any ideas?

image.png

  • 0
    TI__Guru**** 481471 points

    Hello,

    I see several errors in there. Is the directory structure of both the CCS installation and also the project (and dependent files) set up the same in the new PC vs the old one?

    Looks like the customer updated the compiler version to v21.6. They will need to do the same with their new PC:

    https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AJRfIGmBSkp9naUDysxAFg__ccs_devtools__FUz-xrs__LATEST

    The last error is regarding J-Link update site. Is the customer using J-Link for their debug probe?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 10 points

    Both version and path of CCS, compiler, and project are the same on both PC. Also, I don't use J-Link, the project is setup with Blackhawk emulator. I am puzzled why this message pops up. 

    Even though if any path would be different, CCS should give a warning but not prevent me from importing!!

  • 0 in reply to Michael Stach
    TI__Guru**** 481471 points

    You can ignore the J-Link error since it is not applicable for you. You can resolved the compiler version issue by using the update manager to install that particular version. The other errors are odd. Please provide the Eclipse log mentioned in the below link:

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

    Also note that you are using a very old and unsupported version of CCS. Due to this, the amount of support we can provide will be limited.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 10 points

    Which log file in particular you are interested in?

    I want to create the same environment when porting the project to a new machine to verify everything is good. I had major problems previously importing project from other CCS / compiler version into a new one. 

    I am aware that it is old and I am installing the latest as I write this to test. 

    Still, I am puzzled what could be the problem here?!

  • 0 in reply to Michael Stach
    TI__Guru**** 481471 points
    Michael Stach said:
    Which log file in particular you are interested in?

    The <WORKSPACE FOLDER>/.metadata/.log file would be most useful.

    Michael Stach said:
    Still, I am puzzled what could be the problem here?!

    Other than the error about the v21.6 compiler, I'm not sure. Did you try installing that compiler version via update? 

  • 0 in reply to Ki
    Prodigy 10 points

    I think I got my issue resolved. I had installed CCS again, but that didn't fix it. it appears that I didn't pay enough attention where the compiler were installed, and I also hadn't 'registered' them with CCS (never had to do this before).

    I now can import and compile just fine. 

    I am still puzzled why CCS would prevent importing a project in this case. 

    Thanks for attending this issue.

    Mike

  • 0 in reply to Michael Stach
    TI__Guru**** 481471 points
    Michael Stach said:
    I think I got my issue resolved.

    Great!

    Michael Stach said:
    it appears that I didn't pay enough attention where the compiler were installed, and I also hadn't 'registered' them with CCS (never had to do this before).

    If the compiler is installed by Resource Explorer or via the CCS Update Manager, then CCS *should* automatically discover it. If it is installed manually outside CCS, then CCS would need to "discover" it first.

    Michael Stach said:
    I am still puzzled why CCS would prevent importing a project in this case. 

    Some projects have a hard dependency on a specific compiler version and not having it can block the import. Older versions of CCS (like 10.x) were also more strict about enforcing this. This behavior was made more lenient in later version where it could import with a warning.

    Thanks

    ki