From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17048 invoked by alias); 7 Oct 2009 16:20:14 -0000 Received: (qmail 17038 invoked by uid 22791); 7 Oct 2009 16:20:13 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 07 Oct 2009 16:20:09 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id E3C062F78024; Wed, 7 Oct 2009 17:20:06 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OdWx2E+H-GRH; Wed, 7 Oct 2009 17:20:05 +0100 (BST) Date: Wed, 07 Oct 2009 16:20:00 -0000 Message-Id: From: Bart Veer To: Jim Bradleigh CC: ecos-discuss@ecos.sourceware.org In-reply-to: <251121.2631.qm@web87016.mail.ird.yahoo.com> (message from Jim Bradleigh on Fri, 2 Oct 2009 14:06:39 +0000 (GMT)) References: <200910021236.44312.ilindner@logopak.de> <413284.87577.qm@web87014.mail.ird.yahoo.com> <251121.2631.qm@web87016.mail.ird.yahoo.com> 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: Re: [ECOS] Debugging Redboot.. X-SW-Source: 2009-10/txt/msg00039.txt.bz2 >>>>> "Jim" == Jim Bradleigh writes: Jim> Hi, Jim> Is there a guide to how to debug "into" redboot? Jim> I`ve managed to get redboot loaded via GDB (using redboot Jim> itself) and I can get the application to run, and certain Jim> breakpoints to function during easrly startup. Jim> However when the redboot prompt appears I cannot Ctrl+C and Jim> any breakpoints don`t seem to trigger (i.e. when debugging Jim> redboot commands) Jim> Are there special options required to allow me to gain full Jim> access to debug redboot? In general you cannot use a ROM RedBoot to debug a RAM RedBoot, or anything along those lines. The problem is that RedBoot always takes over certain bits of hardware, including the h/w exception vector(s) used for debugging and the uart for communicating with the host. Hence shortly after the RAM RedBoot start running the ROM RedBoot will become disconnected from the rest of the world, and can no longer interact with gdb. Changing this behaviour is non-trivial. Hence debugging RedBoot itself generally involves jtag or similar h/w debug support. If that is not available then you may have to resort to debugging via diag_printf()'s. Bart -- Bart Veer eCos Configuration Architect eCosCentric Limited The eCos experts http://www.ecoscentric.com/ Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. >>>> Visit us at ESC-UK http://www.embedded.co.uk <<<< >>>> Oct 7-8 on Stand 433 at FIVE ISC, Farnborough <<<< -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss