• State
  • Locked Locked
  • Replies 17 replies
  • Subscribers 53 subscribers
  • Views 3981 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.

CCS/MSP432P401R: fatal error #1965: cannot open source file

sfloydtn
Intellectual 340 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

First, some background... We are just beginning the process of migrating a set of "stand-alone" CCS installations to a common CCS environment that is intended to be used in a team environment (e.g. 3-4 developers, 4 projects). It will have a core/common set of routines/libraries for things like HAL, NV memory access library, Proprietary OTA & serial protocol for the writing/reading of MCU memory, etc. Exactly how best to setup CCS for team usage is a conversation I wish to have with CCS experts, but this isn't my current question. Perhaps I can add a related question to address this later.

For now, as a first step, we wanted to see if we could take one known-good/working project from one developer's machine, put everything needed to build it into Source Code Control (Subversion), and see if another developer could pull it out of subversion & it build cleanly with no (or very minimal) changes.

We have been able to get a known-working CCS setup into Subversion from the source machine and pull it out onto the destination machine. We want to leverage variables like workspace_loc, and ProjName to make references relative for each developer, e.g., no absolute paths (other than workspace_loc). However, we are unable to get past compilation errors surrounding include files accesses.

Example error:

"../startup_msp432p401r_ccs.c", line 40: fatal error #1965: cannot open source file "Build_Configuration.h"

We have tried many things to get it to build successfully:

- Compared CCS parameters between the source & destination machines, and see no differences (other than the workspace_loc definition change). There were no obvious differences.

- Scrutinized the definition of the variables for syntax issues.

There were slashes '/' and back-slashes '\' used in the paths, but fixing had no effect.

- "${workspace_loc:/${ProjName}/LIS3DH_Ware}" looks suspect with the last curly bracket not immediately after workspace_loc; and the colon ':' also looked squirrely. Systematically changing them had not effect.

- Changed the ordering of the paths with no effect.

- Deleted all and recreated one to try to deal with the first compiler error, and couldn't get past that.

- Deleted all relative references to our include and added explicit absolute paths to where the files are know to be. Still, "cannot open source file".

The source machine works, and the destination doesn't.

