From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [SOLVED] Strange / Unreadable console output
Date: Thu, 16 Aug 2012 19:30:31 +0200 [thread overview]
Message-ID: <502D2E37.4020903@gmail.com> (raw)
In-Reply-To: <20120816182411.c71f8044-f6ce-44d2-8a93-0c3c724000f0.mhubig@imko.de>
On 16.08.2012 18:51, Markus Hubig wrote:
> Hi Andreas,
>
> On Thu, Aug 16, 2012 at 05:33:26PM +0200, Andreas Bie?mann wrote:
>> On 16.08.2012 17:07, Markus Hubig wrote:
>
> <snip>
>
>>> But it definitly dosn't work here. I checked with an oscilator, if I toggle
>>> the pin in board_init() I can nicely see it going high and low but if I
>>> toggle it in board_early_init_f() *nothing* happens!
>>
>> Well as mentioned in my mail the mdelay() can not work in
>> board_eraly_init_f() cause the timers are not setup at this stage. You
>> need to provide some nop-loop based delay here to have proper delay!
>> As mentioned before my at91sam9263 (running at about 200 MHz produce 38
>> us out of a mdelay(10); I dunno what your g20 variant with about 400 MHz
>> produces here). A simple test could be to move the timer init in
>> a/a/lib/board.c before board_early_init_f in the init_sequence. Then the
>> mdelay() will work as expected!
>
> You were right! The problem was the missing delay after setting the pin!
> Just moving the timer_init() before board_early_init_f() in the init_sequence
> didn't work because we need the clocks from board_early_init_f() first. But I
> found the
>
> | board_postclk_init()
>
> function and the corresponding
>
> | CONFIG_BOARD_POSTCLK_INIT
>
> switch, so I put everything there and now it all works fine! ;-)
great!
>> send a patch (including working serial console output ;)
>
> Unfortunately the board_postclk_init() function was not in the init_sequence
> at arch/arm/lib/board.c so I added it there. I will provide two patches, one
> for the board stuff and one for the stamp stuff, if this is OK with you ...
I think adding the postclock stuff to arm is ok. Albert is responsible
for that so if he is willing to accept that the stamp9g20 stuff is no
problem.
Best regards
Andreas Bie?mann
prev parent reply other threads:[~2012-08-16 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 9:16 [U-Boot] Strange / Unreadable console output Markus Hubig
2012-08-11 12:15 ` Jerry Van Baren
2012-08-13 11:17 ` Markus Hubig
2012-08-14 0:12 ` Jerry Van Baren
2012-08-14 9:16 ` Markus Hubig
2012-08-14 6:22 ` Andreas Bießmann
2012-08-14 9:08 ` Markus Hubig
2012-08-14 12:03 ` Andreas Bießmann
2012-08-14 15:11 ` Markus Hubig
2012-08-15 10:55 ` Andreas Bießmann
[not found] ` <20120816150738.GA17112@imko.de>
2012-08-16 15:33 ` Andreas Bießmann
2012-08-16 16:51 ` [U-Boot] [SOLVED] " Markus Hubig
2012-08-16 17:30 ` Andreas Bießmann [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=502D2E37.4020903@gmail.com \
--to=andreas.devel@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox