From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25601 invoked by alias); 25 Feb 2002 20:04:34 -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 25531 invoked from network); 25 Feb 2002 20:04:32 -0000 Received: from unknown (HELO conn.mc.mpls.visi.com) (208.42.156.2) by sources.redhat.com with SMTP; 25 Feb 2002 20:04:32 -0000 Received: from grante.comtrol.com (grante.dsl.visi.com [208.42.141.248]) by conn.mc.mpls.visi.com (Postfix) with SMTP id AE79D81BD for ; Mon, 25 Feb 2002 14:04:31 -0600 (CST) Received: (qmail 13667 invoked by uid 500); 25 Feb 2002 20:11:42 -0000 Date: Mon, 25 Feb 2002 12:04:00 -0000 From: Grant Edwards To: Charles-Henri Balet Cc: gdb@sources.redhat.com Subject: Re: GDB using Angel error on an OKI board Message-ID: <20020225141141.A13658@visi.com> References: <005801c1bd6a$b6545e10$0401a8c0@CHARLESHENRI> <20020225102723.A11481@visi.com> <000f01c1ebb8$84dbc630$0401a8c0@CHARLESHENRI> <20020225131735.A13155@visi.com> <000501c1be32$8ea031f0$0401a8c0@CHARLESHENRI> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <000501c1be32$8ea031f0$0401a8c0@CHARLESHENRI>; from charles-henri@bluewin.ch on Mon, Feb 25, 2002 at 08:28:08PM +0100 X-SW-Source: 2002-02/txt/msg00310.txt.bz2 > I have tried this command "set rdiheatbeat off" but the result > is the same, with the "maint rdilogen on" as : > tx: [T=0 L=36] 03 01 00 01 05 00 03 00 00 00 00 00 ff ff ff ff ff ff ff ff 01 00 00 00 00 c0 00 00 01 00 00 00 80 25 00 00 > R=00030005 H->T CI_HBOOT: ADP_ParamNegotiate 00000001 0000c000 00000001 00002580 > rx: [T=0 L=36] 03 02 01 01 05 00 03 80 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00 01 00 00 00 00 c0 00 00 80 25 00 00 > R=80030005 H<-T CI_HBOOT: ADP_ParamNegotiate 00000000 00000001 0000c000 00002580 > tx: [T=0 L=20] 03 02 00 01 06 00 03 00 00 00 00 00 ff ff ff ff ff ff ff ff > R=00030006 H->T CI_HBOOT: ADP_LinkCheck Ah yes. That link check command isn't sent by the heartbeat feature -- it's part of the serial-port negotiation sequence. It's possible for both ends to switch baud rates after the initial parmeter negotiation, so a link check is sent to make sure both ends are still talking. The board isn't responding to the link check command. It is supposed to reply with another link check frame. [At least that is what happens with the ADP devices I have.] I suppose you could go into the rdi code and try to skip over that step in the start-up process to see if the board handles the rest of the ADP commands correctly. Or, you could try to capture the sequence used by the debugger that works. [Please cc: the mailing list, since it is the collective memory of the gdb community. We certainly don't want to depend upon either my memory or my record-keeping skills.] -- Grant Edwards grante@visi.com