oxidecomputer / oxidecomputer/hubris

need basic RoT ID info via sprot

Open
#1,262 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3.6k
Forks
239
Avg merge
1d 12h
Merged PRs (30d)
23

Description

As part of our RFD 360 topo and inventory information and related docs around secure boot and more, we want to be able to grab the following information and make it available over sprot for the SP to share. See https://rfd.shared.oxide.computer/rfd/0360#_lpc55s69 for more information:

  • The 128-bit UUID at 0x0009_fc70 (§7.31.6 [lpc55s6x-ds])
  • The DEVICE_ID0 register (§4.5.88 [lpc55s6x-um])
  • The DIEID register (§4.5.89 [lpc55s6x-um])
  • The NMPA (NXP Manufacturing Programmed Area) metal revision at 0x9fc10 (§2.4 [rfd274])

In addition to that hardware information, we also want the following information about the NXP firmware:

  • ISP Bootloader Version (§2.3 [rfd274]).
  • ISP Target Version (§3.2 [rfd274]).
  • NMPA ROM patch ID that is present at address 0x9fc14 (§3.3 [rfd274]).

It's probably already present, but we want to make clear the software revisions that are available in the stage0 slot, the A slot, and B slot. I mention those, because it's most likely that we want to have a single sprot endpoint that can get us all this ID info.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with RFD 360, especially the LPC55S69 and RFD274 sections, and trace the existing sprot path for software revisions in the stage0, A, and B slots. Define the single sprot endpoint around the listed UUID, registers, metal revision, bootloader and target versions, and ROM patch ID, then verify that all requested values are exposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
embedded-iot, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.