Skip to main content

Creating firmware

This guide describes how to create firmware.

To learn more about Peridio firmware in general, see the firmware reference.

Prerequisites​

In order to create a firmware it must be associated with a preexisting product. To learn how to create a product, see the creating products guide.

fwup archive creation​

Create a dummy asset​

echo "russet" > tuber.txt

Create a fwup conf​

Create fwup.conf containing:

meta-architecture = "arm"
meta-misc = "{\"foo\":\"bar\",\"baz\":12}"
meta-platform = "Jetson Nano"
meta-product = "Smart Potato"
meta-vcs-identifier = "23758867219c8d84c8363316e6dd2f9fd7ae3049"
meta-version = "1.0.0"

file-resource tuber.txt {
  host-path = "tuber.txt"
}

Create a fwup archive​

fwup \
  -c \
  -f fwup.conf \
  -o demo.fw

Sign the fwup archive​

See signing keys.

fwup \
  -S \
  -s fwup-key.priv \
  -i demo.fw \
  -o signed-demo.fw

Verify the fwup archive is signed​

fwup \
  -m \
  -p fwup-key.pub \
  -i signed-demo.fw

A failure would print an error like:

fwup: Firmware archive's meta.conf fails digital signature verification.

Submission to Peridio​

Web Console​

See the Peridio Web Console.

CLI​

peridio firmwares create \
  --firmware-path signed-demo.fw \
  --product-name "Smart Potato"

API​

Use the Peridio Admin API create a firmware endpoint.