The system design reuse problem is described and the disadvantage of the old methodologies is highlighted. The Motorola DSP Developers Kit (MDDK) solves this by providing dual functions at the behavioural and DSP implementation levels. Having developed a behavioural algorithm in Matlab or a system-level model in Simuiink designers can replace some or all of the implementation independent floating-point functions by fixed-point equivalents that execute actual DSP code on a cycle-accurate co-simulator for the selected DSP core or chip within the Matlab/Simulink environment. The concurrent implementation allows users to view DSP memory from Matlab or the DSP simulator. They can opt to run the DSP functions interactively in which case a fully-featured debugger allows them to debug user-written functions or modify the supplied tinctions. A robust API between Matlab/SimuIink and the underlying simulators coupled with a 'Custom Function Builder' provide advanced users with the means of developing their own functions. Performance profiling features allow optimization by providing information on memory usage, instruction and cycle count. Resimulating the system model in the same tool using the same test fixture provides the user with a very controlled and convenient way of transitioning the design into detailed software implementation.
Click to purchase paper as a non-member or you can login as an AES member to see more options.
No AES members have commented on this paper yet.
To be notified of new comments on this paper you can
subscribe to this RSS feed.
Forum users should login to see additional options.
If you are not yet an AES member and have something important to say about this paper then we urge you to join the AES today and make your voice heard. You can join online today by clicking here.
