DSPLIB CCSv5.2

In CCSv5, the warning for "function declared implicitly" is turned on by default, which was not the case with older versions of CCS 3.3. You will notice the option --diag_warning=225 added by default for projects created in CCSv5. We added this by default to help users catch those cases where a function prototype is missing.

The diagnostic is a sign of either forgetting to include a header, or using a function when the prototype, declaration or definition has not been seen at the point in the file where the function is called.

It is a problem because when code calls an undeclared function, it makes assumptions about it (as specified by the C language spec.; it's not even allowed in C++), such as all its arguments are treated as either int or double and it returns an int, and if the real function is written differently then the arguments will likely be corrupted when the function tries to use them.  Given the various type sizes available with embedded processors, this can be a much bigger problem than on other platforms.

Barring a problem with the compiler - this is the compiler forum and I'm not aware of a bug related to prototypes - you will probably get better information in one of the DSP forums in case something has changed with that product.  

Hi,

I have the same prototype problem with other function of DSPLIB: 

#include <ti/dsplib/src/DSPF_sp_fir_r2/DSPF_sp_fir_r2.h>

I would to know if you have the solution of this problem?

Thanks,

Gerson

This thread needs to be moved to the DSP device specific forum, where expertise on DSPLIB is likely to be found.  Which device family is being used here?  C6000, C5500, or what?

Thanks and regards,

-George

Hi George,

thanks for your reply and excuse me (I had not seen the reply).

I'm working with a C6000 DSP family (C6748).

Thanks,

Gerson

Murad,

Which device are you using, and which DSPLIB version are you using?

For now, we will let this land in the BIOS forum where lots of good library-related answers are found. With your answer to the above, we may find a better fit.

Regards,
RandyP

Dear TI:

I meet a prolem that I can not open .tcf file using ccs5, the pop-up dialog box said "Unable to Creat BIOS Config Server"

and I reinstall ccs5,but  the same problem happened.

I updata dsp/bios   to bios_ccsv4_setupwin32_5_41_13_42.exe, but can not slove the problem also.

I have find the same question in the link

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/t/6911.aspx
 
I have followed the steps which  AartiG suggeted ,make a complete unintallation ,clean all relative files ,and then reinstall the ccs5, ,but the same question happened again.
my CCS version is ccs 5.1.0 , and my DSP/BIOS 5.41.10.36 is under "Discoverd tools"

I am able to pen the .tcf file in a text editor .

I have another question, I will choose tci6614 for my new paltform , can I still use DSP/BIOS5  for my OS ,or must I use SYS/BIOS in tci6614?

I am using CCSv5.2.004

C6678 EVM

dsplib_c66x_3_1_0_0

Murad,

What happens if you explicitly include the C66x header file for this function?

#include <ti/dsplib/src/DSP_fir_gen/c66/DSP_fir_gen.h>

Put that line after your include for dsplib.h and let us know if the error message goes away or not. Either way it will give a good answer; if it works, this is not "the" answer, just a good clue.

Do you get any other warnings or error messages during the build process for the C file that calls these DSPLIB functions?

Regards,
RandyP