Changes

{{InfoBoxBottom}}

=== ConfigID ===

{{ImportantMessage|text=It is worth remembering that ConfigID and UniqueID are independent from [[Product_serial_number|product serial number]].}}

DAVE Embedded Systems <u>recommends to be up-to-date with Official SOM's BSPs</u> for taking advantages of ConfigID/UniqueId features: this is the '''only''' required action.

* '''UniqueID advantage''': to trace univocally each individual SOMs and, in turn, all the on-the-field equipments

ConfigID is a N-bit (typically N>8) signed integer, that can have the following values:

** values are reported accordingly with the specific product table

The following paragraphs briefly describe the available solutions for storing the ConfigID.

Some SOCs provides programmable OTPs (eg. for security, MAC address, boot modes, etc). Usually, some of these are general purpose registers and can be managed by the user.

* typically, a very selective lock can be forced. In general, for reliability and/or security reasons, OTP areas used to store ConfigIDs may be locked during the manufacturing process.

This implementation requires a 1-wire memory chip.

This implementation requires connecting an EEPROM to an I2C bus of the SOC. Moreover, routing a write protect pin to the SOM connector is required.

This implementation requires a NOR flash connected to the SPI bus of the SOC.

DAVE's SOCs implement the ConfigID feature depending on hardware Capabilities of the SOCs. The following list shows the priority used for its implementation:

## example: latest XELK, DIVELK, BELK Carrier Boards implement CB ConfigID using the onboard 1-wire device (DS2431)

u-boot integrates the software routines for reading and displaying the ConfigID: hereunder an example of SOM ConfigID at startup:

</pre>

It is possible to read the ConfigID/UniqueID via <code>procfs</code>; for example:

root@axel-lite:~#

</pre>