public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MPC8349E-MDS working
Date: Fri, 21 Jul 2006 10:51:39 -0700	[thread overview]
Message-ID: <44C1142B.5090507@ovro.caltech.edu> (raw)
In-Reply-To: <1153490473.19682.118.camel@saruman.qstreams.net>


Hi all,

Thanks Dave and Ben, I can now boot with the latest U-Boot.

I was incorrectly flashing the image to the older 0xFE700000
location.

Since this will likely bite someone else, I would like to
create

u-boot/doc/README.mpc8349emds

since there isn't one there already. Is there a standard
style I should follow, or can I just work in the style of
README.mpc83xxads?

Something like this:

1. U-Boot build procedure

2. Upgrading to the latest U-Boot from the Freescale 1.1.3
    patched U-Boot delivered on the board

3. Configuring U-Boot for the board operating in PCI
    agent mode

I've now performed 1 & 2, but haven't looked at 3.

Using od, I see that the HCRW at the start of the U-Boot
image is for PCI Host mode with arbiters enabled,
i.e., the RCW words are (0x04040000, 0xB060A0000).
For agent mode RCW words would need to be
(0x04040000, 0xB060A0000). So when I get to the
PCI agent testing stage, I'll take a look in
the U-Boot source to see is there is a config
option to select agent mode. If you guys have used
that mode, or know of any other changes I would need
to make, please feel free to comment.

Thanks guys!

Regards,
Dave

      reply	other threads:[~2006-07-21 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21  4:25 [U-Boot-Users] MPC8349E-MDS broken in git head, ok at U-Boot-1_1_4 David Hawkins
2006-07-21  5:59 ` Liu Dave-r63238
2006-07-21 13:26 ` Ben Warren
2006-07-21 14:01 ` Ben Warren
2006-07-21 17:51   ` David Hawkins [this message]

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=44C1142B.5090507@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=u-boot@lists.denx.de \
    /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