Displaying 20 results from an estimated 600 matches similar to: "Implementing opus codec on ARM cortex m3"
2011 Sep 21
1
Speex on NXP LPC1768 embedded microprocessor
I purchased a Code Red RDB1768v2r3 Rev B1 board.
I'm trying to use the NXP provided example for the Speex codec from
App Note:
NXP AN11085
http://ics.nxp.com/support/documents/microcontrollers/zip/an11085.zip
Does this example application run reliably on the Code Red
RDB1768v2r3? Is there a modified version of Speex available that is fully
functional?
When
2014 Oct 09
2
Speex on M3 for a device for a disabled person to use
I am trying to develop a device for a disabled person and need low bitrate
voice, speex looks good, however I need to find optimized M3 code and can
not, searched online all over, I use Keil also if that helps.
My M3 is 128kbps/64kram 72mhz, i only need to do a encode in one part and
decode in another.....
Please let me know if you can help this project with a link to optimized
code
Thanks!
2014 Oct 09
1
Speex on M3 for a device for a disabled person to use
Hi Tristan,
well... if speed is really his problem (and looking at those 72 MHz it
probably is), wouldn't Speek surpass Opus by far?
I agree that Opus is way better, but it's sadly also using more resources...
But yeah, Richard you should give Opus a try if possible ;) It's
generally easier to use then Speex and also more feature rich.
Yours sincerely,
Ren? Sch?mann
*From:*
2019 May 27
0
opus-1.3.1 patch for ARM Cortex-M4F (single precision)
The patch prevents KEIL MDK compile warnings, like:
warning: #1035-d: single-precision operand implicitly converted to
double-precision
Actually ARM Cortex-M4F has only a *single precision* (float) FPU.
It's suit for all platforms.
See the comment at the begin of patch file.
Sincerely
Forrest Zhang
-------------- next part --------------
Specify the floating point constant with single
2011 Oct 31
1
Can CELT / libopus on a ARM cortex M3 or M4 (fast enough ?)
Hello everyone,
For a private project I would like to make a new Internet Intercom
device (for my kids and me).
At the moment I use a separate DSP with Ogg/Vorbis (VS1053) but I like
a challenge ;-)
Is a eg. ST32F10x (cortex m3) or a new ST32F40x (cortex m4) powerful
enough to do encoding and decoding ?
Any existing projects to learn from?
Thanks for your time,
Edwin van den Oetelaar
2009 Oct 22
2
[LLVMdev] arm cortex-m3
Now that there is good thumb2 support in the ARM backend, would someone
please add "cortex-m3" to the "-march" list for the ARM backend. This
should produce pure thumb2 only code. At some point, when the subsets
are public, "cortex-m1" and "cortex-m0" should also be added.
thanks,
bagel
2009 Nov 22
2
[LLVMdev] arm cortex-m3
Here is a one-line patch to support the cortex-m3.
For those who plan the features for ARM, the new cortex-m0 implements
only a subset of the Thumb2 instructions. I still have yet to see a
document that details what's in the subset.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: arm.diff
URL:
2009 Nov 24
0
[LLVMdev] arm cortex-m3
Looks OK to me, but I don't have any Cortex-M3 docs to confirm the
choice of v7-A without NEON.
deep
On Sun, Nov 22, 2009 at 9:47 PM, Bagel <bagel99 at gmail.com> wrote:
> Here is a one-line patch to support the cortex-m3.
> For those who plan the features for ARM, the new cortex-m0 implements only a
> subset of the Thumb2 instructions. I still have yet to see a document that
2012 Jul 18
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
Hi there,
I'm trying to switch from GCC to llvm (clang++) for cross-compiling
a firmware of mine for a stm32 (ARM cortex-m3).
After looking in the documentation and a bit of googling here is what
I did (in case someone else in the future is having the same problem)
cd llvm
git clone http://llvm.org/git/llvm.git
cd llvm/tools
git clone http://llvm.org/git/clang.git
cd llvm/projects
git
2012 Jul 18
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Wed, Jul 18, 2012 at 3:52 PM, Renato Golin <rengolin at systemcall.org> wrote:
> On 18 July 2012 14:33, salvatore benedetto
> <salvatore.benedetto at gmail.com> wrote:
>> but I still haven't figure out how to build for cortex-m3
>>
>> clang -march=armv7-m -mfloat-abi=soft <something missing?> testReference.cpp -c
>
> -march should have done
2012 Jul 18
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Wed, Jul 18, 2012 at 4:33 PM, 陳韋任 (Wei-Ren Chen)
<chenwj at iis.sinica.edu.tw> wrote:
>
> Do you tell clang to use the right binutils for ARM not x86 host?
>
Not really. I'm not even sure how to do that.
I thought that would have done automagically by llvm.
Any readings to point me to?
S.
2012 Jul 18
1
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 18 July 2012 17:08, salvatore benedetto
<salvatore.benedetto at gmail.com> wrote:
> I of course own you a beer :-) Thank you very much.
I will remind you of that, next year, on EuroLLVM 2013. :D
> Which part of gcc I'm using with that option?
> Just the libc, libgcc et all?
AFAIK, it uses the name to find the tool chain, and guess all other
binaries from it. So it calls
2012 Jul 22
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
> Any suggestions?
Try to specify CPU explicitly.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2012 Jul 22
2
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Sun, Jul 22, 2012 at 9:42 PM, Anton Korobeynikov
<anton at korobeynikov.info> wrote:
>> Any suggestions?
> Try to specify CPU explicitly.
Already did.
clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple
thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3
fatal error: error in backend: CPU: 'cortex-m3' does not support ARM
mode execution!
S.
2012 Jul 22
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
> clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple
> thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3
> fatal error: error in backend: CPU: 'cortex-m3' does not support ARM
> mode execution!
Ok, and what's about -mthumb then?
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2012 Jul 22
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Sun, Jul 22, 2012 at 10:37 PM, Renato Golin <rengolin at systemcall.org> wrote:
> On 22 July 2012 20:42, Anton Korobeynikov <anton at korobeynikov.info> wrote:
>>> Any suggestions?
>> Try to specify CPU explicitly.
>
> He shouldn't have to, but that might help. Maybe setting -march? This
> is a big mess...
>
> I thought that v7 always assumed
2012 Jul 23
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Darwin, if -march is armv7 clang's driver will assume you want thumb2 unless you also give it -mno-thumb but that is irrelevant with mcpu=cortex-m3.
I agree its a mess.
-Chris
On Jul 22, 2012, at 4:37 PM, Renato Golin wrote:
> On 22 July 2012 20:42, Anton Korobeynikov <anton at korobeynikov.info> wrote:
>>> Any suggestions?
>> Try to specify CPU explicitly.
>
2012 Jul 23
2
[LLVMdev] Setting up a cross-compiler for cortex-m3
On 23 July 2012 17:03, Chris Cadwallader <ccadwallader at arxan.com> wrote:
> On Darwin, if -march is armv7 clang's driver will assume you want thumb2 unless you also give it -mno-thumb but that is irrelevant with mcpu=cortex-m3.
I think that Thumb2 should be the default for v7 on any system, not
just Darwin. Maybe some ARM folk can comment on this...
--
cheers,
--renato
2012 Jul 23
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Mon, Jul 23, 2012 at 8:14 PM, Renato Golin <rengolin at systemcall.org> wrote:
> On 23 July 2012 17:03, Chris Cadwallader <ccadwallader at arxan.com> wrote:
>> On Darwin, if -march is armv7 clang's driver will assume you want thumb2 unless you also give it -mno-thumb but that is irrelevant with mcpu=cortex-m3.
>
> I think that Thumb2 should be the default for v7
2012 Jul 24
0
[LLVMdev] Setting up a cross-compiler for cortex-m3
On Jul 24, 2012, at 1:29 PM, Renato Golin <rengolin at systemcall.org> wrote:
> IIRC, it took him a week or so to do all that, and months waiting for
> answers, then years waiting for more answers. It was more than just
> tests, and until today I have no idea what it was... There was always
> something wrong but no one could tell what, but it stopped the patch
> anyway.