search for: 20kbytes

Hi Ted, Thanks a lot for this analysis. > In FLOAT_DIVU() it hangs at the following: > while (a.m >= b.m) > { > e++; > a.m >>= 1; > } > for the case where a and b are both zero (yes, division by zero). > This happens from mdf.c: True, that needs to be fixed even after I fix the rest. > leak_estimate =

...is not so small at > all) to be added to the build. Right, need to cleanup that part... > With these changes, the link was successful, using testecho.c with some > modifications for the C55 environment. The code and data memory > requirements were a lot more than I had hoped (>20kbytes of dynamic data > memory for block size=128, tail length = 1024), and I will probably not be > able to fit it in the production build without some trimming. Yes, there may be a bit of memory reduction possible here. Of course, decreasing the tail length is also a rather easy way. > Whe...

...ld. > > > > Right, need to cleanup that part... > > > >> With these changes, the link was successful, using testecho.c with some > >> modifications for the C55 environment. The code and data memory > >> requirements were a lot more than I had hoped (>20kbytes of dynamic data > >> memory for block size=128, tail length = 1024), and I will probably not > >> be > >> able to fit it in the production build without some trimming. > > > > Yes, there may be a bit of memory reduction possible here. Of course, > > dec...

...sed and required smallft.c (which is not so small > at all) to be added to the build. > > With these changes, the link was successful, using testecho.c with some > modifications for the C55 environment. The code and data memory > requirements were a lot more than I had hoped (>20kbytes of dynamic data > memory for block size=128, tail length = 1024), and I will probably not be > able to fit it in the production build without some trimming. > > When I run the build, it goes into an infinite loop in FLOAT_DIV32 (mdf.c > line 660), which occurs because adapt_rate i...

...gt; Right, need to cleanup that part... > > > > > >> With these changes, the link was successful, using testecho.c with some > > >> modifications for the C55 environment. The code and data memory > > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > > >> data > > >> memory for block size=128, tail length = 1024), and I will probably not > > >> be > > >> able to fit it in the production build without some trimming. > > > > > > Yes, there may be a bit of memory reduc...

...because there were not used and required smallft.c (which is not so small at all) to be added to the build. With these changes, the link was successful, using testecho.c with some modifications for the C55 environment. The code and data memory requirements were a lot more than I had hoped (>20kbytes of dynamic data memory for block size=128, tail length = 1024), and I will probably not be able to fit it in the production build without some trimming. When I run the build, it goes into an infinite loop in FLOAT_DIV32 (mdf.c line 660), which occurs because adapt_rate is < 0, which happens...

...[Speex-dev] Speex echo canceller on TI C55 DSP, but this is a more general topic) >> With these changes, the link was successful, using testecho.c with some >> modifications for the C55 environment. The code and data memory >> requirements were a lot more than I had hoped (>20kbytes of dynamic data >> memory for block size=128, tail length = 1024), and I will probably not >> be >> able to fit it in the production build without some trimming. > > Yes, there may be a bit of memory reduction possible here. Of course, > decreasing the tail length is als...

...t; all) to be added to the build. > > Right, need to cleanup that part... > >> With these changes, the link was successful, using testecho.c with some >> modifications for the C55 environment. The code and data memory >> requirements were a lot more than I had hoped (>20kbytes of dynamic data >> memory for block size=128, tail length = 1024), and I will probably not >> be >> able to fit it in the production build without some trimming. > > Yes, there may be a bit of memory reduction possible here. Of course, > decreasing the tail length is als...

...ld. > > > > Right, need to cleanup that part... > > > >> With these changes, the link was successful, using testecho.c with some > >> modifications for the C55 environment. The code and data memory > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > >> data > >> memory for block size=128, tail length = 1024), and I will probably not > >> be > >> able to fit it in the production build without some trimming. > > > > Yes, there may be a bit of memory reduction possible here. Of course,...

...leanup that part... > > > > > >> With these changes, the link was successful, using testecho.c with > > >> some > > >> modifications for the C55 environment. The code and data memory > > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > > >> data > > >> memory for block size=128, tail length = 1024), and I will probably > > >> not > > >> be > > >> able to fit it in the production build without some trimming. > > > > > > Yes, there may be a...

...> > > > > > >> With these changes, the link was successful, using testecho.c with > > > >> some > > > >> modifications for the C55 environment. The code and data memory > > > >> requirements were a lot more than I had hoped (>20kbytes of dynamic > > > >> data > > > >> memory for block size=128, tail length = 1024), and I will probably > > > >> not > > > >> be > > > >> able to fit it in the production build without some trimming. > > > > >...