All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Latest git not working for MPC8349EMDS
Date: Tue, 01 May 2007 16:24:34 -0500	[thread overview]
Message-ID: <4637B012.90709@freescale.com> (raw)
In-Reply-To: <CF7E46FCFF66AD478BB72724345289EC279636@twx-exch01.twacs.local>

Benedict, Michael wrote:
> David Hawkins wrote:
>>> 	I am trying to update U-Boot on my MPC8349EA-MDS.  
>> How old was the U-Boot version that you upgraded from?
>>
> I am upgrading from 1.1.3, that shipped on the board.
> 
>> The MPC9349E boot sequence was modified at one point, and
>> so to boot a new kernel you had to also change the HRCW.
>> I forget the details, but here's my notes ...
>>
>> http://www.ovro.caltech.edu/~dwh/powerpc_mpc8349e.pdf
>>
>> see the comments on p18.
>  
> I am pretty confused by your notes as they relate to my image.  For me,
> I am flashing at fff00000.  This is sufficient to brick the board :-D.
> It seemed like your notes were reflecting a change in the boot address
> between versions?  I tried to use the addresses you mention and 1)
> fe000000 tells me it is not erased, even after I erase it (?) and 2)
> fe700000 seems to have no effect. I thought those were the u-boot
> locations for the mpc8349ITX (?).

The ITX can boot from FE000000 or FEF00000 if you're using the latest code from denx.de. 
FE700000 is the address of the "alternate" U-Boot location.  If you flip a jumper, 
addresses from FE000000-FE7F0000 are swapped with FE800000-FEFFFFFF.  This causes the 
U-Boot that used to be at FE700000 to appear at FEF00000.

Michael, I think your problem is in the configuration.  For instance, you're building a 
U-Boot from the wrong config file, or you're flashing it to the wrong address, or there's 
some low-level config option that's set wrong, like a LAWAR or LAWBAR.

I would use a BDI.  You need to find out which instruction is causing the hang/panic.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  reply	other threads:[~2007-05-01 21:24 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 [this message]
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
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=4637B012.90709@freescale.com \
    --to=timur@freescale.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.