DSPLIB for C6455+CCSv3.3

问题描述：

Hello everybody,

I was looking for DSPLIB libraries optimized for C6455 processors. I found this page: http://software-dl.ti.com/sdoemb/sdoemb_public_sw/dsplib/latest/index_FDS.html.

But the last release, as I found out after installing it, has precompiled libraries for CCS v4+Code Generation Tools v7.2, while I'm using CCS v3.3+CGT v6.0.8 and I'd prefer to keep using that one, since it's the version that came with the DSK board I'm using.

I even tried to use those precompiled libraries with CCS v.3.3, but CCS didn't even recognize them as libraries when I try to add them to a project.

Is there any archive with some older version of the dsplib64plus.lib library which could be used with CCS v3.3?

Regards,

Francesco Annese

解决办法：

Vito,

I wasn't able to get to the link that you provided.  I believe the official link to the 64x+ DSP Library is here:http://focus.ti.com/docs/toolsw/folders/print/sprc265.html

I downloaded the package from the location above.  It seems there are two library binaries here dsplib.a64P and dsplib.a64PE.  The first is the little endian version, the second is the big endian version.  In the past, I believe that these were all shipped with names like *.lib, but the naming convention was changed because of the many variations of libraries that we now support.  There are variants for Family, Big/Little Endian, and now even Coff/ELF file format in the newest versions of the compiler/linker.  So, all of these options are now being encoded in the file extension.

I don't have CCS 3,3 installed anymore, but if memory serves, in order to add a library to a project, it had to have a specified extension, either .lib or there may have been one other extension it supported.

There are two ways that you can fix this....

a) You can just rename the library that you are using to have a .lib extension, and then add it to your project.  Physically, there is no difference between a .a64P and a .lib file that was built using the same options.

b) Don't include the library in your project, instead put a directive in your linker command file to link it.  (This is probably the preferred method)  This consists of a line that looks like (that's a dash lowercase L)

-l dsplib.a64P

If you're using DSP/Bios which generates a linker command file for you, to do this you need to create your own linker command file and then link to the bios generated one.  This file would look something like

-l dsplib.a64P

-l <bios_generated_lcf_name>.cmd

The compiler/linker version that you are using should not matter.

Regards,

Dan