From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9829 invoked by alias); 23 Feb 2009 02:47:15 -0000 Received: (qmail 9821 invoked by uid 22791); 23 Feb 2009 02:47:14 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-gx0-f172.google.com (HELO mail-gx0-f172.google.com) (209.85.217.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Feb 2009 02:47:09 +0000 Received: by gxk20 with SMTP id 20so4485993gxk.2 for ; Sun, 22 Feb 2009 18:47:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.90.66.14 with SMTP id o14mr885320aga.112.1235357226974; Sun, 22 Feb 2009 18:47:06 -0800 (PST) In-Reply-To: References: <6aca9e460902221017h6303f9eej4403f68d4f95cd1@mail.gmail.com> Date: Mon, 23 Feb 2009 02:47:00 -0000 Message-ID: <6aca9e460902221847k448f0f1ctb27dd4ae92338544@mail.gmail.com> From: joseph biswal To: Chris Zimman Cc: Gary Thomas , ecos-discuss@sources.redhat.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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] Redboot run image issues X-SW-Source: 2009-02/txt/msg00100.txt.bz2 Hi Chris; As i stated in my earlier email, i am using a raw binary image version i.e redboot.bin. I hope "-r" would not be a problem in that case. I am using the rom_ram versions of the redboot image as defined by my cdl configuration. When i load the image using BDI, i issue the following command: BDI> load 0x8ff00000 redboot.bin BDI>rm pc 0x8ff00000 BDI>go Then on the serial console, i get the messges for a working image boot. Following is a snapshot from the hyperterminal O/P. NAND part info: 0xaa2c, 0x1580, 0x0050, 0xb476 flash_hwr_init(g_bbt=0x00014208) Searching for BBT table in the flash ... Found version 1 Bbt0 at block 2047 (0xffe0000) Total bad blocks: 1 ... Read from 0x0fee0000-0x0ff00000 at 0x00080000: . ... Read from 0x0fed3000-0x0fed4000 at 0x0009f000: . PMIC ID: 0x0000009d [Rev: 3.5] LAN92xx Driver version 1.1 SMSC LAN9217: ID = 0x117a REV = 0x0 LAN92XX: Waiting to get all clear. LAN92XX: Starting status := 0x40000 LAN92XX: Starting status := 0x40000 Ethernet eth0: MAC address 92:92:92:12:12:16 IP: 172.20.102.116/255.255.0.0, Gateway: 172.20.0.1 Default server: 172.20.16.36 Clock input is 26 MHz RedBoot(tm) bootstrap and debug environment [ROMRAM] Non-certified release, version FSL 200814 - built 12:49:42, Feb 22 2009 Platform: Freescale (i.MX) MX31 3-Stack (Freescale i.MX31 based) PASS 2.0 [x32 D DR] Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited RAM: 0x00000000-0x0ff00000, [0x00014200-0x0fed1000] available FLASH: 0x00000000 - 0x10000000, 2048 blocks of 0x00020000 bytes each. Whereas, when i load and runthe same redboot.bin from an existing working version of "redboot.bin " in RAM, i get the following : It gets stuck after printing "phys_addr=0x80100000" on the serial console. I am guessing something somewhere is wrong in the memory location but i am not sure where to start with. Would it be a problem with the linker script, mlt file or something else? ARe there other files in the HAL i need to look into? WHat actuallly happens when "LaunchRunIMage" in the redboot code is invoked?? ion FSL 200814 - built 14:08:19, Oct 6 2008 Platform: Freescale (i.MX) MX31 3-Stack (Freescale i.MX31 based) PASS 2.0 [x32 D DR] Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. RAM: 0x00000000-0x0ff00000, [0x000141c0-0x0fed1000] available FLASH: 0x00000000 - 0x10000000, 2048 blocks of 0x00020000 bytes each. == Executing boot script in 2.000 seconds - enter ^C to abort ^C RedBoot> ^C RedBoot> ip -l 206.44.17.239/24 -h 206.44.17.89 IP: 206.44.17.239/255.255.255.0, Gateway: 172.20.0.1 Default server: 206.44.17.89 RedBoot> load -v -r -b 0x100000 redboot.bin_paragon Using default protocol (TFTP) | Raw file loaded 0x00100000-0x00144a5b, assumed entry at 0x00100000 RedBoot> run 0x100000 load entry_address=0x100000 virt_addr=0x100000 phys_addr=0x80100000 On Sun, Feb 22, 2009 at 3:19 PM, Chris Zimman wrote: >> If i run the same image by loading it to ram from a JTAG(BDI3000), it >> works just fine. >> I am not able to understand what is the difference when i run the same >> image from JTAG and when i do a "run" from a already running image. > > You need to provide more information on *what* it is that you're loading. > What Gary was asking is if it's an ELF file, SREC, etc. that you're loading > versus a flat binary image. If you're not aware of which type it is, running > 'file' on it will tell you. > > Can you post the exact command you're giving the BDI to load the image? > For the avoidance of doubt, I'm not asking for 'load' or 'load image', but > rather 'load [mem address] image [bin | elf | srec]' -- like the full line. > > --Chris > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss