code composer 3.3 with LabView

[diko]

Does anybody konw how to change a set-up of Labview to invoke Code Composer 3.3 ?

I have the following error with autotest.

Failed to build executable!
Error code: 3
Error source:
System Exec.vi. Command was "C:\CCStudio_v3.1\plugins\bios\gconfgen "embedded.cdb" "

 I changed "Makefile" and "Makefile.sub.mk", but this doesn't help.

Thanks,

[Hillman]

Hi Diko,

Thanks for the post!

I see you've not had any system thus far.

Does this command work in the windows cmd?

Kind Regards,

[diko]

I am a beginer for a Labview,  but I am familar with Ptolemy project(UC Berkeley).

Currently, I am porting "Microprocessor SDK" on DM3xx(TI, ARM9 core) with PrOS(ITRON) operating system.

But, I will use TI's code composer for compiler/linker.

For the first step, I downloaded Labview 8.6 and Embeded Module and try to test an existing DSP/BIOS target with Labview 8.6 to check how a Code Composer compiler/linker are called by Labview 8.6.

My current version of CC Studio is 3.3. I searched the whole sub-directories under "National Instruments" folder and found several Makefiles and Makefile.sub.mk containing  "CCStudio_v3.1". I changed paths to "CCStudio_v3.3" within those files. But this doesn't help.

Please point me a right direction for this task.

Dongik Ko

Software Engineer

Texas Instruments Inc.

[diko]

I just followed "Testing Your Target Implementation" from Microprocessor SDK Porting Guide" and did "Tools»Microprocessor SDK»Run C Generator Tests" for Embedded:DSP/BIOS:DSK6713 Application without making anew project.

[Hillman]

Hi,

Thanks for the reply and I hope your well today. 

I was going to suggest the guide - did it work?

Could clearly explain your exact question - finding it hard to pick it out?

And the image didn't work!

Kind Regards,

[diko]

Let me simplify my question.

I want to know how to call "C:\CCStudio_v3.3" compiler/linker for generating execution file for ARM9.

LabView 8.6 is now accessing "C:\CCStudio_v3.1".

I don't know how to change a configuration for using "C:\CCStudio_v3.3".

Thanks,

 Dongik Ko

[Hillman]

Hi Dongik Ko,

Thanks for the clarification. 

If you install Code Composer Studio somewhere other than c:\CCStudio_v3.1, which is the default location, you must change the Compiler path and the Linker path in the Build.

This came from the help, maybe trying altering the path?

It seems old the help mentions 3.1, are you sure 3.3 can be used with LabVIEW 8.6?

Kind Regards

[diko]

I am not sure if LabView 8.6 works with "CCStudio_v3.3".

BTW, to change the Compiler path and the Linker path in the Build for "C:\CCStudio_v3.3", which VIs or some other configuration files within LabView 8.6 do I have to change ?

I already changed two files related to "Makefiles" within LabView 8.6 for DSP/BIOS target as below.

"LabView 8.6\Targets\NI\Embedded\dsp_bios\DSK6713\build\analysis\development\build\DSK6713\Makefile"

"LabView 8.6\Targets\NI\Embedded\dsp_bios\DSK6713\Makefile.sub.mk"

export PREFIX = C:/CCStudio_v3.3/C6000/cgtools/bin/ 

It was originally "export PREFIX = C:/CCStudio_v3.1/C6000/cgtools/bin/"

But even after this modification, LabView 8.6 still tries to access "C:CCStudio_v3.1", not "C:\CCStudio_v3.3".

One more thing, is there any way to get LabView 7.1 or 8.2 or something if Labview 8.6 is not compatible with CCStudio_v3.3 ?

Thanks,

 Dongik

[Hillman]

Hi Dongik,

Thanks for the reply. 

Here is some more information:

The Spectrum Digital DSK6713 uses the TI Code Composer Studio toolchain. Install Code Composer Studio from the CD in the DSP Starter Kit. Refer to the DSP Starter Kit (DSK) for the TMS320C6713 (16 Mb) Quick Start Installation Guide on the CD for hardware installation and set up instructions. The quick start guide is available with the DSP Starter Kit. If you install Code Composer Studio in the default location, refer to c:\CCStudio\docs\pdf\manuals_ccs_full_c6000.html for a complete list of related documentation, including how to set-up Code Composer Studio.

If you install Code Composer Studio somewhere other than c:\CCStudio_v3.1, which is the default location, you must change the Compiler path and the Linker path in the Build Specification Properties dialog box for every LabVIEW project you create that uses the Code Composer Studio toolchain.

This was from the LabVIEW 8.6 Microprocessor SDK Help thus I feel you should be okay. But yes, the most recent license entitles you to previous releases of labVIEW. I guess I would suggest contacting your ISR / local NI branch to discuss your options.

Please let me know how you get on, 

Kind Regards