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

Creating a DSPBIOS dependent static library

Cam Grant
Expert 1145 points

Hi, I was going to create a library of basic functions for my hardware to use for different development projects and I am left wondering how to include references to the dspbios library when it isn't included until you create a tcf file which is irrelevant to the library and the "${BIOS_INCLUDE_DIR}" variable has no value. Do I just take the path to the DSPBIOS include directory and add it to the compiler paths or is it not possible to use references to DSPBIOS in a static library.

Thanks.

  • 0
    TI__Mastermind 20480 points

    Hi Cam,

    you can create a CCS project DSP/BIOS project as a static library. Project->New CCS Project. Select Output type: Static Library

    You should be able to find a dspbios.lib file in your Debug (or Release) folder within the project.

  • 0 in reply to Tom Kopriva
    Expert 1145 points

    Hi Tom,

    I don't see a debug directory. I'm using CCS 5.2.1.

    I do the following

    File/New/CCS Project

    I select output type "Static Library"

    I select project template "Empty Project"

    I only get an includes directory that has C:/ti/ccsv5/tools/compiler/c5500_4.4.1/include in it.

    If I put a source file in it and compile, I'll naturally get my debug folder but I don't have a dspbios.lib file and I don't have the appropriate include file anywhere either.

    I did put "c:\ti\bios_5_41_13_42\packages\ti\bios\include" in my include directory in include options and it seems to compile ok but I don't know if this is the best way to do it.

  • 0 in reply to Cam Grant
    TI__Mastermind 20480 points

    Hi Cam,

    DSP/BIOS is already a library. The .tcf file is only needed for the end application which consumes the DSP/BIOS libs.

    Cam Grant said:

    Do I just take the path to the DSPBIOS include directory and add it to the compiler paths ...

    Yes, you are correct.

    ${BIOS_INCLUDE_DIR} is a build variable that expands to the include paths. The image shown below is from a DSP/BIOS example that I just created using the CCS project wizard. I'd create another DSP/BIOS example and include the same paths into your empty static library project. You can manually enter the same include paths or create the build variables by defining it in the "Build -> Variable" tab.

    Your end DSP/BIOS app should have the .tcf file updated to "plug-in" any Tasks, Hwi's, and etc that exist in your library.

  • 0 in reply to Tom Kopriva
    Expert 1145 points

    Thanks Tom!