in HWinfo i can see the two first core go at 3.5 Ghz all other are in 3.1Ghz but in Cbr20 they fall bellow 3Ghz but power is in the 230W while I think on my other board thy were in the 3.1 3.2 Ghz range. With 3.9 bios every time I get a better multithread score my single score drop and never really get close to the Asrack board will drop back to bios 3.1 and see. (there could probably be a firmware fix for specter or meldown or soemthing else at play also maiby cpu governer limiting turbo or maiby AVX loads?)
in HWinfo i can see the two first core go at 3.5 Ghz all other are in 3.1Ghz but in Cbr20 they fall bellow 3Ghz but power is in the 230W while I think on my other board thy were in the 3.1 3.2 Ghz range. With 3.9 bios every time I get a better multithread score my single score drop and never really get close to the Asrack board will drop back to bios 3.1 and see. (there could probably be a firmware fix for specter or meldown or soemthing else at play also maiby cpu governer limiting turbo or maiby AVX loads?)
i have tested 8222CL & 8175M on BIOS 3.8a with no such issues, after that i sold my X11SPM-F.
sure newer microcodes can cause this. ASRock's BIOS 2.10 includes very very old with microcode from 2019.
Bios 3.9 had a extra spector fix 3.4 does not seem to have.
Getting closer using bios 3.4 can get nicer single core speed and still somewhat good multithread scores. Not as hight as the Asrock board but getting closer.
Getting closer using bios 3.4 can get nicer single core speed and still somewhat good multithread scores. Not as hight as the Asrock board but getting closer.
can you compare the all core clock of the two boards ? use CPU-Z stress cpu to load (std.setting)
i think the ASRock allows more time to exceed TDP (PL1 time window)
and
i can make acustom BIOS 3.4 later today, if you have the time and wiling to check this.
can you compare the all core clock of the two boards ? use CPU-Z stress cpu to load (std.setting)
i think the ASRock allows more time to exceed TDP (PL1 time window)
and
i can make acustom BIOS 3.4 later today, if you have the time and wiling to check this.
You are going above and beyond. I was also thinking it is probably a PL1 PL2 thing. Unfortunally i do not have the asrack board with me a this time only took the supermicro one to thinking with over the weekend.
But if you are really intereested I will make time to get you those numbers a a later time the least I can do with all the help you provided to me and others.
they are castrated to 3+1 VRM, not way for anything over 165W. some seller have pictures of the 5+1 variant but ship the 3+1.
and if they have BIOS TDP lock, you have to do a BIOS modd too, works with clamp and USB programmer because BIOS is signed.
they are castrated to 3+1 VRM, not way for anything over 165W. some seller have pictures of the 5+1 variant but ship the 3+1.
and if they have BIOS TDP lock, you have to do a BIOS modd too, works with clamp and USB programmer because BIOS is signed.
Yep, I'd be very happy with 125W TDP support.
I could not find the datasheet of the VRM FETs (3 x 59953MC and 1 x 59954MC), but I guess they are 35-40A max, so ~160A total, which is 144W at 0.9V. That would be enough for me to run 6138 and such CPUs.
AFAIK the TDP lock is NOT in the BIOS, because some owners already tried various BIOS versions that support any CPU in the "normal" T42S board, but still does not post with the crippled board.
So I think BIOS mod is not necessary, only VRM controller mod. Or am I missing something?
AFAIK the TDP lock is NOT in the BIOS, because some owners already tried various BIOS versions that support any CPU in the "normal" T42S board, but still does not post with the crippled board.
So I think BIOS mod is not necessary, only VRM controller mod. Or am I missing something?
I could not find the datasheet of the VRM FETs (3 x 59953MC and 1 x 59954MC), but I guess they are 35-40A max, so ~160A total, which is 144W at 0.9V. That would be enough for me to run 6138 and such CPUs.
3+1
3 are VCCCore, 1 is VCCIA IntelAgent.
all scalables use FIFR, the VRM delivers 1.6-1.7Volt constant. a FET with max. 40A can not deliver constant 40A (PWM)
changing the ICC_MAX does not change phase current or something similar. change ICC_MAX just allows to start.
edit:
CSD59953Q5MC datasheet only under NDA.
3+1
3 are VCCCore, 1 is VCCIA IntelAgent.
all scalables use FIFR, the VRM delivers 1.6-1.7Volt constant. a FET with max. 40A can not deliver constant 40A (PWM)
changing the ICC_MAX does not change phase current or something similar. change ICC_MAX just allows to start.
edit:
CSD59953Q5MC datasheet only under NDA.
yeah only 3 phases for Vcore then. I am not familiar with FIVR. Then it's around 90A for Vcore, which gives around 150W @1.7V.
Yes I also found these mosfets are customer specifics super top secret sh*t.
Datasheet is not really important as I can monitor the mosfets overload with my infra cam. If they get hot, I know there is trouble
Also have to put a heatsink on them as they are also missing.
So next step is to find the pins for I2C. Worst case I'll have to solder directly on the IC legs, but I am sure they can be found somewhere.
Is there pinout diagram for the TPS53679? Found it
The Thermal Design Current(TDC) of those processors is 255A, std.default is 228A(TDP=165-205W) and lower.
You can see this TDC value with AIDA, HWinfo does not show this parameter or as PL4. View attachment 26505
actualy there are three ways to do this, except for boards with PXE1610C ( only supported by MCP2221a )
1) MCP2221a (Adafruit)
i made a c# console app for automatic programming ( MCP2221a_iccmax_FF(18122023).7z ) vrm TPS53679/PXE1610C/MP2955A
(if you have concerns using my exe on your system: use iLSpy to see/get the c# sourcecode of them, and recomplie your own)
typical usage(cmd window)
"MCP2221a_iccmax_FF -MP2955A 20"
or
"MCP2221a_iccmax_FF -PXE1610C 60"
or
"MCP2221a_iccmax_FF -TPS53679 58"
2) only MP2955A used in
X11SPM-T(P/F)
X11DPi-N(T) rev.2.x and up
and others
you need I2C interface MPS EVKT-USBI2C-02:
MPS Software V4.5.11 ( if you don't get the Software with MP2955A support, PM me )
3) only for mboards use MPS MP2955A and TI TPS53679
Note:
If you don't have suported CPU(s) to do the modification try it with the high TDC CPU(s), mostly this works,
the system just turns on but you will get no display, the CPU(s) reset is helt low.
you can do now the VRM modification. With supported CPU(s) enter the BIOS and start modifying.
Do not power the X11SPM, install a CPU and connect the EVC2SX or MCP2221a header with a 3 wire Cable to the JVR1 header of the X11SPM View attachment 26506
Connect the EVC2SX with the USB Cable to your PC and start the EVC2 Software.
Now you can power on the X11SPM, click on I2C1 and click "Find Devices" the MP2955A should be found and visible under I2C1.
Click on this entry to open the Device: View attachment 26507
click "Monitoring" to see the value of ICC_MAX.
you can select the standard or max. ICC_MAX in the dropdown menu. View attachment 26508
STORE_USER_ALL is to save the setting permanent. View attachment 26509
With a click at "Apply changes" the new ICC_MAX is written and if you choosed "yes" for STORE_USER-ALL this setting is copied in the NVM of the VRM controller. View attachment 26510
If you have any questions, ask me.
X11DPi-N(T):
i have successfully modified a X11DPi-N(T) rev. 2.01A to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is similar than decribed above, you will see two MP2955A (adr 0x20 and 0x21)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin)
X11SPL-F X11SPi-TF X11DPL-i 11DPH-i :
we have successfully modified a X11SPL-F (adr 0x58), X11SPi-TF (adr 0x58), X11SPH (adr 0x58), X11DPL-i (adr 0x58 / 0x60) and X11DPH-i (adr 0x58 / 0x60) to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is siliar than decribed above, you will see one or two TPS53679
X11SPL-F & X11SPM-(T)F (may block TDP higher than 165W, Guide to make BIOS 3.8a with 255W support )
X11SPi-TF, X11SPH-nCT(P)F
JVR(M)1 pin1 = SCL
JVR(M)1 pin2 = SDA
JVR(M)1 pin3 = GND
X11DPi: View attachment 26511View attachment 26512
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin) X11DPH:
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
T-SGPIO1 Header Pin3/6 = GND (or any other GND pin) X11DPL-i: (set to 228A to run up to 205W SKU)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2 Header pin7/8 = GND (or any other GND pin)
The Thermal Design Current(TDC) of those processors is 255A, std.default is 228A(TDP=165-205W) and lower.
You can see this TDC value with AIDA, HWinfo does not show this parameter or as PL4. View attachment 26505
actualy there are three ways to do this, except for boards with PXE1610C ( only supported by MCP2221a )
1) MCP2221a (Adafruit)
i made a c# console app for automatic programming ( MCP2221a_iccmax_FF(18122023).7z ) vrm TPS53679/PXE1610C/MP2955A
(if you have concerns using my exe on your system: use iLSpy to see/get the c# sourcecode of them, and recomplie your own)
typical usage(cmd window)
"MCP2221a_iccmax_FF -MP2955A 20"
or
"MCP2221a_iccmax_FF -PXE1610C 60"
or
"MCP2221a_iccmax_FF -TPS53679 58"
2) only MP2955A used in
X11SPM-T(P/F)
X11DPi-N(T) rev.2.x and up
and others
you need I2C interface MPS EVKT-USBI2C-02:
MPS Software V4.5.11 ( if you don't get the Software with MP2955A support, PM me )
3) only for mboards use MPS MP2955A and TI TPS53679
Note:
If you don't have suported CPU(s) to do the modification try it with the high TDC CPU(s), mostly this works,
the system just turns on but you will get no display, the CPU(s) reset is helt low.
you can do now the VRM modification. With supported CPU(s) enter the BIOS and start modifying.
Do not power the X11SPM, install a CPU and connect the EVC2SX or MCP2221a header with a 3 wire Cable to the JVR1 header of the X11SPM View attachment 26506
Connect the EVC2SX with the USB Cable to your PC and start the EVC2 Software.
Now you can power on the X11SPM, click on I2C1 and click "Find Devices" the MP2955A should be found and visible under I2C1.
Click on this entry to open the Device: View attachment 26507
click "Monitoring" to see the value of ICC_MAX.
you can select the standard or max. ICC_MAX in the dropdown menu. View attachment 26508
STORE_USER_ALL is to save the setting permanent. View attachment 26509
With a click at "Apply changes" the new ICC_MAX is written and if you choosed "yes" for STORE_USER-ALL this setting is copied in the NVM of the VRM controller. View attachment 26510
If you have any questions, ask me.
X11DPi-N(T):
i have successfully modified a X11DPi-N(T) rev. 2.01A to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is similar than decribed above, you will see two MP2955A (adr 0x20 and 0x21)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin)
X11SPL-F X11SPi-TF X11DPL-i 11DPH-i :
we have successfully modified a X11SPL-F (adr 0x58), X11SPi-TF (adr 0x58), X11SPH (adr 0x58), X11DPL-i (adr 0x58 / 0x60) and X11DPH-i (adr 0x58 / 0x60) to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is siliar than decribed above, you will see one or two TPS53679
X11SPL-F & X11SPM-(T)F (may block TDP higher than 165W, Guide to make BIOS 3.8a with 255W support )
X11SPi-TF, X11SPH-nCT(P)F
JVR(M)1 pin1 = SCL
JVR(M)1 pin2 = SDA
JVR(M)1 pin3 = GND
X11DPi: View attachment 26511View attachment 26512
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin) X11DPH:
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
T-SGPIO1 Header Pin3/6 = GND (or any other GND pin) X11DPL-i: (set to 228A to run up to 205W SKU)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2 Header pin7/8 = GND (or any other GND pin)
you find it in the first page. JVR1 or JVRM1
no jumper. X11SPL-F & X11SPM-(T)F (may block TDP higher than 165W, Guide to make BIOS with 255W support )
X11SPi-TF, X11SPH-nCT(P)F
JVR(M)1 pin1 = SCL
JVR(M)1 pin2 = SDA
JVR(M)1 pin3 = GND
you find it in the first page. JVR1 or JVRM1
no jumper. X11SPL-F & X11SPM-(T)F (may block TDP higher than 165W, Guide to make BIOS with 255W support )
X11SPi-TF, X11SPH-nCT(P)F
JVR(M)1 pin1 = SCL
JVR(M)1 pin2 = SDA
JVR(M)1 pin3 = GND View attachment 34228
The Thermal Design Current(TDC) of those processors is 255A, std.default is 228A(TDP=165-205W) and lower.
You can see this TDC value with AIDA, HWinfo does not show this parameter or as PL4. View attachment 26505
actualy there are three ways to do this, except for boards with PXE1610C ( only supported by MCP2221a )
1) MCP2221a (Adafruit)
i made a c# console app for automatic programming ( MCP2221a_iccmax_FF(18122023).7z ) vrm TPS53679/PXE1610C/MP2955A
(if you have concerns using my exe on your system: use iLSpy to see/get the c# sourcecode of them, and recomplie your own)
typical usage(cmd window)
"MCP2221a_iccmax_FF -MP2955A 20"
or
"MCP2221a_iccmax_FF -PXE1610C 60"
or
"MCP2221a_iccmax_FF -TPS53679 58"
2) only MP2955A used in
X11SPM-T(P/F)
X11DPi-N(T) rev.2.x and up
and others
you need I2C interface MPS EVKT-USBI2C-02:
MPS Software V4.5.11 ( if you don't get the Software with MP2955A support, PM me )
3) only for mboards use MPS MP2955A and TI TPS53679
Note:
If you don't have suported CPU(s) to do the modification try it with the high TDC CPU(s), mostly this works,
the system just turns on but you will get no display, the CPU(s) reset is helt low.
you can do now the VRM modification. With supported CPU(s) enter the BIOS and start modifying.
Do not power the X11SPM, install a CPU and connect the EVC2SX or MCP2221a header with a 3 wire Cable to the JVR1 header of the X11SPM View attachment 26506
Connect the EVC2SX with the USB Cable to your PC and start the EVC2 Software.
Now you can power on the X11SPM, click on I2C1 and click "Find Devices" the MP2955A should be found and visible under I2C1.
Click on this entry to open the Device: View attachment 26507
click "Monitoring" to see the value of ICC_MAX.
you can select the standard or max. ICC_MAX in the dropdown menu. View attachment 26508
STORE_USER_ALL is to save the setting permanent. View attachment 26509
With a click at "Apply changes" the new ICC_MAX is written and if you choosed "yes" for STORE_USER-ALL this setting is copied in the NVM of the VRM controller. View attachment 26510
If you have any questions, ask me.
X11DPi-N(T):
i have successfully modified a X11DPi-N(T) rev. 2.01A to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is similar than decribed above, you will see two MP2955A (adr 0x20 and 0x21)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin)
X11SPL-F X11SPi-TF X11DPL-i 11DPH-i :
we have successfully modified a X11SPL-F (adr 0x58), X11SPi-TF (adr 0x58), X11SPH (adr 0x58), X11DPL-i (adr 0x58 / 0x60) and X11DPH-i (adr 0x58 / 0x60) to run TDC 255A TDP 240W SKUs(i.e. Amazon AWS customs)
With CPU in both sockets installed the procedure is siliar than decribed above, you will see one or two TPS53679
X11SPL-F & X11SPM-(T)F (may block TDP higher than 165W, Guide to make BIOS 3.8a with 255W support )
X11SPi-TF, X11SPH-nCT(P)F
JVR(M)1 pin1 = SCL
JVR(M)1 pin2 = SDA
JVR(M)1 pin3 = GND
X11DPi: View attachment 26511View attachment 26512
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2/3 pin7/8 = GND (or any other GND pin) X11DPH:
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
T-SGPIO1 Header Pin3/6 = GND (or any other GND pin) X11DPL-i: (set to 228A to run up to 205W SKU)
Remove the JVRM1/2 jumpers and connect the I2C :
JVRM1 pin2 = SCL
JVRM2 pin2 = SDA
USB2 Header pin7/8 = GND (or any other GND pin)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.