TBD{{InfoBoxTop}}{{Applies To Bora}}{{Applies To BoraX}}{{InfoBoxBottom}} == History =={| class="wikitable" border="1"!Version!Date!BELK version!Notes|-|1.0.0|November 2015|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|3.0.0]]|First release|-|} ==Instructions==It is assumed that the development environment has been set up properly as described [[Build_system_(BELK)|here]]. ConfigID is a new feature of DAVE Embedded Systems products. It's main purpose is providing an automatic mechanism for the identification of the product model and configuration.With ConfigID, we aim at:completing the hardware configuration information that the software can't normally auto-detect (i.e. RAM chip version,...), implementing a dedicated reliable detect procedurewhen required, overriding the auto-detected hardware configuration informationWhen implemented, this mechanism allows for:initializing in the proper way the hardware platform, based on the specific features and parameters of the product, using a common software base (eg: a typical case is the SDRAM controller parameters, which must be configured by U-Boot depending on the particular memory chip, which can be different for the various SOM models)getting the complete hardware configuration (combining ConfigID with the information collectable at runtime) of a product deployed on the fieldIn simple words, model identification means the capability of reading a numerical code, stored in an available device (SOC's OTP , I2C EEPROM, 1-wire memories, protected NOR flash, etc.)There are two ConfigIDs:SOM ConfigID: which reflects the characteristics of the SOM (stored on the SOM itself)Carrier Board (CB) ConfigID: which reflects the characteristics of the carrier board that hosts the SOM (stored on the carrier board itself and read by the SOM at boot time)An additional attribute is UniqueID, which is a read-only code which univocally identifies a single product and is used for traceability.3.4.8.1 Customer's actionDAVE Embedded Systems recommends to be up-to-date with Official SOM's BSPs for taking advantages of ConfigID/UniqueId features: this is the only required action.ConfigID advantage: to allow U-Boot bootloader to be executed only with the correct configuration (if the U-Boot loaded is not the proper one, it may stop execution avoiding incorrect behaviour)UniqueID advantage: to trace univocally each individual SOMs and, in turn, all the on-the-field equipments3.4.8.2 ConfigID valuesConfigID is a N-bit (typically N>8) signed integer, that can have the following values:< 0: error-1: not initialized= 0: ConfigID legacyfor prototypes (ConfigID not yet defined) or for products manufactured before the introduction of the ConfigID feature> 0: valid ConfigIDvalues are reported accordingly with the specific product table3.4.8.3 ConfigID hardware implementation on BoraBORA uses the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32)3.4.8.4 ConfigID software implementation on BoraU-Boot integrates the software routines for reading and displaying the ConfigID. Hereunder an example of SOM ConfigID at startup:U-Boot 2014.07 (Jul 24 2015 - 14:30:55) [belk-2.2.0] Board: BORAI2C: readyDRAM: ECC disabled 1 GiBNAND: 1024 MiBMMC: zynq_sdhci: 0SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiBIn: serialOut: serialErr: serialSOM ConfigID#: 00000002SOM UniqueID#: fffffefc:fffffefcCB ConfigID#: 00000001CB UniqueID#: a600000f:24188b2dNet: Gem.e000b000zynq-uboot>For accesing these information on Linux procfs, the device tree must be modified (using u-boot fdt command): for example:zynq-uboot> print loadfdt configid_fixupfdtloadfdt=tftpboot ${fdtaddr} ${fdtfile}configid_fixupfdt=if configid checkfdt ${fdtaddr} som_configid ${som_configid#}; then if configid checkfdt ${fdtaddr} cb_configid ${cb_configid#}; then configid fdt_uniqueid ${fdtaddr}; fi; fi zynq-uboot> run loadfdt configid_fixupfdtGem.e000b000 Waiting for PHY auto negotiation to complete....... doneUsing Gem.e000b000 deviceTFTP from server 192.168.0.13; our IP address is 192.168.0.77Filename 'bora/bora.dtb.as'.Load address: 0x2000000Loading: T ## 1000 Bytes/sdoneBytes transferred = 10019 (2723 hex)FDT: property som_configid FDT: override 'som_configid' with '00000002'FDT: property cb_configid matchFDT: override 'som_uniqueid' with 'fffffefc:fffffefc'FDT: override 'cb_uniqueid' with 'a600000f:24188b2d'It is possible to read the ConfigID/UniqueID via procfs; for example:root@bora:~# for f in /proc/device-tree/*id*; do echo -n "$f: "; cat $f; echo; done/proc/device-tree/cb_configid: 00000001/proc/device-tree/cb_uniqueid: a600000f:24188b2d/proc/device-tree/som_configid: 00000002/proc/device-tree/som_uniqueid: fffffefc:fffffefcdf646299:0b0579d4root@axel-lite:~#