k3-chipinfo SR1.0 vs SR2.0: the TI silicon revision field

The Linux k3-chipinfo driver reads the TI K3 chip-ID register on boot and prints a line like:

k3-chipinfo 43000014.chipid: Family:AM62AX rev:SR1.0 JTAGID[0x0bb8d02f] Detected

Three fields decode:

• Family = AM62AX: the K3 silicon family. Note this is the family name, not the marketing part number (which for this board is AM62A7).
• rev = SR1.0: the silicon revision, in TI's Silicon-Revision notation. First public revision of a new K3 family is typically SR1.0; a respin (with bug fixes or process shrink) becomes SR2.0.
• JTAGID = 0x0bb8d02f: the IEEE 1149.1 JTAG identification code. Uniquely identifies the silicon at the JTAG level.

Why silicon revision matters on K3: DMSC firmware ABI compatibility windows are tied to silicon rev. A DMSC image built and signed for SR1.0 will not necessarily boot on SR2.0 hardware, and vice versa. TI ships different SYSFW binaries for different silicon revs; picking the wrong one produces a boot that hangs before Linux comes up.

If you're bringing up a new K3 board, the k3-chipinfo line is the ground-truth answer to "which SYSFW binary do I need." If your board reports SR2.0 but you're loading an SR1.0-only firmware image, you'll see DMSC hang or fail to authenticate long before the kernel line prints: check the TI SYSFW release notes for the SR window each firmware version supports.