tCL tCWL dependency
Currently, tCWL depends on tCL as the following is stated:
| Timing | Safe | Tight | Extreme |
|---|---|---|---|
| tCWL1 | tCL | tCL - 1 | tCL - 2 |
The problem is that tCL is changed after tCWL is tuned. Then there is no mention of tuning tCWL again. To fix this, we can simply tune tCL before tCWL but i'm not sure if that will have a negative outcome.
I'm open to discussion. What do you think of this solution?
I just came to state the same observation. I think there should be a reminder at the tCL step to go back. According to this setting tCWL to tCL comes with low risk, but I cannot judge on that.
But your idea of tuning tCWL right after tCL seems more logical if it indeed is that easy.
I think it should be the other way around (placing the tCL step before that table where the tCWL recommendations are in step 3) since the intention is to tune secondaries to speed up memory testing.
Are there any disadvantages to tuning tCL as the first step generally speaking?
I just noticed the same. I chose to set tCWL relative to the XMP value for tCL, in my case XMP tCL = 14, so I set tCWL = 12, then run TM5+OCCT VRAM, OCCT SSE, OCCT AVX and Prime95 successfully. I guess if it had failed I would've just bumped tCWL up and run the tests again.