Manufacturing EEPROM - DS1013

Alveo V80 Data Center Accelerator Cards Data Sheet (DS1013)

Document ID
DS1013
Release Date
2024-05-08
Revision
1.0 English

A manufacturing EEPROM is connected to the adaptive SoC via the I2C main interface. See Table 1 for the address. The following table provides the manufacturing EEPROM register map. Data locations 0–127 are in a write protected area of the device and are set at time of manufacturing. Data locations 128–255 are in a re-writable area and can be accessed/modified by the user. The AMI tool can be used to view EEPROM information using the ami_tool mfg_info and ami_tool eeprom_rd/eeprom_wr commands.

Table 1. Manufacturing EEPROM Register Map
Location (Hex) Location (Dec) No. of Bytes Field Name Stored Format
0 0 4 EEPROM Version ASCII
4 4 2 Data Checksum Literal/Binary
6 6 36 Alveo Product Name ASCII
2A 42 24 Alveo Part Number ASCII
42 66 16 Manufacturing Alveo Part Number ASCII
52 82 5 Manufacturing Alveo Part Revision ASCII
57 87 14 Product Serial Number ASCII
65 101 4 Manufacturing Date Literal/Binary
69 105 1 Number of MAC IDs Literal/Binary
6A 106 6 MAC ID 1 Literal/Binary
70 112 16 UUID Literal/Binary
80 128 128    

The following sections provide the description of the various fields. Unless stated, all values must be programmed starting with the MSB at the lowest address (that is, Big Endian method). All the trailing unused bytes in each field must be set to 0xFF at the time of EEPROM programming. For example, the maximum length of Alveo Product Name is 36 bytes. A 24-byte long Alveo Product Name leaves the last 12 bytes set to the default value of 0xFF.

EEPROM Version

Format: (ASCII) NN.N

Up to 4 characters (including ‘.’) when N is numeric, to identify the EEPROM version, for example, 4.0.

Data Checksum

Format: 2-byte numeric value

Inverted value of the sum of data in locations 6 to 128.

Note: The product name and serial number can be tracked by scanning the 2D barcode printed on the Alveo accelerator card with the AMD Device Lookup app downloadable on Android and iOS.

Number of MAC IDs

Format: 1-byte number defining the quantity of MAC IDs

MAC ID 1

Format: 6-byte Hexadecimal notation, for example, AB3241CDAB9F with colons omitted

The number of MAC IDs required is product dependent but fixed and contiguous (as defined in ARDs). The MAC ID 1 field is the mandatory field. Management controller firmware reads the MAC ID 1 field and calculates all the other required MAC IDs using the Number of MAC IDs field and passes on required information via in-band or out-band, as needed.

UUID

Format: 128-bit UUID conforming to UUID V1

Hyphens/dashes in UUID are not encoded into this field.