public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Running vanilla u-boot v2012.10 on Guruplug
Date: Sun, 13 Jan 2013 10:25:24 +0100	[thread overview]
Message-ID: <20130113102524.48fb2cff@lilith> (raw)
In-Reply-To: <2223756.IMG4ajZrZq@moria>

Hi Dirk,

On Sat, 12 Jan 2013 20:41:36 +0100, Dirk Heinrichs
<dirk.heinrichs@altum.de> wrote:
> Am Samstag 12 Januar 2013, 16:51:51 schrieb Wolfgang Denk:
> 
> > Did you read the FAQ?  Especially
> > http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted
> > InRAM ?
> 
> Now I did :) Thanx a lot.
> 
> Interesting that [1] states it's possible, though...
> 
> Bye...
> 
> 	Dirk

My experience with starting U-Boot from RAM is that it's usually
impossible when U-Boot is meant to start directly from FLASH, mostly
(but not only) because the code at some point will rely on being able to
keep on running even through access to DRAM is not possible.

Now, starting U-Boot *may* be possible when U-Boot is loaded in DRAM
before starting it, but is a very tricky and undependable process. For
instance, on the Wireless Space target I am maintaining, and which is
supposed to be preloaded from FLASH into DRAM by a ROM monitor, if I
start the OpenOCD server, then in the console, do a break and / or a
reset halt, I won't be able to load_image u-boot; whereas if I do the
same actions as -c options when launching OpenOCD. And I have checked
countless times that the DRAM init sequence in the config file is
bit-for-bit identical to that used by the KWB which wraps the U-Boot
image, and which boots fine on its own.

Amicalement,
-- 
Albert.

  parent reply	other threads:[~2013-01-13  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  8:00 [U-Boot] Running vanilla u-boot v2012.10 on Guruplug Dirk Heinrichs
2013-01-12 15:51 ` Wolfgang Denk
2013-01-12 19:41   ` Dirk Heinrichs
2013-01-12 20:41     ` Jason
2013-01-12 21:30       ` Jeroen Hofstee
2013-01-12 21:57         ` Jason Cooper
2013-01-12 22:32         ` Jason
2013-01-13  7:44       ` Dirk Heinrichs
2013-01-13  9:25     ` Albert ARIBAUD [this message]
2013-01-13 16:25       ` Stefan Herbrechtsmeier
2013-01-13 20:49 ` Dirk Heinrichs

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=20130113102524.48fb2cff@lilith \
    --to=albert.u.boot@aribaud.net \
    --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