I was wondering how people handle a firmware change in the manufacturing process. One thing we are considering is issuing a new part number for every firmware release. The number may be a "Rev B" or some extension of a base part number, but it would be unique for each firmware release. Then, when a unit is built, it must use a certain "part number" that is really a firmware release, probably in the form of some FLASH programming device, or at least a file that contains the memory image for a micro-controller.
A problem comes into play if there are already manufactured units ready to ship when a new firmware release is issued. I would think the micro-controller, or EPROMs, or whatever form the firmware is released in would have a sticker on it with maybe the part number? Or should the sticker have the firmware revision number, or both?
We also thought of forgetting about the part number scheme and just having some sort of list or database with the "correct" firmware release listed. The advantage there would be special runs of an older firmware release (something we have to do at times) could easily be made without worrying about using a part number that was obsoleted by a newer one.
I know the best way can cepend on the manufacturing/part number/ECO system in use. But I am sure others have been down this road before and may have some good suggestions. I am all ears and thankful for those that may wish to reply.
Lou