VRM modify ICC_MAX to run high TDC OEM cpu

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Z

Zhengrankela

Member
Oct 12, 2024
42
5
8
SakuraX said:
Hello friend, thank you very much for your tutorial, which helped me successfully use a high TDP/TDC CPU. Here is a screenshot of the success. I don't quite understand this sentence "remaining attempts = 0C (normaly 0D) so one OTP bank was used." Will it affect the follow-up? --------My English is not very good, these words are from Google Translate.

View attachment 39653
Click to expand...
oh，i saw this photo, you can actually speak Chinese to me
here are the Chinese version Guide.
 
C

conan2095

Member
Aug 3, 2020
38
9
8
MAY I ASK THE ASUS WS C621E SAGE THIS MOTHERBOARD CHIP SHOULD BE 1610C, THE LOCATION OF THE JUMPER I PROBABLY FOUND HERE, I DON'T KNOW WHAT CODE TO USE TO BRUSH,Corrected the error, the 5.3V in the figure below should be 5.3Ω
1.jpg

2.jpg

3.jpg

4.jpg
 
Last edited:
R

RolloZ170

Well-Known Member
Apr 24, 2016
9,022
2,867
113
germany
conan2095 said:
MAY I ASK THE ASUS WS C621E SAGE THIS MOTHERBOARD CHIP SHOULD BE 1610C, THE LOCATION OF THE JUMPER I PROBABLY FOUND HERE, I DON'T KNOW WHAT CODE TO USE TO BRUSH,Corrected the error, the 5.3V in the figure below should be 5.3Ω
Click to expand...
scan the bus.
"MCP2221a_iccmax_FF.exe -scan 20 7F"
 
A

a7260

New Member
Oct 28, 2024
1
0
1
Slothstronaut said:
Your help has gotten me further this morning than all of last week. Thanks!

Here is where I am stuck, and I am betting its something dumb:

