From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6621 invoked by alias); 25 Jul 2005 16:38:10 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 5976 invoked by uid 22791); 25 Jul 2005 16:37:37 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 25 Jul 2005 16:37:37 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j6PGbadQ019048 for ; Mon, 25 Jul 2005 12:37:36 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j6PGbaV31117; Mon, 25 Jul 2005 12:37:36 -0400 Received: from 172.16.50.80 (vpn50-80.rdu.redhat.com [172.16.50.80]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j6PGbX2k003881; Mon, 25 Jul 2005 12:37:35 -0400 From: Mark Salter To: don.osburn@iscointl.com Cc: ecos-discuss@sources.redhat.com In-Reply-To: <000e01c59132$985f6c70$9c8534cc@iscointl.com> References: <000e01c59132$985f6c70$9c8534cc@iscointl.com> Content-Type: text/plain Date: Mon, 25 Jul 2005 16:38:00 -0000 Message-Id: <1122309452.3293.20.camel@gienah.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [ECOS] Redboot ROM image using RAM? X-SW-Source: 2005-07/txt/msg00260.txt.bz2 On Mon, 2005-07-25 at 11:04 -0500, Don Osburn wrote: > Greetings, and I hope this is the correct group this time... > > We have a new custom board we are attempting to bring up and are having some > difficulty with Redboot. Our design is intel IXP425 reference with the > following exceptions. We are using an IXP420 with an LXT971A PHY attached > to ethernet 0 only. (The ref design has LXT972A attached to ethernet 0 and > ethernet1 on an IXP425.) > > We have successfully burned redboot into flash and can boot. The problem is > we can not understand where / how to load the snapgear images into flash to > boot linux. > > I am using the NPE-enabled binaries for Redboot v2.01. I use the > redboot_ROM.bin file from the ixdp425 directory and burn it into Intel > strata_flash. It boots with a warning about NPE A. Not sure about that > warning, but I can do an fconfig and fis init and everything looks fine. > (The warning may be do to the PHY difference.) > > At this point I do a > RedBoot> load -r -v -b 0x01600000 zImage > and it works. However, when I attempt a > RedBoot> load -r -v -b 0x00800000 ramdisk.gz > > The processor hangs. After poking around in memory for a while, we are > pretty confident that what is happening is redboot is using memory around > 0x00800000 to run itself. So, when we attempt to write to that area in RAM, > we are stomping on the bootloader. (?) Why is that? Our understanding was > if you loaded the ROM image, it should not use RAM? RedBoot is mostly C code, so of course it uses RAM. The startup banner which RedBoot prints will tell you what RAM area is available for the user. For IXDP425, I see: RAM: 0x00000000-0x10000000, [0x00029888-0x0ffd1000] available This tells me that 0x00029888-0x0ffd1000 is not being used by RedBoot. If RedBoot is indeed using RAM in this area, then it is a bug. I would make sure that the zImage and ramdisk.gz files actually fit into the available RAM area without overrunning into RAM used by RedBoot. > > We are having great difficulty understanding the documentation on this. > What is the difference between the ROM and the RAM images? Also, when we > attempted to burn / load the RAM image, it doesn't work at all. ROM RedBoot is located in and runs from ROM (although it also uses RAM for .data, .bss, etc). RAM RedBoot is meant to be loaded into and run from RAM. ROMRAM RedBoot is located in ROM, but copies itself into RAM and thereafter executes from RAM exclusively. --Mark -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss