From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 31/31] 83xx, kmeter1: added bootcount feature
Date: Thu, 29 Jan 2009 10:22:06 +0100 [thread overview]
Message-ID: <4981753E.2080205@denx.de> (raw)
In-Reply-To: <20090128201206.f9b4959d.kim.phillips@freescale.com>
Hello Kim,
Kim Phillips wrote:
> On Wed, 28 Jan 2009 10:41:02 +0100
> Heiko Schocher <hs@denx.de> wrote:
>
>> diff --git a/cpu/mpc83xx/cpu.c b/cpu/mpc83xx/cpu.c
>
>> +#ifdef CONFIG_BOOTCOUNT_LIMIT
>> +
>> +#if !defined(CONFIG_BOOTCOUNT_ADDR)
>> +#define CONFIG_BOOTCOUNT_ADDR 0x11bff8
>
> it's CONFIG_SYS and magic number, but now that I've found it, sorry, I
> can't accept this - not all 83xx have a QE and thus this MURAM. Even
Hmm.. maybe we make this dependent on CONFIG_QE ?
> if they did this would require changing the device tree muram node
> property, to indicate its size has shrunk 8 bytes, right? In fact, not
Yes, we should do this.
> all QE's have 48Kbytes of MURAM either - the 8323 only has 16Kbytes.
Thats why you could define it with CONFIG_BOOTCOUNT_ADDR, where
exactly this 8 bytes are.
> Problem is, I don't know of a better place to put the
> bootcount. Ideas?
I thought to make it as on 82xx (using parameter Ram of SCC1), because
UCC5 should be compatible to the SCC1 see 8360ERM.pdf Table 19-11 on
page 19-20. But on the 8360, after reset, the complete parameter RAM is
initialized with 0 ... so that didn't work. Other places I couldn't
found for this feature :-(
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-01-29 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 9:41 [U-Boot] [PATCH 31/31] 83xx, kmeter1: added bootcount feature Heiko Schocher
2009-01-29 2:12 ` Kim Phillips
2009-01-29 9:22 ` Heiko Schocher [this message]
2009-01-29 16:28 ` Kim Phillips
2009-01-29 19:00 ` Wolfgang Denk
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=4981753E.2080205@denx.de \
--to=hs@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