All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems flashing kernel
Date: Tue, 8 Jun 2010 19:34:14 +0200	[thread overview]
Message-ID: <20100608173414.GD28991@boggieman> (raw)
In-Reply-To: <4C0E5B31.3010903@denx.de>

On Tue, Jun 08, 2010 at 05:01:05PM +0200, Stefano Babic wrote:
> Kristoffer Ericson wrote:
> 
> > It worked earlier for unknown reasons, but no longer does. It has 
> > only worked once. Erasing all the flash (aside from first 512kb)
> > works without any error messages, but when trying to flash it still
> > insists that the flash is not erased. Looking with md also seems to
> > confirm that (data found).
> 
> Maybe it has nothing with your problem, but because you have Intel flash
> it could be possible you need to send the Unlock sequence. Have you
> tried setting CONFIG_SYS_FLASH_PROTECTION ?

I noticed something atleast inside the old bootloader (blob)
and also the kernel. It seems to add enable/disable routines for
the flash by setting PPSR |= PPC_LDD7 (on), PPSR &= ~PPC_LDD7 (off).

> 
> Best regards,
> Stefano Babic
> 
> -- 
> =====================================================================
> 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
> =====================================================================

      parent reply	other threads:[~2010-06-08 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 12:40 [U-Boot] Problems flashing kernel Kristoffer Ericson
2010-06-08 13:05 ` Stefano Babic
2010-06-08 13:21   ` Kristoffer Ericson
2010-06-08 14:31     ` Stefano Babic
2010-06-08 14:41       ` Kristoffer Ericson
2010-06-08 15:01         ` Stefano Babic
2010-06-08 16:34           ` Kristoffer Ericson
2010-06-08 17:34           ` Kristoffer Ericson [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=20100608173414.GD28991@boggieman \
    --to=kristoffer.ericson@gmail.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.