Configuration control of Programmable hardware
Configuration control of Programmable hardware
(OP)
I believe I know the answer to my issue but I was curious if there are any other ideas...
We Design camera systems and the Circuit card assemblies within. I usually have put the software PN in the CCA bom but I am beginning to realize I may want to create one more BOM level thus separating the "hardware" from the Software, The next level BOM would contain the CCA BOM and any SW PNs- "A programmed CCA" BOM. This way the boards can be built to one number and as SW functions change the new "programmed" CCA BOM can be created (dash no.) with different SW PNs, no need to change CCA (hardware) PN....
-Sometimes there are several programmable IC's.
-The Assemblies can be re-programmed at any time.
uuugh.
Any one with experience with this issue?
RTaylor
We Design camera systems and the Circuit card assemblies within. I usually have put the software PN in the CCA bom but I am beginning to realize I may want to create one more BOM level thus separating the "hardware" from the Software, The next level BOM would contain the CCA BOM and any SW PNs- "A programmed CCA" BOM. This way the boards can be built to one number and as SW functions change the new "programmed" CCA BOM can be created (dash no.) with different SW PNs, no need to change CCA (hardware) PN....
-Sometimes there are several programmable IC's.
-The Assemblies can be re-programmed at any time.
uuugh.
Any one with experience with this issue?
RTaylor
RE: Configuration control of Programmable hardware
If you have on physical CCA that you then put different firmware on to create different part numbers then having separate levels and maybe using - numbers sounds a reasonable approach.
KENAT,
Have you reminded yourself of FAQ731-376: Eng-Tips.com Forum Policies recently, or taken a look at posting policies: http://eng-tips.com/market.cfm?
What is Engineering anyway: FAQ1088-1484: In layman terms, what is "engineering"?