Recipes4Linux
Recipes4Linux
DDD-2000 has been extensively tested on the following commercial distributions:
RHL 7.x
RHL 8
RHL 9
The following information has to be filtered when applied to different host distributions. If you did not install all packages doing a custom installation, you may need to install individual RPM files, as required.
All recipes on this site make assumptions about the host, to keep things simpler in the recipes. See this link to review the basic assumptions.
Just above the gdb console window, a new console window is displayed, with the prompt [Not Connected]. This is essentially a telnet interface window with simple command-line editing capabilities.
The telnet window has a simple command-line editor. Input is accepted at the prompt at the bottom of the window. Regardless of where the cursor is positioned, when keyboard input is displayed, the window is scrolled to the last prompt line.
A command line is buffered until a newline is parsed, then the command string is sent to the telnet agent. Backspace is supported to delete characters, but the user is not allowed to backspace over the prompt.
The system specific parameters required to access the BDI-2000 are collected in this menu. All parameter values are text strings and can be modified to reflect your system settings. The settings include parameters that allow the user to telnet to, and connect gdb to, the BDI-2000. Also included are all of the bdisetup parameters required to configure the BDI-2000 the first time you use it. Please see the Abatron BDI-2000 User's Guide for more information on these parameters. The Help button on this dialog box displays information about these parameters, as well. By default, your new settings will be saved when DDD-2000 exits, allowing your settings to survive across multiple-invocations of DDD-2000.
This menu supports the following commands:
| COMMAND | DESCRIPTION |
| connectBDI | open telnet session to BDI-2000 |
| connectGDB | issue gdb target remote call to BDI-2000 |
| reset | issue reset command to BDI-2000 |
| bdiSetup->Version | issue bdisetup -v command (requires serial connection) |
| bdiSetup->Erase | issue bdisetup -e command (requires serial connection) |
| bdiSetup->Update | issue bdisetup -u command (requires serial connection) |
| bdiSetup->Configure | issue bdisetup -c command (requires serial connection) |
| registers | issue rdump command to BDI-2000 |
| breakHard | set breakpoint mode to Hard |
| breakSoft | set breakpoint mode to Soft |
When the bdiSetup commands are running, the status bar at the bottom of the main window is updated to reflect this state. The GUI is unresponsive during these times. One command in particular, the update operation, can take a number of minutes to complete. When any of the bdiSetup commands complete, a dialog box is displayed with information about the command, including the exact command-line that was issued and the response from the BDI-2000.
Contact tmike@recipes4linux.com
Copyright © 2004 Tools Made Tough