From: Arvid Brodin <arvid.brodin@xdin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How/Where does "_start" get assigned a value ?
Date: Wed, 9 Oct 2013 21:54:51 +0200 [thread overview]
Message-ID: <5255B48B.9040808@xdin.com> (raw)
In-Reply-To: <1381334837993-165089.post@n7.nabble.com>
On 2013-10-09 18:07, djoker wrote:
> Hi Everyone,
>
> I have a armv7 board and am looking at the "_start" symbol address, using
> the following command:
> *nm u-boot | grep -w _start*
>
> It returned the following:
> *67000020 T _start*
>
> I couldn't help notice that the the _start value is very "close" in vlaue to
> the value of CONFIG_SYS_TEXT_BASE defined in my board file:
> *#define CONFIG_SYS_TEXT_BASE 0x67000004*
>
> But, I have searched through the source code, but not found where _start
> gets assigned a value.. Could someone please help me understand this ?
This symbol is declared in arch/<...>/start.S, as the entry point for the
u-boot code, if I understand things correctly.
>
> Thanks,
> ~vj
>
>
>
> --
> View this message in context: http://u-boot.10912.n7.nabble.com/How-Where-does-start-get-assigned-a-value-tp165089.html
> Sent from the U-Boot mailing list archive at Nabble.com.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
--
Arvid Brodin | Consultant (Linux)
XDIN AB | Knarrarn?sgatan 7 | SE-164 40 Kista | Sweden | xdin.com
next prev parent reply other threads:[~2013-10-09 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 16:07 [U-Boot] How/Where does "_start" get assigned a value ? djoker
2013-10-09 19:54 ` Arvid Brodin [this message]
2013-10-09 23:02 ` Djoker
2013-10-12 20:53 ` Albert ARIBAUD
2013-10-09 22:55 ` djoker
2013-10-10 15:37 ` Gerhard Sittig
2013-10-12 0:30 ` Djoker
2013-10-13 14:26 ` Gerhard Sittig
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=5255B48B.9040808@xdin.com \
--to=arvid.brodin@xdin.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 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.