public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot for Vertex4-based board.
Date: Wed, 14 Feb 2007 17:21:08 +0100	[thread overview]
Message-ID: <87d54cww0b.fsf@denx.de> (raw)
In-Reply-To: <406A31B117F2734987636D6CCC93EE3CB05891@ehost011-3.exch011.intermedia.net> (Leonid@a-k-a.net's message of "Wed, 14 Feb 2007 07:24:49 -0800")

Dear Leonid,

"Leonid" <Leonid@a-k-a.net> writes:

> On Tuesday, February 13, 2007 10:55 PM Markus Klotzb?cher:
>> > I'm porting u-boot on Vertex-4 based board (with PPC405 inside);
> I'm
>> > trying use ml403 u-boot as example. I have first stage boot
> loader,
>> > taking my u-boot image from serial and loading it to SDRAM, u-boot
> is
>> > configured to boot from main memory. 
>
>> Are you aware that this setup is strongly discouraged? Have you read
>> this:
>
>>http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarte>
> dInRAM?
>
> [Leonid] The answer in DULG FAQ chapter you are referring to doesn't
> say that such practice is bad, it simply states that u-boot doesn't
> support such an option. That could be truth in the time of DULG FAQ
> writing but now there are many platforms, naturally using 3-stage
> booting. For example, ATMEL ARM boards have small boot program which
> fetches u-boot from flash, loads it to RAM and then starts. I would
> like to hear why do you think it's so bad, but in any case this way
> u-boot is normally used for such boards (at91rm9200-ek for instance).

I didn't say it's bad to do this, I just wanted to point out that
starting U-Boot from RAM is not the standard way and you might
experience difficulties. Having said that, yes, I'm well aware there are
boards doing this, to be honest I have done it myself. Sometimes there
is no other way.

> In my case I probably could change EDK project to put flash on the end
> of the memory, but I prefer to load u-boot via XMD debugger or serial
> directly to RAM - much more convenient for debugging - since otherwise
> I will need to burn flash each time I change something and I cannot
> use BDI2000 on this board. Xilinx tools are not that convenient for
> frequent flash burning.

Well, I guess I would still burn U-Boot to flash if I had the
choice. This setup has been tested much better. But as you seem to know
what you are doing, it's ok.

Best Regards

     Markus

--
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany

  reply	other threads:[~2007-02-14 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  3:51 [U-Boot-Users] u-boot for Vertex4-based board Leonid
2007-02-14  6:55 ` Markus Klotzbücher
2007-02-14 14:28   ` Grant Likely
2007-02-14 17:17     ` Leonid
2007-02-14 17:35       ` Grant Likely
2007-02-14 18:31         ` Leonid
2007-02-14 15:24   ` Leonid
2007-02-14 16:21     ` Markus Klotzbücher [this message]
2007-02-15  4:45     ` [U-Boot-Users] PLB TMAC 3.0 drivers for ML403 u-boot Leonid
2007-02-16  0:46     ` [U-Boot-Users] u-boot for Vertex4-based board Wolfgang Denk
2007-04-29 23:11 ` mikeIngle
2007-04-30  4:50   ` [U-Boot-Users] Spartan-3e Starter Kit SW EDK application for SPI serial flash Leonid

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=87d54cww0b.fsf@denx.de \
    --to=mk@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