Command Line Error - Missing Source File Name

Lee,

There is an extra "" at the end of each of the build commands.  This is what the compiler is complaining about.  My bet would be that there is a macro in the build options that is not defined so it gets inserted into the build command as a blank string.  Does your project use some macros in the build options maybe something for 55x CSL directory.  If so make sure to define these macros on the macro tab of the build options dialog.

Regards,

John 

John

Below describes the hello project build settings and properties:

Build Properties:

Basic Options --> v5505, Full Symbolic Debug (--symdebug:dwarf,-g) no optimizations

Include Options --> "${CG_TOOL_ROOT}/include" "${PROJECT_BUILD_DIR}" "${BIOS_INCLUDE_DIR}" "${RTDX_INCLUDE_DIR}"

Runtime Model Options: --> Use large memory model

Tconf Script Compiler: --> Configuration import path --> "${BIOS_CG_ROOT}/packages"

Build Settings: --> ${CCE_INSTALL_ROOT}/utils/gmake/gmake -k

Macros --> BIOS_CG_ROOT, BIOS_INCLUDE_DIR, BIOS_LIB_DIR, BuildArtifactFileBaseName, BuildArtifactFileExt, BuildArtifactFileName

Macros cont'd --> BuildArtifactFilePrefix, Builder Version, ConfigDescription, ConfigName, PROJECT_BUILD_DIR, PROJECT_ROOT

Macros cont'd --> RTDX_INCLUDE_DIR, RTDX_LIB_DIR, TargetArchList, TargetOsList, ToolChainVersion, XDC_CG_ROOT

CCS Build Settings: --> Device Variant --> TMS320C55XX,TMS320C5505 DSP/BIOS version --> 5.40.03.23

Debugger --> Connect to exact CPU --> Texas Instruments XDS 100 USB Emulator_0/C55xx [TMS320C55X]

Project Tree --> hello, Includes, Debug, std.h, hello.c, hello.ccxml [Active], hello.tcf

hello.ccxml --> Texas Instruments XDS 100 USB Emulator --> USBSTK5505

hello.tcf --> utils.loadPlatform("ti.platforms.ezdsp5505"); bios.enableRealTimeAnalysis(prog); bios.enableRtdx(prog); bios.enableTskManager(prog);

hello.tcf cont'd --> bios.LOG.create("trace"); bios.HST.HOSTLINKTYPE = "NONE"; bios.RTDX.ENABLERTDX = 0; prog.gen();

The project is shown as a RTSC project even though I did not select RTSC for the project.

I interpreted the "" at the end of the build cycle where the error was generated as missing the hellocfg.s55 file since the build used hellocfg.s?? as input to that build cycle and that the following "" represented the results of missing the hellocfg.s55 file since the build specified the -k option resulting in continuation of the build after the error was detected.

Thanks

Lee

Lee,

Good point that "" is matching up with the source file name location.

The project ends up being a RTSC project as even BIOS5 uses RTSC to build under the hood.

I have one of those sticks so I will give the same project a try.  Did you happen to rename the project or the config file at any time?

John

Wow the formatting was horrible for that post I am going to recreate it.  Sometimes these forums drive me nuts.

Lee, I created a hello project for 5505 using BIOS5. I tried to use the same names as you used. It builds ok for me and I have "hellocfg.s55" at the end of that build command

'Building file: hellocfg.s55'

'Invoking: Compiler'

"C:/Development Tools/Programs/Code Composer Studio v4.1.0 RTM/ccsv4/tools/compiler/c5500/bin/cl55" -v5505 -g --include_path="C:/Development Tools/Programs/Code Composer Studio v4.1.0 RTM/ccsv4/tools/compiler/c5500/include" --include_path="C:/Development Tools/Workspaces/4.1RTM/hello/Debug" --include_path="C:/Development Tools/Programs/Code Composer Studio v4.1.0 RTM/bios_5_41_02_14/packages/ti/bios/include" --include_path="C:/Development Tools/Programs/Code Composer Studio v4.1.0 RTM/bios_5_41_02_14/packages/ti/rtdx/include/c5500" --diag_warning=225 --ptrdiff_size=16 --memory_model=large --preproc_with_compile --preproc_dependency="hellocfg.pp"  "hellocfg.s55"

'Finished building: hellocfg.s55'

Here are the exact steps that I went through to create my project:

