search for: 55x

...ing in C rather than C++. But my choices might be limited. :-) I'll come back to this point when all the TI stuff arrives and I've looked through it all. I've just had notification it has been despatched. > 5. You should take a close look at the intrinsic definitions on the > 55x when making your (the?) integer implementation. When you port to > the 55x you can substitute the intrinsics and get alot of MIPS > reduction right away. We've seen alot of similar intrinsics on other > (non-TI) DSPs too. OK. Noted. I've also been told by a TI applications B...

...ally, if it is open source, I expect people might want to use more than just TI DSPs. We use TI DSPs alot and tried to say we'd never put it anywhere else. But, we found you can never say never. > > OK. Noted. > > I've also been told by a TI applications BOD that although the 55x is a > fixed point device, it does contain some internal features which speed > up running floating point code. This was done to meet certain > requirements in the Mobile market and they suspect that there may be > enough computing power to running a floating point codec on the 55x. I&...

...other FFT implemented > #endif > > My guess is that every DSP and many other processors will have their own > specific FFT and iFFT. What method should be used to drop in a DSP specific > FFT? > Should just use something like this for fftwrap.c? > > #if defined(__TMS320C55X__) > #include "FFT_TI55.h" > #endif > > #ifdef USE_SMALLFT > ... > #elif defined(USE_KISS_FFT) > ... > #else // Use FFTWrap_*.h file to supply processor specific functions. > #if defined(OVERRIDE_FFT_INIT) > void *spx_fft_init(int size) {}; > #endi...

...ned(USE_KISS_FFT) ... #else #error No other FFT implemented #endif My guess is that every DSP and many other processors will have their own specific FFT and iFFT. What method should be used to drop in a DSP specific FFT? Should just use something like this for fftwrap.c? #if defined(__TMS320C55X__) #include "FFT_TI55.h" #endif #ifdef USE_SMALLFT ... #elif defined(USE_KISS_FFT) ... #else // Use FFTWrap_*.h file to supply processor specific functions. #if defined(OVERRIDE_FFT_INIT) void *spx_fft_init(int size) {}; #endif #if defined(OVERRIDE_FFT_INIT) void spx_fft_destro...

I saw a thread in the list archives about a speex port to TI 55x DSP. Wondering how that worked out (is working out)? Also wondering if there is a source archive for it, or if the patch in the email archives is still current, or if there's been updates. Any info appreciated. Thanks Paul

...the device we have chosen is the TMS320C6711 See http://focus.ti.com/docs/prod/productfolder.jhtml?genericPartNumber=TMS320C6711 B) We will then plan to do some porting work to the TI fixed-point range. Most likely TMS320VC5510 - basically because our project is battery powered the TI TMS320C55xx series is excellent as regards power consumption. See http://focus.ti.com/docs/prod/productfolder.jhtml?genericPartNumber=TMS320VC5510 C) TI within the UK are aware of what we are doing and are supporting us in various ways. In principle they seem happy with anything which reduces the barrie...

Hi Andrew!I have read your mail about speex porting on DSP, I'm student and I 'm trying to port speex 1.1.7 on DSK6711 floating point with Code composer studio but I have a lot of errors....Can you give me help? Thanks Carlo -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Giornata faticosa? Rilassati con il Cuscino per Massaggi che vibra!

...rd a. Should a totally objective measure be formed? Object + Subjective? b. Should MOS scoring or the like be used? (Yuck expensive) c. Should a bit-exact integer implementation be formed? I would suggest that a fixed point model be formed on Linux, Cygwin and/or Windoze first. Then port to the 55x (see comment 4). 4. I think the codec is portable to more fixed point embedded devices if you stick to C rather than C++ code. If you follow the TI XDAIS standard you'll wind up creating an object-oriented codec but you can do it all in C (Relocatable, re-entrant code, state structure, etc.)....

...ds, Paul -----Original Message----- From: Jamey Hicks [mailto:jamey.hicks@hp.com] Sent: Thursday, March 03, 2005 7:14 AM To: Paul Gryting Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Speex for TI 5509 DSP Paul Gryting wrote: >I saw a thread in the list archives about a speex port to TI 55x DSP. >Wondering how that worked out (is working out)? > >Also wondering if there is a source archive for it, > or if the patch in the email archives is still current, or if there's been >updates. > > > My patch to provide fixed-point support for Speex on the TI 55xx DSP...

...may require minor adjustments. Although support could be improved (optimizations, codebook packing), the patch should at least allow Speex to run on a C55. Jean-Marc Le mercredi 02 mars 2005 ? 15:00 -0600, Paul Gryting a ?crit : > I saw a thread in the list archives about a speex port to TI 55x DSP. > Wondering how that worked out (is working out)? > > Also wondering if there is a source archive for it, > or if the patch in the email archives is still current, or if there's been > updates. > > Any info appreciated. > Thanks > > Paul > > ______...

Paul Gryting wrote: >I saw a thread in the list archives about a speex port to TI 55x DSP. >Wondering how that worked out (is working out)? > >Also wondering if there is a source archive for it, > or if the patch in the email archives is still current, or if there's been >updates. > > > My patch to provide fixed-point support for Speex on the TI 55xx D...

...) floating point hardware is more complicated than fixed point, thus more expensive. Energy) more transistors at a given feature size and clock speed require more watts The fixed point chips often supply specialized instructions to aid in floating point emulation. For example, TI 54x and 55x include a single-cycle instruction that gets the number of significant bits in an accumulator. I've programmed a couple of TI DSP chips. One float, and one fixed. The floating point was certainly easier to program, since I never delved into assembly (but I didn't get stellar performance e...

Jean-Marc, >> I incorporated Stuarts fixed_c55x.h file, and that eliminated the >> artifacts, >> at the expense of a ~30% increase in MIPs. Now the male.wav file through >> encoder/decoder produces a bit-exact match with the C64x test that I did >> earlier. I will do some more testing to isolate the, but it may be a fe...

Hi everyone, I've recently been making various changes to the way the modes work and the supported frame size. On new feature that may be of interest to some is that CELT should soon support changing the frame size dynamically within a stream. By that I mean varying the amount of audio (in time) transmitted at once, not the compressed size -- which has always been variable. That would

Stuart, Jean-Marc, >> 1) We need our own "fixed_xx.h" header file. I don't know why, and >> haven't >> had time to investigate, but there is a definite improvement when I use >> the >> attached fixed_c55x.h file which has turned all the maths into inline >> functions. > > Did you try with fixed_generic.h or just with fixed_debug.h? > fixed_debug.h uses int and short directly, so I know it won't work with > the C5x. However, I think fixed_generic.h should work and has all the &g...