1 ® Development Tools The CodeWarrior Development Studio everything the professional embedded CodeWarrior® Development provides a highly visual and automated developer needs: Studio is a complete framework that accelerates the development • CodeWarrior C/C++ Compiler Suite of even the most complex applications. • Runtime libraries integrated development Creating applications is fast and easy for • Assembler environment (IDE) from developers of all experience levels. As • Standard template library (STL) hardware bring-up through a single development environment, it is consistent across all supported workstations programming embedded and personal computers with an organization. Source-Level Debugger applications. By combining On each of the supported platforms, the Provides a high-performance windowed source-level debugger equipped with the state-of-the-art debugging features and uses are identical. There is no need to worry about host-to-host latest productivity—enhancing graphical technology with the simplicity incompatibilities. Learn once, use everywhere. features to shorten board bring-up and of a robust development application development time; uses the environment, CodeWarrior The CodeWarrior Development Studio symbolics database to provide source-level contains all of the tools needed to complete debugging; supports symbol formats such Development Studio takes a major embedded development project. as Microsoft® CodeView®, Debug With source-level debugging Arbitrary Records Format (DWARF) and embedded application Complete Set of Tools and STABS. From text editors to compilers and debuggers, development to a new level. CodeWarrior development studio provides 2 Instruction Set Simulator Text Editor Source Browser Jump-starts application development with Enables the creation and manipulation Maintains a symbolics database for the an integrated instruction set simulator (ISS). of source code and other text files and program (examples of symbols include is completely integrated with other names and values of variables and functions); Project Manager IDE functions. uses the symbolics database to assist code Handles top-level file management for the navigation; links every symbol to other software developer; organizes project items locations in the code related to that symbol; by major group, such as files and targets; Search Engine processes both object-oriented and tracks state information (such as file Finds a specific text string or replaces found procedural languages. modification dates); determines build order text with substitute text across multiple and inclusion of specific files in each build; files and directories; allows use of regular coordinates with plug-ins to provide services expressions; provides file-comparison and like version-control and RTOS support. differencing functionality. Debugger By combining a state-of-the-art IDE with the simplicity of a windowed environment, the debugger takes C/C++ source-level debugging to a new level. The debugger assembles a wide array of high- powered components and features into a powerful GUI to help get projects completed and to market ahead of schedule and under budget. All of the debugger hardware and software features provide simple access and execution. Any debug operation desired is done through an intuitive “point-and-click” interface to make debugging fast, flexible and easy. Window-Based Workspace Seamless Integration Single-Stepping Environment The debugger is fully integrated with a variety Supports the common single-stepping The debugger enables developers to operate of run-control devices like Ethernet TAP and mechanisms (Step Into, Step Over, Step more efficiently with user-friendly debugging, CodeWarrior USB TAP, resulting in optimized Out), stepping statements in source-level multiple windows, point-and-click capabilities run-control and faster downloads. display and instructions in Assembler and and outline format. mixed-mode level display. Single-stepping can be performed in any of the source code Full-Featured Debugging display windows (stack crawl window, class The debugger’s interface allows users to The debugger provides a rich set of browser window, source file window and customize the workspace to fit their needs: debugging features designed to help symbolics window). to create custom buttons, toolbars and the developer quickly find and repair menus, and to “float” windows that are an software defects. Contextual Data integral part of the debugger so that they Displays data values at a glance for become independent windows on the work Stack Crawl Window variables in source windows during station. This provides increased visibility and Displays information about a suspended execution. In addition to standard toolbar control over the display of information in the thread or process while debugging—all in tool tips common to applications, the debugger. Windows that have been separated debugger reveals contextual data when the primary window used during a debug from the debugger can also be “docked” to developers mouse over the variable in the session. The stack crawl window can be rejoin the main debugger workspace controls. source statement. used to view the call stack for a function, view function variables and global data, The debugger’s workspace allows users view a routine in source, assembler or Preprocessor Information to focus on complex debugging tasks. mixed-mode, view the current program Provides clear understanding of the code Each workspace contains just the set of being generated and relevant scoping counter indicating the statement about views needed for the task at hand. The used during the build cycle in the current to be executed, view and set breakpoints application workspace provides a high-level debug context. for the current function or single-step view of the target software, while the through the current function from the hardware workspace provides a low-level program counter. view of the target hardware. 3 Breakpoints Special Breakpoints Register Details Window Sets breakpoints in source display windows Special breakpoints halt program execution Shows the contents of a given register in with a simple click on the window’s left for very specific reasons, such as when pro- a format similar to a processor data book. margin or by dragging a source statement gram execution arrives at the beginning of the Register and bit field descriptions are included or assembly instruction to the breakpoints function main(), a C++ exception occurs or an along with logical groupings of bits into value window. A separate breakpoints window event occurs that the debugger plug-in has fields. Bit field values can be modified manu- in the debugger allows developers to view defined as a break event. Developers cannot ally or from a list of relevant value choices. all breakpoints consolidated into a single change or delete special breakpoints, but they The display of register details is controlled by worksheet and save them to disk for use can enable and disable them. a user-modifiable XML register description file. later or for sharing with other project members. Memory Window Cache Window CodeWarrior Debugger Displays data in various data formats: raw Displays current values and state of cache Offers Many Different hexadecimal and ASCII, standard C data contents for each data and instruction cache Types of Breakpoints types, structures and enumeration types within the target processor. Cache writes allow from the current debug project, or as developers the freedom to edit cache contents Eventpoints machine instructions either in machine and experiment with cache behavior as it Eventpoints are used to perform a task language assembly or displayed related to relates to the current code being debugged. when program execution arrives at a source code. The memory window displays specific line of source code or when an data in a “raw” hexadecimal format, as well Object File Format associated conditional expression evaluates as ASCII, with the word-length variable Supports STABS and ELF/DWARF to true. Developers can set an eventpoint through a drop-down selection at the bottom (version 1 and 2) object file output formats. that performs a task such as logging or of the screen. The memory window allows speaking a string or expression and then for the display and editing of memory Multi-Thread/Process Debugging* recording messages to the log window, locations. Allows for editing in the context Enables debugging of multi-threaded applications pausing execution just long enough to refresh of the current display format—for example, and multiple processes. Debugging can select debugger data, running a script, playing a “view as int” allows editing an integer value. and debug a single thread, multiple threads sound, skipping execution of a line of source Establishes selected memory addresses as or all threads—based on debug preferences. code or collecting trace data. An eventpoint is a watchpoint for conditional execution simply Each thread being debugged can be managed equivalent to a breakpoint that performs a task by right-click mouse selection. through the threads window or separate stack other than halting program execution. crawl windows per thread. Register Window *This capability is not available for all processors. Watchpoints Shows a complete list of available processor Watchpoints halt program execution when and peripheral registers, both built-in and a specific location in memory changes value. memory mapped. Registers are grouped Multi-Core Debugging