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

6418EVM ccs 3.3 examples: port to css 5.2

Alberto Biancalana
Intellectual 380 points
Other Parts Discussed in Thread: CCSTUDIO

Hi, I'm just starting to work with 6418EVM and also starting to work with CCS 5.2. I have no previous experience of CCS. I need to import to ccs5 the EVM6418 examples in the Spectrum Digital site, to check the board. I use the Legacy CCSv3.3 import option and this doesn't work.

In the migration log I have these warnings that i can solve by removing the -ml3 compile option in the original pjt file:

!CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.C6000.Debug.1702011948' [Thu Oct 04 13:08:40 CEST 2012]  !TOOL: 'com.ti.ccstudio.buildDefinitions.C6000_7.3.exe.compilerDebug.320281555'   !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C6000_7.3.exe.compilerDebug.320281555::-ml3 !CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.C6000.Release.94709594' [Thu Oct 04 13:08:40 CEST 2012]  !TOOL: 'com.ti.ccstudio.buildDefinitions.C6000_7.3.exe.compilerRelease.1358856819'   !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C6000_7.3.exe.compilerRelease.1358856819::-ml3   

But the real problem is that the debug build does nothing, and the release build don't work because of this error:

 --preproc_with_compile --preproc_dependency="ledprd.pp"  "../ledprd.c" "../ledprd.c", line 36: fatal error #5: could not open source file "ledprdcfg.h"

As far as I understand now the .cmd file should have been invoked to create the missing header file and other files but this doesn't happen.

I searched around but I'm really not able to understand where is the problem and if similar to this one have been reported.

Could anyone address me about this?

 

Thank You very much.

 

