Man page - nvme-rpmb(1)
Packages contains this manual
- nvme-fdp-set-events(1)
- nvme-sndk-get-error-recovery-log(1)
- nvme-zns-reset-zone(1)
- nvme-micron-pcie-stats(1)
- nvme-predictable-lat-log(1)
- nvme-netapp-ontapdevices(1)
- nvme-fid-support-effects-log(1)
- nvme-intel-lat-stats(1)
- nvme-cmdset-ind-id-ns(1)
- nvme-get-lba-status(1)
- nvme-ocp-set-dssd-async-event-config(1)
- nvme-wdc-vs-cloud-log(1)
- nvme-transcend-healthvalue(1)
- nvme-toshiba-vs-smart-add-log(1)
- nvme-gen-hostnqn(1)
- nvme-sndk-vs-smart-add-log(1)
- nvme-wdc-vs-fw-activate-history(1)
- nvme-sndk-set-latency-monitor-feature(1)
- nvme-sndk-vs-device-waf(1)
- nvme-solidigm-temp-stats(1)
- nvme-get-log(1)
- nvme-list-endgrp(1)
- nvme-disconnect-all(1)
- nvme-resv-notif-log(1)
- nvme-wdc-id-ctrl(1)
- nvme-id-ctrl(1)
- nvme-wdc-get-drive-status(1)
- nvme-error-log(1)
- nvme-huawei-id-ctrl(1)
- nvme-toshiba-vs-internal-log(1)
- nvme-sndk-clear-assert-dump(1)
- nvme-nvm-id-ctrl(1)
- nvme-ocp-get-plp-health-check-interval(1)
- nvme-sndk-vs-drive-info(1)
- nvme-sndk-get-unsupported-reqs-log(1)
- nvme-fdp-update(1)
- nvme-dsm(1)
- nvme-virtium-show-identify(1)
- nvme-sed-initialize(1)
- nvme-wdc-capabilities(1)
- nvme-solidigm-parse-telemetry-log(1)
- nvme-wdc-vs-internal-log(1)
- nvme-wdc-drive-resize(1)
- nvme-ocp-device-capability-log(1)
- nvme-sndk-vs-nand-stats(1)
- nvme-micron-nand-stats(1)
- nvme-self-test-log(1)
- nvme-ocp-set-dssd-power-state-feature(1)
- nvme-sndk-vs-hw-rev-log(1)
- nvme-connect-all(1)
- nvme-micron-temperature-stats(1)
- nvme-seagate-plugin-version(1)
- nvme-wdc-enc-get-log(1)
- nvme-wdc-vs-error-reason-identifier(1)
- nvme-attach-ns(1)
- nvme-ns-rescan(1)
- nvme-sndk-capabilities(1)
- nvme-sndk-get-dev-capabilities-log(1)
- nvme-sndk-get-drive-status(1)
- nvme-sed-discover(1)
- nvme-solidigm-market-log(1)
- nvme-ns-descs(1)
- nvme-solidigm-latency-tracking-log(1)
- nvme-zns-offline-zone(1)
- nvme-persistent-event-log(1)
- nvme-sed-lock(1)
- nvme-nvme-mi-recv(1)
- nvme-wdc-get-error-recovery-log(1)
- nvme-telemetry-log(1)
- nvme-sanitize-log(1)
- nvme-sndk-namespace-resize(1)
- nvme-intel-id-ctrl(1)
- nvme-wdc-vs-nand-stats(1)
- nvme-id-nvmset(1)
- nvme-wdc-vs-hw-rev-log(1)
- nvme-wdc-clear-assert-dump(1)
- nvme-resv-report(1)
- nvme-netapp-smdevices(1)
- nvme-zns-close-zone(1)
- nvme-effects-log(1)
- nvme-ocp-error-recovery-log(1)
- nvme-io-passthru(1)
- nvme-device-self-test(1)
- nvme-resv-register(1)
- nvme-micron-clear-pcie-errors(1)
- nvme-set-feature(1)
- nvme-ocp-clear-pcie-correctable-error-counters(1)
- nvme-fdp-feature(1)
- nvme-ocp-set-telemetry-profile(1)
- nvme-huawei-list(1)
- nvme-dapustor-smart-log-add(1)
- nvme-resv-release(1)
- nvme-list(1)
- nvme-ocp-eol-plp-failure-mode(1)
- nvme-flush(1)
- nvme-wdc-purge(1)
- nvme-micron-selective-download(1)
- nvme-wdc-vs-device-waf(1)
- nvme-fdp-events(1)
- nvme-seagate-get-host-tele(1)
- nvme-wdc-namespace-resize(1)
- nvme-show-hostnqn(1)
- nvme-sed-password(1)
- nvme(1)
- nvme-get-ns-id(1)
- nvme-ocp-set-plp-health-check-interval(1)
- nvme-wdc-get-unsupported-reqs-log(1)
- nvme-sndk-vs-temperature-stats(1)
- nvme-detach-ns(1)
- nvme-dir-send(1)
- nvme-pred-lat-event-agg-log(1)
- nvme-seagate-vs-smart-add-log(1)
- nvme-io-mgmt-recv(1)
- nvme-id-domain(1)
- nvme-discover(1)
- nvme-seagate-vs-internal-log(1)
- nvme-fdp-usage(1)
- nvme-write-zeroes(1)
- nvme-seagate-vs-temperature-stats(1)
- nvme-seagate-get-ctrl-tele(1)
- nvme-write-uncor(1)
- nvme-solidigm-id-ctrl(1)
- nvme-seagate-vs-log-page-sup(1)
- nvme-ocp-get-dssd-power-state-feature(1)
- nvme-solidigm-vs-smart-add-log(1)
- nvme-show-regs(1)
- nvme-solidigm-workload-tracker(1)
- nvme-fdp-stats(1)
- nvme-compare(1)
- nvme-dim(1)
- nvme-wdc-clear-fw-activate-history(1)
- nvme-capacity-mgmt(1)
- nvme-set-property(1)
- nvme-fw-download(1)
- nvme-solidigm-vs-internal-log(1)
- nvme-sndk-log-page-directory(1)
- nvme-get-feature(1)
- nvme-sndk-clear-fw-activate-history(1)
- nvme-sed-unlock(1)
- nvme-io-mgmt-send(1)
- nvme-ocp-get-dssd-async-event-config(1)
- nvme-seagate-help(1)
- nvme-wdc-vs-temperature-stats(1)
- nvme-toshiba-clear-pcie-correctable-errors(1)
- nvme-show-topology(1)
- nvme-wdc-vs-smart-add-log(1)
- nvme-wdc-vs-telemetry-controller-option(1)
- nvme-changed-ns-list-log(1)
- nvme-seagate-clear-fw-activate-history(1)
- nvme-wdc-clear-pcie-correctable-errors(1)
- nvme-id-iocs(1)
- nvme-zns-zone-mgmt-send(1)
- nvme-list-ctrl(1)
- nvme-sndk-vs-telemetry-controller-option(1)
- nvme-endurance-event-agg-log(1)
- nvme-sndk-vs-error-reason-identifier(1)
- nvme-delete-ns(1)
- nvme-sndk-drive-resize(1)
- nvme-ocp-clear-fw-activate-history(1)
- nvme-zns-report-zones(1)
- nvme-tls-key(1)
- nvme-reset(1)
- nvme-fw-log(1)
- nvme-format(1)
- nvme-wdc-drive-essentials(1)
- nvme-list-ns(1)
- nvme-wdc-drive-log(1)
- nvme-sndk-vs-fw-activate-history(1)
- nvme-zns-zone-append(1)
- nvme-zns-open-zone(1)
- nvme-ocp-unsupported-reqs-log(1)
- nvme-transcend-badblock(1)
- nvme-write(1)
- nvme-virtium-save-smart-to-vtview-log(1)
- nvme-get-property(1)
- nvme-solidigm-clear-pcie-correctable-errors(1)
- nvme-security-send(1)
- nvme-rpmb(1)
- nvme-supported-log-pages(1)
- nvme-sndk-get-latency-monitor-log(1)
- nvme-zns-changed-zone-list(1)
- nvme-solidigm-log-page-directory(1)
- nvme-lockdown(1)
- nvme-solidigm-clear-fw-activate-history(1)
- nvme-solidigm-vs-drive-info(1)
- nvme-zns-id-ctrl(1)
- nvme-inspur-nvme-vendor-log(1)
- nvme-seagate-version(1)
- nvme-solidigm-garbage-collect-log(1)
- nvme-ocp-internal-log(1)
- nvme-seagate-vs-fw-activate-history(1)
- nvme-fdp-configs(1)
- nvme-zns-zone-mgmt-recv(1)
- nvme-seagate-vs-pcie-stats(1)
- nvme-help(1)
- nvme-wdc-get-crash-dump(1)
- nvme-verify(1)
- nvme-micron-internal-log(1)
- nvme-ana-log(1)
- nvme-endurance-log(1)
- nvme-smart-log(1)
- nvme-sndk-vs-internal-log(1)
- nvme-sndk-vs-cloud-log(1)
- nvme-wdc-get-latency-monitor-log(1)
- nvme-fdp-status(1)
- nvme-wdc-vs-drive-info(1)
- nvme-seagate-clear-pcie-correctable-errors(1)
- nvme-intel-temp-stats(1)
- nvme-wdc-get-dev-capabilities-log(1)
- nvme-admin-passthru(1)
- nvme-nvme-mi-send(1)
- nvme-wdc-cap-diag(1)
- nvme-sed-revert(1)
- nvme-solidigm-vs-fw-activate-history(1)
- nvme-mi-cmd-support-effects-log(1)
- nvme-intel-internal-log(1)
- nvme-zns-finish-zone(1)
- nvme-sanitize(1)
- nvme-wdc-purge-monitor(1)
- nvme-ocp-latency-monitor-log(1)
- nvme-ocp-smart-add-log(1)
- nvme-security-recv(1)
- nvme-intel-smart-log-add(1)
- nvme-solidigm-smart-log-add(1)
- nvme-intel-market-name(1)
- nvme-wdc-get-pfail-dump(1)
- nvme-disconnect(1)
- nvme-id-ns(1)
- nvme-copy(1)
- nvme-primary-ctrl-caps(1)
- nvme-sndk-clear-pcie-correctable-errors(1)
- nvme-dera-stat(1)
- nvme-subsystem-reset(1)
- nvme-boot-part-log(1)
- nvme-fw-commit(1)
- nvme-connect(1)
- nvme-micron-smart-add-log(1)
- nvme-zns-id-ns(1)
- nvme-wdc-log-page-directory(1)
- nvme-resv-acquire(1)
- nvme-dir-receive(1)
- nvme-sndk-vs-pcie-stats(1)
- nvme-list-subsys(1)
- nvme-read(1)
- nvme-create-ns(1)
- nvme-ocp-telemetry-string-log-page(1)
- nvme-zns-set-zone-desc(1)
- nvme-lba-status-log(1)
apt-get install nvme-cli
Manual
NVME-RPMB
NAMESYNOPSIS
DESCRIPTION
OPTIONS
EXAMPLES
NVME
NAME
nvme-rpmb - Send RPMB commands to an NVMe device
SYNOPSIS
nvme rpmb
<device> [--cmd=<command> | -c <command>]
[--msgfile=<data-file> | -f <data-file>]
[--keyfile=<key-file> | -g <key-file>]
[--key=<key> | -k <key>] [--msg=<data> |
-d <data>]
[--address=<offset> | -o <offset>]
[--blocks=<512 byte sectors> | -b <sectors>]
[--target=<target-id> | -t <id>]
[--output-format=<fmt> | -o <fmt>] [--verbose |
-v]
DESCRIPTION
For the NVMe device given, send an nvme rpmb command and provide the results.
The <device> parameter is mandatory and NVMe character device (ex: /dev/nvme0) must be specified. If the given device supports RPMB targets, command given with --cmd or -c option shall be sent to the controller. If given NVMe device doesnβt support RPMB targets, a message indicating the same shall be printed along with controller register values related RPMB.
OPTIONS
-c <command>, --cmd=<command>
RPMB command to be sent to the device. It can be one of the following
info - print
information regarding supported RPMB targets and
access and total sizes. No further arguments are
required
program-key -
program 'key' specified with -k option or key read from
file specified with --keyfile option to the specified
RPMB target given with --target or -t options. As per
spec, this is one time action which can't be undone.
read-counter -
Read 'write counter' of specified RPMB target. The
counter value read is printed onto STDOUT
read-config -
Read 512 bytes of device configuration block data of
specified RPMB target of the NVMe device. The data read
is written to input file specified with --msgfile or -f
option.
write-config - Write 512 byes of device configuration block
data
from file specified by --msgfile or -f options to the
RPMB target specified with --target or -t options.
read-data -
Supports authenticated data reading from specified
RPMB target (--target or -t option) at given offset
specified with --address or -o option, using key
specified using --keyfile or -k options. --blocks or
-o option should be given to read the amount of data
to be read in 512 byte blocks.
write-data -
Supports authenticated data writing to specified RPMB
target (--target or -t option) at given offset
specified with --address or -o option, using key
specified using --keyfile or -k options. --blocks or
-o option should be given to indicate amount of data
to be written in 512 byte blocks.
For data
transfer (read/write) commands, if the specified size is not
within the total size supported by a target, the request is
failed
nvme-rpmb without sending it to device. RPMB target 0 is
used as the
default target if --target or -t is not specified. 0x0 is
used as the
default address if no -address or -o option is
specified,
-t <target>, --target=<target>
RPMB target id. This should be one of the supported RPMB targets as reported by info command. If nothing is given, default of 0 is used as RPMB target.
-k <key>, --key=<key>, -g <key-file>, --keyfile=<key-file>
Authentication key to be used for read/write commands. This should have been already programmed by program-key command for given target. Key can be specified on command line using --key or -k options. Key can also be specified using file argument specified with --keyfile or -g options.
-f <data-file>, --msgfile=<data-file>
Name of the file to be used for data transfer commands (read or write). For read command, if an existing file is specified, it will be appended.
-d <data>, --msg=<data>
These options provide the data on the command line itself.
-o <offset>, --address=<offset>
The address (in 512 byte sector offset from 0) to be used for data transfer commands (read or write) for a specified RPMB target.
-b, --blocks=<sectors>
The size in 512 byte sectors to be used for data transfer commands (read or write) for a specified RPMB target.
-o <fmt>, --output-format=<fmt>
Set the reporting format to normal , json or binary . Only one output format can be used at a time.
-v, --verbose
Increase the information detail in the output.
EXAMPLES
β’ Print RPMB support information of an NVMe device
# nvme rpmb /dev/nvme0 --cmd=info
β’ Program SecretKey as authentication key for target 1
# nvme rpmb /dev/nvme0 --cmd=program-key -key='SecretKey' --target=1
β’ Read current write counter of RPMB target 0
# nvme rpmb /dev/nvme0 --cmd=read-counter --target=0
β’ Read configuration data block of target 2 into config.bin file
# nvme rpmb /dev/nvme0 --cmd=read-config --target=2 -f config.bin
β’ Write 200 blocks of (512 bytes) from input.bin onto target 0
# nvme rpmb /dev/nvme0 -c write-data -t 0 -f input.bin -b 200 -k 'SecretKey'
β’ Read 200 blocks of (512 bytes) from target 2, at offset 0x100 and save the
β’ data onto output.bin
# nvme rpmb /dev/nvme0 -c read-data -t 2 -f out.bin -b 200 -o 0x100
NVME
Part of the nvme-user suite