DESK-RZ-L/General/ConfigID

From DAVE Developer's Wiki
Jump to: navigation, search
History
Issue Date Notes
2025/12/16 DESK-RZ-L-1.x.x release



ConfigID[edit | edit source]

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

ZERO[edit | edit source]

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

System and ConfigID Overview[edit | edit source]

A system is defined by the combination of a System on Module (SOM) and a carrier board. To uniquely identify the actual hardware configuration, two distinct ConfigIDs are used, effectively describing the SOM + carrier board pair as a single system.

For clarity, the two identifiers are named as follows:

  • SOM ConfigID: identifies the SOM configuration
  • CB ConfigID: identifies the carrier board configuration

Example from the U-Boot boot log[edit | edit source]

...
SOM ConfigID#: 00000001
SOM UniqueID#: 00000000:00000000
CB ConfigID#: 00002003
CB UniqueID#: f2000041:21226b2d
...

Meaning of the ConfigIDs[edit | edit source]

In general:

  • SOM ConfigID Identifies the SOM variant and its base hardware features, including possible hardware revisions.
  • CB ConfigID Identifies the carrier board, defining the available peripherals and I/O interfaces.

ConfigIDs in U-Boot[edit | edit source]

During the U-Boot boot process, the following lines are particularly relevant:

  • SOM ConfigID#: for example 00000001
  • CB ConfigID#: for example 00002002

The SOM ConfigID is used to select the correct SOM-specific configuration.

The CB ConfigID is used to select the correct carrier-board-specific configuration, ensuring that the proper peripherals, pin multiplexing, and interfaces are enabled.

This separation allows the same SOM to be safely and correctly used with different carrier boards while preventing incorrect hardware initialization.

ConfigID & BOM Mapping[edit | edit source]

Identifying the SOM and Carrier Board and Their Capabilities[edit | edit source]

The BOM code is printed on the physical label of the board under consideration.

This code, together with the ConfigID, allows unambiguous identification of the System on Module (SOM), the Carrier Board, and the set of hardware features that are available.

SOM ConfigID[edit | edit source]

The following table shows the relationship between the SOM ConfigID, the corresponding BOM, and the SOM description.

ConfigID BOM Description
0x00000001 DSABA30000I1R SOM spin 1
Carrier Board (CB) ConfigID[edit | edit source]

The table below lists the supported Carrier Board configurations, identified by CB ConfigID and BOM.

ConfigID BOM Description
2000 EB23000xI1R Generic OSM SoM carrier board
2001 EB23010xI1R Routing for ZERO SoM – 9-axis motor demo
2002 EB23020xI1R Routing for ZERO SoM – full Linux support, no motor interface
2003 EB23030xI1R Routing for ZERO SoM – 6 motors only, remaining pins available for Linux peripherals

This mapping enables the bootloader and the operating system to automatically select the correct hardware configuration, preventing incorrect peripheral initialization and reducing the risk of hardware damage.