原创 RF5架构的替代方案

2010-5-24 14:15 1912 2 2 分类: 处理器与DSP

TI是这样解释的:

The Reference Frameworks were created to enable people to plug their XDAIS-compliant algorithms into a production ready framework. There was nothing that was wrong per se with the Reference Frameworks. Rather TI needed a more flexible framework that could be used on newer processors that might be DSP-only, ARM+DSP, ARM+accelerator, or even ARM only. So you might say that Codec Engine along with its underlying components like DSP/BIOS Link and the Framework Components have replaced the Reference Frameworks. Like the Reference Frameworks, XDAIS remains at the heart of Codec Engine. There has also been an extension to XDAIS called XDM (XDAIS Digital Media).

Here are some related links:
http://tiexpressdsp.com/index.php/Codec_Engine_Overview
http://tiexpressdsp.com/index.php/Codec_Engine_FAQ
http://tiexpressdsp.com/index.php/Framework_Components_FAQ
http://tiexpressdsp.com/index.php/XDM_FAQ

If your project is being done on a 6713 then you may want to continue using Reference Frameworks. Codec Engine came into business after the 64x+ core had already been released. It supports the 64x+ core and the 674x core. I don't believe it supports 6713 as cache would be different on 67x.

大致意思是说,TI为了满足不同器件的要求,需要一个更有灵活性的架构。用Codec_Engine及其底层的Framework_Components和XDM替代了RF5.从64x+开始就不再支持RF5了。红色的部分大概是说RF5本身没有错,不知理解的对不对?



PARTNER CONTENT

文章评论0条评论)

登录后参与讨论
EE直播间
更多
我要评论
0
2
关闭 站长推荐上一条 /3 下一条