Displaying 6 results from an estimated 6 matches for "speex_c55_test".
2006 Jul 21
2
Using Speex on OMAP5910 OSK board
Hello,
I have an OMAP5910 OSK board with C55 dsp and ARM9 processor. I just want to
use speex as a simple application on the platform in order to check dsp's
working well or not.
First, I found speex's source codes include "ti/speex_C55_test" directory so
I thought speex could run on my platform well.
Second, I open "Code Composer Studio" and then open the project file in the
ti/speex_C55_test directory, build it. At last I got "speex_C55_test.out" file
in ti/speex_C55_test.
001. How can I t...
2005 Aug 31
0
Fwd: Patch, related to TI DSP C54x C55x C6x builds
...en i saw your mail about this, i decided to ask you for
send me those files above:
include\config.h (not automatically generated, sets memory sizes,
enables manual alloc)
include\speex\speex_config_types.h (match Speex types to compiler
types, not generated from types.in
<http://types.in>)
speex_c55_test\speex_c55_test.cmd (C5509A linker command file)
speex_c55_test\speex_c55_test.pjt (Code Composer Studio Project File )
src\boot.asm (to force wait states to 0 for the simulator, otherwise
cycle count is much too high)
src\testenc-54x.c (derived from testenc.c, manual alloc, byte
packing/unpacking...
2005 Aug 18
0
Patch, related to TI DSP C54x C55x C6x builds
...allows private memory allocation, for cases where it is not
desirable to use the normal heap.
Added files:
include\config.h (not automatically generated, sets memory sizes, enables manual alloc)
include\speex\speex_config_types.h (match Speex types to compiler types, not generated from types.in)
speex_c55_test\speex_c55_test.cmd (C5509A linker command file)
speex_c55_test\speex_c55_test.pjt (Code Composer Studio Project File )
src\boot.asm (to force wait states to 0 for the simulator, otherwise cycle count is much too high)
src\testenc-54x.c (derived from testenc.c, manual alloc, byte packing/unpacking...
2005 Aug 17
2
Updated MIPs and memory requirements for TI c54x or c55DSPs
Hi,
Just a couple tips to reduce complexity. First, I think you'd get a good
speedup by enabling the PRECISION16 switch (if it's not done already).
This (very) slightly reduces quality, but means you convert a lot of
"emulated" 16x32 multiplications into 16x16. There are also several
routines that would benefit from platform-specific optimizations. There
are already
2006 Apr 24
0
Major internal changes, TI DSP build change
...crubbed...
Name: speex_C54_test.pjt.patch
Type: application/octet-stream
Size: 1464 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20060424/82413d6a/speex_C54_test.pjt-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: speex_C55_test.pjt.patch
Type: application/octet-stream
Size: 753 bytes
Desc: not available
Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20060424/82413d6a/speex_C55_test.pjt-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: speex_C64_test.pjt.patch
Type: a...
2006 Apr 20
5
Major internal changes, TI DSP build change
Hi Jim,
> Build 11169 in SVN works correctly.
Good. I'll try not to forget the EXTEND32 from now on.
> I have attached a zip file (renamed
> .txt) with a patch to bits.c to make the byteswapping for TI DSPs
> consistent.
Seems like unzip can't read it. Either it's in an unknown format or the
file got corrupted. Could simply send as multiple (uncompressed)