1. File -> New -> CCS Project 
2. Called it hello, selected C5500 as the project type 
3. Selected TMS320C5505 as the device variant and selected BIOS 5.41 as my BIOS 
4. Finished with the wizard 
5. Right clicked on my project and selected New -> DSP/BIOS 5.xx Configuration file, used the default name (hello.tcf) 
6. selected the ezdsp5505 as the platform, clicked next and then clicked finish. Tcf editor opens but I just moved it to the side for now 
7. created a new source file called hello.c 
8. typed h and hit CTRL-SPACE, selected hellobios5 from the little popup window to insert the BIOS5 hello world template 
9. saved the file 
10. went back to the tcf editor, expanded instrumentation, selected LOG and right clicked and inserted a new log and called it "trace" 
11. saved the tcf file 
12. built my project 

Regards,

John

John

I followed the procedure you followed when creating and building the hello project.

I received a Refresh Message Box with the following message: An internal error occurred during: Refresh I remember seeing this message before but dismissed the message box and continued. This may be my problem. This message appeared immediately after creating the DSP/BIOS 5.xx Configuration file.

The following are differences between your CCS and CCS Tools and mine:

My CCSv4 is version 4.0.0.1600 as received with the USBSTK5505, liscenced only for use on USBSTK5505, my bios is version 5_40_03_23, my ptrdiff_size=32, I also get --ptrdiff_size=32, --fp_reassoc=off. I occasionally get timing skew warnings during the build.

Thanks

Lee

Lee,

If you go to the Project view and expand the \Debug folder are the following files present:

hellocfg.h

hellocfg_c.c

hellocfg.s55

hellocfg.cmd

These are all files that are generated when the .tcf file is "built".  If these files are not present then it would lead to the compile errors you were seeing.  That "Refresh" error could be related to a problem with generating the files.  I will check with one of the BIOS guys on that.

I am running CCSv4.1.0 however I don't think much changed in this area.  Could UAC on Vista or Windows7 be blocking the creation of these files?  Perhaps it is an admin priv issue?

Regards,

John

John

The hello3 project generated the following config files: hello3cfg.h, hello3cfg_c.c, hello3cfg.s55, hello3cfg.cmd, hello3cfg.h55.

hello3.cdb, makefile, objects.mk, sources.mk, and subdir.mk were also inside the debug directory.

Lee

Lee,

I am trying to get some others to look into this as well.

1. Does hello3 have the same problem as the first project?
2. What version of windows do you have?
3. If Win7 or Vista is UAC on?

John

John

I have Microsoft XP Professional.

I tried another hello project (hello4) that uses the sample hello.c source that uses the printf function in the main function instead of the LOG_printf function that includes the hellocfg.h generated header file. I tried the LOG_printf version in a hello5 project that included the hello5cfg.h as an included generated header.

The hello5 project had the same settings as the hello4 project (Device Variant --> TMS320C5505, Linker Cmd File --> lnkx.cmd, Runtimesupport Library --> rts55x.lib, DSP/BIOS 5.40.03.23 except using the LOG_printf function in the hello5 project and the printf function in the hello4 project and using hello5cfg.h in the hello5 project instead of no hellocfg.h for the hello4 project.

The hello4 project went through the build and debug processes and produced the hello world output. The hello5 project has the same problem as the hello3 project - "could not open source file "hello5cfg.h".  I had deleted the hello3 project after I generated the hello4 project.

The target configuration in all cases was the USBSTK5505 as the Texas Instruments XDS 100 Emulator.

In the process of generating and trying to build the different hello projects, I lost the ability to build projects. I had to delete the .metadata file to do a clean of the CCS4. After launching CCS4 and importing the projects, I was able to build projects again.

Thanks

Lee

Hi

I got the same error ("Command-line error: missing source file name" on the DSP/Bios file compilation), but on a C64x+ architecture.

It appeared that it was a problem of directory. My source files and DSP/Bios configuration file are located in a subdirectory named "src".

The compiler try to compile the s62 file in "Debug/src" directory whereas this file is in "Debug" directory. Same thing for **cfg_c.c file.

I moved the DSP/Bios configuration file to the root directory of the project, and compiled ok.

This seems to be a bug !

Pascal

Hi Pascal,

I uploaded a printscreen of my ez-dsp Workspace Folder on the previous post.

I reworked my hello4 project that was able to build with the printf function instead of the LOG_printf function. I used the LOG_printf function and the generated hello4cfg.h as an include to the c souce. The following are the results:

**** Build of configuration Debug for project hello4 ****

C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all

'Building file: ../hello4.tcf'

'Invoking: TConf Script Compiler'

"C:/Program Files/Texas Instruments/xdctools_3_15_03_67/tconf" -b -Dconfig.importPath="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages"; "../hello4.tcf"

'Finished building: ../hello4.tcf'

' '

'Building file: ../hello4.c'

'Invoking: C5500 Compiler'

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/bin/cl55" -v5505 -g --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/include" --include_path="F:/ez-dsp Work Folder/hello4/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/rtdx/include/c5500" --diag_warning=225 --sat_reassoc=off --ptrdiff_size=32 --fp_reassoc=off --memory_model=large --asm_source=mnemonic --preproc_with_compile --preproc_dependency="hello4.pp" "../hello4.c"

'Finished building: ../hello4.c'

' '

'Building file: hello4cfg.s??'

'Invoking: C5500 Compiler'

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/bin/cl55" -v5505 -g --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/include" --include_path="F:/ez-dsp Work Folder/hello4/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/rtdx/include/c5500" --diag_warning=225 --sat_reassoc=off --ptrdiff_size=32 --fp_reassoc=off --memory_model=large --asm_source=mnemonic --preproc_with_compile --preproc_dependency="hello4cfg.pp" ""

Hi,

I have a c5505 ezdsp tool. I am using the audio filter demo code from the googlecode website. I chose sampling rate to be 12 KHz and 64 point FFT. I need to log some FFT values. printf() was not working properly and Tommy G said the following

"On the issue of printf(), I believe that the reason you are seeing playback problems is because printf() is a very heavy burden on an embedded processor that is doing real-time operations.  A better choice if you need to send messages while your audio application is running is to use the LOG-printf() feature available in DSP/BIOS for the DSP.  This is a specially designed communications method that has very low overhead and should not impact your real-time performance.  DSP/BIOS is included in your Code Composer Studio installation."

Can someone give a  step by step guide to how to set up DSP bios and use LOG-printf? I right clicked on the project name and clicked on "New DSP/BIOS v5.xx Configuration File", selected my platform ti.platforms.ezdsp5505, checked real-time-analysis,RTDX,TSKmanager and clicked finish. But if I try to build the same audio filter project after this

'Building file: VC5505 FFT Filter Democfg.s??'
'Invoking: C5500 Compiler'
"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/bin/cl55" -vcpu:3.3 --symdebug:coff --define="_DEBUG" --define="C55X" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/emulation/boards/usbstk5505/tests/fft/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/rtdx/include/c5500" --diag_warning=225 --sat_reassoc=off --ptrdiff_size=32 --fp_reassoc=off --algebraic --no_mac_expand --memory_model=huge --asm_source=algebraic  --preproc_with_compile --preproc_dependency="VC5505 FFT Filter Democfg.pp" ""
Command-line error: missing source file name
1 fatal error detected in this compilation.
Compilation terminated.

>> Compilation failure
C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [VC5505 FFT Filter Democfg.obj] Error 1
'Building file: VC5505 FFT Filter Democfg_c.c'
'Invoking: C5500 Compiler'
"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/bin/cl55" -vcpu:3.3 --symdebug:coff --define="_DEBUG" --define="C55X" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c5500/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/emulation/boards/usbstk5505/tests/fft/Debug" --include_path="C:/Program Files/Texas Instruments/bios_5_40_03_23/packages/ti/rtdx/include/c5500" --diag_warning=225 --sat_reassoc=off --ptrdiff_size=32 --fp_reassoc=off --algebraic --no_mac_expand --memory_model=huge --asm_source=algebraic  --preproc_with_compile --preproc_dependency="VC5505 FFT Filter Democfg_c.pp" ""
Command-line error: missing source file name
1 fatal error detected in this compilation.
Compilation terminated.

>> Compilation failure

Hi JohnS,

I ran you axample on two different CCS versions.

On Version 4.0.0.16000 it compiled just fine (using large memory model).

On Version 4.1.3.00038 (on another xp machine through) it fails with the same error (also using large memory model):

-preproc_dependency="hellocfg.pp" ""

EDIT3: If I create the project with the newer CCS in the mitigated workspace. It also works. Can this be related to the work space then???

Stefan,

Yes it could be workspace related.  Specifically a macro/path that is defined in the workspace is undefined in the workspace where you are getting the build error.

For migrated projects there are typically a lot of macros used in the include options.

John

Stefan,

Unfortunately Eclipse workspaces are not really meant to be shared.  Projects can be shared though.  I believe there is an SVN plug-in for Eclipse 3.2 that you can use.

John

hello.cmd file is missing in ccs 5 directory how to get it.