PLL Pinmod Overclocking Methods and Examples

Hi,

what is an "IPD"?

bye
Tom

 

Hi,

IPD = Internal pull down:
http://en.wikipedia.org/wiki/Pull-up_resistor

Also you can email Abo (creator of setfsb), follow his instructions on his website.
He may be able to help you.

Bye

 

Hi,

thanks alot moral hazard. As I mentioned before = you guys are genius.
I return from launch break at the moment. I bought a 15x magnificient glass.
It should substitude my 4x glass I use actually. I hope, I can now verify my soldering a bit more.

I will follow "nando4" instructions today evening. But he only show me FSB values up to 183MHz. Do you know the hex strings for >200MHz?

bye
Tom
P.S. sorry for my bad english

 

Hi,

I can give you hex strings for >200MHz.
But I think it will not be too hard to get setfsb working properly.

Bye

 

Hi moral hazard,

I tried your suggestions yesterday.
ICS9LPRS3 55xxx and ICS9LPRS3 55xxx show same behavior.
OC freezes system, downclock freezes too. Even when I change nothing
only get fsb -> set identically fsb system freeze.

The hex values for 0D 0E are unchangeable. Every changed parameter + [in/out]-Button stay unchanged.

Mhhh..now I know no further possibilities.
P.S. the new magnificent glas shows no solder-shortcut between PCI1 <-> TMP/PCI2 <-> PCI3

Bye
Tom

 

Can you please do the following:
1. select ICS9LPRS355.
2. Click on the diagnosis tab.
3. press getfsb.
4. move the top slider.
5. press setfsb.
6. take a photo of setfsb with a camera before the notebook restarts.

Then upload the photo here for me.

Thanks

 

Hi moral hazard,

I followed your instructions yesterday evening.
Because I use an old dv camcorder instead of
a new sd-card / hdd model I have to capture
the "movie" via firewire. Actually I'm not able
to do that, but I will send you the pics till monday.

I can only report one "optical" difference during
the crash at the moment. The xxxx355xx PLL
crashes immediately with black screen.
The xxx365xxxm PLL crashes with reduced
brightness only. (As if I run on battery and use
energysaving for longer lifetime).

Bye + nice weekend
Tom

 

Hi guys,

""But I think it will not be too hard to get setfsb working properly.""

I hope so, because my last pic (before screen goes black) is this...
This happens with xxx365xxx and xxx355xxx PLL. PLL xxx509xxx doesnt work properly = Pll id error during "get fsb".

When I look at the 2510p PLL screenshots carefully, I see 6x registers changes. Not only the 0D / 0E for the FSB. Maybe you are right - I did the tmp=off hardmod, so the pll wont work for me. As you can see, I only apply the "get FSB" values, no changes.

Abo isnt responding to my inquiry till today.

Mhh...

Bye
Tom

 

Hi Tom,

I have attached the datasheet for your PLL to this post.
You may find it useful.

 

Please try this:

Press getfsb.
Change byte 21 from 00 to 01, then press update and apply.
Then move the top slider to the right.
Then press setfsb.

Let me know if it helped.

 

Hi moral hazard,

thanks for the pdf.
I already used this to find out the pin-situation on my squared version of that pll. I have to say that my electricial knowhow isnt good enought for the rest of this document, e.g. electricial characteristics.

I think you refer to page 19f, because of the register explenation. It is hard for me to "transform" the bytes so they look like the setfsb main screen. Maybe you can help me.

Bye
Tom

 

Maybe this pic will help.

 

more detail

 

Hi moral hazard,

thank you once again. My mistake was to read the bit of each byte from left to right not vice versa. Do you agree, byte 00 is very important too: FSA, FSB, FSC, SRC_main_sel...

bye
Tom

 

Yes, that is a very important byte.

Too bad that FSA, FSB and FSC are read-only bits. Otherwise it would be very easy to overclock.

Did you get a chance to try this:
Press getfsb.
Change byte 21 from 00 to 01, then press update and apply.
Then move the top slider to the right.
Then press setfsb.

I think it should work (hopefully).

 

Hi moral hazard,

the hint setting 21 from "0" -> "1" was very helpful.
NOW I can adjust the "0D" + "0E" + "17" + "18" Bytes.
But all setting refer to the pci-e and pci clock.
I set the pci-e clock to 100-106-112MHz and pci was
between 16-42MHz. I cant capture with setfsb because
the system run instable with any non-default setting.
BUT it does not crash completely.

Using the top slider ends with the same behavior - black
screen + hdd led permanent on + nothing responding.

