All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Flashing PPC440gx Using BDI3000
Date: Wed, 28 Oct 2009 06:56:41 +0200	[thread overview]
Message-ID: <200910280556.41347.sr@denx.de> (raw)
In-Reply-To: <20759a560910271721wea72f18uc58b0c8db113dab9@mail.gmail.com>

Hi Kyle,

On Wednesday 28 October 2009 01:21:21 Kyle Smith wrote:
> I realize this isn't a BDI3000 mailing list but I was hoping to get some
> input on my problem. I am trying to program u-boot onto the flash
> (S29GL512N) of a ppc440gx target using a BDI3000 but I am getting some
>  weird behavior.
> 
> With my current BDI3000 (firmware v1.18) configuration (using SDRAM as the
> BDI workspace) the first program attempt always fails. Successive attempts
> after the failed one will work.

<snip>

> One interesting thing is when I dump the failed programming attempt and
>  diff it's contents versus my u-boot image it's only the first 512 bytes
>  that are incorrect. Within the 512 bytes I can partially see the contents
>  of the image with some of the data corrupted.
> 
> Another characteristic of my problem is I can program the flash if I allow
> u-boot to configure the board.

This sounds like a memory configuration in your BDI script for me. I suggest 
you check again the SDRAM controller parameters against the ones configured in 
U-Boot.
 
Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

      reply	other threads:[~2009-10-28  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28  0:21 [U-Boot] Flashing PPC440gx Using BDI3000 Kyle Smith
2009-10-28  4:56 ` Stefan Roese [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=200910280556.41347.sr@denx.de \
    --to=sr@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 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.