When posting please ensure your entire message is in English. 

@a213m
I really appreciate your continued effort over the years!
I hope to see it running soon on my Intel B760.

Kepp up the good work!

BTW I've ordered some missing parts yesterday.
I noticed that the value of the I2C pull up resistors is very low.
Did you had problems with the usual values arround 4.7k or what is the reason for 2k resistors?
Cable length is a bit longer but I hadn't any problems so far with 4.7k.

I didn't have any issues with either 4.7k or 2k, you can use any value, as long as they are the same, or even not use any at all.
Higher value pull up resistor can have issues with some EEPROMs when fast mode is enabled, but if you are not having issues, 4.7k is fine.

Did some testing with older Crucial DDR4 today as I'm waiting for a DDR5 socket to arrive.
These modules have a ST M34E04 SPD EEPROM which need pin 7 (write control) connected to ground to enable RSWP control.

I had soldered the related cable to socket pin 78, but didn't connect it during the first tests.
To disable RSWP was (of cause) not possible, but as I tried to write the EEPROM anyway during playing arround, I got some odd behavior.
When I click on next to some of the write error messages the app crashes or gives me an exeption error message.
After the crash or the error message the EEPROM is completely corrupted, even with write protection enabled.
I've repeated this a few times and got the same result. Random corrupted data all over the EEPROM.
Just letting you know, maybe you can prevent the crash or the error to keep the EEPROM uncorrupted If somebody tries the same.
I'll upload some pics later, sadly no time left today.
 
With write control grounded, as intended, everthing works great as it should.
 

I don't have any DIMMs with ST M34E04 EEPROM unfortunately, so I can't really test what you have been experiencing. I did, however, test a couple of older DDR2 sticks that use EEPROMs with pin 7 used for hardware write protection control, and SPD-RW detected write protection properly, when pin 7 was shorted to VCC.
 
Your EEPROM is interesting, because it is partially compatible with older hardware EE1002 definition. According M34E04 product info, it is compatible with Jedec's EE1004 definition, however EE1004 doesn't use pin 7, and EE1004 definition is compatible with EE1002 only protocol-wise. Pin 7 was used for hardware write protection in EE1002 EEPROMs, and write protection is disabled if it is left floating by default, or is grounded. Only when pin 7 is connected to VCC, hardware write protection is enabled. And in TSE2002av definition, pin 7 is used for temperature events, since hardware write protection and permanent software write protections were removed.
 
I have modified the schematic to disable hardware write protection by adding a resistor between pin 7 and the ground (to avoid shorting VCC to ground, if hardware write protection is enabled on a DIMM). (https://github.com/1a2m3/SPD-Reader-Writer/commit/af25beb440f49ede1e157c808aaad74285601e90)
 
I suspect your DIMM is hardware write protected, and by grounding pin 7 you are overriding hardware write protection, thus disabling it. Check the resistance between pin 7 and pin 8 of M34E04 EEPROM on isolated DIMM only.
 
Also, if you are willing to send me your DIMM for further testing, PM me to arrange.

Hello, i am trying to find my way to overclock my G.Skill F3-1600C9-8GRSL DDR3 sticks for quite some time and i found a couple problems with my setup. At first i tried using Thaiphoon Burner and when i do the write protection check it says that my ram is hardware write protected so i took a closer look at the SPD chip and i believe its a AT24C02C from Microchip that has a WP (write protection) pin that sets the protection. The funny thing is that this pin is connected to the ground, so write protection is actually disabled by default. Then i found your project (its awesome how much effort you have put into it, thank you for ytour work) and when i try to write something using your software through Smbus it says that writing to EEprom is disabled in bios. My motherboard is AsRock IMB-180 with mobile QM87 chipset so i tried changing the SPD lock byte in the SmBusPei part of the bios image to 0 but pc does not boot after i flash the modded bios (and its the same with my other B85 motherboard). Is there anything that i could try to go around this problem or going the Arduino way is the only way to go for me? I wasnt eager to try flashing with Arduino because im not entirely sure if its possible to connect arduino straight to the spd chip through sodimm socket without any additional circuitry since there is no write protection.

Karalux
Hello, i am trying to find my way to overclock my G.Skill F3-1600C9-8GRSL DDR3 sticks for quite some time and i found a couple problems with my setup. At first i tried using Thaiphoon Burner and when i do the write protection check it says that my ram is hardware write protected so i took a closer look at the SPD chip and i believe its a AT24C02C from Microchip that has a WP (write protection) pin that sets the protection. The funny thing is that this pin is connected to the ground, so write protection is actually disabled by default. Then i found your project (its awesome how much effort you have put into it, thank you for ytour work) and when i try to write something using your software through Smbus it says that writing to EEprom is disabled in bios. My motherboard is AsRock IMB-180 with mobile QM87 chipset so i tried changing the SPD lock byte in the SmBusPei part of the bios image to 0 but pc does not boot after i flash the modded bios (and its the same with my other B85 motherboard). Is there anything that i could try to go around this problem or going the Arduino way is the only way to go for me? I wasnt eager to try flashing with Arduino because im not entirely sure if its possible to connect arduino straight to the spd chip through sodimm socket without any additional circuitry since there is no write protection.

 
Hi, you got several options to try.
 
Check if your motherboard supports enabling SPD write disable bit. (On Asus boards it is available in "Extreme Tweaker > Tweaker's Paradise > SPD Write Disable". Not sure if Asrock has similar option, check your manual to see if it does.)
 
If it doesn't, you'll have to use hardware flasher, whether it's Arduino based or any other I2C capable programmer. Since DDR3 EEPROM uses 256 byte SPD only and doesn't require page switching to access the entire memory array, DDR3 EEPROM can be programmed using any I2C capable programmer, like portable USB CH341A programmer, if you don't want to fiddle with Arduino. If your chip is in SOP8 package, you can use included clip from the kit pictured below to program EEPROM directly, otherwise you'll have to source DDR3 slot/adapter to access your EEPROM. Or desolder the EEPROM off your DIMM and solder it onto one of the included SOIC/TSSOP adapter boards if the clip won't work for you.
 

Hi,
I'd like to try this utility, it sounds great, but Microsoft Defender Antivirus finds there a virus Trojan:Win32/Wacatac.H!ml.
I tried last three versions, but everytime is the same. Whats wrong in this case?
  

Liubo
Hi,
I'd like to try this utility, it sounds great, but Microsoft Defender Antivirus finds there a virus Trojan:Win32/Wacatac.H!ml.
I tried last three versions, but everytime is the same. Whats wrong in this case?

False positive, SPD-RW is safe: https://github.com/1a2m3/SPD-Reader-Writer/issues/34
 
Add program files to exclusion list.