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.

Error importing project. Location cannot be resolved

Other Parts Discussed in Thread: MSP432WARE, MSP430WARE

Hi,

I am having trouble importing any of the MSP430ware or MSP432ware example projects using the Resource Explorer.


I made them available offline first. This seemed to succeed in downloading and extracting those files. However, when I click the Import to IDE button for any of the examples I get the following error:

Error importing project. Location cannot be resolved: "C:/Users/joe/Documents/dev/MSP430Work/@ti-rex-content/msp/msp432ware__3.50.00.02/examples/boards/MSP-EXP432P401R/MSP-EXP432P401R_Software_Examples/Firmware/Source/OutOfBox_MSP432P401R/CCS/OutOfBox_MSP432P401R.projectspec"!

C:/Users/joe/Documents/dev/MSP430Work/ is my work directory. There is no @ti-rex-content directory in the work directory.

I cannot figure out how to get the projects imported. I can browse the content by clicking on the files. For instance, I can read the main.c in the Out of Box demo from within the Resource Explorer.

CCS 6.2.0 / Window 10 64bit


My user is NOT an admin user (I do not use admin users on windows any more than I would have my main unix user be root.) Could there be a permissions issue?

I am new to CCS. SO I really don't know where to start looking.

Thanks.

  • Joseph Laffey said:
    I made them available offline first. This seemed to succeed in downloading and extracting those files.

    Which directory did the MSP432Ware extract to? Is it in c:\ti\tirex-content?

  • Thanks for the reply. Yes, it looks like it is here:

    C:\ti\tirex-content\msp\msp432ware__3.50.00.02\


    Thoughts?

  • Would you check if the following file exists in your machine:

    C:\Users\[....]\ti\CCSExternalReferences\TIRex_2

    If yes, what is in the file?

  • Thanks for the reply.

    That file does not exist on my machine. In fact there is no CCSExternalReferences directory in the C:\users\joe\ti\ directory.

    I only see:

     Directory of C:\Users\joe\ti

    09/18/2016  12:20 AM    <DIR>          .
    09/18/2016  12:20 AM    <DIR>          ..
    09/18/2016  12:18 AM    <DIR>          .license
    09/30/2016  04:36 PM    <DIR>          CCSActiveInstances
    09/30/2016  03:49 PM    <DIR>          tirex-localserver
                   0 File(s)              0 bytes
                   5 Dir(s)  128,660,549,632 bytes free

  • OK. I did some further research with the knowledge that the CCSExternalReferences is needed for this to work. So I found that is was caused by some bug in the install or update process.

    I normally run as a non-admin user on Windows (as any security conscious person would). When I installed CCS I was logged in as my normal user. When I ran the installer it asked for the admin user credentials in order to elevate privileges to install. This is what most installer programs do... and most work fine.

    However, some portion of the installer, or one of the upgrades, looked up the home directory of the admin user (because it read the environment after elevating privileges, rather than before) and put the CCSExternalReferences directory in the ti directory of the admin user, rather than in my normal user's home directory.

    The installer needs to get all the user's environment variables to determine install paths BEFORE elevating privileges so that in can put files in the right place. Most installers do this properly nowadays, but some, like apparently the one used by CCS, do not.

    This is a bug in the install process. Installers must work properly when used from user accounts. Can you please pass this on to whomever handles the installer for CCS?

    I copied the CCSExternalReferences directory from the admin user's home directory into my normal user's home directory, and now things seem to work.

    Please pass this bug on to the installer team. Thanks.
  • Thank you for the analysis on what was triggering this issue, and glad that you were able to move ahead after copying over the CCSExternalReferences directory.

    We have filed a bug report to track this from our end. The tracking # is REX-1028.