From: Christopher Harvey <chris@basementcode.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] newbie questions regarding some config options.
Date: Mon, 13 Jun 2011 07:31:17 -0500 [thread overview]
Message-ID: <b084ad5f7cd8dd91a57ae3768960ff97@basementcode.com> (raw)
As per the README file:
Subscribe to u-boot mailing list;
if (clueless)
email("Hi, I am new to U-Boot, how do I get started?");
I'm messing around with uboot and QEMU (qemu-system-arm -M
realview-pbx-a9 -kernel u-boot.bin), things are going pretty well in the
sense that I'm not having too much trouble reading most of the code and
creating a new board. I have some questions that I can't figure out by
reading the code. What is the CONFIG_SYS_TEXT_BASE variable and how can
I figure out what it should be?
I randomly set it to 0x0...then tried to debug u-boot under qemu, but
when stepping in the start.S file it was instantly clear that it wasn't
really working because gdb said the code ran right though the
_start: b reset
instruction and qemu eventually crashed with the following output:
qemu: fatal: Trying to execute code outside RAM or ROM at 0xfeb70cdc
R00=00000000 R01=ffff0000 R02=00000000 R03=000108ac
R04=ffff0000 R05=ffbedf70 R06=ffff0000 R07=00000010
R08=00001000 R09=ffff0000 R10=000108ac R11=00000000
R12=00001078 R13=ffbedf60 R14=00000960 R15=feb70cdc
PSR=600001d3 -ZC- A svc32
Aborted
Apart from that everything is pretty clear to me, but I want to make
sure I'm getting this points right:
Is the environment the set of variables that can be modified with
setenv?
How can I determine the "size of the environment"? Is it the number of
characters including variable names?
Also, is there anything special I need to do with gdb to get it to
follow relocating code?
thanks,
-Chris
next reply other threads:[~2011-06-13 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 12:31 Christopher Harvey [this message]
2011-06-13 13:09 ` [U-Boot] newbie questions regarding some config options PHIL.EDWORTHY at renesas.com
2011-06-13 13:59 ` Matthias Weisser
2011-06-13 14:08 ` PHIL.EDWORTHY at renesas.com
2011-06-13 14:12 ` Christopher Harvey
2011-06-13 16:00 ` Wolfgang Denk
2011-06-13 15:59 ` Wolfgang Denk
2011-06-13 15:58 ` Wolfgang Denk
2014-08-22 3:49 ` Chris
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=b084ad5f7cd8dd91a57ae3768960ff97@basementcode.com \
--to=chris@basementcode.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.