From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5101 invoked by alias); 24 Feb 2002 16:55:28 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 5002 invoked from network); 24 Feb 2002 16:55:27 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 24 Feb 2002 16:55:27 -0000 Received: from makita.cygnus.com (makita.cygnus.com [205.180.230.78]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id IAA18178; Sun, 24 Feb 2002 08:55:23 -0800 (PST) Received: from localhost (keiths@localhost) by makita.cygnus.com (8.8.8+Sun/8.6.4) with ESMTP id IAA25058; Sun, 24 Feb 2002 08:55:23 -0800 (PST) X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs Date: Sun, 24 Feb 2002 08:55:00 -0000 From: Keith Seitz X-X-Sender: To: Charles-Henri Balet cc: Insight Maling List Subject: Re: GDB error for angel on ARM oki board In-Reply-To: <001001c1eb76$4f96b670$0401a8c0@CHARLESHENRI> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q1/txt/msg00156.txt.bz2 On Wed, 24 Apr 2002, Charles-Henri Balet wrote: > another infos for the gdb error, this is the message receive when start gdb > and connect > $ arm-elf-gdb > GNU gdb 5.1.1 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "--host=i686-pc-cygwin --target=arm-elf". > (gdb) set remotebaud 9600 > (gdb) target rdi com1 > RDI_open: undefined error message, should reset target > RDI_open failed > Excellent. This is exactly what I wanted to know. You are having problems with the command line, so you need to send this to gdb@sources.redhat.com, where they deal with backend problems with the debugger. They should be able to help you there. I think that you can add the debug stuff into rdi-share by adding "-DDEBUG" to your CFLAGS, i.e., make CFLAGS="-g -DDEBUG" in gdb directory. > (gdb) target rdi com1 > Unexpected read on channel 4, length 192 // > for each reset, I obtain this message > Unexpected read on channel 4, length 192 This isn't so unexpected. The RDI code that ARM "donated" to us really sucks. I don't believe that it can handle re-opening the target like this. You may need to do "detach" first. > "I have tested after this with the ARM SDT 2.50 and the board work fine with > no error to 9600 and 19200 baud" Ok, this is good to know: this removes the possibility that your cable or something is at fault. > the message returned at the connection of the ARM SDT with the board is : > > Angel Debug Monitor V1.20 (ARM Ltd unreleased) for ML671000 CPU Board(OKI) > Built for ARM7TDMI Serial(x1), IRQ > Unreleased build Mar 14 2000 > Serial Rate: 9600 > > You think, ARM has make an proprietary Angel for OKI ???? and not fully > compatible ? and has the little or big endian > mode any importance ? It is possible, that ARM has a special Angel protocol for OKI, but I don't know; it has been a while since I last played with ARM and RDI. You're best bet is to ask over on the gdb list. There are bound to be more people over there that can help. Don't forget to send them the info above (gdb -nw session and that it works using ARM's tools). This is very important for them. Good luck. Keith