From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23339 invoked by alias); 17 Dec 2012 19:01:15 -0000 Received: (qmail 23326 invoked by uid 22791); 17 Dec 2012 19:01:12 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from tetra.codeconfidence.com (HELO tetra.codeconfidence.com) (94.229.66.225) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Dec 2012 19:00:53 +0000 Received: from cog.dallaway.org.uk (cpc1-cmbg10-0-0-cust34.5-4.cable.virginmedia.com [81.102.132.35]) by tetra.codeconfidence.com (Postfix) with ESMTP id 4C163234C030; Mon, 17 Dec 2012 19:00:51 +0000 (GMT) Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id qBHJ0olX001268; Mon, 17 Dec 2012 19:00:50 GMT Message-ID: <50CF6BE2.1020305@dallaway.org.uk> Date: Mon, 17 Dec 2012 19:01:00 -0000 From: John Dallaway User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121120 Thunderbird/10.0.11 MIME-Version: 1.0 To: schuster_bernd@gmx.net CC: eCos Discussion References: <20121217172456.214150@gmx.net> In-Reply-To: <20121217172456.214150@gmx.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: GDB stub support X-SW-Source: 2012-12/txt/msg00030.txt.bz2 Hi Bernd On 17/12/12 17:24, Bernd Schuster wrote: > unfortunately I couldn`t get GDB working as expected. > > At the moment, I`m able to run Redboot at my target system - mips32 > 24kc processor as ROMRAM version. When redboot starts, I`m able to > see all messages from the redboot bootloader by my serial port ttyS0 > (configurated with 115200 baud). After that redboot starts my > application which is located at the addr 0x800400BC by a short boot > script. > > Now, I`m trying to add GDB support by using the same serial interface > ttyS0. I`m not totally sure if that could be already the problem, > because my application also puts some messages to this serial interface. > > When I enable GDB with the following commands I can see that cutecom - > terminal programm - will go from the open to the close state. That`s > seems a correct behaviour to me. Furthermore I got a very small message > on the serial terminal - something like that: > > RedBoot> > RedBoot>+$#00 You have two host-side applications competing for incoming characters arriving on a single serial port. In the above example, your terminal emulator has received characters intended for GDB. You must close your terminal program before attempting to connect to RedBoot's GDB stub. It is perfectly feasible to use a single channel for both debug and diagnostics as you suggest. You should configure eCos (for your application build) with CYG_HAL_STARTUP == "RAM" and with CYGSEM_HAL_USE_ROM_MONITOR enabled. You should then find that (by default) diagnostic/trace messages from your application are routed via the GDB stub and appear within your GDB session on the host. For avoidance of doubt, you can use the GDB "load" command to download your application to RAM when debugging an application configured for RAM startup. It is not necessary to load it at the "RedBoot>" prompt. I hope this helps... John Dallaway eCos maintainer http://www.dallaway.org.uk/john -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss