public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot flash for yellowstone board with external programmer
Date: Fri, 21 Jul 2006 19:13:44 +0200	[thread overview]
Message-ID: <20060721171344.F0CB2352660@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 21 Jul 2006 18:38:53 +0200." <60E856FD577CC04BA3727AF4122D3F160123856C@3bit.vector.com.pl>

In message <60E856FD577CC04BA3727AF4122D3F160123856C@3bit.vector.com.pl> you wrote:
>
> for some reason we need to replace flash chip on yellowstone board and program it with external programmer. 
> The question is that for external programmer flash is visible as 0-64M, and I'm not sure where should I program 512k of u-boot? I assume that at the end of the chip (CPU is looking at the end, at 0xfffffffc),am I right?

The normale image address for U-Boot on the  yelowstone  is  FFF80000
(flash  being  mapped  ion the FC000000 ... FFFFFFFF area); so if you
see 0 ... 64M = 04000000, then you will have to program the image  at
0x3F80000

> Also concerning endianness -as board has swapped data and address
> signals (flash_A0->cpu_A30, flash_D0->cpu_D15) I assume that image

There are no swapped signals. Just keep in mind that on PowerPC MSB =
Bit 0.

> can be programmed "as is" - 16-bit word-by-word without any
> conversion? Please fix me if I'm wrong.

Right.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Beware of programmers carrying screwdrivers."      - Chip Salzenberg

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 16:38 [U-Boot-Users] u-boot flash for yellowstone board with external programmer Andriy Korud
2006-07-21 17:13 ` Wolfgang Denk [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=20060721171344.F0CB2352660@atlas.denx.de \
    --to=wd@denx.de \
    --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