From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24002 invoked by alias); 31 Mar 2003 18:17:33 -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 23995 invoked from network); 31 Mar 2003 18:17:33 -0000 Received: from unknown (HELO wf-rch.cirr.com) (12.237.214.24) by sources.redhat.com with SMTP; 31 Mar 2003 18:17:33 -0000 Received: from acm.org (desk.minyard.local [192.168.27.131]) by wf-rch.cirr.com (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id h2VIHSu05029; Mon, 31 Mar 2003 12:17:28 -0600 Message-ID: <3E888638.4060308@acm.org> Date: Mon, 31 Mar 2003 18:17:00 -0000 From: Corey Minyard User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021204 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Svein E. Seldal" CC: gdb@sources.redhat.com Subject: Re: Porting advice References: <3E81F982.5080802@solidas.com> In-Reply-To: <3E81F982.5080802@solidas.com> X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00417.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You would save yourself a lot of work if you went to Google and type "TI DSP gdb". It gives the following web site: http://www.elec.canterbury.ac.nz/c4x/ - -Corey Svein E. Seldal wrote: | Hello, | | I'm working on porting a new target for gdb, the tic4x, or Texas Instruments TMS320C3x and TMS320C4x (DSP's). I have been looking into the gdb sources and I have a couple of questions regarding the porting job. | | The configuration patch is done, and since tic4x exists already in binutils, bfd and opcodes are also done. The only work needed, it seems like, is gdb and sim. | | - What approach is the best when doing a new port? I have read the gdb internals manual, but I must admit that I dont quite get the overall picture from it. | | - Are there any other targets which serve good as a "template"? I see references in the gdbint manual to d10v. Please note that the tic4x target will always be a cross target, never native. | | - For a cross target what is required? | | I have written a TCP gdbserver which accepts the standard gdb remote commands which talks to actual hardware. My primary use of gdb is to be able to talk to this gdbserver and to examine the runtime code, set breakpoints, etc. My second (distant) use of gdb is to use a simulator. | | My problem is that I cannot find any references to any cross targets not linking in a simulator. Is this the case? If I edit my local gdb/config/tic4x/tic4x.mt and remove the "SIM = " line, compilation of gdb croaks and dies because of missing sim symbols. Is it possible to build a target gdb without the usage of a simulator? | | - What does the "SIM_OBS =" line in the gdb/config/tic4x/tic4x.mt file do? | | - Should I enable multi-arch support now? I mean, this being a totally new target and all? | | - What "struct gdbarch" methods do I need to have implemented in gdb/tic4x-tdep.c? Is there a collected documentation of the methods somewhere? (I've read gdbarch.sh, but more detailed examples would be very nice.) | | | Hmmm.. Too many questions to get any consistent answer... Well, lets try anyway... | | Regards, | Svein Seldal | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+iIY2IXnXXONXERcRAqE7AJ9j/e7UrnM/20Yhzy/rjYX9Wo9MIACfaSEB buydFbeMAoXp7y7vqacaGjY= =5AlP -----END PGP SIGNATURE-----