From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16272 invoked by alias); 25 Jul 2005 16:03:48 -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 16257 invoked by uid 22791); 25 Jul 2005 16:03:44 -0000 Received: from sp0061.sc0.cp.net (HELO n016.sc0.cp.net) (64.97.136.61) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 25 Jul 2005 16:03:44 +0000 Received: from ISCOIL001175 (4.79.76.210) by n016.sc0.cp.net (7.0.038) (authenticated as don.osburn@iscointl.com) id 42D5DEA1001768CC; Mon, 25 Jul 2005 16:03:42 +0000 Reply-To: From: "Don Osburn" To: Date: Mon, 25 Jul 2005 16:03:00 -0000 Message-ID: <000e01c59132$985f6c70$9c8534cc@iscointl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: [ECOS] Redboot ROM image using RAM? X-SW-Source: 2005-07/txt/msg00258.txt.bz2 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? 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. I have been loading images into an Avila eval board for some time with no issues, so I am familiar with the process. However, I have not done any customization to RedBoot on that board. Can someone please explain the difference between the ROM and RAM images for the IXDP425 reference, and hopefully provide some more information on how we should be using this? Our hope was to use the IXDP425 reference bootloader for initial startup, and then customize it later (to reduce memory, etc). FYI, we have read/reviewed all the Intel app notes, and the RedBoot websites. Any help would be appreciated. Don Osburn Lead Engineer Isco International 847-391-9481 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss