Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add humility tooling to erase SP and RoT

Abierto
  • ¿Algo no está bien?
#742 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
587
Forks
64
Merge medio
2 d 1 h
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oxidecomputer/humility

Todos los issues de oxidecomputer/humility

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.