This directory contains Build configuration JSON config and schema files and will be visited by module cros.factory.utils.config_utils
.
To add files, create the right JSON (config and schema) files in board overlay factory-board/files/py/config/
and install into system.
This is a sample config file for enabling separate registration code for custom label projects. While using this, ODM/OEM needs to:
{ "phaser360": { "laser": false, "dopefish": false }, "bobba360": { "gik360": false } }
Note:
phaser360
/bobba360
should be the model name of your device which could be get by #cros_config / name
in dut.dopefish
/gik360
is the custom-label-tag of the custom label device belongs to the model listed as the first level keys. The name could be get by #cros_config /identity custom-label-tag
in dut.
true
: the feature is enabled, which means ODM/OEM applied separate registration code bundle for the device, the software will check the registration code according to the custom label device name.
false
: the feature is disabled, which means ODM/OEM doesn’t apply separate registration code bundle for the device and will use the same registration code bundle as the model it belongs to, the software will check registration code according to the model name.
factory.par gooftool verify_vpd
will pass.