From: Sascha Hauer <s.hauer@pengutronix.de>
To: Igor Plyatov <plyatov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: delay in the IMXCFG file
Date: Wed, 19 Aug 2015 16:04:43 +0200 [thread overview]
Message-ID: <20150819140443.GZ18700@pengutronix.de> (raw)
In-Reply-To: <55D442E9.6030306@gmail.com>
Hi Igor,
On Wed, Aug 19, 2015 at 11:48:41AM +0300, Igor Plyatov wrote:
> Dear all,
>
> for debugging purposes I need to add some delays into the <BOARD
> NAME>.imxcfg file, but does not know which format it is. It looks
> like some kind of C, but it is confusing.
>
> Where is defined "wm 32", "soc", "dcdofs", "loadaddr" command and others?
They are interpreted in the imx-image tool, see scripts/imx/README and
scripts/imx/imx-image.c. The imx-image tool converts the commands into a
dcd table which is understood by the Freescale i.MX ROM Code. The ROM
code does not provide a delay command, so what you are looking for does
not exist. All the is is a nop command. This is currently not
implemented in imx-image, you would have to add it.
>
> Which commands I can use in the IMXCFG file to create very early
> delay, before initialization of DRAM?
As said, there is nop. Otherwise there is a 'check' command to poll for
setting/clearing bits.
See the i.MX reference manual in the "Device Configuration Data (DCD)"
section for further information.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-08-19 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:48 delay in the IMXCFG file Igor Plyatov
2015-08-19 14:04 ` Sascha Hauer [this message]
2015-08-20 12:20 ` Igor Plyatov
2015-08-20 12:47 ` Sascha Hauer
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=20150819140443.GZ18700@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plyatov@gmail.com \
/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.