CCS weird error

David Marcus said:

 I have an old version of software and when I directly program it to the DSP the ADC works.  However. if I load the project code into CCS, don't change a thing, recompile build, and then program the DSP, the ADC does not work.

The old version of the software - what version of CCS was used to build it? And do you have the actual project (*.pjt) for it? Is it the same one that you tried to recompile?

Thanks

ki

I believe them to be the same version but the computer that it was originally programmed on died so I had to install it on another one.  I have the actual project still as well.  Yes it is the same one I tried to recompile.

David Marcus said:

I believe them to be the same version but the computer that it was originally programmed on died so I had to install it on another one.  I have the actual project still as well.  Yes it is the same one I tried to recompile.

If you are using the same version of CCS with the same *.pjt + source and same version of the build tools, then there should not be an issue. You can try diffing the *.out files. Try running the ofd2000.exe utility on your *.out files and diff the output (stream the output to a file). ofd2000.exe is located in <CCSv3 INSTALL DIR>\C2000\cgtools\bin. run the utility to get the help for it.

ki

What do you mean * diffing?  It won't let me add a *.  Also when the script is run the command window is filled with stuff but then closes.  Is there a log made somewhere?

I just meant compare the ofd output of the two files. pipe the output to a text file

ex:

> ofd2000 myout.out > myout_ofd.txt

I am having trouble trying to do this.  When I open CMD it starts at C:\users\dmarcus

what do I enter in CMD to get to progrma I need?

David Marcus said:

what do I enter in CMD to get to progrma I need?

inside your command window, browse to the location of your out files

ex:

> cd C:\path\to\my\outfiles

Note: replace 'C:\path\to\my\outfiles' it with the actual path to your outfiles

Then run ofd on your outfiles

> <CCSv3 INSTALL DIR>\C2000\cgtools\bin\ofd2000.exe myout.out > myout_ofd.txt

Note: do not enter '<CCSv3 INSTALL DIR>' but replace it with the actual path of your CCSv3 root directory. Also rename' myout.out' with the name of your first outfile. Rename 'myout_ofd.txt' to some unique name.

repeat above for the second out file.

Thanks.  I got it working.  Now when I I run the out file that works in the program I get this report:

OBJECT FILE: release43.out

Object File Information

File Name: release43.out
Format: TI-COFF Version 2
File Type: executable file
Time Stamp: Tue Oct 09 10:32:47 2012
Machine: TI C2000
Machine Endian: little endian
Entry Point: 0x0033cda8
Vendor: Texas Instruments, Inc.
Compiler Version: 5.0.x
Number of Sections: 81
File Length: 292355
Symbol Table File Offset: 0x0003ff3a
String Table File Offset: 0x000461f2
TI-COFF f_flags: 0x00001183
TI-COFF f_flag: F_RELFLG (relocation info stripped)
TI-COFF f_flag: F_SYMMERGE (debug type information merged)
CPU Generation: 0x8
Control Data Endian: little endian
Start of .text Section: 0x00338000
Start of .data Section: 0x00000000
Size of .text Section: 20743
Size of .data Section: 0
Size of .bss Section: 0

when I run the outfile after it was recompiled this is the report generated:

BJECT FILE: recmp43.out

Object File Information

File Name: recmp43.out
Format: TI-COFF Version 2
File Type: executable file
Time Stamp: Wed Mar 20 11:14:44 2013
Machine: TI C2000
Machine Endian: little endian
Entry Point: 0x0033cda9
Vendor: Texas Instruments, Inc.
Compiler Version: 5.0.x
Number of Sections: 81
File Length: 292047
Symbol Table File Offset: 0x0003fe06
String Table File Offset: 0x000460be
TI-COFF f_flags: 0x00001183
TI-COFF f_flag: F_RELFLG (relocation info stripped)
TI-COFF f_flag: F_SYMMERGE (debug type information merged)
CPU Generation: 0x8
Control Data Endian: little endian
Start of .text Section: 0x00338000
Start of .data Section: 0x00000000
Size of .text Section: 20743
Size of .data Section: 0
Size of .bss Section: 0