Code: 
## Commands I ran with comments added
I2C>[0xC0 0x0 0x20]    # Write to device 0xC0 register 0, page 0x20
I2C START BIT
WRITE: 0xC0 ACK
WRITE: 0x00 ACK
WRITE: 0x20 ACK    # got an ACK, all good
I2C STOP BIT
I2C>[0xC0 0x73 [0xC1 r:2] # Write to device 0xC0 again with the command 0x73, followed by read from same device
I2C START BIT
WRITE: 0xC0 ACK
WRITE: 0x73 NACK ###### Uh oh, NACK received, didn't like that command
I2C START BIT
WRITE: 0xC1 ACK
READ: 0xFF  ACK 0xFF # Gibberish data back
NACK
I2C STOP BIT
Clearly my read command is not correct, as it balks at the 0x73 command and dumps 0xFF as a reply. If i sniff around using other commands, I do get results back. Reverse-engineering your application a bit, it appears you are doing basically the exact same thing but handing off the actual SMBus communication to the DLL which is where i lose visibility into how the packets are constructed. Can you offer any guidance? Once i can get this packet formatted correctly, the rest I can figure out.

Again, thank you so much for the quick assistance!
Click to expand...
could you show me the image that Adafruit MCP2221A links to JVRM1/2, I need your help
 
C

chinesestunna

Active Member
Jan 23, 2015
662
227
43
58
RolloZ170 said:
Guide in the Guide:
modify X11SPL-F & X11SPM-(T)(P)F BIOS 3.9 & 4.0 to support 255Watts
download the BIOS 3.9 or 4.0 from supermicro.
download HxD or use your favorite Hex Editor and open the BIOS file.

( A5 hex = 165 dec. / FF hex = 255 dec. )


X11SPL BIOS 3.6
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF C3 23"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF C3 6F"
X11SPL BIOS 3.9
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 62 6C"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 62 B8"
X11SPL BIOS 4.0
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 81 7A"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 81 C6"

X11SPM BIOS 3.4
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 82 9D"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 82 E9"
X11SPM BIOS 3.5
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 82 65"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 82 B1"
X11SPM BIOS 3.8a
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF C3 EE"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF C3 3A"
X11SPM BIOS 3.9
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 62 4A"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 62 96"
X11SPM BIOS 4.0
( this is only correction of ProjectPeiDriver.ffs checksum )
search for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 81 7E"
replace with "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF 81 CA"


X11SPL / X11SPM all BIOS
search for "6C 68 A5 00 00 00 68"
replace with "6C 68 FF 00 00 00 68"

X11SPL / X11SPM all BIOS
search for "FB B9 A5 00 00 00 5E"
replace with "FB B9 FF 00 00 00 5E"

save as "BIOS_X11SPL-096E_20230315_3.9_255W.bin" respective "BIOS_X11SPL-096E_20230620_4.0_STD.bin"
save as "BIOS_X11SPM-095D_20230315_3.9_255W.bin" respective "BIOS_X11SPM-095D_20230620_4.0_STD.bin"
its works now, here is a proof
View attachment 26864
Click to expand...
@RolloZ170 with current BIOS of X11SPL-F at v4.4 what is the ProjectPeiDriver.ffs checksum we should be searching for and replacing with? Apologies but I was not able to find update to this.
 
R

RolloZ170

Well-Known Member
Apr 24, 2016
9,022
2,867
113
germany
chinesestunna said:
with current BIOS of X11SPL-F at v4.4 what is the ProjectPeiDriver.ffs checksum we should be searching for and replacing with? Apologies but I was not able to find update to this.
Click to expand...
load modified BIOS with UEFITool. find ProjectPeiDriver, click on it.
UEFITool will report bad chksum and tell you expected value.
 
  • Like
Reactions: chinesestunna
C

chinesestunna

Active Member
Jan 23, 2015
662
227
43
58
RolloZ170 said:
load modified BIOS with UEFITool. find ProjectPeiDriver, click on it.
UEFITool will report bad chksum and tell you expected value.
Click to expand...
I believe I was able to complete this correctly for X11SPL-F Bios 4.4:
  1. First I performed the 2 changes with HxD at end of your post
    1. search for "6C 68 A5 00 00 00 68"
      replace with "6C 68 FF 00 00 00 68"
    2. search for "FB B9 A5 00 00 00 5E"
      replace with "FB B9 FF 00 00 00 5E"
  2. Then loaded this mod_bios.bin into UEFITool v0.28, surely enough I got the ProjectPeiDriver.ffs Checksum error in Message Window: value 61h and expected ADh
  3. Using HxD, I searched for "26 22 9C 73 64 32 54 44 99 1C 8D C4 4A 73 D6 AF" as the last 2 HEX blocks change with each version
    1. Found 2 blocks, 2nd block contained "02 61"
    2. Changed 61h to ADh
  4. Verified in UEFITool v0.28 again and the checksum error is gone.
  5. Flashed BIOS via IPMI interface, initially the system seems to be dead, power on but no video signal of any kind
  6. After full power off and disconnect, it booted successfully (I don't have a 165W+ chip to test if the Mod was actually successful at this point)
 
Last edited:
  • Like
Reactions: RolloZ170
D

dsenela

New Member
Apr 4, 2019
8
1
3
Hi guys. Need help in identifiying correct pins for supermicro X11DPG-QT motherboard.

Instructions shows as follows:
1730478465127.png

The 2 JVRM jumpers on my board are labelled as follows:jvrm1.jpg

jvrm2.jpg

Can I connect to either or it must be pin 2 of each? Sorry for my confusion. I know a few people on this thread have been able to succeed in modding this board. but I cannot find clear instruction on how they connected the pins to programmer. (I have a MCP2221A)

Thanks!
 
Last edited:
R

RolloZ170

Well-Known Member
Apr 24, 2016
9,022
2,867
113
germany
dsenela said:
Hi guys. Need help in identifiying correct pins for supermicro X11DPG-QT motherboard.

Instructions shows as follows:
1730478465127.png


The 2 JVRM jumpers on my board are labelled as follows:
Click to expand...
different revision.
JVRM1 is like at X11SPL,X11SPM.
X11DPG-QT
JVRM1 is as shown.
CLK = SCL
DAT = SDA
GND = Ground

JVRM_SEL1
PCH or BMC access for VRM unit:
only if you have issues by mod, remove jumper.
 
You must log in or register to reply here.
Top Bottom