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

Problem using C6Flo+EVM320DM6437+CCS 3.3

Dimitris Kas
Prodigy 90 points
Other Parts Discussed in Thread: CCSTUDIO

Hello everyone, 

I am using EVM320 DM6437 and i try to make a project using C6Flo,  but i have some problems....

CCS 3.3 returned me the following 4 Compilation errors. I don't realy undestand what is going on. The only sure is that "dm6437dspapp_1cfg.h" is missing. But why?             C6Flo is responsible for generation of this file?

Also what about the message """js: "./dm6437dspapp_1.tcf", line 18: exception from uncaught JavaScript throw: TypeError: Cannot call method "destroy" of undefined (./dm6437dspapp_1.tcf#18)"". ?????

Any idea is welcome

Thanks.

 

 ----CCS 3.3  RETURNED THIS-------------------------------------------------------------------------------------------------------------------------------

-------------------------  dm6437dspapp_1.pjt - Debug  -------------------------

[dm6437dspapp_1.tcf] "C:\CCStudio_v3.3\bios_5_31_02\xdctools\tconf" -b -Dconfig.importPath="C:/CCStudio_v3.3/bios_5_31_02/packages"  dm6437dspapp_1.tcf

js: "./dm6437dspapp_1.tcf", line 18: exception from uncaught JavaScript throw: TypeError: Cannot call method "destroy" of undefined (./dm6437dspapp_1.tcf#18)

[dm6437dspapp_1_blocks.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_blocks.c"

"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include/dm6437dspapp_1.h", line 7: fatal error: could not open source file "dm6437dspapp_1cfg.h"

1 fatal error detected in the compilation of "dm6437dspapp_1_blocks.c".

Compilation terminated.

>> Compilation failure

[dm6437spapp_1_main.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_main.c"

"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include/dm6437dspapp_1.h", line 7: fatal error: could not open source file "dm6437dspapp_1cfg.h"

1 fatal error detected in the compilation of "dm6437dspapp_1_main.c".

Compilation terminated.

>> Compilation failure

[dm6437dspapp_1_threads.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1" -i"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_threads.c"

"C:/Program Files/Texas Instruments/C6Flo_1.02/work/ProcessFlow1/dm6437dspapp_1/include/dm6437dspapp_1.h", line 7: fatal error: could not open source file "dm6437dspapp_1cfg.h"

1 fatal error detected in the compilation of "dm6437dspapp_1_threads.c".

Compilation terminated.

 

>> Compilation failure

 

Build Complete,

  4 Errors, 0 Warnings, 0 Remarks.

  • 0
    TI__Expert 8890 points

    Dimitris,

    It looks like you are using an older version of DSP/BIOS that isn't compatible with C6Flo.  I recommend updating to DSP/BIOS 5.41, which you can download here:

    Close CCS before running the DSP/BIOS installer.  Then, the next time you run CCS, go to the Help->About->Component Manager screen.  Expand the list on the left side of the screen to Target Content (DSP/BIOS)->TMS320C64XX, and select the new (5.41) version.  Save your settings and restart CCS.  When you're done, you should see DSP/BIOS 5.41 listed on the Help->About screen.

    Hope this helps.  Let me know if you have any trouble upgrading your DSP/BIOS version.

  • 0 in reply to Joe Coombs
    Prodigy 90 points

    First of all i would like to thak you for your advice. The configuration at Component Manager was exactly what it needed.

    I have one more question about the build process. I have an error that i suppose to be caused from my build options. (linking), as you will se above returned an error at

    >> C:\\CCStudio_v3.3\\MyProjects\\ProcessFlow1\\dm6437dspapp_1\\Debug.lkf, line 2:   error:


    *******************************************************************************************************************************************************************

    -------------------------  dm6437dspapp_1.pjt - Debug  -------------------------
    [dm6437dspapp_1.tcf] "C:\CCStudio_v3.3\bios_5_41_09_34\xdctools\tconf" -b -Dconfig.importPath="C:/CCStudio_v3.3/bios_5_41_09_34/packages"  dm6437dspapp_1.tcf

    [dm6437dspapp_1_blocks.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_blocks.c"

    [dm6437dspapp_1_main.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_main.c"

    [dm6437dspapp_1_threads.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1_threads.c"

    [dm6437dspapp_1cfg.s62] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1cfg.s62"

    [dm6437dspapp_1cfg_c.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -fr"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/Debug" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1" -i"C:/CCStudio_v3.3/MyProjects/ProcessFlow1/dm6437dspapp_1/include" -mv6400+ -@"Debug.lkf" "dm6437dspapp_1cfg_c.c"

    [Linking...] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -@"Debug.lkf"
    <Linking>
    >> C:\\CCStudio_v3.3\\MyProjects\\ProcessFlow1\\dm6437dspapp_1\\Debug.lkf, line 2:   error:
                   unterminated quote

    >> Compilation failure
    *******************************************************************************************************************************************************************

    Do you have something to suggest me about this?

  • 0 in reply to Dimitris Kas
    TI__Expert 8890 points

    Dimitris,

    What version of the code gen tools are you using?  You can check your current version on the Help->About screen, just like we did for DSP/BIOS.  I recommend upgrading to 6.1.9 or later if you aren't already using a recent version.  You can download the C6000 codegen tools on this page:

    Once downloaded and installed, you may have to select the new version in the CCS component manager, as before.

    Also, as a general step, I recommend using "rebuild all" (instead of an incremental build) just in case CCS is trying to use some of the files that were generated by your older version of DSP/BIOS.

    Hope this helps.  If not, please post the Debug.lkf file (from the same folder as your pjt file) so I can take a look at it.

  • 0 in reply to Joe Coombs
    Prodigy 90 points

    Once again you were right..                                                                                                                                                                                                                                                                       At Component Manager it was selected Code Generation Tools Version 6.0.8 (and i change it to version 7.0.3. Now i completely understood the importance of Code Component Manager.

    I succesflully build an example project!

     

    Thanks for all.

  • 0 in reply to Dimitris Kas
    TI__Expert 8890 points

    I'm glad to hear that!  Some of these configuration steps can be a little counter-intuitive in CCS3.3.  Fortunately, now that you've gone through this once, you should be set for any C6Flo app.

  • 0 in reply to Joe Coombs
    Prodigy 90 points

    Yes,

    but it seems that it has a lot of restrictions (correct me if i am wrong..). Is there a supplemental library package just like some similar (simulink based) packages like imaq ?

     

  • 0 in reply to Dimitris Kas
    TI__Expert 8890 points

    Dimitris,

    All of the libraries that your C6Flo application needs are copied to the "lib" folder relative to the pjt file.  Similarly, required header files are copied to the "include" folder.  This means that the application folder is relatively portable; you can move it around (or even to another PC) and still be able to build it without worrying about any SDKs or separate library packages.  The only separate installations you need are the ones we've already discussed: DSP/BIOS and the TI codegen tools.

  • 0 in reply to Joe Coombs
    Prodigy 90 points

    Dear Joe,

    Thanks for the instructions relative to the "lib" and "include files".

    But When i said that it seems to have some restictions i meant that it seems to have a small number of functions in blocks. Then i asked if there is additional libraries that would reduce the development time further more. Moreover can someone make C6Flo Block functions from functions writen to C?

     This intergration would be very flexible ability....

    Anyway, it seems a very attractive and  easy to use tool that already gives a lot of capabilities. 

     

  • 0 in reply to Dimitris Kas
    TI__Expert 8890 points

    Dimitris,

    Sorry, I misunderstood your question.  You're right that the current set of blocks in C6Flo is somewhat limited.  However, there is some good news:

    1. TI will continue to add more blocks to the standard set
    2. C6Flo allows anyone to add their own blocks

    The upcoming v1.03 release (due out before the end of 2010) will add some audio processing blocks to the standard set.  We also have plans to add more blocks (in that category and in others) throughout 2011.

    For more information on how to add your own block(s) to C6Flo, please check out the following wiki article:

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

    Creating a block requires some knowledge of JavaScript, but it should be pretty straightforward to use existing blocks as templates for your own creations.

    Hope this helps.