Am Montag, den 08.10.2018, 15:09 +0300 schrieb Grazvydas Ignotas:
Hi,
So if we're using 532, we're indeed running at a lower clock speed (unless it means dual-die is 2x532 - but even then we're off, as that would be 1064 instead of 1066... very weird).. so it should be 533. Is there a reason the OMAP is set to 532? Can't it go higher?
532MHz is specified as the maximum supported frequency by the OMAP5 datasheet. And DDR3-1066 (for example) refers to bits per second per pin, as it's DDR (dual data rate) it's 533MHz.
That's pretty weird, if the JEDEC Standard is 533MHz.
So which RAM chips do we have, DDR3-1866?
No, we have the DDR3L-1600 (11-11-11).
We could try overclocking OMAP to 533, it's < 1% overclock so maybe it would not hurt. But I guess there must be a reason why TI capped it to 532.
The 2GB is also clocked at 532MHz then? Maybe this is why some 2GB RAM boards (even uEVMs) freeze randomly as well.
With DLL enabled, it might work fine with most of them, but for some, the tolerance level might be worse, so it causes hiccups.