Alberto

  • 0
    TI__Guru**** 474421 points

    Hi Alberto,

    Alberto Biancalana said:
    I need to import to ccs5 the EVM6418 examples in the Spectrum Digital site, to check the board. I use the Legacy CCSv3.3 import option and this doesn't work.

    If you just want to get your 3.3 project working with v5, I would suggest you use the v3.3 compiler with v5. You can tell v5 to use it via:

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

    That way you don't have to deal with the deprecated/removed option in the newer compiler and other build migration issues.

    In the meantime, a small test case would be helpful to see why your project is not building with the new compiler

    Thanks

    ki

  • 0
    TI__Guru**** 171349 points

    Alberto,

    These projects were created for CCSv2.2/3.1, therefore the import tool does not properly recognize the old DSP/BIOS configuration file in these projects (extension .cdb).

    One step for that to work, is the BIOS confguration file will need to be converted to a more recent version of DSP/BIOS (5.3, which was used by CCSv3.3) and then imported to the tool.

    Please check the appendix A.3 of the DSP/BIOS 5.40 Tconf User's Guide (SPRU007).

    Just for your reference, I did the conversion in the command line and show at the end of this post.

    Hope this helps,

    Rafael

    CDB_conversion said:

    Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\ti\Boards\evm6418\examples\led>set BIOS_INSTALL_DIR=c:\ti\bios_5_41_13_42

    C:\ti\Boards\evm6418\examples\led>\ti\bios_5_41_13_42\packages\ti\bios\config\update\cdb2tcf led.cdb

    Application: led.cdb
    Original seed file: c:/ti/bios_5_41_13_42/packages/ti/bios/config/update/4.90.270/c64xx.cdb
    Loading application CDB file
    Device name: DM642
    Catalog: ti.catalog.c6000
    Generating CSL files
    Unloading the application CDB file
    Loading original seed: c:/ti/bios_5_41_13_42/packages/ti/bios/config/update/4.90.270/c64xx.cdb Finding user changes
    Loading new seed file
    New seed: c:/ti/bios_5_41_13_42/packages/ti/bios/config/cdb/c64xx.cdb
    Applying changes
    Warning: Field CSLNAME no longer exists in cdb file.
    Saving original led.cdb in led.cdb.Thu_Oct_04_09.55.05_2012
    Creating TCF file: C:/ti/Boards/evm6418/examples/led/led.tcf
    Tconf search path information is required for running the generated tcf file. The search path info for the Tconf.exe command line has been saved in tcfopts.dat.

    C:\ti\Boards\evm6418\examples\led>

     

  • 0 in reply to desouza
    Intellectual 380 points

    Rafael, thanks for your help.

    I did everithing (I dont'have the c:\ti\boards directory inside my ccs, I worked on the directory where I unzipped the spectrum digital examples) but the process don't complete for an error:

    Application: ledprd.cdb Original seed file: d:/ti/bios_5_41_13_42/packages/ti/bios/config/update/4.90.27 0/c64xx.cdb Loading application CDB file Device name: DM642 Catalog: ti.catalog.c6000 Generating CSL files Unloading the application CDB file Loading original seed: d:/ti/bios_5_41_13_42/packages/ti/bios/config/update/4.90 .270/c64xx.cdb Finding user changes Loading new seed file New seed: d:/ti/bios_5_41_13_42/packages/ti/bios/config/cdb/c64xx.cdb Couldn't open d:/ti/bios_5_41_13_42/packages/ti/bios/config/cdb/c64xx.cdb Error code 25

    I have seen other posts on this issue of the c64xx.cdb file missing.

    There are many c64xx.cdb files in the update.zip file located in \ti\bios_5_41_13_42\ packages\ti\bios\config\update, but for different versions and with different dates (and, I think different contents) and one is already present in the bios_6_33_05_46 directory.

    Should I copy the  bios_6_33_05_46 directory version inside \ti\bios_5_41_13_42\ packages\ti\bios\config\cdb ? or what do you suggest?

    Thanks

    Alberto

     

  • 0 in reply to Alberto Biancalana
    TI__Guru**** 171349 points

    Alberto,

    Is your CCS install directory under D:\ or C:\? The error message says it can't find the c64xx.cdb file, but it indicates the D:\ drive.

    Also, did you check if the c64xx.cdb is under the directories mentioned above? You shouldn't need to copy anything anywhere (I have the same BIOS version as you and all the files).

    I am pretty sure you already did this, but the first step required is to set the BIOS_INSTALL_DIR environment variable (the tool asked for it).

    Apart from this I am not sure what may be happening in this case; the only thing different is the drive letter (I have everything on C:\ drive) - maybe you could try to copy the entire bios to the C:\ drive and see if you can conver this...

    Also, after converting the .tcf file you will have to modify the .pjt file to point to the .tcf instead of the original .cdb. Simply open the .pjt file in a text editor, locate the entry [Source Files] and change the name of the .cdb file listed there.

    Also, delete the original <ledcfg.cmd> file as it will throw errors during build.

    You will also need to download the C6418 CSL library, which used to be shipped with CCS2.x and 3.x, install it and add some configurations to the Build options:

    - The imported project already creates a build variable for the CSL include and lib directories, therefore simply add a Build Variable named C6000_CSL_CG_ROOT: right-click on the project --> Properties --> Build --> tab Variables --> select the button Add and then type C6000_CSL_CG_ROOT as Variable name and the path to the installed CSL directory in the field Value.

    - If you expand the tree under the Build entry then go to C6000 Compiler --> Include Options, you will see an entry to this Build variable in the top box

    - In the expanded tree under Build, select C6000 Linker --> File Search Path and then add the required library cslDM642.lib to the top box (don't ask me why they used the DM642 library, I really have no idea). In the bottom box edit the entry "{C6000_CSL_CG_ROOT}/lib", and modify it to list "{C6000_CSL_CG_ROOT}/lib_3x" - the correct directory name.

    That should help you get going.

    Some of these steps are required due to the fact the project was created with an older version of CCS.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 380 points

    Hi Rafael.

    Thanks for all the infos, they really make me enhance my currently low understanding.

    In this reply I answer to your question, in the next I will give you results.

    Yes my ccs 5 is installed in D: because this is suggested in the install manual for Windows (at least it is for 5.1 which is the first version I installed). 

    So it's ok, the procedure searches the file in the right place.

    I set BIOS_INSTALL_DIR=d:\ti\bios_5_41_13_42 (I have here the msdos window still open) and this should be ok.

    The c64xx.cdb file don'exist where it should be.

    The strange thing is that also in the 5.1 version, installed from TI dvd, the file didn't exist and for this reason I fully uninstalled 5.1 and installed 5.2 from internet (thinking about problems in the dvd setup).

    So I really need a c64xx.cdb file to proceed...... I'll give a try copying the 6.x one, or I don't know what to do.

    BTW: is it possible to copy everything on C: and make ccd run there, without having problems?. Shouldn't I reinstall everything on C:?

    Alberto

  • 0 in reply to Alberto Biancalana
    TI__Guru**** 171349 points

    Alberto,

    Not sure what may be happening in your install, but it is possible you selected just a few device families during install - not sure, though.

    You can either reinstall CCSv5.2.x in C:\, download and install the standalone BIOS5.41.13.42 (link here) or use the attached <c64xx.cdb> file from my BIOS 5.41.13.42. This file is different than the one under bios_6.x directory and should be copied to the directory of the missing file indicated in the output you sent earlier.

    If you plan to install the standalone BIOS, keep in mind there are several dependencies (XDC, IPC, etc.) that require install - if unsure, reinstall CCS.

    Copy CCS from one directory/drive to another may lead to problems. I wouldn't do it.

    Cheers,

    Rafael

     

     

     

    c64xx.rar
  • 0 in reply to desouza
    Intellectual 380 points

    Thanks Rafael, using your file the conversion worked and ccd 5 imported the project.

    At first sight in the ccs GUI the custom modifications in the tcf reflect the example code.

    There are still build problems due to missing CSL and build variables, as you anticipated, but a first step is done.

    I complete this thread and I'll open another if I have problems with the remaining part of the work.

    Tomorrow I'll reinstall ccs 5.2 on c: to be quite sure that the missing cdb file problem is an accident.

    it is strange that I selected only a few device families: it has been a full install, and the only unchecked boxes was for boards I was not interested in (I kept only TI and Spectrum Digital EVMs). I'll take care of this in the new install.

    Thanks so much

    Alberto

  • 0 in reply to desouza
    Intellectual 380 points

    Ok, I reinstalled CCS V5.2 on C: and  c64xx.cdb reappeared in the right folder. 

    Misteries of install and Windows.

    Then I again made the full conversion procedure via command line and all worked fine. 

    Now I'm going to resolve the build problems you anticipated.

    Thanks

    Alberto

  • 0 in reply to desouza
    Intellectual 380 points

    Rafael, your help has been invaluable.

    I followed exactly your instructions and now both release and debug builds complete with no errors.

    Thank you so much.

    Alberto