I checked my modding several times, but I would even
ask you this... I lifted the TMP/PCI2 pin and soldered it
with 10K to GND. I cut the pin from the pcb, not unsolder.
Is it possible that I pushed some metal (conduction) below
the pll so I shortcut PCI1<->PCI3?


Bye
Tom

 

I think I know what your problem is.

Please try this:
Click the diagnosis tab.
press getfsb.
set 21 from "0" -> "1".
Press update and apply.
move the top slider.
press setfsb, before your notebook restarts, take a photo with a camera for me please. Then upload the photo for me.

 

Hi moral hazard,

sorry for my stupid questions. I apprechiate all your work.
What do you hope to see on that last picture before "BSOD"
BlackScreenOfDeath { )?

I'm at the point of capitulation. I'm very close to tweak the
converse. E.g. undervolt and underclock with rmclock and
the hardwire VID-mod for reaching values below 0.9750 barrier.

Maybe, the point of interest is: does my xxx355/365B.K.L. differ
to the supported xxx355/365B.G.L.F.?

You wrote: FSA/B/C are read-only. The screenshots of the HP2510p thread in this forum shows a change from 37->31. How can this happen? Does the pll set this by itself becaus some divider changes?

Bye
Tom

 

You can pin mod the PLL to change the values for FSA/B/C.

You ask "What do you hope to see on that last picture before "BSOD""

I am hoping to see bit 1 of byte 0 = 1.
Which would mean the source for SATA clock = "SATA = PLL2".
Which makes the system unstable.

So please watch that bit and tell me if it changes after you press "setfsb".

 

My 2510P's ics9lprs355 is TME locked. I worked with abo to have it supported by setfsb. Abo is apply some sort of TME workaround, which is why I would suggest not using the ics9lprs355 to attempt to alter the FSB on your system as you have removed TME mode.

A better idea would be to email abo and request his assistance to create a PLL entry for your B.K.L PLL.

If no joy that way, if you have Linux and can tweak code a bit, consider using the grub2 bootloader overclocking package to do the overclocking/testing instead. It's based off the lfsb source code and compiles a standalone setfsb you can use in Linux. You can provide the full sequence of bytes to send the PLL and easily evaluate what's happening.

Otherwise Moral_Hazard's suggestion of directly pinmodding FSLA, FSLB, FSLC is a good one. Can get a hardware set overclock that way. It's definitely doable, one way or another.

 

Hi moral_hazard,
hi nando4,

I think, modding the fsb with wire (bsel+pin57 = pin64 on my pll) wont boot the system because a +66 from 200->266 ist to high. I guess my ddr2 800 and cpu cant handle that. I hoped to reach 250 with setfsb.

Sorry, I'm not a linux enthusiast. I know grub from my M$ WAIK preinstalled environment recovery cds - thats all. But your suggestion reminds me to think about OS power management access.

Is it possible, the crash depends on some sort of speedstep; superfetch; energy management. Should I try "safe mode"?

I mailed Abo one week ago. No response.

Bye
Tom

 

Your CPU will probably be stable.
I did overclock from 200mhz FSB to 272mhz and my CPU was fine, my ram was unstable though.

You can use thaiphoon burner to flash the ram to a lower frequency, so it will be stable.

I think you should try a 266mhz fsb.

 

Hi moral hazard,

does the fsb influense the RAM/FSB divider so I do not need DDR2 PC8500 1066MHz?
1:2 mean 200:400(DDR800) / 266:533(DDR1066)
2:3 mean 266:400(DDR800)

I understand, a BSEL-trick w/o FSB_TEST_MODE-pin modding results in a lock at lowest multi. If I have no time to do the BSEL-trick (the pll lies very good accessable below the keyboard, but the socket is on the bottom of the mainboard), is it enough to do the PIN64 modding or must be the two frequencies identical.

Bye
Tom

 

Do not do the BSEL mod.


Just modify the PLL.
If your memory becomes unstable, then download thaiphoon burner and lower the frequency of the ram. I can help you with that.
I suggest lowering the ram frequency before you pin mod the PLL.

 

Hi moral hazard,

thaiphoon burner. Never heared about it before. Does it change MHz or CAS latency? I apprechiate every info relating this topic.

Return to start:
- if the setfsb-version doesnt work because of SATA=PLL2
- if Abo is not responding my ICS9LPRS355B.K.L inquiry
- if the PIN64-version needs to much knowledge about SPD flashing
I will keep my hands off and do the undervolt procedure.

Bye
Tom

 

