Updating Customer Data into BCT

Update customer data, such as skuinfo and others, using the --customer-data option provided with the create_bsp_images.py, flash_bsp_images.py, or bootburn.py script.

Signed Customer Data

Signed customer data can only be updated at creation type as a key is needed to sign the customer data. The source of truth for signed customer data is the host created Br Bct. The signed customer data is not merged with the target but is completely replace by the image from the host. As such, the specification of signed customer data is different from unsigned customer data. Both are specified in the board specific json.

"f_SignedCustomerData":"p3710_signed_customer_data.json"
"f_SignedCustomerDataSchema":"nv-customer-data-schema-orin-signed.json"

The default for f_SignedCustomerDataSchema is nv-customer-data-schema-orin-signed.json. There is no default for f_SignedCustomerData. If f_SignedCustomerData is unspecified then Signed customer data is initialized to zero. Absolute path can be used for f_SignedCustomerData and f_SignedCustomerDataSchema if the default locations for the files are not used. Signed Customer Data is not target unique data but product unique data and can be used to specify the Sku Info, Product Info and System Bom Info. Signed Customer data should be considered constants that all targets in a product line need.

Unsigned Customer Data

Unsigned customer data is target specific data. It can be specified at any time – creation or flashing. The unsigned customer data is updated using a read, modify and write process so that individual items can be updated.