Re: Remote target (CRIS) DejaGNU config scripts

Daniel Jacobowitz
2004-02-19T17:19:33Z

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On Thu, Feb 19, 2004 at 05:32:52PM +0100, Orjan Friberg wrote:
> The CRIS target I'm running the DejaGNU testsuite on runs Linux. Since
> I'm having problems running a few of the testcases and there seem to be
> quite a few DejaGNU configurations for remote targets I was wondering if
> the way I've implemented the CRIS-specific files is totally backwards.
> (There's no on-chip support for downloading code, like a monitor ROM or
> similar.) Thanks in advance for any suggestions.

It sounds like you're doing this the hard way :) If you are using
current CVS GDB, then you can use the gdbserver-sample.exp baseboard in
current DejaGNU as a template. Please do change the paths - I have
absolutely no idea how that file I posted to gdb@ some months ago ended
up in a DejaGNU release :)

I've attached a modified version that I'm using as I type. It works
pretty much OK. You may need to change host_exec to server_exec in the
call to gdbserver_gdb_load in config/gdbserver.exp, depending on your
setup.

--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer

[-- Attachment #2: gdbserver-board.exp --]
[-- Type: text/plain, Size: 1342 bytes --]

# gdbserver running over rsh.

load_generic_config "gdbserver";

process_multilib_options "";

# The default compiler for this target.
#set_board_info compiler "[find_gcc]";

set_board_info assembler "arm_v5t_le-as";
set_board_info compiler "arm_v5t_le-gcc";
set_board_info c++compiler "arm_v5t_le-g++";

set_board_info rsh_prog /usr/bin/rsh
set_board_info rcp_prog /usr/bin/rcp
set_board_info protocol standard
set_board_info hostname innovator
set_board_info username tools
set_board_info gdb_server_prog /usr/bin/gdbserver

# We will be using the standard GDB remote protocol
set_board_info gdb_protocol "remote"

# Name of the computer whose socket will be used, if required.
set_board_info sockethost "innovator:"

# Port ID to use for socket connection
# set_board_info gdb,socketport "4004"

# Use techniques appropriate to a stub
set_board_info use_gdb_stub 1;

# This gdbserver can only run a process once per session.
set_board_info gdb,do_reload_on_run 1;

# There's no support for argument-passing (yet).
set_board_info noargs 1

# Can't do input (or output) in the current gdbserver.
set_board_info gdb,noinferiorio 1

# Can't do hardware watchpoints, in general
set_board_info gdb,no_hardware_watchpoints 1;

global board_info
set board_info(innovator,rsh_prog) /usr/bin/rsh
set board_info(innovator,rcp_prog) /usr/bin/rcp