To Next Page

To Previous Page

#mstconfig xml2bin /tmp/template.xml /tmp/confs.bin

Saving output...

Done!

# hexdump -C /tmp/confs.bin

00000000 80 00 00 00 |....|

00000004

mstconfig create_conf Command

The create_conf command assists in creating an NV configuration file that can be used forLifeCycle

and Secure Firmware Updates purposes. The flow for creating a configuration file isthe same as the

flow for xml2bin. The user must provide the command with an XML filecontaining the required

configurations and their values. The command can sign the configurationfile, if the user provides a

private key and UUID. The sign result will be appended to the end ofthe configuration file. If no private

key and UUID are provided, the tool will compute anSHA256 digest and append it to the file. The

generated signature will be used by the firmware forauthentication purposes.

Example:

#mstconfig create_conf --private_key privatekey.pem --key_uuid

"29ee36ee-13b7-11e7-83de-0cc47a6d39d2" /tmp/template.xml /tmp/nvconf.bin

Saving output...

Done!

mstconfig apply Command

The apply command can be used to apply the NV configurations files to the firmware using theapply

command.Only Firmware that supports applying configurations files can be used.

Example:

#mstconfig -d 41:00.0 apply /tmp/nvconf.bin

Applying...

Done!

Currently the only supported NV configurations types are CS tokens, Debug tokens and MLNX

ID which are used for Secure Firmware Updates. Additionally, it supports two RSA keys of 2048

or 4096 bits length.



The NV configurations files must have the applicable_to configuration.



Nvidia MSTFLINT User Manual

Other manuals for Nvidia MSTFLINT