Also, there's a warning we can't seem to chase down:  "Invalid project path: Include path not found (C:\ti\tirex-content\simplelink_msp432_sdk_1_20_00_45\source). DevPlatform_Basic pathentry Path Entry problem"

  • 0
    TI__Guru**** 440401 points
    Hello,
    Where does "Build_Configuration.h" reside on the destination machine? What are the include paths that appear for the project in the Project Explorer view (a screenshot of the paths would be helpful)?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 340 points

    Build_Configuration.h resides in "C:\_MyFiles\_Projects\__Invisible Fence\MSP432\BP 2.0\DevPlatform_Basic\Proj_Includes".

    I have a screen shot, but unable to find a way to move it to here. 'Paste from Word' looked promising, but only allows pasting of text. Will post this, and keep trying to get it to you.

  • 0 in reply to sfloydtn
    Intellectual 340 points

    I cannot figure-out how to paste an image or upload a file using the interface here. I systematically looked at each icon, and throughout the page. I tried in Chrome, and in IE. Please provide details on how to associate image information on this thread.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points
    Did you see the second FAQ in the forum readme?
    e2e.ti.com/.../3131

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 340 points

    Yes. I read the FAQ before making my original post. I see the “Insert Code, Attach Files and more…”  link in the screen shot in the FAQ. The screen in the FAQ is not the same screen I see when making these posts. No such link exists on the pages I see when entering posts. Also, I did a 'find' on the page (^F) and searched for "Insert" and "Code", and no such text exists on the page. Not sure if it will help, but the URL I'm currently on (which has no "Insert Code..." link) is: https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/2669441/reply?ReplyToContentTypeID=1

    I'll try to get the requested screen shots (and the ones showing the pages without the "Insert Code..." link) to you via email through our TI support (Blake Carpenter.)

    Regards,

    Steve Floyd

  • 0 in reply to sfloydtn
    Intellectual 340 points

    Ok, I figured it out! Even though the "Insert/Edit Media" icon (above the text entry box) is greyed-out, it is functional. Whew. Sorry for the troubles. My experience of not seeing the screen referenced is in the FAQ, and the counter-intuitive greyed-out icon were road-blocks for me.

    Here is the screen shot you requested.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points
    Thanks for the screenshot. Notice how some paths have "..." after the path. If you hover your mouse pointer over it, a tool tip with the expanded path should pop up. Note that there are some paths that does not have the "...". I'm not sure why those do not. It could be because the expansion points to an invalid path (but there is some underscore symbol which I am not sure what that is about). If you expand one of the ones that do have it, say for ${workspace_loc:/${ProjName}/RSC_Includes}, what does that expand to?

    Also, what are the paths that appear under the "Includes" folder for the project in the Project Explorer view?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 340 points

    I just re-opened the project, went directly to 'Include Options', and the ellipsis are now there. It seems that exiting CCS and restarting it changed something.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points
    This looks better. But I assume you are still getting the build error.

    Can you provide the full build output? basically all the output that appears in the build console when you build the project?
  • 0 in reply to Ki
    Intellectual 340 points

    I found the problem. If I do a "Clean Project", it automatically (and immediately) begins a build that fails. However, I was assuming that the build it started was a 'Build Project' of the currently selected (Active) project. However, it apparently begins a 'Build All' in response to a user-initiated 'Clean Project', and the compile errors are unrelated to the 'Active' project.

    Why is it when I invoke 'Clean Project', it interprets that as 'Clean Project' and 'Build All'? Is there a way I can suppress it from doing that?

  • 0 in reply to sfloydtn
    Intellectual 340 points

    I further characterized the behavior, and it seems the issue is that the Project-level context of the command ‘Clean Project’ is not honored if 'Build Automatically' is selected for another project. Of course ‘Build Automatically’ should build automatically, but only in response to relevant triggers that happen in the project that is set to 'Build Automatically'.

    ...I just realized that 'Build Automatically' must apply globally to all projects within a workspace / is not a per-project setting. If so, it being under the 'Project' menu seems inappropriate. It is more of a workspace-level attribute.

    It appears I'm making my way up the learning curve amid some counter-intuitive things.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points

    sfloydtn said:
    ...I just realized that 'Build Automatically' must apply globally to all projects within a workspace / is not a per-project setting.

    yes, this is accurate. 

    sfloydtn said:
    If so, it being under the 'Project' menu seems inappropriate. It is more of a workspace-level attribute.

    the 'Project' menu refers to menu item commands that apply to creating/importing/building projects in general. It is not always related to just the project in contex. As you know, some commands apply to all projects, others apply to the project in context. 

    sfloydtn said:
    It appears I'm making my way up the learning curve amid some counter-intuitive things.

    But I see you point on how this can be unclear. We should do some clarification on our end.

    With that said, I still do not see the issue where a "Clean Project' command is triggering a "Build All". Despite "Build Automatically" being enabled, a "Clean Project" would only apply to the project with context and would then trigger a standard "Build Project" for the project in context and NOT a "Build All"). One thing I want to clarify, the issue is that it builds other projects, right? It is not just simply building all the build configurations of a single project, correct?

  • 0 in reply to Ki
    Intellectual 340 points

    It is not just simply building all the build configurations of a single project, correct?

    That is correct. I asked 2 colleagues to try to reproduce the issue and both did. The repro is to click on (make Active) a project you are not interested in (say Project_B), In the 'Project' menu at the top, check 'Build Automatically'. Additionally say you also have Project_C, and Project_D in the same workspace. Now, Click on the project you are interested in (say Project_A) to make it Active, right-click on Project_A, and select 'Clean Project' from the pop-up menu. All projects will be built.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points
    Hi Steve,
    Sorry for the delay on this. This issue is not reproducible for us and without a test case, it is difficult for use to debug. It must be an issue related to the common environment across you and your colleagues. I'd like to focus on the version control. Do you see this issue for projects not in version control? Can you try an environment with a workspace without any projects in version control?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 340 points

    No problem, I have been busy too. While the files are in version control, CCS knows nothing about subversion, e.g., it is working only on files sitting in a local directory. The files are copied from the repository to a local folder, CCS is opened, and the workspace is opened from the local folder.

  • 0 in reply to sfloydtn
    TI__Guru**** 440401 points

    sfloydtn said:
    . While the files are in version control, CCS knows nothing about subversion, e.g., it is working only on files sitting in a local directory.

    Ok, just to confirm, there is no SVN integration with CCS/Eclipse at all (SVN plugin to Eclipse?

  • 0 in reply to Ki
    Intellectual 340 points

    That is correct. No SVN plug-in or any other integration with any source code control system.

    That said, we desire to add SVN integration to CCS, but nothing has been done to make that happen.