public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] hardware flash protect kept during a reboot?
Date: Mon, 17 May 2010 10:55:05 +0200	[thread overview]
Message-ID: <201005171055.05858.sr@denx.de> (raw)
In-Reply-To: <4BEDA588.8080107@freescale.com>

Hi Timur,

On Friday 14 May 2010 21:33:28 Timur Tabi wrote:
> If I enable CONFIG_SYS_FLASH_PROTECTION and have a support flash chipset,
> are my protected sectors supposed to remain protected during a reboot?
> 
> That is, if I protect some flash sector, and then reboot U-Boot, I know
> U-Boot will not show the sector as being protected, because the
> info->protect[] array is initialized on every boot.  However, since I was
> using hardware protection, I expect the chip will still protect the sector.

This protection is chip specific. IIRC, then some Intel (Strata) chips either 
protect all sectors or have a sectore-wise protection mechanism. You need to 
check your FLASH documentation for the exact behaviour. Which chip are you 
using?

Please note that we have the special "unlock" env variable. By setting it to 
"yes", all sectors will be unlocked upon startup. At least on Intel Strata 
FLASH chips.

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:[~2010-05-17  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 19:33 [U-Boot] hardware flash protect kept during a reboot? Timur Tabi
2010-05-17  8:55 ` Stefan Roese [this message]
2010-05-17 14:11   ` Timur Tabi
2010-05-18  8:10     ` Stefan Roese

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=201005171055.05858.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox