public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Don Osburn" <don.osburn@iscointl.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Redboot ROM image using RAM?
Date: Mon, 25 Jul 2005 16:03:00 -0000	[thread overview]
Message-ID: <000e01c59132$985f6c70$9c8534cc@iscointl.com> (raw)

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

             reply	other threads:[~2005-07-25 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 16:03 Don Osburn [this message]
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       ` [ECOS] Can not get redboot to load / run linux binaries on IXP420 Don Osburn
2005-07-26 17:59         ` 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='000e01c59132$985f6c70$9c8534cc@iscointl.com' \
    --to=don.osburn@iscointl.com \
    --cc=ecos-discuss@sources.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).