public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Don Osburn" <don.osburn@iscointl.com>
To: "'Mark Salter'" <msalter@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>,
	"Frank Mancuso \(E-mail\)" <frank.mancuso@iscointl.com>
Subject: [ECOS] Can not get redboot to load / run linux binaries on IXP420
Date: Tue, 26 Jul 2005 17:47:00 -0000	[thread overview]
Message-ID: <001d01c5920a$326f7260$9c8534cc@iscointl.com> (raw)
In-Reply-To: <1122390354.5359.5.camel@gienah.localdomain>


Mark,

Thanks again for the help so far.  I am really stumped.  I can not get
redboot to load / run linux on our platform.  I have tried a number of
things with no luck.  Can you or someone help out (please)?

Here's my config;  I am using Redboot v2.01.  Our platform is an IXP420 with
32MB RAM.

I originally used the redboot_ROM.bin image from the npe_enable_bin/ixdp425
directory to boot our platform.  It booted properly (even though we only
have 32MB of RAM).  I then attempted a

>load -r -v -b 0x01600000 zImage
which worked fine.  Then I attempted a
>load -r -v -b 0x00800000 ramdisk.gz
which would hang up every time.  It appeared like the problem was that the
load was writing to RAM being used by redboot, and that was causing it to
hang.

Since I knew we had a different memory config, I rebuilt redboot, modifying
the ixdp425.h file's SDRAM configs.  Specifically, I changed the following
#defines;

#define SDRAM_SIZE                         0x2000000  // 32MB
#define IXP425_SDRAM_CONFIG_INIT  (SDRAM_CONFIG_CAS_3 |
SDRAM_CONFIG_4x16Mx16)

I used the SDRAM_CONFIG_4x16Mx16 because we determined from chapter 7 of the
developer's manual that we needed to set the SDRAM config register to 0x11.
The rebuild worked, and I was able to update the redboot image successfully.

Unfortunately, when I attempted to load the linux images, I got the exact
same result as before.  zImage would load fine, but ramdisk.gz would hang
loading it at 0x00800000.

At this point, I decided to try something different.  The ramdisk.gz image
will load if I put it somewhere else.  Therefore, I did the following:

>load -r -v -b 0x01600000 zImage
>fis create -b 0x01600000 -l 0xc0000 -e 0x00800000 -r 0x01600000 zimage
>load -r -v -b 0x1000000 ramdisk.gz
>fis create -b 0x1000000 -l 0x2e0000 -e 0x00800000 -r 0x1000000 ramdisk
>fis load zimage
>fis load ramdisk
>exec -b 0x01600000

This time the kernel started to boot, but then it failed stating it could
not find a ramdisk at location 0.  Given that, I reloaded the images and
this time did a
>exec -b 0x01600000 -l 0x2e0000 -r 0x100000 -x 0x2e0000
and received the exact same results.  The kernel started, then died when it
could not find a ramdisk a location 0.

There is one last thing we attempted.  We found a note in a mini-howto
document that said for Redboot version 2.01, you are supposed to use
0x11600000 and 0x10800000 instead of 0x01600000 and 0x00800000 respectively.
I attempted the load using these values and got similar results.  (It would
hang during the load.)

At this point I am totally stumped.  How am I supposed to load the zImage
and ramdisk.gz images into my IXP420 board?  How do I get linux up and
running on this board using Redboot?

Help would be greatly appreciated.  This is grinding our project to a halt.

TIA,
Don


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-07-26 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 16:03 [ECOS] Redboot ROM image using RAM? Don Osburn
2005-07-25 16:38 ` Mark Salter
2005-07-26 14:40   ` [ECOS] Where is hal_platform_extras ? Don Osburn
2005-07-26 15:06     ` [ECOS] " Mark Salter
2005-07-26 17:47       ` Don Osburn [this message]
2005-07-26 17:59         ` [ECOS] Can not get redboot to load / run linux binaries on IXP420 Gary Thomas
2005-07-26 18:43           ` Mark Salter
2005-07-29 13:47             ` [ECOS] Can not get redboot to load / run linux binaries onIXP420 Don Osburn
2005-07-29 14:03               ` Mark Salter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001d01c5920a$326f7260$9c8534cc@iscointl.com' \
    --to=don.osburn@iscointl.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=frank.mancuso@iscointl.com \
    --cc=msalter@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).