The files have not been altered.  Why are some things different?

David Marcus said:

The files have not been altered.  Why are some things different?

It is hard to say. Unfortunately the full compiler version is not given in the ofd output. So we don't know what exact version was used to build the old .out file. Do you have any more details on the exact environment used to build the old out file? I'm looking for:

-Host OS

-Exact CCS version (was it 3.3.82.13)?

-Exact Compiler version

-Exact DSP/BIOS version (if applicable)

I will try and do my best to answer these questions.  The computer this was on died but I have the hard drive.

-The OS was XP i know that

-I think the DSP/BIOS is 5.20.00.06 but i have 3 folders 5.31.02, 5.31.08, and 5.32.02

I have access to the hard drive can you tell me where on the old hard drive I can find the information you need.  Where can I find the CCS version, compiler version, and the DSP/BIOS version that were used? 

David Marcus said:

-The OS was XP i know that

What OS do you have on your new machine?

David Marcus said:

-I think the DSP/BIOS is 5.20.00.06 but i have 3 folders 5.31.02, 5.31.08, and 5.32.02

Does you project use DSP/BIOS? If it does not, then it is a moot point

David Marcus said:

I have access to the hard drive can you tell me where on the old hard drive I can find the information you need.  Where can I find the CCS version, compiler version, and the DSP/BIOS version that were used? 

On the old hard drive, browse to:

C:\Program Files\Common Files\Texas Instruments

There should be a file called ccs_Compdb.ini. Zip it up and attach it to this thread.

Thanks

ki

The new machine is Xp as well.

I do not think I am using the DSP BIOS.

There is nothing in the texas instruments folder

could it be located in the CCstudio_v3.3 folder?

David Marcus said:

There is nothing in the texas instruments folder

could it be located in the CCstudio_v3.3 folder?

No. The location is fixed to the path I mentioned.

Note that when I gave this path:

'C:\Program Files\Common Files\Texas Instruments'

I gave it from the standpoint that the old drive is the system (C) drive. You would need to change the drive letter to whatever your old drive shows up as when you access it now (E? F? etc).

Basically look for the 'Program Files' directory in the root location of the old drive.

David - your last post is blank....

That was really weird .  I said you can see that the folder is blank.  I hope this isn't the only place I can find the information.

That is disappointing. This sometimes happens when there is some corruption with CCS. That file would have told us exactly what version of CCS you have and the versions of all the various plug-ins and tools. That file is the database the CCS uses to maintain.

How many versions can there be to just guess and check?  Can I down grade the versions until I find one that works?  Or Do I now need to modify the ADC to get it to work with the new version?  If so can I post my code on the ADC for you too look at and correct to make it work?

By looking at file version numbers of various components, we can piece back together some information but there will still be a lot of variables. If you are certain that you are not using DSP/BIOS (is the a CDB ot TCF file in your project?) and are certain that you were using the compiler that comes within CCS, you can browse to .CCStudio_v3.3\C2000\cgtools\bin and check the compiler version by looking at the properties of cl2000.exe. At least you can check to see if you are using the same compiler version.

David Marcus said:

Or Do I now need to modify the ADC to get it to work with the new version? 

Honestly this is the best. Use the debugger to see where in your code the issue is occurring and try to diagnose the problem.

David Marcus said:

If so can I post my code on the ADC for you too look at and correct to make it work?

I can't help you too much there as my expertise on the device is limited. The experts in the C2000 forums can help you best.

But i doubt there is any issue with your source code. If you are using the same pjt, source, cmd files as the original working version, then there is no reason why your source would be the issue.

Okay I did what you said.

-I don't think I am using the Bios because that folder is empty in my project.

also I compared the compilers too and they are different.  ONe is v4.1.3 and the other is 5.0.0B2.

Could this be causing my error?

David Marcus said:

also I compared the compilers too and they are different.  ONe is v4.1.3 and the other is 5.0.0B2.

