From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unable to understand flow of U-Boot Code.
Date: Wed, 15 May 2013 22:46:27 +0530 [thread overview]
Message-ID: <5193C2EB.9050301@gmail.com> (raw)
In-Reply-To: <CAONsvZWCk6fskQdD6SH1r1bJQw+Nda+X=2eW0KpKFUWFrBtiaw@mail.gmail.com>
Hello,
On 5/15/2013 3:35 PM, Rajdeep Vaghasia wrote:
> Hello,
>
> I am trying to understand the flow of U-boot code, but unable to get the
> complete link.
This question has been asked *innumerous* times in the list.
One sample from the archive
<http://lists.denx.de/pipermail/u-boot/2013-January/144950.html>
Dig in to the archives, you'll find more.
> I can not understand how the flow goes. In which sequence the code executes.
Do you have a board and a JTAG? If yes, just hook in the JTAG and load
u-boot to see where it goes from the reset vector.
> So, please give me some reference, which can explain the complete flow of
> execution of U-Boot code.
Sorry, there is no such ready reckoner available which would give you
the _complete_ flow.
Start with the README in the root folder.
Good luck,
Vikram
prev parent reply other threads:[~2013-05-15 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 10:05 [U-Boot] Unable to understand flow of U-Boot Code Rajdeep Vaghasia
2013-05-15 17:16 ` Vikram Narayanan [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=5193C2EB.9050301@gmail.com \
--to=vikram186@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 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.