Per a conversation with @adamlouis earlier, manufacturing would really like it if humility could use reference designators ("refdes") when referring to components on a board. These designators are typically used to refer to a component when additional testing or rework is necessary, and the mfg folks are currently having to do some unpleasant things like maintaining their own tables of I2C addr/mux pairs to refdes, which I wish they didn't have to do.
Hubris and its build system already know the refdes of most components, since they are used to refer to them in the IPCC and MGS inventories. The app.toml has a field for annotating a component with its refdes. So, humility ought to be using this information as well.
I've started out by making the code for parsing a Hubris config from an archive or core also look at the refdes fields in the TOML, and print them in humility manifest. Once that's done, I think we will want to make at least the humility validate command and the open-pin check also include refdes in their output. There are probably other places where we should include this as well (sensors? pmbus? anything else?)
Per a conversation with @adamlouis earlier, manufacturing would really like it if
humilitycould use reference designators ("refdes") when referring to components on a board. These designators are typically used to refer to a component when additional testing or rework is necessary, and the mfg folks are currently having to do some unpleasant things like maintaining their own tables of I2C addr/mux pairs to refdes, which I wish they didn't have to do.Hubris and its build system already know the refdes of most components, since they are used to refer to them in the IPCC and MGS inventories. The app.toml has a field for annotating a component with its refdes. So,
humilityought to be using this information as well.I've started out by making the code for parsing a Hubris config from an archive or core also look at the refdes fields in the TOML, and print them in
humility manifest. Once that's done, I think we will want to make at least thehumility validatecommand and the open-pin check also include refdes in their output. There are probably other places where we should include this as well (sensors?pmbus? anything else?)