| |||
| Home > About Previous Releases > Changes between RVDS v3.0 and RealView Developer Suite v2.2 SP1 > Debugger support in RVDS v3.0 | |||
The major changes to RealView Debugger v3.0 are as follows:
RealView Debugger runs as a single process. The Target Vehicle Server (TVS) no longer exists as a separate entity.
The Connection Control window has been re-engineered. See the RealView® Debugger User Guide for more information.
The features on the Synch tab are available in a separate Synchronization Control window. See the RealView® Debugger User Guide for more information.
The Register pane has been re-engineered. You can create a user-specific view by copying selected registers to a User tab. See the RealView® Debugger User Guide for more information.
The RealView Debugger project manager and related functionality has been removed, so you can no longer create projects and build images within RealView Debugger. However, the source code editing and searching features are still available.
To create and build your projects in RVDS v3.0, use CodeWarrior for RVDS (see CodeWarrior for RVDS changes in RVDS v3.0).
Simulator support has changed. See Simulator support in RVDS v3.0 for more information.
RealView Broker (RVBroker) has been re-engineered. Although RealView Debugger still runs RVBroker automatically for local host, RealView ARMulator® ISS connections, starting RealView Broker for remote simulator connections has changed. You must specify a username when starting RealView Broker on a remote workstation. See the RealView® Debugger Target Configuration Guide for more information.
Support for Multi-ICE® direct connect has been removed in RVDS v3.0.
For more information about the changes to RealView Debugger, see the RealView® Debugger Essentials Guide.