similar to: [Fwd: Re: Errors in speex lib with Blackfin]

Hi, ? Is there a fix for this issue??? ---> http://permalink.gmane.org/gmane.comp.audio.compression.speex.devel/2959 ? I am seeing the same thing when I compile speex in visualdsp ? These are the errors I get from using the assembly version of vq_nbest: ? ..\..\..\..\algorithms\voice\speex\src\vq.c [Error ea5004] "C:\Users\coder\AppData\Local\Temp\acc22e8547f000\acc22e8547f001.s":482

> 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

Here some Blackfin inline assembly, mainly picked and adapted from speex. It's helps a little on my BF537 eval board. Julien -------- /** @file fixed_bfin.h @brief Fixed-point operations for the ADI BF5xx DSP family */ /* Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: -

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

> 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

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

Most asm statements clobber ASTAT bits (shifts, maxes, etc...) but do declare the register as clobbered. Same thing with CC in a few places. Some places make an attempt at clobbering some hardware loop registers, but it's very incomplete compared with how many asm statements actually use hardware loops. Signed-off-by: Mike Frysinger <vapier at gentoo.org> --- libspeex/bfin.h

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

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

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

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

Hi Bernhard, It seems like I messed up somewhere in the lpc code. However, it seems like your patch is also removing some code, which is probably why you see small differences between your asm version and the fixed point. I don't have my setup working at the moment, but could you test the following patch: Index: lpc_bfin.h ===================================================================

nautiluz wrote: >I am starting project to develop open implementation of some (naturally open >codec) for simply designed embedded devices which can be used by small to >big VoIP operators or hobbyists which wants to build their own small and >low cost VoIP phone. >Speex seems to be great choice. And greater will be if there should be >some guys who want to help ;-). Sorry

I bought a ADSP-BF533-EZkit-LITE V2.1 to develop a speech codec application using SPEEX. I have tested SpeexEcho project from both BlackfinSDK-Rel201 and BlackfinSDK-Rel310. When disabling SPEEX processing, i.e. using PASS-THROUGH mode, the output voice is ok, which is exactly as the input voice. However, when enabling SPEEX processing, the output is bad, no matter how to set the parameters in

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

Hello all! I'm having trouble with a cross compiled libopus for an embedded application and would like some help. preamble: embedded details: processor: bf537 kernel: Linux release 3.0.8-ADI-2011R1-svn4693, build #2834 Fri Apr 22 12:35:34 ADT 2016 toolchain: bfin-linux-uclibc-gcc release gcc version 4.3.5 (ADI-2011R1-RC4) audio interface: ALSA

There are ~4300 uses of pr_warn and ~250 uses of the older pr_warning in the kernel source tree. Make the use of pr_warn consistent across all kernel files. This excludes all files in tools/ as there is a separate define pr_warning for that directory tree and pr_warn is not used in tools/. Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. Miscellanea: o Coalesce formats and

There are ~4300 uses of pr_warn and ~250 uses of the older pr_warning in the kernel source tree. Make the use of pr_warn consistent across all kernel files. This excludes all files in tools/ as there is a separate define pr_warning for that directory tree and pr_warn is not used in tools/. Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. Miscellanea: o Coalesce formats and