Firmware
Revision changes in the code
When the hardware changes revision, firmware should know exactly what changed, without archaeology in email threads.
How you work it in Colleag
- 1
Ask what differs between rev B and rev C.
- 2
The colleague compares the revisions' documentation.
- 3
The answer lists affected signals, registers and drivers.
- 4
Adapt the code before the new boards arrive.
A worked example
“What changed in pin mapping and registers between rev B and rev C of the X200 main board?”
A list of changed pins, register addresses and the drivers affected, with the document versions the comparison was built on.
Screenshot from Colleag. The example uses invented figures.
The material
- The revisions' design documents
- Pin mapping per revision
- The change history in the archive
You approve
Everything the colleague produces is a proposal with sources. Nothing is published, sent or saved to the archive without a human approving it, and every figure traces to its material.
Curious what it feels like?
We run pilot programs with a few manufacturing companies at a time. Tell us about your business and we will show what the colleagues can do with your documents and your data.