public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: reduce Orange Pi Zero DRAM clock speed
Date: Thu, 31 May 2018 19:36:57 +0200	[thread overview]
Message-ID: <9b6855ca-e562-5da0-2c44-2127cb6ae56b@web.de> (raw)
In-Reply-To: <CAD6G_RTarL22A2hspoaFxS4p6M0EH_Ur_k-Es5wQfkzF9G=Beg@mail.gmail.com>

On 2017-08-11 12:21, Jagan Teki wrote:
> On Mon, Jul 24, 2017 at 1:44 AM, Clément Bœsch <u@pkh.me> wrote:
>> Using `fel-boot-lima-memtester-on-orange-pi-pc 672` on an Orange Pi
>> without heatsink results in the following error after a few minutes:
>>   WRITE FAILURE: 0x00200000 != 0xffdfffff at offset 0x0137f47c (bitflip).
>>
>> Also, the constructor repository (github/orangepi-xunlong) seems to
>> contain that 624 Mhz clock speed in its u-boot fork. It may be that 672
>> Mhz is the advertized overclocked speed.
>>
>> According to http://linux-sunxi.org/Orange_Pi_PC#DRAM_clock_speed_limit
>> it may be worth decreasing that value with other Orange Pi boards.
>>
>> See also e7d6aa0b74b7f4d08ee68da8a586c76c761348e2.
> 
> Applied to u-boot-sunxi/master
> 

I've a 1.5 years old OPi Zero that was running uboot 2017.01 so far. I
just tried to update to 2018.05, also using the new defconfig. The
result was that uboot got stuck early during the first lines of output.
Then I changed the DRAM clock back to 672, and things seem to work find.

Are we facing different board revisions that need different settings, or
could the lowering be incorrect?

Jan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180531/6f150647/attachment.sig>

  reply	other threads:[~2018-05-31 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23 20:14 [U-Boot] [PATCH] sunxi: reduce Orange Pi Zero DRAM clock speed Clément Bœsch
2017-08-11 10:21 ` Jagan Teki
2018-05-31 17:36   ` Jan Kiszka [this message]
2018-05-31 18:02     ` Jan Kiszka

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=9b6855ca-e562-5da0-2c44-2127cb6ae56b@web.de \
    --to=jan.kiszka@web.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