From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29699 invoked by alias); 4 May 2007 11:43:45 -0000 Received: (qmail 29691 invoked by uid 22791); 4 May 2007 11:43:43 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.176) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 04 May 2007 11:43:41 +0000 Received: by py-out-1112.google.com with SMTP id u77so941547pyb for ; Fri, 04 May 2007 04:43:39 -0700 (PDT) Received: by 10.35.75.1 with SMTP id c1mr5153942pyl.1178279019331; Fri, 04 May 2007 04:43:39 -0700 (PDT) Received: by 10.35.113.15 with HTTP; Fri, 4 May 2007 04:43:39 -0700 (PDT) Message-ID: <876437dd0705040443q5be9b8b6tf8e614fd28525e2b@mail.gmail.com> Date: Fri, 04 May 2007 11:43:00 -0000 From: "alysson brito" To: "Chris Zimman" , ecos-discuss@ecos.sourceware.org In-Reply-To: <876437dd0705030554jf8667edq4f9cd13021e93f2a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <876437dd0705020801t68d84716s9a8c1c8be3dfa2a3@mail.gmail.com> <876437dd0705020802p3aa1463dud27d963ed09fa5eb@mail.gmail.com> <4638A9E0.2000909@mlbassoc.com> <876437dd0705021017l3d684b0y88b25d40ec4fdcee@mail.gmail.com> <4638C9B6.4020504@jkmicro.com> <876437dd0705030435p1f891falfa3e256a1e495c3e@mail.gmail.com> <4B24CC52E8A6EB4A95B414126492987C0334836E@lo2525.corp.bloomberg.com> <876437dd0705030554jf8667edq4f9cd13021e93f2a@mail.gmail.com> X-IsSubscribed: yes 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] Re: Trash when running RAM image X-SW-Source: 2007-05/txt/msg00032.txt.bz2 Hi On 5/3/07, alysson brito wrote: > Hi Chris > > On 5/3/07, Chris Zimman wrote: > > Alysson, > > > > Hook up GDB and see where it's crashing. There's not nearly enough > > information to tell you much further. What is the image that you're > > trying to run? > > > > --Chris > > > > -----Original Message----- > > From: ecos-discuss-owner@ecos.sourceware.org > > [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of alysson > > brito > > Sent: 03 May 2007 12:35 > > To: ecos-discuss@ecos.sourceware.org; Adam Yergovich > > Subject: Re: [ECOS] Re: Trash when running RAM image > > > > Thanks for the reply! Actually I am trying to run an RAM image of > > redboot, not a ramdisk, I might have written something wrong, sorry. > > > > The problem still persists, I have seen that Gary wrote today on "Re: > > [ECOS] standalone Redboot configuration" that some ARM have to get > > some massage to runging RAM images, I do not know whether this is a > > case, since xscale is arm based. > > > > If some one can help me out really I'd really apreciated some more tips. > > > > -- Alysson > > > > > > Yeah, It might be the only way to go, since I can not figure out what > the problem might be .... leider ... > > I am trying to run an redboot_RAM.srec file, that came along with the > board (processor xscale ixdp425) software toolkit. If you wanna, I can > send it to you via email. > > Thanks > > --Alysson > Sorry, for the question, but I am wondering whether I can hook up on gdb server of redboot rom image an debug the redboot_ram. I even tryed, but I got a SIGTRAP after some instructions (is the board been reset cause redboot ram image ?). Then "nexti" command does not go any further ... Could anyone pls tell me if it is possible to use gbd to test a redboot ram image ? Or must I really use a JTAG? -- Alysson -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss