public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] On simple standalone applications
Date: Sun, 31 Aug 2008 00:50:05 -0700	[thread overview]
Message-ID: <48BA4D2D.1010008@manoweb.com> (raw)
In-Reply-To: <20080830203008.52E2C248C3@gemini.denx.de>

Wolfgang Denk wrote:

> Are you sure about this? Normally ARM systems have flash memory (or
> some other ROM) mapped at 0, because this is where execution starts
> out of reset.

Yes I am. On this system (at least as it is now) U-boot is executed from
memory when DDR has already been initialized. So yes, I confirm DDR is
mapped from 0x00000000 to 0x3fffffff but I only have 64MB so the end of
physical RAM is 0x03ffffff.

>> First problem: I can compile U-boot with ELDK 4.1 but if I enter the
>> "examples" directory and issue a make:
> 
> Who says you should do that? The examples are automatically built when
> running "make all" (or just "make") in the top level directory.

Sorry my fault.


>> I do not have RAM at that location! Shall I modify the Makefile for this?
> 
> Yes, you have to adjust the link address to your actual memory map.

Well now it is somewhat clearer and I think I understand. I will do some
experiments on the target on Tuesday, after labor's day of course :)


> It's not only gly, but also error-prone. You should not use plain
> pointer accesses to read or write to registers, but the correct
> accessor functions/macros ({in,out}[bwl]).

Uh... are those defined for U-boot as well? Thanks.


bye!
as

      reply	other threads:[~2008-08-31  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30  0:53 [U-Boot] On simple standalone applications Alessio Sangalli
2008-08-30 20:30 ` Wolfgang Denk
2008-08-31  7:50   ` Alessio Sangalli [this message]

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=48BA4D2D.1010008@manoweb.com \
    --to=alesan@manoweb.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