From: Marcel <korgull@home.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] skip relocation
Date: Sun, 2 Jan 2011 21:54:36 +0100 [thread overview]
Message-ID: <201101022154.36352.korgull@home.nl> (raw)
In-Reply-To: <4D20E0B1.2070601@emk-elektronik.de>
Dear Reinhard,
> Dear Marcel,
>
> >> Is there any example that boots from NOR ?
>
> looking at the defines below, you are not really booting u-boot from NOR...
>
> > #define CONFIG_SKIP_LOWLEVEL_INIT
>
> If you do that, you must have an initial boot code before u-boot. See
> below...
>
> > #define CONFIG_SKIP_RELOCATE_UBOOT
>
> Not used anymore.
>
> > /* SDRAM */
> > #define CONFIG_NR_DRAM_BANKS 1
> > #define PHYS_SDRAM 0x70000000
> > #define PHYS_SDRAM_SIZE 0x08000000 /* 128 megs */
>
> Those defines have had their names changed.
These I have changed already. I think they are fine.
> > #define CONFIG_SYS_GBL_DATA_SIZE 128
>
> This constant is wrong, use the auto-generated value.
OK
> > /*
> >
> > * Size of malloc() pool
> > */
> >
> > #define CONFIG_SYS_GBL_DATA_SIZE 128 /* 128 bytes for initial data */
>
> This constant is wrong, use the auto-generated value.
OK
> > Forgot to mention a few items :
> >
> > I flash the NOR at address 0x10020000
> > TEXT_BASE is 0x10020000
>
> That really implies you have another boot program running before u-boot.
> Proably AT91 bootstrap? Is it configured to jumo to 0x1002000, or does it
> copy u-boot to some SDRAM address and jumps there?
Yes I run AT91 bootstrap. Is there a way to skip this ?
That's a good question if at91bootstrap jumps to the right address. How can I
tell ? (maybe I find out myself, at least your question got me thinking ! )
Let's say it does copy u-boot to SDRAM, do I need to set that address as
TEXT_BASE ?
I tried setting TEXT_BASE to 0x10020000 or 0x73f00000
If I use another address, AT91bootstrap doesn't do anything, but at both of
these addresses it behaves the same.
> Have a look at the current implementation for top9000 in u-boot-arm/master
> and compare your files to it. Any differences to your code that are not
> board and/or SoC specific probably have to be fixed in your board code or
> you should be able to reason why it must be different for your board.
Thanks a lot for your reply. I have a few new things to try and read
(bootstrap)
,
Marcel
next prev parent reply other threads:[~2011-01-02 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 15:31 [U-Boot] {Spam?} skip relocation Marcel
2011-01-01 22:52 ` Albert ARIBAUD
2011-01-02 9:07 ` Marcel
2011-01-02 18:35 ` Marcel
2011-01-02 19:00 ` Marcel
2011-01-02 19:47 ` Marcel
2011-01-02 20:31 ` [U-Boot] " Reinhard Meyer
2011-01-02 20:54 ` Marcel [this message]
2011-01-02 21:08 ` Reinhard Meyer
2011-01-03 17:57 ` Marcel
2011-01-03 18:57 ` Marcel
2011-01-03 19:41 ` Marcel
2011-01-03 20:34 ` Reinhard Meyer
2011-01-03 22:16 ` Marcel
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=201101022154.36352.korgull@home.nl \
--to=korgull@home.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.