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

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

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

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

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

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

-----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(). >

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

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

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 Jean-Marc, As I told you, bank is a reserved keyword in Analog Devices compiler for Blackfin architecture. So we need to change the variables named bank to something else. Here's a patch that changes bank to bnk in the 3 concerned files. (Hope the format is OK) About my previous problems with the Blackfin: -> strange block repetition that could be cancelled by the AEC I was busy

Hello everybody, I'm currently trying to run speex on the Blackfin (BF-537) STAMP evaluation board unter uCLinux. Using 1.2 beta 3, I encountered problems when activating the Blackfin assembler optimizations. Without optimizations for blackfin, i.e. calling ./configure --enable-fixed-point --host=bfin-uclinux everything seems to work fine. But when I add the --enable-blackfin-asm flag to

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

Hi, when I compile with FIXED_DEBUG enabled, I get an error -- both when make tries to build testenc.o and when I try to link my app against the speex lib: lorenz@panelmaker:~/Blackfin/tests/speex_loopthrough$ make bfin-uclinux-gcc -c -g -I/home/lorenz/include -o main.o main.c bfin-uclinux-gcc -gl -elf2flt -L/home/lorenz/lib -o speex_through main.o -lspeex_debug -lspeexdsp -lm

Hello I'd like to configure Asterisk so that... 1. I ring it from my cellphone with CID number displayed, just to notify Asterisk that I wish to make a call 2. Asterisk waits until I hang up, calls me back, and prompts me for the number I wish to call 3. Asterisk puts me on hold through Flash(), which is apparently the equivalent of hitting the R key on European handsets 4. Asterisk calls the

Hello all, I'm testing the Speex codec for my diploma thesis on a BF-533 Blackfin under uCLinux (2005R3 RC3 release). I successfully compiled the Speex (1.1.11-svn) and I can encode/decode wav-files on my STAMP-board using the speexenc/speexdec sample apps. But I encountered that the decoded file sounds strange/noisy, when compiling with "--enable-blackfin-asm" +

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