Ok.

Thaiphoon burner lets you change anything, MHz and latency (even voltage, but DO NOT CHANGE THE VOLTAGE).

Please be careful with thaiphoon burner. I will give you instructions if you need them.
You should only flash one stick. DO NOT FLASH BOTH STICKS OF RAM.

When you lower the frequency of one stick, the other stick will also run at the lower frequency so you do not have to flash it.
Same goes for the latency.

Make sure you leave one stick of ram alone. It is very important, it will let you fix your ram if you do a bad flash.

It's not too hard.

 

Hi moral hazard,

seams you are online 24/7 { )
If the SATA=PLL2 problem is not resolvable today evening (pics follow) I will give the 200@266 mod a last try. Before, I would like to know your volt/temp scores with prime or orthos or OTTC.

Actually with my mods...
1.) extend fan suckhole to 50x50mm from the default 25x50mm
2.) 0,9750Vc@2000
3.) acrtic silver 5 instead of the default compound
...I only achieve 51°C in coretemp during gaming
(with HD4650 heating up the heatpipe 78°C additionally)

Bye
Tom

 

Hi moral hazard,

here are the pics of 3x crashes.
It is PAL only 720x576, and I cant see something helpful.
I worked keyframe accurate. 1sec is only made of 25frames,
so I cant catch the needed 0,0000001sec.

bye
Tom

 

Hi moral hazard,

myself - once again this evening ;-)

I try changing the byte "0"...
0100001=41 to
0100011=43 SATA=PLL2 - everything is fine
0100101=45 SRC_Main=PLL3 - exactly same crash like set fsb
0100111=47 SATA+SRC - exactly same crash like set fsb

So I think we have to look for PLL3. Btw if it is not inconvinient
to you, please post me the DDR2 SPD flash procedure.

Bye
Tom

 

Download thaiphoon burner here:
http://jungle.at.tut.by/download.html

Start the program.
Click on "Read".
Read the SPD from one stick of ram.
Then click "Save".
Save the SPD image (this will be used as a backup).

Now click on "Editor".
Here you can change the frequency.
Lower the frequency.
Then use the Editor to flash the new SPD onto one stick of ram.

Then restart the notebook.
Use CPUz to check if your memory is running at the frequency that you set.

If you have a problem, take out the stick of ram that you have flashed.

Only flash one stick.

I can give you screenshots if you need them.

 

I have one last thing for you to try before you do the pin mod.

1. Press getfsb.
2. Change byte 17 from A5 to A8, then press "update".
3. Change byte 18 from F1 to F4, then press "update".
4. Change byte 21 from 00 to 01, then press "update".
5. Press apply.

Check cpuz to see if the FSB changed.

If that doesn't work, try doing this:
1. Change byte 0 from 41 to 46, then press "update".
2. Change byte 17 from A5 to A8, then press "update".
3. Change byte 18 from F1 to F4, then press "update".
4. Change byte 21 from 00 to 01, then press "update".
5. Press apply.

 

Hi moral hazard,

thank you. I will try your suggestions.
Abo answered me and asked me for some screenshots and pics.

Maybe he can help us understanding the xxx355B.K.L version.

bye
Tom

 

Hi,

Make sure you tell Abo the following (it is important for him to know):

 

Hi moral hazard,

of course - everything done.
I wrote a little summary (with all our investigations) + pics.

bye
Tom

 

Hi moral hazard,

I red the thread once again from the beginning, with our newest facts in mind.
On the bottom of page 1 is written...

"Abo hasn't explained how he did it, but to me it looks like he is switching the clock SRC as shown in setfsb's diagnosis window here. We see register 0, bit2: SRC MAIN=PLL1(0) changes to PLL3(1) after setfsb use on ICS9LPRS355. Moving the slider then changes the VCO frequency dividers that are set using byte 14(PLL1)/OEh and byte 17(PLL3)/11h. Setfsb altering both PLL1 and PLL3 VCOs (why?)."

This is exactly the problem! If I change Byte "0"=01000001 to 01000 101 the system crashes.

Bye
Tom

 

Well it looks like you're getting somewhere.
I would expect it to be easy for Abo to make you a test version, hopefully it will work

 

Hi moral hazard,

Abo informed me, he is busy. He will analyze our facts next time.
Yesterday I tried your last two suggestions.

Moddifying 17+18+21 results in PCI dropping from 33,20 -> 29,20MHz.
FSB did dot change. Editing 00+17+18+21 crashes, because "00"=46
set Main_SRC=PLL3. My problem.

