From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30150 invoked by alias); 8 Dec 2003 22:53:53 -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 30135 invoked from network); 8 Dec 2003 22:53:52 -0000 Received: from unknown (HELO SMTP.Lamicro.com) (66.163.8.251) by sources.redhat.com with SMTP; 8 Dec 2003 22:53:52 -0000 Received: from Spooler by SMTP.Lamicro.com (Mercury/32 v3.32) ID MO00F2C3; 8 Dec 03 17:55:33 -0500 Received: from spooler by Lamicro.com (Mercury/32 v3.32); 8 Dec 03 17:55:21 -0500 Received: from Connotech.com (216.162.71.146) by SMTP.Lamicro.com (Mercury/32 v3.32) with ESMTP ID MG00F2C1; 8 Dec 03 17:55:08 -0500 Message-ID: <3FD5041B.82C5C29B@Connotech.com> Date: Mon, 08 Dec 2003 22:53:00 -0000 From: Thierry Moreau X-Accept-Language: en MIME-Version: 1.0 To: Torsten Mohr CC: gdb@sources.redhat.com Subject: Re: transfer own data via GDB remote protocol, flash a micro References: <200312082123.40897.tmohr@s.netic.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-12/txt/msg00150.txt.bz2 Torsten Mohr wrote: > Hi, > > lets say i'm building a hardware debugger that understands > GDB remote protocol. And further, that debugger needs > some info about the hardware that it is attached to. > > Can i somehow transfer this data via GDB remote protocol? > > I didn't see anything in the info pages, so i think > this does not work. > > As an example, i may want to tell the hardware the > target voltage, the quarz frequency, some settings > like, ... > > Another question, is it somehow possible to "flash" > an attached micro via GDB remote protocol? > My understanding is that *hardware debugger* is somehow outside the scope of the GDB project. The various commercial hardware debuggers I worked with (three of them) used a combination of a) implicit knowledge of the target processor/debug port architecture, b) editable definition files, and c) debugger command script files. I guess that you need to implement at least a) and c) in your GDB project. GDB sould have a command and protocol frame that selects the target architecture, so the flavor of a) can be selected among the target families that you support. If you find necessary or convenient to use some editable definition files (b)), you might find useful to download these files with some protocol. The flash algorithm is perhaps part of a). Alternatively, the flash operation can be performed by the target itself if you can download a program in the target RAM and let this program do the flash programming (I found this approach effective, but my target HW has plentiful RAM resources). Sincerely, -- - Thierry Moreau CONNOTECH Experts-conseils inc. 9130 Place de Montgolfier Montreal, Qc H2M 2A1 Tel.: (514)385-5691 Fax: (514)385-5900 e-mail: thierry.moreau@connotech.com