<feed xmlns='http://www.w3.org/2005/Atom'>
<title>amd-psp-re.git/psp_out/sys_drv_code.bin, branch main</title>
<subtitle>AMD PSP reverse engineering, emulator and vulnerability research</subtitle>
<id>https://git.sl0p.foo/amd-psp-re.git/atom/psp_out/sys_drv_code.bin?h=main</id>
<link rel='self' href='https://git.sl0p.foo/amd-psp-re.git/atom/psp_out/sys_drv_code.bin?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/amd-psp-re.git/'/>
<updated>2026-09-22T09:20:28Z</updated>
<entry>
<title>Track the firmware images and keep the symbol maps alongside them</title>
<updated>2026-09-22T09:20:28Z</updated>
<author>
<name>Peter Geissler</name>
<email>peter@haxx.in</email>
</author>
<published>2026-09-22T09:20:28Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/amd-psp-re.git/commit/?id=771ecaa4ec30e342116bc248873f62cdf6b16500'/>
<id>urn:sha1:771ecaa4ec30e342116bc248873f62cdf6b16500</id>
<content type='text'>
Adds 301 PSP/SMU firmware images (*.bin, *.elf, ~33 MB) that were previously
gitignored. They are public material: the module images come from
linux-firmware and publicly mirrored VBIOS dumps, and nothing was decrypted --
the encrypted on-flash stages (BOOT_LOADER#1, TRUSTED_OS) remain encrypted and
unanalysed, so sOS is the earliest stage present.

Checked the whole-flash dumps before publishing: they carry board SKU strings
only (XFX D702_XTX / 113-31XFSHBS1), no serials, MACs or unique per-board
identifiers.

With the images tracked, the symbol maps in psp_out/phase3/, vdiff/, sigs/ and
handover/symbols/ are now directly reproducible against the exact bytes they
were derived from, and data/MANIFEST.sha256 still pins all 301 hashes.

Still excluded: IDA databases (228 MB, regenerable and churn-prone),
psp_out/decompiled/ (Hex-Rays output mechanically derived from AMD code), and
AMD-internal register maps, which are vendor documents rather than public
firmware.
</content>
</entry>
</feed>
