Bureaucrats, dave_user, Administrators
8,154
edits
Changes
→DAVE Embedded Systems' hardware implementation
{{Applies To Diva}}
{{Applies To Bora}}
{{Applies To BoraLite}}
{{AppliesToAxel}}
{{AppliesToAxelLite}}
== Introduction ==
=== ConfigID ===
An additional attribute is '''UniqueID''', which is a read-only code which univocally identifies a single product and is used for traceability.
{{ImportantMessage|text=NXP (former FSL) guarantees It is worth remembering that processors UIDs to be unique over the whole iMX6 family, olders i.MX ConfigID and future i.MX products. This system was developed by FSL in early 2000 yearsUniqueID are independent from [[Product_serial_number|product serial number]].}}
== Customer's action ==
== Hardware 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 ===
## DIVA and BORA use the first 32bytes OTP block on NOR SPI to store ConfigID (and its CRC32), UniqueID (and its CRC32)
# I2C Eeprom
## example: DIVA family processor (AM335x) or BORA Lite processor (ZYNQ) implements ConfigID using I2C Eeprom when NOR SPI is not present (module boots from NAND or SD)## DIVA and BORA use the first 32bytes on I2C EPROM to store ConfigID (and its CRC32), UniqueID (and its CRC32)
# 1-wire
## example: latest XELK, DIVELK, BELK Carrier Boards implement CB ConfigID using the onboard 1-wire device (DS2431)
