Generating tcf files in CCS5.1

Oscar Herranz

Other Parts Discussed in Thread: OMAP3530, SYSBIOS

Hi guys!!

First of all, I apologize because to write in a wrong forum...Now, I tell you my problems&doubts

I have uptaded the new version of CCS for Linux, specifically the version 5.1. I am working with omap3530 (multi-core platform -->ARM+DSP) and I want to develop one application for twice cores. Also, I will use the DSPBIOS like operating system for DSP. I have some questions about this procedure:

1.Reading documentation about this topic and the generation the .tcf files I have seen that in previous versions of CCS(for instance v3.3) there was other methods with graphical interface, about how to generate a *cdb file (DSPBIOS Configuration). In the new version of CCS the user has only the option to generate a .tcf file. Where is the graphical interface? How is the procedure in the new version to configure the operating system for DSP?

2.Also, in earlier versions, once the .cdb file is modified, saved and added to the project, the configuration manager will create and load, between others, the following files(according my docs):

-nameoffile_cfg.s62 (assembly file)

-nameoffile_cfg.h62 (header file for assembly)

This files, in new version of CCS, is not generated automatically when I save and compile the project. Now, I create a new project CCS, choose the DSP(C64+ for me) and the kind of output (executable) but when I compile the project this files not exist!! For this reason, when I debugging by means emulator, the window of CCS writes the next message: "file not found: namefile.s62" or something similar.I have seen the environment of CCSv3.3 and this files are in a folder called Generated Files...Where are this files in the new version? Maybe this topic is related with to select the family of DSP in the initial configuration(C64+ or C6000)? I do not know why happens that..

3.Lastly, also is needed to add other file with extension .cmd for OMAP3530. This file is used in order to link .c programs (Is it right?) Where can I find this file? Or download it?

Sorry, so many questions..Advices & suggestions please!! Thanks in advance!!

Óscar Herranz

over 13 years ago

0 Steven Connell over 13 years ago

TI__Mastermind 45025 points

Hi Óscar,

It sounds like you were using DSP/BIOS 5.x (or earlier) before. Which version of BIOS are you using now? Is it SYS/BIOS 6.x?

Thanks,

Steve

0 Sasha Slijepcevic over 13 years ago

TI__Mastermind 37985 points

Oscar Herranz said:

I have uptaded the new version of CCS for Linux, specifically the version 5.1. I am working with omap3530 (multi-core platform -->ARM+DSP) and I want to develop one application for twice cores. Also, I will use the DSPBIOS like operating system for DSP. I have some questions about this procedure:
1.Reading documentation about this topic and the generation the .tcf files I have seen that in previous versions of CCS(for instance v3.3) there was other methods with graphical interface, about how to generate a *cdb file (DSPBIOS Configuration). In the new version of CCS the user has only the option to generate a .tcf file. Where is the graphical interface? How is the procedure in the new version to configure the operating system for DSP?

Oscar,
it seems you moved from WIndows to Linux. The graphical interface for DSP/BIOS 5 is an executable, which as far as I know, was never ported to Linux. Since the latest version of BIOS, SYSBIOS 6, is using a different graphical interface, there are no plans to port DSP/BIOS 5 GUI to Linux. If you want to configure DSP/BIOS on Linux, you'll have to use textual configuration.

There are also other differences between DSP/BIOS 5 and SYS/BIOS 6. One of the differences is that the names and the extensions of the generated files changed. Once you answer Steve's questions from the previous post, we'll be able to tell you how you can configure your app.

0 Oscar Herranz over 13 years ago in reply to Steven Connell

Intellectual 770 points

Thanks for your answer Steve!

I am using the DSP/BIOS 5.41 with Linux like OS..I expect your suggestions!!

Regards

Óscar Herranz

0 Sasha Slijepcevic over 13 years ago in reply to Oscar Herranz

TI__Mastermind 37985 points

Oscar,
if you are using DSP/BIOS 5 on Linux (or something similar that can run CCS 5 but it's not Windows), you'll have to use Text Editor to configure DSP/BIOS. I posted a link to the Tconf User Guide in my previous post.
You build projects in the same way you would if you configure them using the GUI, right click on the project and then Build Project. If you don't get any errors, the files that you expect to be generated are under Debug or Release tree in your project view. If these files are not generated, your build might have some errors and you should be able to see such errors in the build dialog window.

As for your questions about link.c, what is that file? Is that your source file, and why does it require a custom linker command file?

0 Oscar Herranz over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thanks for your answer Sasha!

According your answer, I understand that the files (with extension .s62 and .h62) have to be under Debug or Release tree. If they are not under this folder, I should be have to look for mistakes in build dialog window, ... independently of the DSP family ( I am working with C64+x family). In earlier tests, I got to generate the .out for DSP successfully but this files was not in this folder...I checked again!!

As for my question about link.c, I was talking about the .cmd file. I have read in DSPBIOS documentation that there is to add a file with extension .cmd to the project in order to link the .c files but I want to be sure. For this reason, I wonder where can I obtain this file (.cmd)? Is it necessary for the project? Thanks in advance

Óscar Herranz

0 Sasha Slijepcevic over 13 years ago in reply to Oscar Herranz

TI__Mastermind 37985 points

Oscar Herranz said:
As for my question about link.c, I was talking about the .cmd file. I have read in DSPBIOS documentation that there is to add a file with extension .cmd to the project in order to link the .c files but I want to be sure. For this reason, I wonder where can I obtain this file (.cmd)? Is it necessary for the project?

A linker command file is generated together with other files and usually you don't have to create one. There is a config parameter MEM.USERCOMMANDFILE, which you can set to 'true' if you want to use your own linker command file. However, the default for that parameter is 'false', and unless you change it, the build will use the generated linker command file.

0 Oscar Herranz over 13 years ago in reply to Sasha Slijepcevic

Intellectual 770 points

Thanks for your help Sasha!! In previous posts, I talked about the generation of the files with extension .s62 or similar using DSPBIOSv5.41 in CCSv5.1 (Linux OS). These files are generated under Debug or Release tree in project view, but I use a makefile in order to build the executable for DSP so that when I build the project I obtain the next files in a diferent folder (according to my makefile structure).

ExampleDSPBIOS.cdb ExampleDSPBIOScfg.cmd ExampleDSPBIOScfg.h62
ExampleDSPBIOScfg_c.c ExampleDSPBIOScfg.h ExampleDSPBIOScfg.s62

I have doubts about if someone of this files must be included to project on CCSv5.1 in order to work ok. Rigth now, all these files are in other folder out project's structure. Do I have to add one file/all files under Debug tree? Suggestions please!!

Thanks in advance

Óscar Herranz

0 Sasha Slijepcevic over 13 years ago in reply to Oscar Herranz

TI__Mastermind 37985 points

If you are building your app using your own makefile, then it's up to you to decide where those files should be. You just have to include the generated files in your compiler and linker command lines. Now, if I understand correctly your first post, the problem is that debugger doesn't know where those files are. Since you are using your own makefile, and not building code as a CCS Project, there is no need to copy files under 'Debug' because that will not make the debugger find the files.

I am guessing you are compiling without -g. In that case, when you get the message that a file cannot be found, that dialog should give you the option of searching for the sources on your own. Can you try that?

You can also try adding -g flag and see if that helps debugger find the source files.

Processors

Processors forum

Generating tcf files in CCS5.1