Difference between revisions of "DESK-MP1-L/General/ConfigID"

From DAVE Developer's Wiki
Jump to: navigation, search
Line 39: Line 39:
 
Generally speaking:
 
Generally speaking:
  
*''SOM ConfigID'' is used to identify the configuration of the basic features of the SOM
+
*''SOM ConfigID'' is used to identify the configuration of the basic features of the SOM, it is stored in the OTPs on the SOC.
*''CB ConfigID'' is used to identify the peripherals and the I/O interfaces.
+
*''CB ConfigID'' is used to identify the peripherals and the I/O interfaces, it is stored in an external one-wire eeprom memory present in the carrier board.
  
 
----
 
----
  
 
[[Category:ETRA]]
 
[[Category:ETRA]]

Revision as of 13:01, 1 August 2023

History
ID# Issue Date Notes
X.Y.Z 01/08/2023 DESK-MP1-L-1.0.0 release


ConfigID[edit | edit source]

This article describes how the ConfigID is implemented in the products supported by the DESK-MP1-L Linux Kit.

ETRA[edit | edit source]

As ETRA is a system-on-module (SOM), the typical mechanism described here is used.

Moreover, a system is composed of the combination of a SOM and a carrier board. In this case, two ConfigIDs are used to identify the actual board configuration like it was a SOM+carrier board system.

For the sake of simplicity, the first ConfigID is denoted as SOM ConfigID, while the second one is denoted as CB ConfigID:

...
SOM ConfigID#: 00000001
SOM UniqueID#: 39303435:33385105:001e0024
CB ConfigID#: 00000001
CB UniqueID#: 0d000035:c4a4762d
Board: ETRA on SBC
...

Generally speaking:

  • SOM ConfigID is used to identify the configuration of the basic features of the SOM, it is stored in the OTPs on the SOC.
  • CB ConfigID is used to identify the peripherals and the I/O interfaces, it is stored in an external one-wire eeprom memory present in the carrier board.