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] Confusion in loading of reset configuration words on MPC8360
Date: Tue, 18 Nov 2008 14:30:37 -0800	[thread overview]
Message-ID: <4923420D.6040704@ovro.caltech.edu> (raw)
In-Reply-To: <20081118131735.AD837280E2@theia.denx.de>

Hi Elison,

> I have confusion in the manner the MPC8360 loads the reset configuration
> words from FLASH. According to the datasheet, it should read from the
> following locations:
> 
> 0x00 0x08 0x10 0x18 0x20 0x28 0x30 0x38

http://www.ovro.caltech.edu/~dwh/carma_board/powerpc_mpc8349e.pdf

p33 has a logic analyzer capture from an MPC834EA board. It'll
be similar on the MPC8360.

The logic analyzer captures the address bits in little-endian
order due to the way the logic analyzer header was routed on
the PCB (and the inability of the logic analyzer to flip them)
so, the 5-bits get shown in bit-reversed order, i.e.,

LA[27..31] bits     logic analyzer trace
   0x00     0_0000   0x00
   0x08     0_1000   0x02
   0x10     1_0000   0x01
   0x18     1_1000   0x03

But the addresses are as per the data sheet.

> But I have observed the following on my board. The LCS goes low for eight
> cycles.

Hmm, the p33 trace show LCS# low always, and its ALE you want
to trigger off. I think I had to rework the Freescale board
to route LALE to the logic analyzer header though ...

> The addresses during these cycles are as follows:
> 
> LA27     LA28     LA29     LA30     LA31
> 0          0          0          0          0
> 0          0          0          1          0
> 0          0          1          0          0
> 0          0          1          1          0
> 0          1          0          0          0
> 0          1          0          1          0
> 0          1          1          0          0
> 0          1          1          1          0
> 
> Thus, the addresses on which I need to write the reset configuration words
> become 0x00, 0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E.

Check your schematic, are the signals routed correctly?

> In the u-boot.bin file, the reset config words are placed not on the above
> addresses but it is according to the datasheet:
> 
> 0x00 : 04 04 04 04 04 04 04 04     0x08 : 04 04 04 04 04 04 04 04
> 0x10 : 00 00 00 00 00 00 00 00     0x18 : 06 06 06 06 06 06 06 06
> 
> 0x20 : B0 B0 B0 B0 B0 B0 B0 B0     0x20 : 60 60 60 60 60 60 60 60
> 0x30 : 00 00 00 00 00 00 00 00     0x38 : 00 00 00 00 00 00 00 00
> 
> This file seems correct to me. Then why does the processor read from the
> wrong addresses? Can anyone point out what is wrong and what needs to be
> done? Has anyone encountered a similar problem?

I'd suspect your logic analyzer pod assignments, or your
PCB at this point.

Use your JTAG debugger to read from specific addresses
and see if the LA[] signals toggle appropriately.

Cheers,
Dave

      reply	other threads:[~2008-11-18 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 13:00 [U-Boot] Confusion in loading of reset configuration words on MPC8360 Elison Niven
2008-11-18 22:30 ` 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=4923420D.6040704@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