thanks for the info.

I would have thought RAM would have been
no issue- coefficients stored in the FLASH  (that's big) , and good packing,  use of the RAM ( as the M4 is pretty good with its alignment options/access options ) , together with the fact that the codec doesn't have a very long state memory.
I'll probably stay with the STM  in order to stay with the crowd. STm32F7. It's just not very s3xy.

Just have to wait for the silicon to settle down the the errata sheet  to shorten a bit.
Actually STM don't call them bugs, they are called "silicon limitations"

Those using STM chips are well advised to read the errata sheet carefully.

73


On 28/07/2015 1:14 PM, Steve wrote:
I think that David said he kept the kissfft only because it was faster. The kissfft however, uses twice as much memory, not being an in-place algorithm.

This can be easily changed in the code though, if a slower in-place is used that still performs the task "fast enough" and you are running out of memory.

He did do a lot of memory optimizations last year, as I recall.

On Mon, Jul 27, 2015 at 7:33 PM, Shane Burrell <[email protected]> wrote:
My last project working with codec2, the code is coupled to kissfft.


------------------------------------------------------------------------------


_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

-- 
- 
Glen English
RF Communications and Electronics Engineer

CORTEX RF
&
Pacific Media Technologies Pty Ltd

ABN 40 075 532 008

PO Box 5231 Lyneham ACT 2602, Australia.
au mobile : +61 (0)418 975077 

------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to