From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12382 invoked by alias); 13 Feb 2004 14:55:25 -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 12343 invoked from network); 13 Feb 2004 14:55:25 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 13 Feb 2004 14:55:25 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3AF9E2B92; Fri, 13 Feb 2004 09:55:24 -0500 (EST) Message-ID: <402CE55C.6070605@gnu.org> Date: Fri, 13 Feb 2004 14:55:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: mohanlal jangir Cc: gdb@sources.redhat.com Subject: Re: hardware support for gdb? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00138.txt.bz2 > I have an ARM board which comes with its own boot monitor, which just brings > up the board. I download RedBoot to bring the target up as well as to > connect with gdb. My question is, what is minimal support required from a > target hardware so that an application like RedBoot can work on it to > connect with gdb and provide debugging. Some sort of "serial" communications channel (from a simple serial device through to mini-tcp on an ethernet device). Andrew