search for: bf531

...you good visibility of what's going on within a small "bare metal" target. But such developers a less likely to integrate speex because it simply doesn't fit. I guess I am one of the few that try to run speex entirely from internal RAM and the fact already forced me to move from BF531 to BF533. BTW, the above exercise in deep philosophy at shallow shores shouldn't be taken too seriously ;) >About the inline assembly, I was under the impression that the syntax >was compatible. Could you tell me what's the problem? If it's just one >bit, you can easily remov...

...nt 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 for Blackfin the most popular choice is uCLinux. And &gt...

...ng(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. >> Mostly GSM and proprietary codecs. Or G.726. I a...