From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21695 invoked by alias); 23 Apr 2004 16:51:02 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21668 invoked from network); 23 Apr 2004 16:51:01 -0000 Received: from unknown (HELO mms3.broadcom.com) (63.70.210.38) by sources.redhat.com with SMTP; 23 Apr 2004 16:51:01 -0000 Received: from 63.70.210.1 by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (MMS v5.6.0)); Fri, 23 Apr 2004 09:50:45 -0700 X-Server-Uuid: 8D569F9F-42CF-4602-970D-AACC4BD5D310 Received: from mail-sj1-5.sj.broadcom.com (mail-sj1-5.sj.broadcom.com [10.16.128.236]) by mon-irva-11.broadcom.com (8.9.1/8.9.1) with ESMTP id JAA23222 for ; Fri, 23 Apr 2004 09:49:49 -0700 (PDT) Received: from ldt-sj3-010.sj.broadcom.com (ldt-sj3-010 [10.21.64.10]) by mail-sj1-5.sj.broadcom.com (8.12.9/8.12.9/SSF) with ESMTP id i3NGmLov005166; Fri, 23 Apr 2004 09:48:21 -0700 (PDT) Received: (from cgd@localhost) by ldt-sj3-010.sj.broadcom.com ( 8.11.6/8.9.3) id i3NGmL500614; Fri, 23 Apr 2004 09:48:21 -0700 X-Authentication-Warning: ldt-sj3-010.sj.broadcom.com: cgd set sender to cgd@broadcom.com using -f To: martini@sci.univr.it cc: GDB Subject: Re: new board References: <006c01c42930$56a2b7d0$2af21b9d@toti> From: cgd@broadcom.com Date: Fri, 23 Apr 2004 17:23:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 X-WSS-ID: 6C9796EE2JG5820893-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00149.txt.bz2 At Fri, 23 Apr 2004 12:42:44 +0000 (UTC), "Stefano Martini" wrote: > I'm writing programs for a specific mips board. > I need to edit the gdb (sim) source files to add this > board. > > Is there any document about this topic? Not really. > I think I have to specify the memory regions for the board. > Which is the right way to do this? See interp.c. But, my personal favorite method -- not currently supported in unmodified sources, I don't think 8-) -- is to have a "no board" option, and specify all of the devices (hardware files, memory regions, etc.) from the command line. Given that there can be ... dozens of possible board configurations that one might want to model, stuffing them into C code in the simultor is not particularly desirable in my opinion. cgd