If the chosen Debug Interface does not have any Debug Configurations, you must create a new Debug Configuration to identify the targets on your development platform, and then connect.

RealView Debugger connects to the specified target using a default connection mode. However, you can specify the connection mode to use.

When connected to a CoreSight component, and that connection is the current connection, only the Registers and Memory views are available in the RealView Debugger Code window.

The state of the Connect to Target window is saved when you exit RealView Debugger. Therefore, the next time you start RealView Debugger in GUI mode, the Connect to Target window is displayed in the same state. That is:

When you first connect to an ARM architecture-based debug target, RealView Debugger might display a warning message in the Cmd tab:

Warning: No stack/heap or top_of_memory defined - setting top_of_memory to 0x00020000.

You can change the top of memory if required:

You can make a connection to a target processor running an OS on your development platform that supports threads.

If you have configured RVISS to use a map file, the memory map is displayed in the Mapfile tab of the Registers view.