From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Internal Boot mode
Date: Tue, 04 Feb 2014 11:10:04 +0100 [thread overview]
Message-ID: <52F0BC7C.8060202@denx.de> (raw)
In-Reply-To: <CAE0zQkv_zCt7BoBXR1S7ZE13K6w8u6nVnXyt7V3g_mkTcSrALw@mail.gmail.com>
Hi Jyoti,
On 04/02/2014 10:07, JYOTI DUBEY wrote:
> Can anybody tell what all happens inside an i.mx6 board when we try to boot
> it in internal mode?
You have already got several answers pointing to the provided
documentation. Please read it. The boot process is descripted with
details in Chapter 8 of the i.MX6 User Manual. There is no short way,
you have to read it accurately.
> Is it that in internal mode the board does not look
> into the flash at all to discover the u-boot image and the image must be
> provided only from the serial port?
No, it is not. Internal mode is very similar to eFuse mode with the
exception that in internal mode the setup can be overwritten by GPIO.
Supported boards in U-Boot are booting in internal mode loading the
U-boot image from a storage (SPI, SD, NAND).
> If yes then what steps should be
> followed to perform internal booting? It would be of great help if commands
> for performing internal booting is provided.
Please read the documentation.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2014-02-04 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 9:07 [U-Boot] Internal Boot mode JYOTI DUBEY
2014-02-04 10:10 ` Stefano Babic [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=52F0BC7C.8060202@denx.de \
--to=sbabic@denx.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