...
The PHYTEC EEPROM data layout is a 32-byte structure located at offset 0 on the EEPROM. The following table details each entry in the structure for the PHYTEC AM572x SOM EEPROM layout.
Byte | Name | Description |
---|---|---|
1-4 | header | PHYTEC EEPROM header. Unsigned 4-byte integer. |
5 | api_version | PHYTEC EEPROM layout API version. Unsigned 1-byte integer. |
6 | mod_version | 0: PCM, 1: PFL, 2: PCA. Unsigned 1-byte integer. |
7 | som_pcb_revision | PHYTEC SOM PCB revision. Unsigned 1-byte integer. |
8-13 | mac | MAC ID for primary ethernet port. Six unsigned 1-byte hex values. |
14 | ksp | 0: No KSP, 1: KSP, 2: KSM. Unsigned 1-byte integer. |
15 | kspno | Number for KSP/KSM module. Unsigned 1-byte integer. |
16-26 | kit_opt | Set of kit options. For the AM572x, this is an 11-character ASCII string with no null termination. |
27-31 | reserved | Reserved bytes that may be utilized by customers or by PHYTEC in a newer PHYTEC EEPROM API version. |
32 | bs | The number of bits set in all of the preceding bytes. Unsigned 1-byte integer. |
Note |
---|
If you would like to utilize the reserved space for your own identification purposes, feel free to do so but be aware that the PHYTEC EEPROM Layout API may change in the future. Additionally, the PHYTEC EEPROM Flashtool will need to be modified to accommodate the reading, writing, and display of this new data. |
...
In the above examples, the read, display, and write commands all look to the configuration file specified by the SOM argument or the first seven characters of the BOM argument. This configuration file is PCM-057.ini for the above examples because of the given arguments. This configuration file may be edited to suit your needs, or a new configuration file may be created by referring to theConfiguration Files Format section and then used by modifying the example commands.
...