From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31761 invoked by alias); 21 Nov 2007 16:10:26 -0000 Received: (qmail 31751 invoked by uid 22791); 21 Nov 2007 16:10:26 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Nov 2007 16:10:19 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ius7X-0007ZY-Bd for gdb@sources.redhat.com; Wed, 21 Nov 2007 16:08:11 +0000 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Nov 2007 16:08:11 +0000 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 21 Nov 2007 16:08:11 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: Memory map with vFlashWrite Date: Wed, 21 Nov 2007 16:10:00 -0000 Message-ID: References: <47444151.90604@geensys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.4 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-11/txt/msg00210.txt.bz2 Guillaume MENANT wrote: > Hello, > > 1 - Is the memory map mandatory for using vFlashXxxx commands ? Yes. The memory map should come as XML via target -- there's 'mem' command that can be used to define memory map from gdb side, but I don't think it can handle flash. > 2 - If yes, how does it works ? Gdb sends a "qSupported" command, then > the stub answers with "qXfer:memory-map:read", then Gdb sends a > "qXfer:memory-map:read::offset,length" and then the stub answers with an > "l data" ? Yes. > 3 - If the process is correct, what values do we use for offset and > length "qXfer:memory-map:read" command ? Do we send the whole XML file > in the "l data" reply ? Who are "we"? GDB generally will try to read data using chunks as bit as the remote side can handle. The remote side should behave as specified in the qXfer documentation -- in particular, I don't think it's allowed to return more data than asked for. - Volodya