53
•
•
•
•
•
Resetting a Timestamp on Device
To reset the timestamp that was set on the device, run:
# mstflint -d /
41
:
00.0
/mt4115_pciconf0 timestamp reset
Resetting the timestamp on device causes invalidation of both “Current timestamp” and
“Next timestamp” fields.
Setting a Timestamp on Device
In case it is not possible to modify the firmware image, it is possible to set the timestamp
directly on the device by specifying the timestamp and firmware version tied to it.
# mstflint -d /
41
:
00.0
/mt4115_pciconf0 timestamp set <UTC time> <Firmware version>
Querying a Timestamp on Device
To view the timestamp that was set on the device, run:
# mstflint -d /
41
:
00.0
/mt4115_pciconf0 timestamp query
Current timestamp : N/A. No valid timestamp found
Next timestamp :
2015
-
12
-21T10:
58
:23Z
12.15
.
0005
“Current timestamp” represents the current running firmware timestamp. If N/A is visible,
then the timestamp entry is invalid (example: first use of the feature or after resetting the
timestamp).
“Next timestamp” represents the next firmware that is allowed to be burnt on the HCA.
Updating the “Next timestamp” requires an equal or newer timestamp to be provided.
Resetting a Timestamp on Device
To reset the timestamp that were set on the device, run:
# mstflint -d
41
:
00.0
timestamp reset
Resetting the timestamp on device causes invalidation of both “Current timestamp” and
“Next timestamp” fields.
Important Notes
Please note the following:
If a firmware image contains a timestamp, the burning tool will automatically attempt to set
it on the device. If the operation succeeds, the firmware will be burnt.
If a timestamp was only set on the device, the burning tool will prevent the burning of any
firmware version different than the one set in the timestamp set operation.
Lack of timestamp in both image and device will cause no checks to be performed.
