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

CCS3.3 Cannot find BIOS header files

David H
Prodigy 60 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I am running into an issue where Code Composer Studio (CCS) 3.3 isn't able to locate DSP/BIOS files when I attempt to load a project.  For example, if I attempt to load the example DSP/BIOS 5.33.03 project "hello.pjt" from C:\CCStudio_v3.3\bios_5_33_03\packages\ti\bios\examples\basic\hello, I get multiple messages stating that Code Composer Studio "Cannot find file: <file name>".  Some of the files that it cannot find are buf.h62, Std.h, Sts.h, Swi.h, Tsk.h, etc.  These files are all located in the bios directory at C:\CCStudio_v3.3\bios_5_33_03\packages\ti\bios\include.  I also noticed that the project *.tcf file is shown in the project documents folder rather than the DSP/BIOS Config folder.  I get errors when I try to build in this scenario.  This has occurred with two different projects.

Any ideas as to why CCS is unable to find the BIOS files and/or how I might fix it? How should CCS know where the BIOS files are located?

In case it helps, I was encountering an issue prior to this one where Code Composer Studio (CCS) 3.3 displayed the following message when I would try to load a project: "No build tools for the target specified in this project were found.  Cannot open project "...". Please use Component Manager to ensure the appropriate project server and build tools are selected."  I saw this message with two different projects, my main project and the DSP/BIOS 5.33.03 "hello.pjt" (in C:\CCStudio_v3.3\bios_5_33_03\packages\ti\bios\examples\basic\hello).  Both projects have the Build Options "Target Version" set to "C64x+ (-mv6400+).  I have C6000 Code Generation Tools v6.1.20 and DSP/BIOS 5.33.03 enabled under TMS320C64XX in the CCS Component Manager.  I got past this message by adding C:\CCStudio_v3.3\C6000 Code Generation Tools 6.1.20;C:\CCStudio_v3.3\C2000 Code Generation Tools 5.2.11; to my PATH environment variable.

I am using CCS 3.3.82.13, with BIOS 5.33.03, and Code Generation Tools v6.1.20 on Windows 7 (64 bit).  I understand that Windows 7 is not an officially supported operating system for CCS 3.3, but we would like to avoid upgrading at this time if at all possible.  I ran all the installations and programs as an administrator.  I installed Code Composer, DSP BIOS, and the code generation tools directly to the C drive (as opposed to in the Program Files folder).

Thanks!

David

  • 0
    TI__Guru**** 450411 points

    Hi David,

    CCS should automatically know where the include files for the run-time library and BIOS. I suspect you are missing some environment variable setting or component manager is not configured properly.

    What is the environment variable 'BIOS_INSTALL_DIR' set to?


    thanks

    ki

  • 0 in reply to Ki
    Prodigy 60 points

    Thanks for the reply Ki-Soo.

    The environment variable 'BIOS_INSTALL_DIR' is set to C:\CCStudio_v3.3\bios_5_33_03.

    David

  • 0 in reply to David H
    TI__Guru**** 450411 points

    That looks correct. What target do you have configured in the CCS setup utility?

  • 0 in reply to Ki
    Prodigy 60 points

    I imported a C6424 target from Spectrum Digital that I had used previously on Windows XP.  The board is called 'EVMC6424_XDS510USB' with a processor type of 'C6400PLUS'.

  • 0 in reply to David H
    TI__Guru**** 450411 points

    Can you take a screenshot of the dialog that appears when you got to 'Help -> About' in CCS?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 60 points

    Sure.  Here it is:

  • 0 in reply to David H
    TI__Guru**** 450411 points

    Thanks.

    I see nothing wrong with your setup. There is something wrong with the BIOS setup within CCS. It seems like you have it configured correctly in component manager but CCS is not recognizing BIOS config files and paths.


    One last thing to check. In component manager, make sure "Project Manager" and "DSP/BIOS" is enabled under the list of plug-ins for "Texas Instruments, Inc."

  • 0 in reply to Ki
    Prodigy 60 points

    It looks like I have them both enabled (DSP/BIOS and Project Management).  I didn't have a "Project Manager", just a "Project Management" option.  Below is a screenshot showing the two options enabled and all the options that are disabled.

    Thanks for the help!

    David

  • 0 in reply to David H
    TI__Guru**** 450411 points

    One last thing to try:

    manually re-register the project management component:

    > regsvr32 C:\CCStudio_v3.3\cc\bin\projsvr.dll

    re-register the build tools:

    > regsvr32 C:\CCStudio_v3.3\C6000\cgtools\bin\bti6000.dll


    make sure you have admin access to do both. Actually you should always run CCSv3.3 with admin rights on win 7.

  • 0 in reply to Ki
    Prodigy 60 points

    I manually re-registered projsvr.dll and bti6000.dll as you suggested.  I didn't notice any change initially after re-registering the dlls and still received the same messages indicating something was wrong with the BIOS information in CCS.

    However, I noticed the messages I received when opening my CCS project seemed to change when I changed the BIOS between 5.33 and 5.31.  The different messages CCS displayed were the two I mentioned in my original post: "No build tools for the target specified in this project were found.." and "Cannot find file: <Some DSP BIOS file name>".  One time, I changed the BIOS from 5.33 to 5.31, started CCS, and loaded the project with no messages indicating a problem.  I was then able to build successfully.  I then restarted CCS, loaded my project, and received one of the two kinds of messages indicating there was some problem with BIOS inside CCS.

    I had been running CCS in Windows XP (Service Pack 3) compatibility mode ever since I encountered a driver problem early on (which compatibility mode didn't solve).  I discovered that if I ran CCS with Compatibility mode disabled, I have been able to open and build my project successfully every time I have tried!  When I re-enable Compatibility mode, I run into issues and receive CCS messages when opening my project.

    It appears that my issues were solved through a combination of re-registering the DLLs and disabling Compatibility mode with CCS.  I am planning on trying to install CCS on a Windows 7 PC that has never had CCS installed to verify that I can repeat all of the installation steps I used to get it working on my current PC.  I should be able to determine if re-registering the DLLs is necessary to get CCS3.3 to work on Windows 7 from that.

    Thank you for all your help!  I appreciated it.

    David

  • 0 in reply to David H
    TI__Guru**** 450411 points

    Glad to here you have resolved the problem!

    However,

    David H said:
     I discovered that if I ran CCS with Compatibility mode disabled, I have been able to open and build my project successfully every time I have tried!  When I re-enable Compatibility mode, I run into issues and receive CCS messages when opening my project.

    this is contrary to what I have always observed. I usually recommend to run v3.3 with XP compatibility mode enabled since this works best for me. So I am surprised that turning it off works better for you. 3.3 support on Win 7 really is a crapshoot. For some, it is a breeze. Others have all sorts of problems. I'm glad that you have resolved yours.

    ki