Send your DDR5 SPD dump to the spdr project

The spdr project decodes DDR5 memory modules. It can only get better by being tested against real modules, and the only way to get those is from people who own them. This page does the fiddly part: it reads your dump, removes the one piece of data that identifies your module, checks that the result is still a faithful image, and hands you a file you can send.

Nothing here leaves your computer. This page has no server and makes no network request. Your file is read by the browser, in this tab, and never sent anywhere until you send it to GitHub yourself.

1 · Choose your dump

Whatever you have: the raw file, or the text a hex-dump tool printed. Drag it here, or click to pick it.

Drop the file here

or use the button below

Raw binary, a hex dump, or a plain block of hex.
How do I get a dump in the first place?

This is the hard part, and it is a hardware problem rather than a software one: the SPD lives on the SMBus of the memory module, and getting it out needs either a UEFI tool or administrator rights on Linux.

Linux. The SPD hub on a DDR5 module is bound to the spd5118 driver, which the kernel has carried since 6.11, and the EEPROM shows up as a file:

dd if=/sys/bus/i2c/drivers/spd5118/0-0050/eeprom of=dump.bin

The bus and device address differ from machine to machine; the address is usually 0x50 for the first slot, and ls /sys/bus/i2c/drivers/spd5118/ lists what is there. ee1004 is the older driver, for DDR4. On a kernel older than 6.11 there is no DDR5 SPD support at all, and the UEFI route below is the way.

Windows. A UEFI tool such as RWEverything can write the SMBus to a file from a UEFI shell. Booting into the UEFI shell and running it there is usually the easiest route.

Either way. If you would rather not produce a binary file, hexdump -C dump.bin > dump.txt produces a text dump this page reads just as well.