| US 7,562,345 B2 | ||
| Firmware management tool | ||
| Brian J. Bogdan, Succasunna, N.J. (US); Roger Ellis Doles, Jr., Licking, Ohio (US); Charles Francis Gullage, Chatham, N.J. (US); and James Baldwin Salisbury, Randolph, N.J. (US) | ||
| Assigned to Lucent Technologies, Inc., Murray Hill, N.J. (US) | ||
| Filed on Aug. 27, 2003, as Appl. No. 10/648,909. | ||
| Prior Publication US 2005/0050479 A1, Mar. 03, 2005 | ||
| Int. Cl. G06F 9/44 (2006.01) | ||
| U.S. Cl. 717—120 [717/101; 717/102; 717/103] | 18 Claims |
| 12. A method of managing a firmware development process, comprising:
saving a firmware source code and a firmware object code in a firmware file;
archiving the firmware file in an archive;
saving edits to the firmware file; and
assigning a status selected from a private status, a test status, and a public status to the firmware file,
wherein the status is also stored in the archive, wherein the private status corresponds to a design stage in the development
process, the test status corresponds to a reviewing stage, and the public status corresponds to a manufacturing stage, and
wherein the private status and the test status restrict access to the firmware file to at least one authorized user, and wherein
assigning the public status includes assigning a part number to the firmware file that provides an indication that the firmware
file is ready to be burned onto a chip and wherein the firmware file cannot be accessed to be burned onto a chip if the part
number is not associated with the firmware file.
|