From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31142 invoked by alias); 3 May 2007 11:35:12 -0000 Received: (qmail 31133 invoked by uid 22791); 3 May 2007 11:35:11 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.182) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 03 May 2007 11:35:09 +0000 Received: by py-out-1112.google.com with SMTP id u77so534274pyb for ; Thu, 03 May 2007 04:35:07 -0700 (PDT) Received: by 10.35.81.2 with SMTP id i2mr3116062pyl.1178192107562; Thu, 03 May 2007 04:35:07 -0700 (PDT) Received: by 10.35.108.11 with HTTP; Thu, 3 May 2007 04:35:07 -0700 (PDT) Message-ID: <876437dd0705030435p1f891falfa3e256a1e495c3e@mail.gmail.com> Date: Thu, 03 May 2007 11:35:00 -0000 From: "alysson brito" To: ecos-discuss@ecos.sourceware.org, "Adam Yergovich" In-Reply-To: <4638C9B6.4020504@jkmicro.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> 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/msg00021.txt.bz2 Hi Adam and all On 5/2/07, Adam Yergovich wrote: > Hi Alysson, > > alysson brito wrote: > > > Thanks Gary! > > > > I really should have payed more attention. > > > > Actually, the result was [almost] the same though :( > > > > RedBoot> load -m xm redboot_RAM.srec > > CCEntry point: 0x00020040, address range: 0x00020000-0x00046d5c > > xyzModem - CRC mode, 3574(SOH)/0(STX)/0(CAN) packets, 5 retries > > RedBoot> go > > $T050f:54000200;0d:ec0ffd03;#e3 > > > > I have also tryed to up load the .bin image (using the -r) but it did > > not work out either: > > > > RedBoot> load -r -m xm -b 0x00020040 redboot_RAM.bin > > CCRaw file loaded 0x00020040-0x00046d9b, assumed entry at 0x00020040 > > xyzModem - CRC mode, 1243(SOH)/0(STX)/0(CAN) packets, 2 retries > > RedBoot> go > > $T0a0f:0002014c;0d:ec0ffd03;#3e > > > > I guess i am almost out of options ... Any other idea of what is still > > wrong ? > > > > In my experience, that is the kind of output you get when you try to > execute something that is not executable or is not properly setup (i.e. > turning on the MMU before executing a kernel). > > Perhaps I have just never done it, but I don't thinnk one usually > executes a ramdisk. I might suggest you take your known good ramdisk in > rom and try to load it the same way to see what happens. > > -Adam > > > -- > Adam Yergovich > Engineer > JK Microsystems > > 1403 Fifth St. Suite D > Davis, CA 95616 > > Tel:(530) 297-6073 > > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > 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 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss