From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18275 invoked by alias); 10 Oct 2003 16:53:43 -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 18231 invoked from network); 10 Oct 2003 16:53:39 -0000 Received: from unknown (HELO ben.lut.ac.uk) (158.125.1.103) by sources.redhat.com with SMTP; 10 Oct 2003 16:53:39 -0000 Received: from [213.107.116.221] (helo=And.Linux) by ben.lut.ac.uk with esmtp (Exim 4.14) id 1A80WI-0008LH-Cf; Fri, 10 Oct 2003 17:53:38 +0100 Subject: Re: GDB --> Parallel Port --> Target?? From: Andrew Batchelor To: Andrew Cagney Cc: GDB Newsgroup In-Reply-To: <3F846765.6070403@redhat.com> References: <1065520908.1048.276.camel@And.Linux> <3F846765.6070403@redhat.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 10 Oct 2003 16:53:00 -0000 Message-Id: <1065804937.1168.19.camel@And.Linux> Mime-Version: 1.0 X-Spam-Score: -4.5 (----) X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *1A80WI-0008LH-Cf*MCfIcCi.tEI* X-Lboro-Filtered: ben.lut.ac.uk, Fri, 10 Oct 2003 17:53:39 +0100 X-SW-Source: 2003-10/txt/msg00178.txt.bz2 On Wed, 2003-10-08 at 20:37, Andrew Cagney wrote: > FYI, it should just work. For GDB, there should really be no difference > between a serial and parallel character interface. [.....] > The correct kernel driver will let GDB talk though to the USB connected > device as if it was a normal serial device. [.....] > Of course, if it's the actual USB chip that your trying to communicate > with, things can get a bit messy. While having the USB chip include a > pseudo-serial interface that talked remote-protocol would work, I've > seen implementations that ended up having a debug agent translate remote > protocol into USB primatives. Thanks for your reply. Oh, right - I guess that saves me a bit of coding then. Have you read the other emails? I'll probably be needing to alter the way GDB sends the characters to the parallel port when I code this protocol converter. Any idea what files I'll be looking at? I've scanned a bit through serial.c and remote.c and found most things I think. Andy