Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Hardware implementations of the ConfigID
{{AppliesToAxel}}
{{AppliesToAxelLite}}
{{AppliesToAXELULite}}
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}
=== ConfigID ===
'''ConfigID''' is a new feature of DAVE Embedded Systems products. It's Its main purpose is '''providing an automatic mechanism for the identification of the product model and configuration.'''
With ConfigID, we aim at:
An additional attribute is '''UniqueID''', which is a read-only code which univocally identifies a single product and is used for traceability.
{{ImportantMessage|text=It is worth remembering that ConfigID and UniqueID are independent from [[Product_serial_number|product serial number]].}}
== Customer's action ==
** values are reported accordingly with the specific product table
== Hardware implementation implementations of the ConfigID ==
The following paragraphs briefly describe the available solution solutions for storing the ConfigID.
=== OTP on the SOC ===
Some SOCs provides programmable OTPs (eg. for security, mac MAC address, boot modes, etc). Usually , some of these are general purpose registers and can be managed by the user.
This is the ideal implementation, because:
* ConfigID is stored in the most important component of the SOM
* the component that hosts the ConfigID is NOT optional
* 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.
=== OTP 1-wire memory ===
This implementation requires a NOR flash connected to the SPI bus of the SOC.
== DAVEEmbedded Systems's Hardware hardware implementation ==
DAVE's SOCs implement the ConfigID feature depending on hardware Capabilities of the SOCs. The following list shows the priority used for its implementation:
</pre>
For accesing accessing these information on Linux <code>procfs</code>, the device tree must be modified (using u-boot '''fdt''' command): for example:
<pre>
It is possible to read the ConfigID/UniqueID via <code>procfs</code>; for example:
<pre>
root@axel-lite:~# cat /proc/device-tree/som/configid && echo
00000003
root@axel-lite:~# cat /proc/device-tree/som/uniqueid && echo
df646299:0b0579d4
root@axel-lite:~#
</pre>
Legacy device tree, has a sightly different <code>procfs</code> structure:
<pre>
