From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Latest git not working for MPC8349EMDS
Date: Wed, 02 May 2007 10:54:34 -0700 [thread overview]
Message-ID: <4638D05A.9020701@ovro.caltech.edu> (raw)
In-Reply-To: <4638CF06.6000608@freescale.com>
> Not quite. The HRCW at fe000000 must indicate that you want to boot
> from fe000000 (actually, fe000100). To do that, configure U-Boot with
> "make MPC8349ITX_LOWBOOT_config" and flash that u-boot.bin at fe000000.
>
>> => md fe000000
>> fe000000: 04040404 04040404 04040404 04040404 ................
>> fe000010: 00000000 00000000 00000000 00000000 ................
>> fe000020: b0b0b0b0 b0b0b0b0 60606060 60606060 ........````````
>> fe000030: a0a0a0a0 a0a0a0a0 00000000 00000000 ................
>
> Your HRCW is 04040000 b060a000, which means lowboot. You must have
> something overriding your HRCW. How is J22 jumpered?
>
Thanks Timur,
So yeah, as I didn't recall, for low-boot, the HRCW is part of the
U-Boot image. So I think you need to check your jumpers.
Timur mentioned; make MPC8349ITX_LOWBOOT_config
But I'm not sure that would be correct for an MPC8349EMDS board.
So his comment in J22 may refer to the ITX board, not the MDS.
Check the MDS manual, and you'll figure it out.
Dave
next prev parent reply other threads:[~2007-05-02 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 20:12 [U-Boot-Users] Latest git not working for MPC8349EMDS Benedict, Michael
2007-05-01 20:33 ` David Hawkins
2007-05-01 21:12 ` Benedict, Michael
2007-05-01 21:24 ` Timur Tabi
2007-05-01 21:30 ` David Hawkins
2007-05-02 17:29 ` Benedict, Michael
2007-05-02 17:48 ` David Hawkins
2007-05-02 17:54 ` Timur Tabi
2007-05-02 17:48 ` Timur Tabi
2007-05-02 17:54 ` David Hawkins [this message]
2007-05-02 17:56 ` Timur Tabi
2007-05-02 18:10 ` Benedict, Michael
2007-05-02 18:32 ` David Hawkins
2007-05-02 18:33 ` Timur Tabi
2007-05-02 18:49 ` Benedict, Michael
2007-05-02 20:59 ` David Hawkins
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=4638D05A.9020701@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