Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add humility tooling to erase SP and RoT

Aperta
  • Qualcosa non va?
#742 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli

Direzione di ricerca

The issue asks for a humility erase subcommand that mirrors the existing humility flash, so start by reading how the flash command is implemented and how it reaches the target over the probe. Work out how to erase the SP and RoT flash, then decide what scope the command should have. Done means a new command can return a board to an unprogrammed state, and the maintainers have agreed on the erase semantics.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Over the last year, I've encountered three situations where it would have been nice to have humility tooling to erase RoTs and SPs and return boards to an unprogrammed state. We have humility flash, why not humility erase? Here are three examples where this would have come in handy:

Example 1: When troubleshooting mfg-troubleshooting #136, I needed a way to make sure the RoT stopped measuring the SP because I was going to cut the signal in the MCU-Link cable that tells the RoT that a programmer is attached to the SP's SWD interface. There is probably an in-band way to tell the RoT "hey, please stop measuring", but it would have been great to humility erase the RoT so it never measures anything again. Ever.

Example 2: Sometimes, I have to troubleshoot hardware bugs that occur before the SP configures itself. To do this, we have an extremely tight window during A2 sequencing to inspect stuff...or we need an board where the SP has never been flashed so we can take our time setting up triggers, etc. Those are rare. It would be extremely useful to have something like an humility erase command that would blow away the SP image.

Example 3: People occasionally need to program hardware before we have an official manufacturing flow for said hardware. I usually try to write instructions for how to do this, because every board is a little different, and as Oxide has grown, we have engineers who may never have programmed hardware manually before. When I write work instructions, I'd like the ability to test them and make sure I have all the steps correct. The work instructions usually assume you start with an unprogrammed board...and I don't have a way to make a board unprogrammed again.

Lingua principale
Rust
Stelle
589
Fork
66
Merge medio
1g 14h
PR unite (30g)
10

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di oxidecomputer/humility

Tutte le issue di oxidecomputer/humility

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.