• Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 3023 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.

Where is the CSL and BSL header files and libraries in CCS v4

Summer Xu
Prodigy 170 points

I am new to CCS v4. CCS v4 doesn't know how to find the CSL and BSL header files and libraries. However, I cannot find where the header files and libraries are after I setup CCS v4.

After searching the web, I found one person said that:

Note that your CSL header files might be in C:\Program Files\Texas
Instruments\C6xCSL\include. Click "OK".

Note that your BSL header files might be in C:\Program Files\Texas
Instruments\DSK6713\c6000\dsk6713\include. Click "OK".

Note that your CSL library might be in C:\Program Files\Texas
Instruments\C6xCSL\lib_3x\csl6713.lib. Click "OK".

Note that your BSL library might be in C:\Program Files\Texas
Instruments\DSK6713\c6000\dsk6713\lib\dsk6713bsl.lib. Click "OK".

However, I cannot find both C6xCSL and DSK6713 folders. What can I do?

In addtion, I am using DSK6416. Where can I find the CSL and BSL header files and libraries of DSK6416?

  • TI__Guru**** 162305 points

    Summer,

    CSL and BSL are not included in CCS.  We used to include CSL.  If you were working with a CCSv3.3 that came with a DSK then the board vendor may have also included BSL on the disk.

    For the BSL for C6416 DSK you will need to get that from Spectrum Digital.  For the C6000 CSL you can get that here: http://processors.wiki.ti.com/index.php/Chip_support_library

  • in reply to JohnS
    Prodigy 170 points

    JohnS, Thank you very much!

    I have included both CSL and BSL in my CCS, and a lot of errors disappeared.

    However, a new error comes up:


    unresolved symbol __strasg, first referenced in C:\\Program 

    I have searched this problem in the web, but no answer was found. Can you help me about this problem?

    Thank you.

     

  • in reply to Summer Xu
    TI__Guru**** 162305 points

    Summer,

    Seems like you are still missing a library of some sort.  If you look at the old CCSv3.3 project can you check the .lib references against the ones included in your new v4 project.

    John

  • in reply to JohnS
    Prodigy 170 points

    Where can I find the libraries used by old CCSv3.3 project?

    Are the libraries in the .cmd file in the old project?

    There are three libraries in this file:

    rtdx64xx.lib, csl6416.lib, rts6400.lib.

    If these .lib should also be included in the new v4 project, where can I find rtdx64xx.lib? In addtion, are they added in the same way as that of CSL and BSL?

  • in reply to JohnS
    Prodigy 170 points

    I saw someone in the web said that .lib in the cmd file of the old project should be all included in the new project.  According to this suggestion, I tried and the problem has been solved.

    However, which libraries should be included in the project if I create the project by myself instead of importing from legacy CCS v3 project. I have no idea.

    In addition, what is the difference between .cdb from the old project and the .tcf in the CCS v4?

    I find that after importing the legacy CCS v3 project, .ccxml file of the target configuration should be generated. Why the information of the target is not inherited from the old project?

  • in reply to Summer Xu
    TI__Guru**** 162305 points

    Summer Xu said:
    However, which libraries should be included in the project if I create the project by myself instead of importing from legacy CCS v3 project. I have no idea.

    Best to ask someone in the device forums.  I am not familiar with the CSL libraries and what each one does.

    Summer Xu said:
    In addition, what is the difference between .cdb from the old project and the .tcf in the CCS v4?

    .cdb VS .tcf VS .cfg is dependent on the version of BIOS being used.  BIOSv4 used .cdb files, BIOS5 used .tcf and BIOS6 uses .cfg.   CCSv4 and CCSv5 support BIOS5 and BIOS6 but not BIOS4.  The BIOS5 should include a utility to convert .cdb files to .tcf.

    Summer Xu said:
    I find that after importing the legacy CCS v3 project, .ccxml file of the target configuration should be generated. Why the information of the target is not inherited from the old project?

    Unfortunately in CCSv3 the target information (emulator used, JTAG scan path info...) is not part of the project so it is not something that can be imported and converted into a .ccxml file.  In CCSv3 the target config was stored in the windows registry or exported to .ccs files, however there was no association with a given project.

    Regards,

    John

  • in reply to JohnS
    Prodigy 170 points

    Thank you for your reply.

    You said "The BIOS5 should include a utility to convert .cdb files to .tcf.". Is there any method to convert .cdb files directly to .tcf. Now I have to generate .tcf by creating a new configuration file.

  • in reply to Summer Xu
    TI__Guru**** 162305 points

    There is some information here:

    http://processors.wiki.ti.com/index.php/Migrating_from_BIOS_4.9_to_BIOS_5.x

    Also if you look in the BIOS5 folder in your CCS installation then go to the docs folder there should be a SetupGuide_CCSv3.html   This doc has more info on how to use the cdb2tcf utility.  If you have further questions on using it your best bet is the BIOS forum.

    Regards,

    John