System-on-Chip Environment: SCE Version 2.2.0 Beta; Tutorial | ||
---|---|---|
Prev | Chapter 5. Embedded Software Design | Next |
After we generated C code for the DSP, we compile the C code into DSP's instruction set and import the instruction set simulator (ISS) for the Motorola DSP56600. To start importing, select File->Import from the menu bar.
Select directory "IP" from the file selection menu by double Left click.
Inside directory IP, select "DspIss.sir" and Left click on Open.
The SIR file contains the instruction set simulator for our chosen DSP. The behavior loads the compiled object code for the tasks that were mapped to DSP and executes it on the instruction set simulator.
Once "DspIss.sir" is imported, we can notice behavior "DspISS" as a new root behavior in the design hierarchy tree. This is because behavior "DspISS" has not been instantiated yet.
In the design hierarchy tree, select behavior "DSP". Right click and select Change Type.
The type of behavior "DSP" may now be changed by selecting DspISS.
By doing this, we have now refined the software part of our design to be implemented with the DSP56600 processor's instruction set. Recall that the software part mapped to DSP has already been compiled for the DSP56600 processor and the object file is ready. As mentioned earlier, the new behavior will load this object file and execute it on the DSP's instruction set simulator. Thus the model becomes clock cycle accurate.
We now have the clock cycle accurate model ready for validation. We begin as usual with compiling the model by selecting Validation->Compile from the menu bar.
The model compiles correctly as shown in the logging window. We now proceed to simulate the model by selecting Validation->Simulate from the menu bar.
Like in the earlier cases, a simulation window pops up. The DSP Instruction set simulator can be seen to slow down the simulation speed considerably. This is because the simulation is being done one instruction at a time in contrast to the high level simulation we had earlier.
It may take hours for the simulation to complete. The simulation may be killed by selecting Validation->Kill simulation from the menu bar.
The demo has now concluded. To exit the SoC environment, select Project->Exit from the menu bar.