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.
(See document for exact affiliation information.)
Click to purchase paper as a non-member or login as an AES member. If your company or school subscribes to the E-Library then switch to the institutional version. If you are not an AES member Join the AES. If you need to check your member status, login to the Member Portal.
