similar to: Blackfin inline assembler and VisualDSP++ toolchain

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Tuesday, June 19, 2007 6:38 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >> Yes, data footprint in the new version is quite manageable. Still I would >> wish better documentation for speex_alloc_scratch(). >

From: Jim Crichton [mailto:jim.crichton@comcast.net] Sent: Tuesday, June 19, 2007 10:47 PM > >For TI DSPs, I used a private memory array rather than the C stack, and a >debug patch in stack_alloc.h to measure the scratch usage: > >#if 1 >extern char *spxGlobalScratchFree; >#define ALLOC(var, size, type) (var = PUSH(stack, size, type),

Hi Jean-Marc I'm trying to integrate your speex codec on our custom Blackfin board. The board is not uCLinux compatible and there is no chance that it will ever be. I am using ADI-supplied VisualDSP++ IDE and corresponding toolchain. As long as I am compiling "C"-only version of the library everything is fine. VisualDSP++ produces working library. There is only one not so minor

-----Original Message----- From: Robin Getz [mailto:rgetz@blackfin.uclinux.org] Sent: Saturday, June 16, 2007 12:11 AM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain >On Wed 13 Jun 2007 12:37, Michael Shatz pondered: >> >> Hi Jean-Marc >> >> I'm trying to integrate your speex codec on our

> >Actually, you're the first I know using the VisualDSP++ toolchain :-) > I guess that's because speex has pretty big memory footprint. So developers that integrate speex tend to have plenty of RAM and once one has plenty of RAM he could install biggish OS. And between biggish OSes for Blackfin the most popular choice is uCLinux. And ucLinux works best with gnu tools. Something

>-----Original Message----- >From: Robin Getz [mailto:rgetz@blackfin.uclinux.org] >Sent: Tuesday, June 19, 2007 9:35 PM > > >On Tue 19 Jun 2007 13:00, Michael Shatz pondered: >> Robin Getz wrote: >> >I never met any hardware that gcc could not run code on. toolchains have >> >nothing do with embedded OSes. >> >> That's true. Add some

Robin Getz a ?crit : > On Tue 19 Feb 2008 11:14, Voss, Stefan, AEAV22 pondered: >> I'm trying to integrate your speex codec on our custom Blackfin board and >> without uCLinux. I am using ADI-supplied VisualDSP++ IDE and corresponding >> toolchain. My question is: Is there anybody who ported speex with enabled >> BFIN_ASM to VisualDSP++ ? > > Nope - two

Hi I'm trying to integrate your speex codec on our custom Blackfin board and without uCLinux. I am using ADI-supplied VisualDSP++ IDE and corresponding toolchain. My question is: Is there anybody who ported speex with enabled BFIN_ASM to VisualDSP++ ? Best Regards, Stefan Voss -------------- next part -------------- An HTML attachment was scrubbed... URL:

Some things to check. Do you compile with VAR_ARRAYS? If not, you can probably reduce the size of the managed stack. In terms of data RAM, everything should fit into SRAM easily. I've done some massive wideband RAM reduction in 1.2beta2. If it's not working on Blackfin, then we'd need to investigate that first. Depending on whether you're using all the bit-rates, you might want to

> -----Original Message----- > From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] > Sent: Thursday, November 22, 2007 12:16 AM > To: St?phane Lesage > Subject: Re: [Speex-dev] Blackfin port on Visual DSP, Michael Shatz ? > > (en passant, tu es francophone?) oui, fran?ais, travaillant pour une soci?t? suisse ;-) > > St?phane Lesage a ?crit : > >

Hi, I'm using the Speex codec on my Blackfin-based board, and plain-C performance is pretty poor. Decoder is OK (something 25 MIPS for wide-band). But Encoder is not (wide-band quality 8, complexity 1): - 162 MIPS with Analog-Devices lib - 128 MIPS with 1.2beta2 (faster but not working) I don't worry that much, as it's not the optimized version, and everything is running in SDRAM.

> -----Original Message----- > From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] > Sent: Wednesday, October 17, 2007 1:56 AM > To: St?phane Lesage > Cc: speex-dev@xiph.org > Subject: Re: [Speex-dev] Blackfin port on Visual DSP, Michael Shatz ? Salut Jean-Marc, After 1 month busy on other projects, I can finally answer you: > Some things to check. Do you

Hi Jean, First, I would like to thank for the prompt reply. Basically, what I have to do is to run a speex coder/decoder on a Blackfin processor, on top of the microC/OS II kernel. I wish I could use uclinux, since I'm familiar with Linux, but this doesn't depend on me. You said that the assembly code is written for gcc, not for VisualDSP++. Furthermore, in the link you sent me, the

Hi all, I'm trying to run speex on the Blackfin processor. I'm not familiar with programming/compiling/linking at all, but I guess the first thing I need is libspeex compiled for Blackfin, so that my program can use the library functions. I've downloaded the source files (version 1.1.10) from www.speex.org and I've been trying to compile libspeex from within VisualDSP++, but it

> I am trying to port speex lib to Blackfin processor. > I am using VisualDSP++ 4.0. I've never used VisualDSP++ 4.0. All the development on Blackfin has been done with gcc, which may explain some problems with the inline asm. Does VisualDSP++ support a syntax close to what gcc uses (with constraints) or more like the MS compilers. > If I am compiling source codes with using

> No I didn't know this macro. > > According to the sources, I understand it's destined to compilers supporting > run-time size for local arrays on the stack. > > But this is not documented (API or user manual), and does not appear in any > header file. > It should appear at least in arch.h, commented and defaulting to #undef... Actually, it's meant to be

Hello! I'v downloaded speex lib 1.1.11.1. I am trying to port speex lib to Blackfin processor. I am using VisualDSP++ 4.0. If I am compiling source codes with using floating point everything ok. When I am compiling with FIXED_POINT defined everything's ok and code works about two times faster. But when I am defining BFIN_ASM I am getting several compiling errors in Blackfin assembler

Hi, I think the (small) readme has been accidentally omitted from the tarball. You can get it at http://svn.xiph.org/trunk/speex/README.blackfin Note however that all the assembly is written for gcc, not VisualDSP++. Jean-Marc Le jeudi 29 septembre 2005 ? 21:24 +0000, Adriano Vilela Barbosa a ?crit : > Hi all, > > I'm trying to run speex on the Blackfin processor. I'm not

> -----Message d'origine----- > De : Jean-Marc Valin [mailto:jean-marc.valin at usherbrooke.ca] > Envoy? : lundi, 15. juin 2009 01:30 > ? : Stephane Lesage > Cc : speex-dev at xiph.org > Objet : Re: [Speex-dev] Resampler saturation, blackfin performance > > - are there buffers who could be placed in scratch memory ? > > (I don't see any speex_scratch_alloc

I am looking into using speex for a decode only application on the blackfin. Encoding would be done elsewhere with voice phrases loaded into FLASH. Code space is a premium in the blackfin app, and mips to a certain extent 1) The source code seems to be codec-centric with encode and decode in many of the same files. Does anyone have any hints on what can be removed easily that is used only