AKA R4900G3 R4700G3Okay, let me make another correction. The VRM pin for H3C C35 platform is J266
Among them, 1 scl, 2 gnd, and 3 sda
Because its PMBUS output is hung on the bridge, the multimeter cannot detect it.
same J266 and pinout on HP DL360/DL380 Gen10, sure ?Okay, let me make another correction. The VRM pin for H3C C35 platform is J266
Among them, 1 scl, 2 gnd, and 3 sda
Because its PMBUS output is hung on the bridge, the multimeter cannot detect it.
suresame J266 and pinout on HP DL360/DL380 Gen10, sure ?
no PXE1610C foundSorry, HPE DL360 Gen10, we find some errors when I run MCP2221a_iccmax_FF -PXE1610C 62 64.Why?
wrong / bad connection, MCP2221a defective.I also ran the command MCP2221a_iccmax_FF.exe -scan 20 70, but no devices were detected within the specified I²C address range.
Thank you, I found the reason. The workstation must be powered on, and then run the command.no PXE1610C found
wrong / bad connection, MCP2221a defective.
scan don't show icc_max. try the mod. and you see.i scan mainboard foxconn RM760-FX , not show icc_max, only show
ok, it workingscan don't show icc_max. try the mod. and you see.
"MCP2221a_iccmax_FF.exe -TPS53679 60 61"
typical behave for no 2nd Gen support BIOS.8259CL not work (maybe bios not support 82xx cpu) it boot but hang when memory init ...
header must not have connection even if close to the VRM controller.Just got a Cisco C240 M5, and I found the vrm chip (PXE1610CDN) which is close to a 4 pin header.
look at the circuit diagram from manufacturer, if you don't have it no.Is there a way to identify them without using fancy equipment?
@RolloZ170 Thanks for the good work. I have a X11DPi-NT Rev: 1.21. Is it impossible to perform this mod?you have to write your own software.
i do support ElmorLabs EVC (XML script) and MCP2221a ( with my c# CLI )
new: CLI for EVKT-USBI2C-02 beta stage.
you have X11DPi-N revision 2.0 or higher ?
if not e.g. rev 1.21 don't work.
1.21: this is the rev. with the VRM design bug, if blowed up, SM will replace it even after warranty period.I have a X11DPi-NT Rev: 1.21. Is it impossible to perform this mod?
I saw the following 3 commands and I am not sure which one applies to me:
MCP2221a_iccmax_FF.exe -scan 10 7F
Thanks for the info. What does the -scan option do? Does it read the addresses? If I really do perform the mod, do I need to run:1.21: this is the rev. with the VRM design bug, if blowed up, SM will replace it even after warranty period.
rev. 1.21 uses still TPS53679 (TI) controller not MP2955A (MPS)
do a
MCP2221a_iccmax_FF.exe -scan 10 7F
BUT I DON'T RECOMMEND TO USE HIGH TDC PROCESSORS ON THIS REVISION.
( bec. it can blow up even with the std. SKUs )
MCP2221a_iccmax_FF.exe -TPS53679
-scan 10 7FThanks for the info. What does the -scan option do?
MCP2221a_iccmax_FF.exe -TPS53679 20 21
sure. this rev. has a VRM design BUGWhen you say even standard SKUs can blow up the VRM for the 1.21 rev board, does it mean even if I stay within 205W TDP (but very close to the limit) as per specs, I risk blowing it too?
not a bad idea.Can I mount an additional heat sink on the VRM for CPU1 on my board to minimize that issue?
correct. there is no TDP block in the BIOS.For BIOS, am I correct in assuming that it does not matter what version I have when running this mod as long as it is one that supports my CPU?