From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Sun, 6 Jul 2014 15:08:00 +0200
Subject: [U-Boot] Giving control to standalone app.
In-Reply-To: <1404651603867-183637.post@n7.nabble.com>
References: <1404645040858-183635.post@n7.nabble.com>
	<53B93029.3070505@myspectrum.nl>
	<1404651603867-183637.post@n7.nabble.com>
Message-ID: <E1X3mAj-0004OX-CS@janus>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi mazen.e,

On Sun, 6 Jul 2014 06:00:03 -0700 (PDT), "mazen.e"
<mazen.ezzeddine@gmail.com> wrote:

> Dear 
> 
> Many thanks for your reply.
> 
> But what if mistakenly or accidentally the standalone application write to
> the memory where u-boot resides, would that cause the standalone application
> to crash? Otherwise (in case the standalone application has written to
> u-boot memory without crash )  what happens if the standalone app exit the
> loop.

You're actually asking the very general question "what happens if some
code behaves badly", and the very general answer is "then bad things
happen".

Specifically, you do realize already that if an application overwrites
the U-Boot code in RAM, then upon returning it'll give control back to
a corrupted U-Boot, which can have all sorts of bad effects.

> Regards, 

Amicalement,
-- 
Albert.