Some questions I asked you before.
- What are your core temps with an oc of +33%?
- Does the new fsb=266 not change fsb/ddr ratio from 1:2 -> 3:2?
- What fsb can quality pc6400 ram handle, +10%=880MHz?

Bye
Tom

 

I have one more suggestion:
1. Press getfsb.
2. Change byte 17 from A5 to A8, then press "update".
3. Change byte 18 from F1 to F4, then press "update".
4. Change byte 21 from 00 to 03, then press "update".
5. Press apply.

My T7300 gets to 90C (max temp with intelburntest).
My T8100 did not go above 80C (max temp with intelburntest).

The T7300 (merom) is 65nm tech, so it runs hot.
The T8100 (penryn) is 45nm tech, very cool

Idle temps are around 60C for the T7300.
The idle of the T8100 was room temp (much cooler at idle).

No.

My PC6400 ram got to 900mhz (unstable). 880mhz is possible for me.
But if you have the PM965 chipset, you 800mhz ram will downclock to 667mhz so you have more room to overclock.

If your ram is running at 800mhz now, I suggest looking for better ram.
Or you can use thaiphoon burner to flash a lower frequency onto the ram.
Flash it to 667mhz, then you will be able to overclock a lot.

Thaiphoon burner lets you change the FSB : DRAM ratio.
Since you can change your ram frequency.

 

Hi moral hazard,

the HP DV6-12xx Intel based series uses the PM45 chipset.
CPUz show in SPD: CL4/400, CL5/667, CL6/800.

bye
Tom

 

You should flash the ram to 667mhz if you want to overclock a lot.

But you never know, your ram could be very stable.

I once overclocked 533mhz ram to 770mhz.
Also I overclocked 667mhz ram to 830mhz.

So you never know how far it can go.

 

Hi all,
hi moral hazard,

it seams not to be as easy as you described for my modifing the CAS/MHz.
I attached you the SPD backup file. Please delete the .ZIP extension to load in thaiphoon burner.

The MHz are locked and the CAS parameter stay at slowest possible value for 800.

Bye
Tom

 

I'll take a look.

I just need to boot into win7, will take 2 mins.

 

The file you gave me is not complete, when I open it with thaiphoon burner, it doesn't show much. Also doesn't let me open the editor.

Can I see a screenshot after you read the SPD?

Also you might want to try using SPDtool to increase the CAS latency.
But be careful with SPDtool, it can sometimes flash a BAD SPD value.

 

Here is my SPD dump if you want to look at it.

 

Hi moral hazard,

the screenshot you need.

bye
Tom

 

Is that the spd of your ram?

You know that you can click on "browser". Then look for similar ram.
You can flash the spd from similar ram onto your ram.

 

Hi,

whats wrong with my ram? Yes, the screenshot + dump is from my ram.
As I explained, I never used thaiphoon before. Maybe I did something wrong.

bye
Tom

 

Ok, do this:

1. Open thaiphoon burner.
2. Click "browser"
3. click "download"
4. change the capacity to 2048 and the architecture to DDR2 SDRAM.
5. click search.
6.scroll down to the samsung ram.

select "samsung M4 70T5663QZ3-CE6 DDR2-667".

then click "save dump".

Then close the browser.
Open the dump that you've just saved.

Then click on "write" and "full rewrite".

That should make your ram run at 667mhz.

Only flash one stick of ram.

Then turn off the notebook, only install the stick that you have flashed.
If it runs at the correct speed then great.
If the notebook wont boot, put both sticks back in.

Be carefull this could kill your ram.

 

Hi moral hazard,

I followed your instruction - but unlucky beginner.
One of the two sticks is flashed with the 667 dump.
The second/other was untouched.

Took out the standard bank and leave in the modded.
No boot, only lights are blinking. Installed the second
bank - no boot also.

Took out the flashed bank and installed unmodified alone,
everything is as before. How can I re-flash? You wrote
before: "flash one stick; if it works install second bank;
then both sticks will synchronize and run on new values"

Now both sticks run on unsupported values if installed
together. Mhh... problem for me - the taiphoon newbie.

Bye
Tom

 

Hi moral hazard,

despairingly I did something, everybody advices not to do:
I installed the broken stick after win7 loaded completely.
The system recognizes 1x2GB. Thaiphoon (thanks the computer
god) recognizes 50h AND 52h 2x2GB. I flashed everything back.

Now - as you can see, I'm writing you from that machine.
The downloaded dump-file from the thaiphoon browser look curious.

Bye
Tom