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.

This project contains unresolved buildable linked resources. It might not build as expected.

I get this warning after a build.  There is no corresponding line in the Console window and I see no indication in the Projectgs window or anywhere else on the CCS screen.  I have no idea what this message really means.

Any ideas?

  • Hi Kurt,

    that I am aware of there are a few different things that can trigger this error

    - library files in wrong directory

    -ccxml file (or potentially other) included in project/build list but not there

    Could please double check a few such things and keep us informed?

    Best Regards,
    Lisa

  • 1) I checked the library files before posting.  They are OK.

    2) there is only one ccxml file included in the project.  a) it is where it should be.  b) it is used by other projects

    when I try to debug the project I get an error, "The target 'Spectrum Digital XDS510USB Emulator_0/C674X_0' could not be found."  but...I am now using an XDS100.  the XDS510xxx.ccxml was removed from the project some time ago.  the file does still exist but the device does not.

     

  • Hi Kurt,

    then it seems like CCS is looking for the previous ccxml for whatever reason (settings, path, error, etc)

    Could you send a bit more details about the settings you use and your path setup?   Does the "old" ccxml show on the list of project files?  Do you have multiple?

    Best Regards,
    Lisa

  • Hi Kurt,

    By the way in double checking whether the files are all linked and brought together properly, have a look here.  As mentioned it seems that there are at least some files CCS is getting a bit confused about.

     

    http://processors.wiki.ti.com/index.php/Portable_Projects#Linking_Files

     

    Best Regards,
    Lisa

  • I went into Debug Properties.  In the Debugger tab, the "CPU resolution options" was set to "Connect to exact CPU", but the selection was blank.  I changed it to "Connect to first compatible CPU".  Now it launches the debugger but cannot find the GEL file.

    The GEL file is in c:\ccs4\ccsv4\emulation\boards\evmc6748_v1-1\gel\c6748.gel but it is looking for it in 'C:\Documents and Settings\kurtjensen.SPIRICON\emulation\boards\evmc6748_v1-1\gel\C6748.gel' 

    So I put a copy of the GEL file in the 'C:\Documents and Settings\...'/ folder since the target configurations seem to have a fondness for it even though the product ios installed somewhere completely different.

    Now I cannot launch the debugger at all and I cannot find pout why.  Al I get is a dialog:

    "Error connecting to target: (Error -151 @ 0x0) This utility failed to open the adpater for a custom emulator. The adapter returned an error. (Release 5.0.429.0)" Cancel or Retry.  I think I will Retry...repeatedly...

    Any ideas now?

  • 1) which path setup?  you will have to be exact and explicit with your requests.  CCS4 is such a bewildering collection of settings, dialog, properties, macros, and configurations that I still get lost even after a full year of banging my head against random crashes, burps, errors, updates, and just plain lockups.

    2) do I have multiple? multiple what?

    3) "old" ccxml? "there is only one ccxml file included in the project"

  • Hi Kurt,

    it seems like there are still not properly linked files.

    Could you please send more information on your settings.  Have you looked at the linked wiki topic I sent you and checked your linked resources in the project?  Ie it would be interesting to see what direction CCS is receiving to for example look for the GEL file.

    I have attached two screen shots showing examples of where some of these paths are set.  You can also right click on a file in the project directory to see where CCS is looking for it.

    REgarding your other points ... I meant multiple ccxml files in the project.

    Best Regards,
    Lisa

     

     

     

     

     

  • I will look at the stuff you posted. 

    Yes, all of my libraries are in the right place.  All of my library include paths are correct.  I checked all of those posting.

    This project was working at one point.  What has changed is that I was forced to uninstall, remove, and reinstall CCS last week because of a problem with your upgrade.  http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/129037/465173.aspx#465173  As far as I know this has nothing to do  with my project and everything to do with problems inside of CCS4. I have spent 3 out of the last 6 days dealing with problems inside of CCS4. 

    When I re-dded this project to my workspace I got the warning.  How do I find oiut EXACTLY what is wrong?  The message is useless because it has me chasing my tail.  How do you find something that is not there?

  • Hi Kurt,

    Did you select to copy the project into the workspace when importing?  Did you try a fresh workspace?

    Anyhow I understand it is frustrating to encounter an issue, but that error message has multiple triggers (as I've mentioned) and mostly indicates that files are not correctly linked (as mentioned).

    I would try reimporting the project.  I would also do the right-click to see where CCS thinks some of these files are located. 

    Aside from that I would need more information from you to go on in order to be able to help you, which I/we are trying our best to do!

    Best Regards,

    Lisa

  • I do not copy the project. I did not try a new workspace.  The files are in version control and they are where they are.

    I have reimported the project - no change. I have checked all of the file locations.  The programs links and runs. But then again..."It might not build as expected".  What I do know is that any indication of a problem will eventually become a show stopper in CCS4.

    What other information do you need?

  • HI Kurt,

    ok.   information that might be useful for us are things to do with the linking etc.  For example are you using relative or absolute paths?  How did you import/link your files into the project?  Where is the project looking for the files (right-clicking on a file and properties) also the general file paths you have set up as per the screenshots a few posts ago.  That information would help.

    In the mean time here is what I hope you might be willing to try.

    1) Create a fresh workspace.

    2) Create a blank project, and as per  http://processors.wiki.ti.com/index.php/Portable_Projects#Linking_Files  do not select use default directory

    3) Manually import the folder/files by specifically linking/adding all those files in.  Again the above link has the steps to do this.  You need to be careful if you are using source control.

    Please let me know how the above goes.

    Best Regards,
    Lisa

  • relative or absolute? both..I think...

    Some of the files are source files linked from another directory - E:\PyrocamIV\workspace\PyrocamIV\Global.c
    Some of the files are libraries linked from other directories - E:\PyrocamIV\workspace\CUnitLibrary\Debug\CUnitLibrary.lib
    Some of the files are in the project directory - E:\PyrocamIV\workspace\UnitTest02b_Util\UtilTest.c

    1 & 2) I will try the new workspace idea later if I can find time. 

    Even if it fixes the problem I will not be moving the files. This really needs to work in the current location.  I cannot just change workspaces evry time there is a problem with CCS4.  This stuff is all in version control.  It is not locked in concrete but it is expensive to move both in time and context.  There are other people.  There are other dependencies. Sorry, but new workspaces simply cannot be part of any solution. I know this is a common suggestion for various problems with CCS4.  Unfortunately it does not work in my real world.

     

     

  • Hi Kurt,

    I thought I would check in to see how things went with the couple items we suggested trying.  And for any update getting the paths and everything fixed up again.

     

    Best Regards,
    Lisa

  • it just started working.  don't know why.

  • Hi Kurt,

     

    very glad to hear.  All the best.

     

    Cheers,
    Lisa