• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 53 subscribers
  • Views 1409 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.

Some include path options being ignored for assembly file

Joshua Strouse
Prodigy 90 points


Hello,

    I'm using Code Composer v5.2.1. I've imported a legacy CCS 3.3 project for a C64xx DSP that uses DSP/BIOS. In the project is an assembly file (a .s64 file). This assembly file uses '.include' to bring in c64.h64 and hwi.h62. I've found the correct locations for those files in the Code Composer installation (specifically E:\TI\bios_5_41_13_42\packages\ti\bios\include). I've added this path in Build Settings->Build->C6000 Compiler->Include Options. However, when I build I get a mangled error message:

ERROR! at line 13: [E1000]
Include/Copy file not
                                                  found
or opened
                 .include c64.h64

    When I look at the command line and it's parameters I notice that not all of the include paths are there, specifically not the path where the file to be included is located.

    Does anyone know the cause of this problem and how to resolve it?

    Thank you!

  • 0
    TI__Guru*** 130875 points

    Hi Joshua,

    it is common for an imported project into v5 to require additions/corrections to the include paths and variables.  This is one thing to check and this wiki should help you

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Another thing to confirm.  Did you use the legacy import?  Project->Import legacy CCSv3.3 PRoject

    And one final thing to check is that you have full permissions and are not using directories with spaces.

    Please keep us informed.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Prodigy 90 points

    Hi Lisa,

        I did use the legacy import, as you describe. Also, I have full permissions (I'm an Administrator on an XP machine) and there are no spaces in any of the project or include paths.

        I've checked the wiki page you pointed me to, but as I wrote in my initial post, I've already added the needed path to the list of include paths.

        Any other ideas?

    Thanks,

    Josh

  • 0
    TI__Guru**** 472351 points

    Joshua Strouse said:
    I've added this path in Build Settings->Build->C6000 Compiler->Include Options.

    This looks right. You should be able to add additional search paths here.

    Joshua Strouse said:
    When I look at the command line and it's parameters I notice that not all of the include paths are there, specifically not the path where the file to be included is located.

    Could you send me a screen shot of the Include Options in the build properties and also the build output window when the asm file is assembled?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 90 points

    Hi Ki,

    Here's a screenshot for you:

    Thanks,

    Josh

  • 0 in reply to Joshua Strouse
    TI__Guru**** 472351 points

    Thanks Josh. I'm able to reproduce this. The -I option seems to have issues with paths on a different drive than 'C' for assembly files. We are investing further...

  • 0 in reply to Ki
    TI__Guru**** 472351 points

    Ki-Soo Lee said:
    Thanks Josh. I'm able to reproduce this. The -I option seems to have issues with paths on a different drive than 'C' for assembly files. We are investing further...

    Sorry, it turns out my test case had a typo in it. I cannot reproduce the issue. I can get it to build successfully. The option gets passed to the compiler on the command line.

  • 0 in reply to Ki
    Prodigy 90 points

    Hi Ki,

    Thank you for looking into it. Any other things to look at or try?

    Thanks,

    Josh

  • 0 in reply to Joshua Strouse
    TI__Guru**** 472351 points

    I am still trying to reproduce the issue. If you could send a small reproducible test case (the smaller the better), that would be great.

  • 0 in reply to Ki
    Prodigy 90 points

    Hi Ki,

        I tried uninstalling CCS 5 and re-installing it on the C: drive, so that everything was located on the same drive. However, I'm still seeing the same problem.

        I've attached a zip with the relevant parts of my project. Unzip it to the C: drive to match my project location. The path to the project file (.pjt) should be C:\Docs\CC_5.2.1_Test\MT-BSL\BSL64xx\BSL64xx.pjt. Hopefully this can help you re-create the issue!

    Thanks,

    Josh

     1803.CCS5.1_Project.zip

  • 0 in reply to Joshua Strouse
    Prodigy 90 points

    Hi Ki,

    Any update on this issue? My customer and I are blocked until this issue is dealt with. Anything you can give me would help.

    Thanks,

    Josh

  • 0 in reply to Joshua Strouse
    TI__Guru**** 472351 points

    Hi Josh,

    The issue (according to the test case you gave me) is that the files in the 'Sources' subdirectory (including bsl_isr.s64) all have file specific options which override the project level properties.

    If I look at the file specific options for bsl_isr.s64, it does not have the path to the bios include directory that is in the project level options:

    Note the little "key" option that specifies that has file specific options.

    You will need to add the bios include folder to the file specific options.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 90 points

    Hi Ki,

    Thank you for your help! Rather than changing the file's specific settings, we set the file to the default settings since we don't need the file-specific build settings.

    For others who might see this thread, I set it back to default by right-clicking the file, going to Resource Configurations->Reset to Default. I then selected all configurations in the window that popped up. After that I was back to default settings without the 'key' on the icon.

    Thanks again,

    Josh