From: DaveKucharczyk <david.kucharczyk@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Memory test post relocation
Date: Fri, 14 Nov 2014 13:20:09 -0700 (MST) [thread overview]
Message-ID: <1415996409828-196228.post@n7.nabble.com> (raw)
In-Reply-To: <1415990472019-196211.post@n7.nabble.com>
Old u-boot was u-boot-2009.08.
I guess the main source of frustration the last 3 weeks could be attributed
to my lack of experience with u-boot and the fact that we were working with
an old Freescale version of u-boot. Not to mention 5 years worth of changes
between the versions. Most of the init functions seem to have moved in the
boot sequence between u-boot-2009.08 and u-boot-2014.07. For instance,
board_init was one of the first functions called before relocation to RAM,
but now it called after relocation.
I have our board almost fully working with mainline u-boot-2014.07, but now
I'm just trying to understand a few how's and why's before continuing.
In u-boot-2009.08 we set CONFIG_SKIP_RELOCATE_UBOOT. When I run with DEBUG
on I confirm that no relocation messages are reported, but this is due to
the fact that u-boot-2009.08 did not have debug messages pertaining to
relocation (that I can tell). I'm not sure how to confirm that relocation
didn't actually happen and where it actually runs from on the mx53, but I
can confirm that memory tests ran all the way to the end of RAM without
issue. We did run the test from within dram_init though, which would be
before relocation. Too bad that doesn't work in u-boot-2014.07.
--
View this message in context: http://u-boot.10912.n7.nabble.com/Memory-test-post-relocation-tp196088p196228.html
Sent from the U-Boot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-11-14 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 22:19 [U-Boot] Memory test post relocation DaveKucharczyk
2014-11-14 8:20 ` Albert ARIBAUD
2014-11-14 14:18 ` DaveKucharczyk
2014-11-14 14:27 ` Fabio Estevam
2014-11-14 14:34 ` DaveKucharczyk
2014-11-14 15:21 ` Albert ARIBAUD
2014-11-14 15:54 ` DaveKucharczyk
2014-11-14 16:07 ` DaveKucharczyk
2014-11-14 17:50 ` Albert ARIBAUD
2014-11-14 17:51 ` Albert ARIBAUD
2014-11-14 18:41 ` DaveKucharczyk
2014-11-14 20:20 ` DaveKucharczyk [this message]
2014-11-14 22:22 ` DaveKucharczyk
2014-11-15 12:13 ` Albert ARIBAUD
2014-11-15 12:26 ` Albert ARIBAUD
2014-11-15 12:37 ` Albert ARIBAUD
2014-11-14 16:15 ` Wolfgang Denk
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=1415996409828-196228.post@n7.nabble.com \
--to=david.kucharczyk@gmail.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