Yeah maybe on AMP mesurement position if you have picky wires ... you will need 4 hands !
2 to maintain multimeter and 2 other for powering the laptop and flash descriptor settings
______________________________________________________________________
For my ME mod, everything is well done from a fresh dump, I can't get to modify BCLK
I will try to redo the pinmod to maybe unlock ME registers ...
With the HM76 chipset, I can't get the "EXTREME" clock capabilities as you get .
ICC tool gave me a "BASIC" even if I fake HM77 in ME
All my registers are locked, and of course the most important SSC3 PARMS.
On boot the new range of DIV2-S are not allowed.
Maybe if I can find where are the Intel Records, I could mod them ?
Still searching
hehe, well, I wasnt talking about run the multimeter with the machine on ^^
I was more going about find alternative points to solder than the traces
so you didnt got BCLK working, right?
well, I didnt fake anything on mine, just picked the me, the pdf, and changed the adjustments the pdf said they needed to be changed for FCIM overclocking and mod the DIV2-S range.
after doing those changes BCLK overclocking was avalible via the intel XTU software.
did you changed the parameters from your ME to the ones from the pdf asked to enable FCIM overclocking?
dont change anything else, I had once all registers locked due some innecesary change.
Yes, I re-started from an unmodded ME dump, and set only what pdf says for FCIM overclocking. I first set SKU as HM76, then try with a fake setting with no change.
All of registers are effective if I read them with
Code:
>cctwin gr current
Intel (R) Clock Commander Tool Version: 7.1.20.1119
Copyright (C) 2010 Intel Corporation. All rights reserved.
FLAGS [0x000120d8]
record_length = 216
REGISTERS
[0x00] CSS = 0x00011a34 [LOCKED]
[0x01] SSS = 0x00133744 [LOCKED]
[0x02] FCSS = 0x00000232 [LOCKED]
[0x03] PLLRCS = 0x000a8cbe [LOCKED]
[0x04] --- = 0x00030e08 [LOCKED]
[0x08] --- = 0x00030e08 [LOCKED]
[0x09] --- = 0x00008000 [LOCKED]
[0x0b] --- = 0x00000080 [LOCKED]
[0x0c] PLLEN = 0x4000000c [LOCKED]
[0x0d] --- = 0x0f1ff1ff [LOCKED]
[0x0e] OCKEN = 0x1fff0f8f [LOCKED]
[0x0f] IBEN = 0x0000002f [LOCKED]
[0x10] DIVEN = 0x000005ff [LOCKED]
[0x12] PM1 = 0x0000001f [LOCKED]
[0x13] PM2 = 0x00000000 [LOCKED]
[0x14] --- = 0x00fbfbfb [LOCKED]
[0x15] --- = 0x0000fbfb [LOCKED]
[0x16] --- = 0x000000ff [LOCKED]
[0x17] --- = 0xbbbbbbbb [LOCKED]
[0x18] --- = 0x0000175d [LOCKED]
[0x19] --- = 0x00000834 [LOCKED]
[0x1c] SEBP1 = 0x00008888 [LOCKED]
[0x1d] SEBP2 = 0x00088888 [LOCKED]
[0x1e] --- = 0x00000000 [LOCKED]
[0x20] DIVSET = 0x00555551 [LOCKED]
[0x21] --- = 0x00000551 [LOCKED]
[0x24] SSCCTL = 0x00000000 [LOCKED]
[0x27] --- = 0x00000020 [LOCKED]
[0x28] --- = 0x00640004 [LOCKED]
[0x29] PI12BiasParms = 0x00000888 [LOCKED]
[0x2a] --- = 0x08880888 [LOCKED]
[0x2b] --- = 0x000087c0 [LOCKED]
[0x2c] --- = 0x00000000 [LOCKED]
[0x2d] --- = 0x00000000 [LOCKED]
[0x2e] --- = 0x15780001 [LOCKED]
[0x2f] --- = 0x00000001 [LOCKED]
[0x30] SSC1PARMS = 0x1270a428 [LOCKED]
[0x31] SSC2PARMS = 0x12704c30 [LOCKED]
[0x32] SSC3PARMS = 0x12704c30 [LOCKED]
[0x33] SSC4PARMS = 0x1270a428 [LOCKED]
[0x38] --- = 0x00000000 [LOCKED]
[0x39] SSC2OCPARMS = 0x00000000 [LOCKED]
[0x3a] --- = 0x00000000 [LOCKED]
[0x3b] --- = 0x00000000 [LOCKED]
[0x40] --- = 0x29c529c5 [LOCKED]
[0x41] --- = 0x29c529c5 [LOCKED]
[0x48] PMSRCCLK1 = 0x76543210 [LOCKED]
[0x49] PMSRCCLK2 = 0x00000f98 [LOCKED]
[0x4d] --- = 0x00000002 [LOCKED]
[0x4f] --- = 0x00000000 [LOCKED]
HECI CMD Status = 0x00000000 (SUCCESS)
They are also all locked, and the MIN an MAX DIV-2S are set back to 100 mghz.
According to the end of
that datasheet the FW don't allow my range as I'm still in "BASIC" ICC
Code:
>cctwin gcc
Intel (R) Clock Commander Tool Version: 7.1.20.1119
Copyright (C) 2010 Intel Corporation. All rights reserved.
icc_hw_version_number = 0002.0000
icc_hw_sku = BASIC //cannot be changed, depending on chipset (AFAIK)
max_size_of_temporary_uob_record = 56
icc_boot_status_report [0x00000c00]:
boot event: "OemClkRangeMinViolation" // OC mod range register not allowed
boot event: "OemClkRangeMaxViolation" // OC mod range register not allowed
HECI CMD Status = 0x00000000 (SUCCESS)
![[Image: sku_ic10.jpg]](http://i72.servimg.com/u/f72/13/57/74/66/sku_ic10.jpg)
![[Image: sku_ic11.jpg]](http://i72.servimg.com/u/f72/13/57/74/66/sku_ic11.jpg)
what is your chipset?
as far I know you are trying to "fake it" but I think some chipset have hardware limitations that cant be overriden since the hardware limitations itself
my L502X have a HM67 chipset.
acording to my experiments and those pdf, overclocking my HM67 chipset is posible and have been already done.
![[Image: hm67f.png]](http://img687.imageshack.us/img687/8994/hm67f.png)
![[Image: hm672.png]](http://img826.imageshack.us/img826/4836/hm672.png)
aparently most ones ended with a "7" are all extreme.
and it seems extreme is required for BCLK OCing
That's exactly what I noticed yesterday .
With HM76 I'm screwed ....
hang on... what does that mean - that with HM67 we have the 'premium' version of overclocking potential?
If so, why can we only tweak from the BIOS by 5% BCLK?
@ Jkbuha
It is true that allowing 90-800 mhz BCLK range could be calling "extreme" ^^
...but in fact, due to the sandy bridge arch, that now link PEG (PCIe) and DMI to BCLK, overclocking is less flexible on that specific parameter.
Ivy could achieve a slightly better 110 mhz but, it is clearly a decision from Intel to push customer to buy their K serie CPU (or XM for mobile ) and play with coef for CPU and Memory ...
thanks sebashi - makes me nostalgic for the good old days of jumper clock setting on the mobo...
given this, surely FSB-based overclocking (such as what I've done with clover) should be the way to go?
another low cost option, would be to get a ES (enginering sample) proccesor instead the expensive extreme/XM ones.
ES are usually even cheaper than the OEM ones , and they usually have unlocked multipliers.
I have in mind replace my cheap i3 with ES i7 when I have some cash ^_^
and well, trying to replicate what JKbuha did with clover (125 FSB OC) would be nice.
too bad clover doest work on windows ):
there must be a way of enable FSB OCing on BIOS, like jkbuha stated, the menus are already there, its just that they need some kind of condition to meet.
its really curius we unlocked all other menus except the most interesting one!
Hi,
I think I read in this thread some time ago that you can boot on-the-fly using BIOS file in USB flash drive. Can anyone explain how to do that? Thanks.