• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 349 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.

DSP BIOS Project Build Problem REPOSTED WITH IMAGE

Vedat Odabas-Geldiay
Prodigy 40 points

I have been successfully using CCS 4.0.1 with DSP BIOS 5.40.02.22 for the past several years with a custom TMS320C6745 design.  I just upgraded to CCS 4.2.4 and DSP BIOS 5.41.10.36 (the two came together in the download) and are getting errors associated with DSP BIOS in building the project.  Finally I decided to load the simplest DSP BIOS example that also came with the same download, i.e. hello world.  This example produced exactly the same errors in building the project.  The initial part of the console output is enclosed below.  After building the hello.tcf and hello.c successfully, it gives  ERROR:no source files, nothing to do, for building the hellocfg.s?? and hellocfg_c.c files and then later it says it can't find file hellocfg_c.obj, as obviously it didn't build it successfully.

Below is the CCS console output section for hellocfg_c.c not built successfully.  There are many other errors related to DSP BIOS (greater than >100) like undefined symbol HWI_INTXX or EVENTXX following this.  If this is a path issue, I can't seem to find it.  If it is an Include issue, it shouldn't be, because this the DSP BIOS hello world sample project that came with the download witgh no modifications whatsoever (code is 6 lines long).   Any help you can provide will be great.  Thank you. 

Vedat Odabas-Geldiay

 

  • 0
    TI__Mastermind 37985 points

    Vedat,
    I would recommend you to install CCS 4.2.4 in a directory without spaces, C:/ti for example. It may or may not fix that particular problem, but a path with spaces will probably cause some other issues later. The path with spaces is the default for CCS 4.2.4, but since then we figured out that there are too many problems with it, and the default installation directory for newer CCS releases is changed to C:/ti.

    Try making that change, and see if that solves the problem.

  • 0 in reply to Sasha Slijepcevic
    Prodigy 40 points

    Hi Sasha,

    Thank you for your input.  It was quite an eye opener to hear about the solution to this problem.  I am glad I did write the post, otherwise I would have never figured this one out in a million years.  I listened  to your advice but installed Code Composer version 5.2.  It did install in C:\ti and it now compiles and builds with no problem.  We were hesitant whether to switch to version 5 or not for other reasons, but this problem caused us to give it a try and so far so good.  We have been able to run our previous applications using CCS version 5.  We may go back to CCS 4.2.4 or we may not.  I will let you know if the problem reoccurs with C:\ti installation in CCS 4.2.4 if we ever give that a try.

    This issue probably needs to go into a FAQ type document for CCS version4.

    Regards,

    Vedat Odabas-Geldiay