From: Arnd Gronenberg <arnd@gronenberg.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] [PATCH 5/7] sun4i: Add support for a number of new sun4i boards
Date: Sun, 28 Sep 2014 21:34:57 +0200 [thread overview]
Message-ID: <542862E1.50908@gronenberg.com> (raw)
In-Reply-To: <54283031.5080700@redhat.com>
On 09/28/2014 05:58 PM, Hans de Goede wrote:
> [...]
>
> On 09/18/2014 06:07 PM, Siarhei Siamashka wrote:
>> Which revision of A10-OLinuXino-LIME do you have? Revision A is known
>> to have troubles running stable at 1008MHz CPU clock speed, as confirmed
>> on a sample set of two boards (mine and Oliver Schinagl's):
>> https://www.mail-archive.com/linux-sunxi at googlegroups.com/msg04343.html
> I have a revision A board.
My Olimex A10 OLinuXino Lime is also labelled "Rev. A"... It is running
stable at 1008MHz and I just tried Olivers djpeg test without any problems.
I'm running Hans' u-boot-sunxi 2014.10-rc1-g7190869 and Linux mainline
3.17.0-rc1-00158-g451fd72.
>> A bunch of revision C boards were all fine in Oliver's tests. And
>> nobody has ever tested revision B so far, so we have no idea whether
>> it is stable or not. A mysterious thing is that the Olimex
>> representatives on IRC were not aware of any fixes of this kind
>> applied to the PCB.
>>
>> My understanding is that the revision A was just a small pre-production
>> batch, donated by OLIMEX to a number of open source developers. Some of
>> these boards were distributed at FOSDEM. I'm not sure if we should
>> really worry about the reliability of the revision A, because none of
>> the 'normal' customers probably have such boards. We only need to
>> clarify the status of revision B.
>>
>> But if we want to support the revision A too, then it probably needs
>> its own config, which would somehow restrict the CPU clock speed.
>> I also ha
> My revision A was actually ordered normally, a couple of days before
> the first batch sold-out. So it is likely that the entire first batch
> was revision A.
>
> Do you have any easy step-by-step document (or ready to use sdcard
> image to download) to do some stress tests on my revision A ?
>
> Maybe the first couple handed out to developers where hand soldered
> or some such ? Either way it would be good to either confirm that
> my revision A has the same issues, or not :)
I bought my revision A from a German distributor (exp-tech.de) and it
doesn't look hand soldered (except for the through hole parts :-) ).
If I correctly compared the schematics for revision A,B and C, there is
only one change in regard to the DRAM: R8 (connected to ZQ) has a
different value:
- Revision A: 237 Ohm / 1%
- Revision B: 430 Ohm / 1%
- Revision C: 330 Ohm / 1%
I checked R8 on my revision A's PCB: It is a 330 Ohm / 1%, therefore the
value specified in the revision C schematic. So it may make sense to
check R8 on the problematic revision A boards and replace it by a 330
Ohm resistor. The DRAM data sheet specifies this resistor with 240 Ohm /
1%...
>> [...]
>>
>> Either way, these settings are outside of the valid range when running
>> at 480MHz (which would be something like DDR3-960 in our case).
>>
>> [...]
The current (probably incorrect) values work fine with my board (even
though they may be out of spec), but the value of R8 may have some
impact here.
Best regards, Arnd
--
Arnd Gronenberg, arnd at gronenberg.com, DJ9PZ / AB2QP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2396 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140928/09c2d278/attachment.bin>
next prev parent reply other threads:[~2014-09-28 19:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 21:25 [U-Boot] [PATCH 1/7] sun4i: add USB EHCI settings Hans de Goede
2014-07-27 21:25 ` [U-Boot] [PATCH 2/7] sun5i: " Hans de Goede
2014-07-28 7:42 ` Ian Campbell
2014-07-28 8:22 ` Hans de Goede
2014-07-27 21:25 ` [U-Boot] [PATCH 3/7] sunxi: Enable EHCI on various sunxi boards Hans de Goede
2014-07-28 7:44 ` Ian Campbell
2014-07-27 21:25 ` [U-Boot] [PATCH 4/7] sunxi: Add CONFIG_MACPWR option Hans de Goede
2014-07-28 7:48 ` Ian Campbell
2014-07-28 7:51 ` [U-Boot] [linux-sunxi] " Chen-Yu Tsai
2014-07-28 7:59 ` Ian Campbell
2014-07-28 8:23 ` Hans de Goede
2014-07-28 8:09 ` [U-Boot] " thomas.langer at lantiq.com
2014-07-28 8:59 ` Hans de Goede
2014-07-27 21:25 ` [U-Boot] [PATCH 5/7] sun4i: Add support for a number of new sun4i boards Hans de Goede
2014-07-28 7:54 ` Ian Campbell
2014-07-28 8:46 ` Hans de Goede
2014-07-28 8:50 ` Ian Campbell
2014-09-18 16:07 ` [U-Boot] [linux-sunxi] " Siarhei Siamashka
2014-09-28 15:58 ` Hans de Goede
2014-09-28 19:34 ` Arnd Gronenberg [this message]
2014-09-28 22:09 ` Siarhei Siamashka
2014-09-29 8:31 ` Arnd Gronenberg
2014-09-29 5:38 ` Siarhei Siamashka
2014-09-29 5:46 ` Siarhei Siamashka
2014-07-27 21:25 ` [U-Boot] [PATCH 6/7] sun5i: Add support for a number of new sun5i boards Hans de Goede
2014-07-27 21:25 ` [U-Boot] [PATCH 7/7] sun7i: Add support for a number of new sun7i boards Hans de Goede
2014-07-28 7:38 ` [U-Boot] [PATCH 1/7] sun4i: add USB EHCI settings Ian Campbell
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=542862E1.50908@gronenberg.com \
--to=arnd@gronenberg.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