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.

CCSv4 Import Legacy C64 Project - missing BIOS_INCUDE_DIR

Other Parts Discussed in Thread: CCSTUDIO

Hello,

I' trying rto import existing library projects for the C64x and C64+ family to CCSv4 (from version 3.3 and/or 3.0). My current tool chain from installation history:

xdais_6_23
ipc_1_00_01_48
xdctools_3_15_02_62
bios_5_40_02_22
bios_6_20_01_41
com.ti.ccstudio.product_4.0.2.01003

I have a strange effect: importing a library project I never see the "Select DSP/BIOS Tools" wizard dialog. And the system variable BIOS_INSTALL_DIR doesn't exist for the project. Creating a new library project has no problem.

Here the Build Settings for the imported project, without BIOS selection boxes in the lower half of the window:

And here the Build Settings for the new project, with BIOS selection boxes in the lower half of the window:

Is this a known issue or pitfall? Or am I doing something wrong?

Kind regards,
Andi

  • Hello Andreas,

    Would it be possible to get .pjt file for the library project that you are trying to import?

    Thanks,
    Martin

  • Hi,

    here is a small stand-alone example.

    Kind regards,
    Andi

    ----------- Project file ------------

    ; Code Composer Project File, Version 2.0 (do not modify or remove this line)

    [Project Settings]
    ProjectDir="$(Proj_dir)/"
    ProjectType=Library
    CPUFamily=TMS320C64XX
    Tool="Archiver"
    Tool="Compiler"
    Tool="CustomBuilder"
    Tool="DspBiosBuilder"
    Config="Debug"
    Config="Release"

    [Source Files]
    Source="src\file1.c"
    Source="src\file2.c"

    ["Archiver" Settings: "Debug"]
    Options=-r -o"$(Proj_dir)/Debug\MSG_CCS40.l64p"

    ["Archiver" Settings: "Release"]
    Options=-r -o"$(Proj_dir)/Release\MSG_CCS40.l64p"

    ["Compiler" Settings: "Debug"]
    Options=-g -fr"$(Proj_dir)\Debug" -d"TOOL_CCS40" -d"_DEBUG" -mv6400+

    ["Compiler" Settings: "Release"]
    Options=-o3 -fr"$(Proj_dir)\Release" -d"TOOL_CCS40" -d"NDEBUG" -mv6400+

    ----------- source file 1 ------------

    #include <std.h>
    #include <SEM.h>

    void foo1 (void)
    {
    }

    ----------- source file 2 ------------

    #include <std.h>
    #include <SEM.h>

    void foo2 (void)
    {
    }

  • Andreas,

    BIOSv5 projects usually contain a .tcf configuration script.  Your project doesn't seem to contain a .tcf file...is there a reason for that?  If you add a .tcf file (even an empty one) into the root of your project before migrating, then CCSv4 will treat your project as a BIOSv5 project, as you're expecting.

    - Baltasar

  • Baltasar,

    This is a new information for me. For library projects we never defined .tcf files, only for executable projects. Is there another reason for using .tcf file for library projects?

    Kind regards,
    Andi

  • Andreas,

    Send me a message to bbelyavsky at ti com with more information about your project setup.

    If your project doesn't contain a .tcf file, then help me understand why you need the project to expose the BIOS tool's version.  The BIOS tool (tconf) has no effect on any files other than .tcf files.

    Historically, CCSv3 always exposed BIOS tool settings for all projects.  CCSv4 supports a wider range of targets, some of which do not support BIOSv5, so our design has changed - we do not want to expose any GUI to users who would never use it, or even understand its purpose.  The migration tool uses some heuristics to determine whether a CCSv3 project is a "BIOSv5 project", such as checking if any build-options have been set on the BIOS tool, or if the project contains a .tcf file.  Your project happens to not be recognized as a BIOS project.  To work-around this issue, you can include an empty .tcf file in your project before migrating it.  But, in any case, send me an email, and once I understand your setup I'll see if maybe we can improve our migration tool to handle your scenario better.

    - Baltasar

  • Andreas,

    I've implemented support for your scenario.  It will be available in CCSv4.1.0.

    You will see a new page in the migration-wizard:

    The new page will allow you to explicitly force to enable DSP/BIOSv5.x support for the migrated project(s).  Your selection on this page will be persisted, so you will be able to run through migration over and over without having to re-select your choice.

    - Baltasar