public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Protect an area in RAM
Date: Thu, 23 Aug 2007 10:59:18 +0200	[thread overview]
Message-ID: <200708231059.19124.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <DC6F86A94046A64094043D44A3A708F7A148D4@sestoex02.enea.se>

Hi Markus,

perhaps CONFIG_PRAM (protected RAM) is what you need.
See README for details.

Matthias

On Thursday 23 August 2007 10:30, Markus Malmgren wrote:
> Hi,
> 
>  
> 
> Many hardware manufactures provide their development platform with
> u-boot. I was wondering if there is a feature (did not find anything) in
> u-boot to protect a specific area in the RAM from being overwritten when
> u-boot boots a microcontroller? The reason for this is that we store
> debug information between restarts from our software and using u-boot
> this is destroyed.
> 
>  
> 
> If this feature does not exist, one general solution would be to add a
> system parameter in which areas that are not to be destroyed could be
> added as a default feature of u-boot. Would this be a feature that
> others need as well? If so I will start to investigate what could be
> done.

  reply	other threads:[~2007-08-23  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23  8:30 [U-Boot-Users] Protect an area in RAM Markus Malmgren
2007-08-23  8:59 ` Matthias Fuchs [this message]
2007-08-23 10:41 ` Wolfgang Denk
2007-08-23 12:32   ` Markus Malmgren
2007-08-23 19:21     ` Wolfgang Denk
2007-08-24 10:38       ` Markus Malmgren
2007-08-24 16:03         ` 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=200708231059.19124.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox