Difference between revisions of "ConfigID management (BELK/BXELK)"
| Line 21: | Line 21: | ||
''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. | ''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. | ||
| − | + | General information about ''ConfigID'' are provided [[ConfigID_and_UniqueID|here]]. The following sections details some Bora/BoraX specific information. | |
| − | + | ==ConfigID hardware implementation on Bora/BoraX== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==ConfigID hardware implementation on Bora== | ||
BORA uses the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32) | BORA uses the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32) | ||
| − | ==ConfigID software implementation on Bora== | + | ==ConfigID software implementation on Bora/BoraX== |
U-Boot integrates the software routines for reading and displaying the ConfigID. Hereunder an example of SOM ConfigID at startup: | U-Boot integrates the software routines for reading and displaying the ConfigID. Hereunder an example of SOM ConfigID at startup: | ||
<pre> | <pre> | ||
Revision as of 10:50, 4 November 2015
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
Contents
History[edit | edit source]
| Version | Date | BELK version | Notes |
|---|---|---|---|
| 1.0.0 | November 2015 | 3.0.0 | First release |
Introduction[edit | edit source]
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.
General information about ConfigID are provided here. The following sections details some Bora/BoraX specific information.
ConfigID hardware implementation on Bora/BoraX[edit | edit source]
BORA uses the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32)
ConfigID software implementation on Bora/BoraX[edit | edit source]
U-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: BORA I2C: ready DRAM: ECC disabled 1 GiB NAND: 1024 MiB MMC: zynq_sdhci: 0 SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB In: serial Out: serial Err: serial SOM ConfigID#: 00000002 SOM UniqueID#: fffffefc:fffffefc CB ConfigID#: 00000001 CB UniqueID#: a600000f:24188b2d Net: Gem.e000b000 zynq-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_fixupfdt
loadfdt=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_fixupfdt
Gem.e000b000 Waiting for PHY auto negotiation to complete....... done
Using Gem.e000b000 device
TFTP from server 192.168.0.13; our IP address is 192.168.0.77
Filename 'bora/bora.dtb.as'.
Load address: 0x2000000
Loading: T ##
1000 Bytes/s
done
Bytes transferred = 10019 (2723 hex)
FDT: property som_configid FDT: override 'som_configid' with '00000002'
FDT: property cb_configid match
FDT: 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:fffffefc df646299:0b0579d4 root@axel-lite:~#
