search for: bf532

...G method is not efficient in reducing the code footprint because the majority of the overhead happens in the points of invocation of the speex_warning rather than in the function itself. With all my suggestion applied there is an opportunity that minimized speex would fit in on-chip code memory of BF532 (48KB). However the original goal of fitting in BF531 (32KB of on chip code memory) seem impossible even then. >> So >> developers that integrate speex tend to have plenty of RAM and once >> one has plenty of RAM he could install biggish OS. And between >> biggish OSes fo...

...#define OVERRIDE_SPEEX_WARNING >#define speex_warning(x) {} >in user_misc.h? That should do the trick. May be. But once again, why not do it in official release? >> With all my suggestion applied there is an opportunity that minimized speex would fit in on-chip >> code memory of BF532 (48KB). However the original goal of fitting in BF531 (32KB of on chip code >> memory) seem impossible even then. > >32 kB for Speex appears quite possible to me. Especially considering >you're only interested in the decoder, right (or was it the encoder)? No, I need both. &gt...