All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cam <camilo@mesias.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] board bring up, mpc8555 custom board
Date: Sat, 28 Jan 2006 12:14:58 +0000	[thread overview]
Message-ID: <43DB6042.9050000@mesias.co.uk> (raw)

Hi

We have used u-boot-1.0 on our 8260 based boards with great success.

We are trying to bring up a new mpc8555 based board with u-boot-1.1.4 
but have run into some problems.

We have a BDI probe which is used for programming flash and exercising 
hardware using JTAG.

Using the BDI probe and a fairly extensive config file (which sets up 
TLBs and LAWBARs) we are able to step through the programmed u-boot 
although it has an alignment exception whilst running 
cpu/mpc85xx/start.S (at the part after the comment "Allocate Initial RAM 
in data cache"). We think it's an alignment exception because it jumps 
to the alignment exception handler address and continues briefly.

The u-boot code is modified from the mpc8560ads code, the main 
difference being the boot flash is 32Mb and we have no localbus SDRAM.

I have a suspicion that we shouldn't be trying to single step this 
initialisation code after the BDI has set up the hardware somewhat. I 
have tried a reduced BDI config file and it still doesn't work, and it 
no longer single steps.

Any suggestions how to proceed would be appreciated, does the alignment 
exception after allocating RAM suggest anything to anyone?

Thanks

-Cam

-- 

                                                                      <--
camilo@mesias.co.uk

             reply	other threads:[~2006-01-28 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 12:14 Cam [this message]
2006-01-28 13:37 ` [U-Boot-Users] board bring up, mpc8555 custom board Wolfgang Denk

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=43DB6042.9050000@mesias.co.uk \
    --to=camilo@mesias.co.uk \
    --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.