similar to: SPEEX Fixed Point Development

Hi I want to port speex to my pocket PC iPAQ1945 which has a Samsung processor 2410, an ARM9-based processor. I would like to write the specific optimized code for this chip. I had some experience at DSP chip and fixed-point coding but know nothing about embedded system and ARM. Could someone tell me some hint how to write optimized code for this pocket PC. If you can give me some links that will

Hi there, I've just started to work with the great speex encoder on ARM9-based embedded platform. This is my configuration: CPU: Cirrus Logic EP9315 @ 200 MHz (ARM920T) o.s.: Linux 2.6.9-rc2-ep93xx GCC: gcc version 3.3.3 (DENX ELDK 3.1 3.3.3-10) without MaverickCrunch support ogg library: 1.0 speex command line configuration: ./configure --enable-fixed-point --enable-arm4-asm The code is

hi, i have searched through the archives but did not manage to find benchmarks of encoding/decoding speex on ARM processor. esp interested in ARM9E. understand that ARM5E has some dsp-like instructions, wonder whether they are compatible with those in ARM9E. thanks in advance. tk -------------- next part -------------- An HTML attachment was scrubbed... URL:

ACE issued following PR: http://www.ace.nl/news/aces-cosy-compiler-framework-outperforms-llvm-arm9-processor Weird that they don't give any number and use ARM 9, do they mean cortex-a9 ?

On Mon, 21 Dec 2009 21:00:01 +0100, <speex-dev-request at xiph.org> wrote: > Thank you for your product Speex. We want to use it in > microcontroller AT91SAM7S256 (48 MHz). I'd strongly advice to use a higher performance micro. Let's consider that you'd succeed in getting it working right after optimizations. The time you want to add other speex features or other

Hello, I would like to run nut 2.6.1 on an embeeded machine ( arm9 ) running linux and uclibc. A working gcc tool chain came with the board. How can I compile and build nut using the cross compiler tool chain ? I know that this is not a very specific question. I have however little experience with cross compiling, and I wonder where to start. A logical point would be the configure script. It

Hi, I have read the decoding side performance on ARM7 or ARM9. Your comment is very useful for us on evaluating the possible usage of Speex on our ARM system. How about the encoding performance? In your article, you mentioned "optimization". What is it? Is it included the 1.1.6 release source codes? thanks, Jay -------------- next part -------------- An HTML attachment was

Hi, I have one question: Will Speex run in realtime (both encode / decode probably simulateusly) on Nokia 6600 --- basicaly ARM9 104MHz with Symbian 7s after porting to its C++ or Java? I am thinking mostly about the worst quality encoding (optionally duplex). Can this processor make it? Oh 6600 has something about 6mb memory if I remember good. Plase cc kangur@polcom.net in replies.

Good day, I have looked around for this information, but I have not been able to gain a clear understanding: what is the status of the LLVM ARM backend? That is, do the following work: 1. Generating Thumb code: I saw a video online where they describe an issue with using the ARM Thumb back-end 2. Generating code for ARM9 (ARMv5?) or ARM7 (ARMv4): again, the same presentation

Hi Jean-Marc, thanks for the response. First, I will clarify again that floating-point solves this - so isn't that a bug in fixed-point? Also, I understand that algorithmically the AEC won't cancel echo properly on a non-linear signal, but why completely distort the output? If the echo just won't get cancelled it would be acceptable, but in the current state it disables the ability to

Hello everyone, Can any body please tell me the compiler options to optimise the speex code for ARM TE architecture. Fixed point is enabled. It currently takes about 700ms to encode 5 sec worth of voice. I need to get it down to under 10ms. Is the option --enable-arm5te-asm supported? I am using speex 1.1.12 version. The configure.ac file does not seem to support --enable-arm5te-asm

Evan, > I'm the code owner of LLVM codegen and targets. I'm also the one of main developers on the original ARM target. That means, I would make the decisions on major development on ARM target if there are decisions to be made. > > But my role is very different from what people are looking for in this thread. To properly qualify a target like ARM which are supported on many

I haven't tried using -Os/z on any ARM device for the last 3 years, and back then, -Os would break many things. People normally care about code size on Cortex-R/M and ARM9 or older, and in there, not many LLVM users. --renato On 27 February 2013 00:38, Jim Grosbach <grosbach at apple.com> wrote: > I've not run any on non-iOS devices, and haven't looked at GCC since >

Hello all, I'm a hardware person who has recently found himself thrust into a software role. So, please forgive any ignorance in the following questions. I've tried to do my homework reading the relevant manual pages and investigating the Doxygen documentation. :-) We're investigating acoustic echo cancellation solutions for a speech application. Our hardware will be a TI C64x+

? There seems to be a memory violation when calling celt_mode_create(48000, 240). ? The function compute_pulse_cache() calls celt_alloc (the second one, bits=celt_alloc()) in order to allocate 343 byte, but it is using about 872 bytes at that location, which will be deleted by the following allocations. ? In this case the following encoder call crashes at first run. ? Sorry, my time is very

On 22 June 2011 11:49, Damjan Marion <damjan.marion at gmail.com> wrote: > # /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c Even though you specified cpu as arm9, it's probably generating generic ARM IR (use -emit-llvm -S and see), which defaults to ARM instructions. If you want thumb, use triple =

On Jul 27, 2012, at 9:36 AM, Sebastien DELDON-GNB wrote: > ACE issued following PR: > http://www.ace.nl/news/aces-cosy-compiler-framework-outperforms-llvm-arm9-processor > Weird that they don't give any number and use ARM 9, do they mean cortex-a9 ? It's impossible to say. This sort of marketing statement is impossible to refute, because there are no details. Who knows whether

On 27 Feb 2013, at 00:45, Renato Golin <renato.golin at linaro.org> wrote: > People normally care about code size on Cortex-R/M and ARM9 or older, and in there, not many LLVM users. There are a lot of A8 devices around with 256KB (or less) of L2 cache (32KB of L1 i-cache), and so code density, if not code size, matters a lot for these. Cache sizes in mobile chips tend to be as small as

Hi all, I'm thinking of using Speex for an embedded project. I would only need the decode part. My question is what percentage of the CPU is used on an optimized (assembly will be done) SH4 or ARM7 or ARM9 speex decoder running at 100Mhz. Thanks, Bolt __________________________________ Do you Yahoo!? Jazz up your holiday email with celebrity designs. Learn more.

Hello everybody, I'm working on implementing the speex codec on ARM966E @ 96Mhz. For the encoding I found that 20ms of sample voice takes 13ms to be encoded. The goal of my project is to built an VoIP application based on ARM966E but with the actually performance it's not possible :( My question is what is approximately the speex encoding time with narrowband mode on ARM9 (ARM926 or