From: Markus Hubig <mhubig@imko.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [SOLVED] Need help to get u-boot running on the taskit stamp9g20
Date: Fri, 27 Jul 2012 10:59:10 +0200 [thread overview]
Message-ID: <20120727085910.GC18866@imko.de> (raw)
In-Reply-To: <20120724154328.GA2815@imko.de>
On Tue, Jul 24, 2012 at 05:43:28PM +0200, Markus Hubig wrote:
> I looked at every single byte on the internet an I found some information
> that in order to get this bad-ass relocation to work, one needs to adapt
> at91bootstrap to work with u-boot. Could this be my problem? At the moment
> I'm using the original at91bootstrap from taskit.
>
> Here is what I think the problem could, maybe, be:
>
> 1. Board gets powered on.
> 2. at91bootstrap magically starts.
> 3. It reads IMG_SIZE from IMG_ADDRESS and writes it to JUMP_ADDR in RAM.
> - IMG_ADDRESS is where I write u-boot to inside NAND?
> - IMG_SIZE should be the size of u-boot.bin? (exactly or is a bigger
> size OK?)
> - JUMP_ADDR is where u-boot is relocated to in RAM. Should be
> CONFIG_SYS_TEXT_BASE?
> 4. at91bootstrap sets the PC to JUMP_ADDR and starts u-boot.
>
> Since IMG_SIZE in at91bootstrap is not the size of my new u-boot.bin it
> crashes after relocation!
Year! This was exactly my problem! Building a new at91bootstrap with a bigger
IMG_SIZE solved it. Now U-Boot starts up!
Im getting closer to a patch! ;-)
Cheers, Markus
prev parent reply other threads:[~2012-07-27 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 19:28 [U-Boot] Need help to get u-boot running on the taskit stamp9g20 Markus Hubig
2012-07-12 6:07 ` Wolfgang Denk
2012-07-12 15:53 ` Markus Hubig
2012-07-12 9:28 ` Andreas Bießmann
2012-07-12 15:49 ` Markus Hubig
2012-07-12 23:04 ` Andreas Bießmann
2012-07-18 13:21 ` Markus Hubig
2012-07-20 13:08 ` Markus Hubig
2012-07-20 14:26 ` Markus Hubig
2012-07-21 22:03 ` Wolfgang Denk
2012-07-24 15:43 ` Markus Hubig
2012-07-27 8:59 ` Markus Hubig [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=20120727085910.GC18866@imko.de \
--to=mhubig@imko.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