User`s manual

Managing Projects with Multiple Devices
Motorola Tips about Special Projects 4-3
As long as a simulated device is configured ON, it is active during execution commands
such as Go, Step,orTrace, and responds to them appropriately. To make a given device
inactive (so that it no longer responds to execution commands), configure it as
OFF.
A simulator maintains a separate window of each of these types for each simulated device:
• Assembly window to display the assembled code loaded for that device;
• Breakpoints window to display the breakpoints defined for that device;
• Calls window to display function calls to that device;
• Input window to display simulated input to that device;
• Memory window to display designated locations on that device;
• Output window to display simulated output from that device;
• Register window to display designated registers of that device with their contents;
• Session window to display session activity with respect to that device;
• Stack window to display the C function stack (if appropriate);
• Source window to display C source code (if appropriate);
• Watch window to display items on a watch list for that device.
Those windows are titled with the device number (e.g., Dv00 Assembly or Dv28 Source)
to help you identify data associated with each device.
A Suite56 simulator can also profile multiple devices
separately. For each device in turn, in the Modify menu,
choose Device, and then select Set Default. While a
given device is the default, in the File menu, choose
Log, and then select Profile. A dialogue box appears for
you to indicate the name and location of the log file in
which to save the profile for that device. Repeat these
steps to create a separate profile for each device in turn.
In the text-based interface, use the
log command with a device number and file name as
parameters and the option
P to indicate profile.
A Suite56 simulator simulating multiple devices can be especially useful when you are
developing real-time application code for a single target device, as we explain in Section
4.2.4, "Simulating Communication between Serial Devices," on page 4-6.