Vissim Code Composer Studio Plug-in not installed

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Submitted by djobrien51 on Fri, 06/17/2011 - 19:48 


In the Embedded Controls Developer Users Guide v8.0 (EmbeddedControlsDeveloper_UGv80.pdf) under the section 'Using the VisSim Code Composer Studio Plug-In' a procedure is described to '...create a [CCS] project that contains all the necessary files (.CMD, .LIB, and generated .C file from VisSim) to successfully build an .OUT file from the code composer environment.'

The menu item to select in CCS v4, 'Tools>VisSim>Create VisSim Project' doesn't exist in my CCS [Eclipse] installation.

Apparently, even though I installed CCS v4 first and then VisSim 8.0, the required CCS [Eclipse] plug-in never got installed.

Is there a way to post install plug-in, and why didn't it get installed correctly?

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    Submitted by Anders89 on Mon, 06/20/2011 - 10:36.

     

    For CCS v4 & v5, you must add the generated C-file, linker .cmd file, libraries and preprocessor definitions by hand, but it's not hard. To do so, choose Project > Properties > C/C++ Build
    For Piccolo, Delfino, and F280x, under C2000 Compiler add the following Predefined Symbols:
    _DSP
    _F28XX_
    _F280X_

    Under Include Options add the following to Add Dir to #include search path
    '\vissim80\vsdk\include'
    '\vissim80\cg\include'

    Under C2000 Linker > File Search Path add the following to Include Library or command file as input:
    '/vissim80/cg/lib/ii_F280X_fpu.lib'
    or, if the target does not have hardware floating point unit:
    '/vissim80/cg/lib/ii_F280X.lib'

    Under C2000 Linker > File Search Path add the following to Add <dir> to library or command file as input:
    '/vissim80/cg/lib'
    '/vissim80/cg'

    For linker .cmd file, add the proper file for your target from /vissim80/cg/lib. The .cmd file will have the name <target>lnk.cmd for RAM linkage and <target>Flnk.cmd for flash linkage. For example, the F28069 flash cmd file is called F28069Flnk.cmd.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    Submitted by DavidTWarner123 on Mon, 04/22/2013 - 17:58.

     

    Issues exporting a Vissim 8.0 project to a C file, and builing with Code Composer Studio v5

    I am running Vissim version 8.0C0 - target processor TI2806 I would like to take this same project (the exported .C file), bring into Code Composer 5.0, and build it.

    I found a forum regarding this topic (forum entitled: /vissim_code_composer_studio_plug-_not_installed)

    I have done all the proper steps that were listed in the forum, built my project from Code Composer 5, but I am getting several errors: Here's an example of one group of them:

     #145 a value of type 'ARG_DESCR *' cannot be used to initialize an entity of type 'CGDOUBLE' #145 a value of type 'DATA_FILE_INFO *' cannot be used to initialize an entity of type 'XFERFUN_INFO *' #145 a value of type 'int' cannot be used to initialize an entity of type 'ARG_DESCR *'  #145 a value of type 'int' cannot be used to initialize an entity of type 'CGDOUBLE *'   #145 a value of type 'int' cannot be used to initialize an entity of type 'IVECTOR *' #145 a value of type 'int' cannot be used to initialize an entity of type 'TIME_DELAY_INFO *' #145 a value of type 'int' cannot be used to initialize an entity of type 'VECTOR *' 

    Q1. In regards to the original Vissim project, when I export the C file, are there any specific steps I need to do? Q2. In regards to the errors listed above, is there an include file or DLL or any other type of file that I am currently not including that would initialize the values properly (ex. CGDOUBLE, ASG_DESCR, etc). Q3. In regards to Code Composer 5, am I missing any other link paths, include libraries, etc?

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    Submitted by Senad H. on Mon, 01/12/2015 - 17:02.

    Hello,

    I am new VisSim user. I have VisSim v8, CCS v4.2.4 and TI Experimental kit with Concerto controller F28M35H52C. I installed CCS first and then VisSim/ECD. I am connecting TI Experimental kit to PC. Then, I am running Vissim and I am selecting the Concerto example Embedded->Examples->Concerto->blink28M3H52. After, VisSim->Tools->Code Gen->Compile, I have next messages:

    'error: cannot find file 'blink28M3H52.obj''
    'error: unresolved symbols remain' 'error: errors encountered during linking; 'blink28M3H52.out' not built'

    I saw above instructions, and I am added the generated C-file, linker .cmd file, libraries and preprocessor definitions by hand, but I get same messages. Please, Can you help me?

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

     

    Submitted by pete on Tue, 01/13/2015 - 21:24.

     

    Dear Senad, Please send us a copy of the text in the DOS compile window.
    You might consider using the latest CCS v6. It is free and may be required for the F228M35.