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

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

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

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

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

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

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

Hi Jean-Marc, after some problems with getting svn to work here I finally made it. Problem is, you write that I cannot use libspeex and libspeexdsp at the same time now -- because I use a "live" system (mic-in -> speex_enc -> speex_dec -> headphone out) and I can run the AD1836 audio codec on 48 kHz only, I cannot use my program now (because I use speex resampling...) So I

Jean-Marc, Frank, I have stumbled across a similar situation regarding optimization. I seem to have a similar setup as Frank does with a fixed 48khz in and out. The wideband mode and ultra-wideband modes are really what I?m looking for. I have a test application that reads audio, downsample to 16kHz (or 32kHz), speex encode, speex decode, upsample back to 48kHz, and playback. If I remove

Hi All, We are using speex for linphone in blackfin fixed point platform. The speex version we are using is svn-14525. If we don't disable vbr by "--disable-vbr", the sound quality will be very bad in linphone. But if we disable it, sound will be perfect. I noticed in the speex.org, there is a comment like this: > >Speex 1.2beta3 is out >December 11, 2007 >The most

Hi Tobias, I don't know if you've noticed, but ST actually released an optimised port of Speex for their chip (see mailing list archive). About disabling wideband, that can be done by defining DISABLE_WIDEBAND. You probably also want to define DISABLE_VBR and DISABLE_FLOAT_API. As you noted, you can also disable more than half the codebooks. That being said, I think adding a bunch of

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

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

Hi Marc, I encountered the problems even with older versions of speex, including 1.2beta2 and 1.1.12, too. I had no time in the last weeks to investigate this issue further, sorry. Hopefully, I'm able to do some more test the next days, but I have no real idea how to proceed Performance and quality seem to be o.k. for me if I deactivate the Blackfin optimizations inside the file

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:

Hello Jean-Marc, I disabled the Blackfin optimization functions one by one and found the error in libspeex/lpc_bfin.h in the autocorrelation computation. Compared to the fixed-point-variant of that function (from lpc.c), the blackfin-code produces correct values except for the zero offset value. Additionally, the loop after the ASM-code assigned values (ac32) wrong to the functions