From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23645 invoked by alias); 7 Feb 2007 14:32:38 -0000 Received: (qmail 23300 invoked by uid 22791); 7 Feb 2007 14:32:37 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,TW_PX X-Spam-Check-By: sourceware.org Received: from Unknown (HELO mail.chez-thomas.org) (204.133.123.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Feb 2007 14:32:31 +0000 Received: by mail.chez-thomas.org (Postfix, from userid 999) id 813E5195035C; Wed, 7 Feb 2007 07:32:29 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on hermes.chez-thomas.org X-Spam-Level: Received: from [192.168.1.101] (hermes_local [192.168.1.101]) by mail.chez-thomas.org (Postfix) with ESMTP id 6841419500A1; Wed, 7 Feb 2007 07:32:27 -0700 (MST) Message-ID: <45C9E2FA.9020703@mlbassoc.com> Date: Wed, 07 Feb 2007 14:32:00 -0000 From: Gary Thomas User-Agent: Thunderbird 1.5.0.8 (X11/20061107) MIME-Version: 1.0 To: Guennadi Liakhovetski CC: ecos-devel@ecos.sourceware.org Subject: Re: RedBoot built with gcc 3.4.4 References: <20070207121127.GK19508@lunn.ch> <20070207125232.GL19508@lunn.ch> <45C9CE2B.6060504@mlbassoc.com> <45C9D74B.9070705@mlbassoc.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2007-02/txt/msg00016.txt.bz2 Guennadi Liakhovetski wrote: > On Wed, 7 Feb 2007, Gary Thomas wrote: > >> To debug RedBoot, you'll need to use your BDI. >> >> Simply connect GDB to the BDI instead of the serial port. >> Something like this: >> (gdb) tar rem bdi:2001 > > Aha, ok, this makes sense, but, unfortunately, bdi doesn't work with > this board. It worked somehow with pxa255 (not very reliably) and I > haven't been able to use it with pxa270. Yes, I do have the necessary > register description etc. files, just it wouldn't work. So, I guess, > it's not an option for me. I could disable bootp, but the point was not > to somehow get it to build and run, but to find the reason of the > mis-compilation and (preferrably) fix redboot. Besides, every > non-booting redboot means about 20 minutes jtag flashing... In that case, what I would do is install a working RedBoot (built with 3.3.2) and then experiment with a RAM version built with the new tools. Put in some diag_printf() to trace the code. You might even be able to debug this using the serial connection and GDB (since that does seem to be alive in your ROM/ROMRAM version) -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------