coreboot-kgpe-d16/util/amdtools
Martin Roth 74129e5141 util: Update description files
- Spelling fix
- Add languages
- Update formatting
- Move notes that shouldn't be in the description file to a README

Change-Id: I4af37327d5834f8546a3f967585658fb5686f17a
Signed-off-by: Martin Roth <gaumless@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/64581
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Felix Singer <felixsinger@posteo.net>
Reviewed-by: Maxim Polyakov <max.senia.poliak@gmail.com>
Reviewed-by: Paul Menzel <paulepanter@mailbox.org>
2022-05-30 13:05:21 +00:00
..
example_input
README.md util/amdtools/README,description.md: add update_efs_spi_speed docs 2022-02-15 23:32:52 +00:00
description.md util: Update description files 2022-05-30 13:05:21 +00:00
k8-compare-pci-space.pl
k8-interpret-extended-memory-settings.pl
k8-read-mem-settings.sh
parse-bkdg.pl
update_efs_spi_speed util/amdtools: Add script to update the SPI speed in the EFS header 2021-09-08 19:41:31 +00:00

README.md

amdtools

Various tools for AMD platforms

A tool to update the SPI speed set in the EFS table

This works for Stoney Ridge and Zen class AMD processors.

  • update_efs_spi_speed

A set of tools to compare (extended) K8 memory settings.

  • k8-compare-pci-space.pl
  • k8-interpret-extended-memory-settings.pl
  • k8-read-mem-settings.sh
  • parse-bkdg.pl

Before you can use them, you need to massage the relevant BKDG sections into useable data. Here's how.

  1. First, you need to acquire a copy of the K8 BKDG. Go here: Rev F: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/32559.pdf
  2. Make sure pdftotext is installed (it's in the poppler-utils package on Debian/Ubuntu).
  3. Run the bkdg through pdftotext: pdftotext -layout 32559.pdf 32559.txt
  4. Extract sections 4.5.15 - 4.5.19 from the file, and save it separately, say as bkdg-raw.data.
  5. Finally run the txt file through the parse-bkdg.pl script like so: parse-bkdg.pl < bkdg-raw.data > bkdg.data

Now we have the bkdg.data file that is used by the other scripts.

If you want to test the scripts without doing all this work, you can use some sample input files from the 'example_input/' directory.