Could this be causing my error?

That is certainly a possibility. Not only is it a major revision difference but your new version is using a beta version of the v5 compiler. Since we don't ship with beta versions of the compiler in CCS, I'm not sure how you got that.

Anyway, let's configure your new v3.3 install to use the same version as the old one. Follow the instructions in the below link to download and install additional compiler versions for CCSv3.3. Make sure you download C2000 4.1.3.

http://processors.wiki.ti.com/index.php/Compiler_Installation_and_Selection#CCStudio_3.x

Thanks

ki

When I use component manager the processor I have to chose is the TMS320C28xx but I am using a TMS320F28335.  Is there s difference between the C and F ones?

I also get this error when I start CCS

I switched the complilers to the older version and I got this error too

>> WARNING: invalid compiler option --float_support=fpu32 (ignored)

I fixed the Gel error

David Marcus said:

When I use component manager the processor I have to chose is the TMS320C28xx but I am using a TMS320F28335.  Is there s difference between the C and F ones?

F has on-chip Flash.

From the component manager's standpoint, there is no different. You can use C28x

David Marcus said:

I also get this error when I start CCS

 

Your setup configuration is pulling in the startup gel file for a 28345 with is odd since you have a 28335. is this intentional? You have an unusual setup.

David Marcus said:

I fixed the Gel error

ah ok. ignore my last post.

David Marcus said:

>> WARNING: invalid compiler option --float_support=fpu32 (ignored)

Sounds like your project build options used a newer compiler option that did not exist. You can ignore as it is a warning. Did you add that in there? I thought you were using the original pjt file that used the older compiler

that's what I thought too.  But at the end of the compile it give me two errors in the program but If I switch the compiler back to the original it compiles just fine.  Also if I use 5.2 the project builds and compiles but the program locks up but it doesn't lock up on the beta one.  What is the next step?  Just keep stepping up the compiler revs?

David Marcus said:

 But at the end of the compile it give me two errors in the program

What these build errors? The last one you mentioned was just a warning

>> C:\DOCUME~1\dmarcus\LOCALS~1\Temp\TI2923, line 22: error:
can't find input file 'rts2800_fpu32.lib'

>> Compilation failure

Build Complete,
2 Errors, 22 Warnings, 0 Remarks.

David - I just realized that we are headed down the wrong path. Your ofd output said the OLD program was built using compiler version 5.0.x. hence our strategy of using 4.x is the wrong one. I assume it used the 5.0 beta version like your current one, which is why you have that odd version installed. In your old hard drive, there must be a standalone version of a C2000 compiler v5.0.x.

Did you create the original project or did you inherit it? If it is the latter, the person that created it would know all the dependencies that old project had.

I inherited this project and this person no longer works here.  However I had to re install it on a new computer and this is why I am having all the issues.

Unfortunately you have a non standard environment and this makes it difficult to troubleshoot. Beta versions of the compiler are being used (why beta? what is the dependency?). Looks like your new CCSv3.3 install has a common hack where people updated a compiler version by overwriting the compiler files in the v3.3 installation instead of properly using the component manager. This is how you have a beta version of the compiler in C:\CCStudio_v3.3\C2000\cgtools\bin. I don't know what other files were overridden and what the dependencies are. if the person who created the pjt left the company, hopefully he documented the project dependencies somewhere. This information would help.

There does not seem to be any notes.  But if I understand what you said correctly you are telling me that switching compilers in a guess and check method is no use because there are other files that i may need?

So I changed the compiler to Version 5.0.0 and the code is working.  THank you for all your help!

That is good news!

David Marcus said:

So I changed the compiler to Version 5.0.0 and the code is working

You changed from the 5.0 beta to 5.0 release?

Yes.5.0.0

Can you tell me what I would have to do to my code to get it to work with newer compilers?

It is tough to provide any insight remotely like this without any details. It is best to simply use the debugger to try and narrow down where the problem is and then perhaps post your question in the compiler forum since an compiler version upgrade seems to cause things to break.

Thanks

ki