• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 301 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.

DSPBIOS example program

Arya Stark42598
Intellectual 465 points


Hello,

 

I have the C6472 EVM and I'm trying to compile and run the DSPBIOS example program (OOBDemo_bios6).

A few includes seem to be missing, but that's easy to fix. After that, I get the following linker message:

"/Program Files/Texas Instruments/ccsv4/emulation/boards/evm6472/ndk_2_1_0/packages/ti/ndk/lib/c64plus/os_bios6.lib<semaphore_bios6.o64p>_xdc_runtime_Error_getMsg_E"

 

Also, I have some unresolved external symbols, like cgiParseVars and ConsoleOpen.

 

What can I do to fix this? Has anyone here worked with this program?

  • 0
    TI__Genius 9915 points

     Did you try to follow the Readme.txt file that is there in the demo folder? just in case i am attaching the file. please go through this and let me know if it works.

     

    thanks,

    Arun.

  • 0
    Prodigy 220 points

    I ran through the same problems.

    For the external symbol like cgiParseVars and ConsoleOpen, you need to link files to your project. i.e for ConsoleOpen you need the file console.c which is located in <YOUR CCSV4 INSTALL DIR>\emulation\boards\evmc6472\ndk_2_1_0\packages\ti\ndk\example\tools\common\console\console.c

    To link a file, click "Project->Link Files To Active Project..."

    The xdc_runtime_Error_get_Msg problem is different. I get rid of it by compiling my project as "debug". Look like NDK is compile as debug and use xdc_runtime_error module and the OOBDemo_bios6 project don't provide the symbol when compiled as "whole_program". To change this, right-click on your configuration project "OOBDemo_Bios6_configuration" and select "Build Properties...". Select "CCS Build" in the left pane and "RTSC" tab in the right pane. Choose "debug" for the "RTSC Build-Profile" field.

    I'm still looking how I can rebuild NDK for non-debug. I look at the package.bld, config.bld and the package.mak file and still did not find how to do to. Can someone help-me with this?

     

     

     

     

     

  • 0 in reply to soldsp
    Prodigy 10 points

    In the configuration script file, common.cfg for your project I used the GUI to add the Error item found in XDCtools section. in XDCtools, Diagnostics choose Error right click "use module"