Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

simulavr(1) [debian man page]

SIMULAVR(1)							   User Commands						       SIMULAVR(1)

NAME
simulavr - Atmel AVR simulator SYNOPSIS
simulavr [OPTIONS]... -d DEVICE [IMAGE] DESCRIPTION
Simulate an avr device. The optional IMAGE file is loaded into the flash program memory space of the device. Options -h, --help Show this message -D, --debug Debug instruction output -v, --version Print out the version number and exit -g, --gdbserver Run as a gdbserver process -G, --gdb-debug Print out debug messages for gdbserver -p, --port <port> Listen for gdb connection on TCP port -d, --device <dev> Specify device type -e, --eeprom-image <img> Specify an eeprom image file -E, --eeprom-type <type> Specify the type of the eeprom image file -F, --flash-type <type> Specify the type of the flash image file -L, --list-devices Print supported devices to stdout and exit -P, --disp-prog <prog> Display register and memory info with prog -X, --without-xterm Don't start disp prog in an xterm -C, --core-dump Dump a core memory image to file on exit -c, --clock-freq <freq> Set the simulated mcu clock freqency (in Hz) -B, --breakpoint <addr> Set a breakpoint (address is a byte address) If the image file types for eeprom or flash images are not given, the default file type is binary. If you wish to run the simulator in gdbserver mode, you do not have to specify a flash-image file since the program can be loaded from gdb via the `load` command. If '--port' option is given, and '--gdbserver' is not, port is ignored If running in gdbserver mode and port is not specified, a default port of 1212 is used. If using the '--breakpoint' option, note the simulator will terminate when the address is hit if you are not running in gdbserver mode. This feature not intended for use in gdbserver mode. It is really intended for testing the simulator itself, but may be useful for testing avr programs too. Currently available device types: Use the '--list-devices' option to obtain the list your version of simulavr supports. at90s1200 at90s2313 at90s4414 at90s8515 atmega8 atmega16 atmega103 atmega128 at43usb351 at43usb353 at43usb355 at43usb320 at43usb324 at43usb325 at43usb326 AUTHOR
Written by Theodore A. Roth. REPORTING BUGS
Report bugs to <simulavr-devel@nongnu.org> COPYRIGHT
Copyright 2001, 2002, 2003 Theodore A. Roth. simulavr is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under the conditions of the GNU General Public License. SEE ALSO
http://savannah.nongnu.org/projects/simulavr/ simulavr 0.1.2.2 @DATE@ SIMULAVR(1)

Check Out this Related Man Page

gdbserver(1)						       GNU Development Tools						      gdbserver(1)

NAME
gdbserver - Remote Server for the GNU Debugger SYNOPSIS
gdbserver tty prog [args...] gdbserver tty --attach PID DESCRIPTION
GDBSERVER is a program that allows you to run GDB on a different machine than the one which is running the program being debugged. Usage (server (target) side): First, you need to have a copy of the program you want to debug put onto the target system. The program can be stripped to save space if needed, as GDBserver doesn't care about symbols. All symbol handling is taken care of by the GDB running on the host system. To use the server, you log on to the target system, and run the `gdbserver' program. You must tell it (a) how to communicate with GDB, (b) the name of your program, and (c) its arguments. The general syntax is: target> gdbserver COMM PROGRAM [ARGS ...] For example, using a serial port, you might say: target> gdbserver /dev/com1 emacs foo.txt This tells gdbserver to debug emacs with an argument of foo.txt, and to communicate with GDB via /dev/com1. Gdbserver now waits patiently for the host GDB to communicate with it. To use a TCP connection, you could say: target> gdbserver host:2345 emacs foo.txt This says pretty much the same thing as the last example, except that we are going to communicate with the host GDB via TCP. The `host:2345' argument means that we are expecting to see a TCP connection from `host' to local TCP port 2345. (Currently, the `host' part is ignored.) You can choose any number you want for the port number as long as it does not conflict with any existing TCP ports on the target system. This same port number must be used in the host GDBs `target remote' command, which will be described shortly. Note that if you chose a port number that conflicts with another service, gdbserver will print an error message and exit. On some targets, gdbserver can also attach to running programs. This is accomplished via the --attach argument. The syntax is: target> gdbserver COMM --attach PID PID is the process ID of a currently running process. It isn't necessary to point gdbserver at a binary for the running process. Usage (host side): You need an unstripped copy of the target program on your host system, since GDB needs to examine it's symbol tables and such. Start up GDB as you normally would, with the target program as the first argument. (You may need to use the --baud option if the serial line is running at anything except 9600 baud.) Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'. After that, the only new command you need to know about is `target remote'. It's argument is either a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT descriptor. For example: (gdb) target remote /dev/ttyb communicates with the server via serial line /dev/ttyb, and: (gdb) target remote the-target:2345 communicates via a TCP connection to port 2345 on host `the-target', where you previously started up gdbserver with the same port number. Note that for TCP connections, you must start up gdbserver prior to using the `target remote' command, otherwise you may get an error that looks something like `Connection refused'. OPTIONS
You have to supply the name of the program to debug and the tty to communicate on; the remote GDB will do everything else. Any remaining arguments will be passed to the program verbatim. SEE ALSO
`gdb' entry in info; Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991. COPYING
Copyright (c) 1993 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. Cygnus Support 2 November 1993 gdbserver(1)
Man Page