similar to: Blackfin inline assembler and VisualDSP++ toolchain

-----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

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 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

> >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

Robin Getz a ?crit : >> As I told you, bank is a reserved keyword in Analog Devices compiler for >> Blackfin architecture. > > This seems lame, and maybe you need to change the header files inside VDSP++. > (This is pretty common for VDSP users to do when name space clashes occur > with open source software). > > Poking at the VDSP docs, says that it uses bank()

-----Original Message----- From: Jean-Marc Valin [mailto:jean-marc.valin@usherbrooke.ca] Sent: Thursday, June 14, 2007 11:17 PM To: Michael Shatz Cc: speex-dev@xiph.org Subject: Re: [Speex-dev] Blackfin inline assembler and VisualDSP++ toolchain Michael Shatz a ?crit : >>> Actually, you're the first I know using the VisualDSP++ toolchain >>> :-) >> >> I guess

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:

-----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),

> -----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 : > >

> -----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

> So, I did following changes: > In every loop I remove %= (In Vis.DSP Help I didn't find such sign) > And loop become able to compile. Let me know if you think of something that would work in both gcc and VDSP. > With parallel issues I found several interesting things: > > 1) > "A0 -= R1.L*R0.H (IS), A1 -= R1.L*R0.L (M,IS) || R0 = [%1++];\n\t" >

> 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

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

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

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

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.

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