From: Igor Plyatov <plyatov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: delay in the IMXCFG file
Date: Thu, 20 Aug 2015 15:20:54 +0300 [thread overview]
Message-ID: <55D5C626.6020103@gmail.com> (raw)
In-Reply-To: <20150819140443.GZ18700@pengutronix.de>
Dear Sascha,
> 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.
Thank you for explanation above!
Everywhere I see references to DCD in the Reference Manual, but I can
not find details about DCD in the MCIMX51RM.pdf Rev. 1 2/2010.
If you know, please give me a link to document where DCD explained in
details, because any attempt to setup GPIO output, fails. Device just
does not boot at all.
wm 32 0x73f88000 0x689c0319 /* hangup line in flash-header.imxcfg */
Best wishes.
--
Igor Plyatov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-08-20 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:48 Igor Plyatov
2015-08-19 14:04 ` Sascha Hauer
2015-08-20 12:20 ` Igor Plyatov [this message]
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=55D5C626.6020103@gmail.com \
--to=plyatov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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