SYSTEM AND METHOD FOR MANAGING HARDWARE CONFIGURATION PARAMETERS

• US 20100088498A1
• Filed: 12/03/2009
• Published: 04/08/2010
• Est. Priority Date: 08/01/2006
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: KREEK, Conrad, Mailloux, Jerry
• Granted Patent: US 7,870,303 B2
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

A system and method manages configuration data within a hardware component of a device to support hardware component changes during development or manufacture of the device. A Standardized Virtual Part (SVP) file is formed as a binary file and includes a SVP header that comprises metadata of one of at least schema version, revision numbers, part numbers, creator and description. The SVP file also includes hardware configuration data and a SVP trailer that includes error checking data for data authentication. The SVP file is loaded onto the device during development or manufacture for configuring the hardware component.

Claims

1-21. -21. (canceled)

22. A method for implementing configuration data within a hardware component of a device when the device is under development or manufacture, which comprises:

creating within a processor associated with an establishment that develops or manufactures the device a standardized virtual part (SVP) file as a binary file comprising hardware configuration data that comprises part-specific data for configuring the hardware component;

loading the SVP file from the processor into an SVP manager application associated with the operating system of the device; and

writing the SVP file from the SVP manager application into a memory of the device for configuring and controlling a specific hardware component within the device under development or manufacture.

23. The method according to claim 22, which further comprises loading the SVP file into a non-volatile random access memory (NVRAM) of the device.

24. The method according to claim 23, which further comprises selecting the SVP file to be loaded into the NVRAM from a Bill of Material (BOM) for the device.

25. The method according to claim 22, which further comprises storing the SVP file within a database containing manufacturing data about the device before loading the SVP file onto the device.

26. The method according to claim 22, which further comprises loading the SVP file into the device using Serial Transfer Protocol (STP) commands.

27. The method according to claim 22, which further comprises configuring register settings within the hardware component based on the hardware configuration data of the SVP file.

28. The method according to claim 22, which further comprises storing the SVP file within a database containing manufacturing data and releasing the SVP file to an appropriate Bill of Material (BOM) before loading the SVP file on the device.

29. The method according to claim 22, further comprising creating the SVP file to include an SVP header that comprises metadata of one of at least schema version, revision numbers, part numbers, creator and description.

30. The method according to claim 29, which further comprises loading the SVP file using a SVP manager application on the device that is operable for at least one of authentication of SVP files, STP commands for loading SVP files, SVP file schema version and revision control on the device, and upgrade/downgrade scenarios.

31. The method according to claim 29, which further comprises tracking hardware configuration data using a part number and version embedded within the header of the SVP file.

32. The method according to claim 22, which further comprises creating the SVP file to include an SVP trailer that comprises error checking data for data authentication.

33. The method according to claim 32, which further comprises adding a cryptographic signature to the SVP trailer for authenticating SVP files.

34. A system for implementing configuration changes within a hardware component of a device when the device is under development or manufacture, comprising:

a processor external to the device and associated with an establishment that develops or manufactures the device, and an associated database that includes data related to manufacturing of the device, said processor operative for creating at least one binary standardized virtual part (SVP) file comprising hardware configuration data that comprises part-specific data for configuring the hardware component; and

a device comprising a memory, a specific hardware component that is under development or manufacture, an SVP manager application into which the SVP file is loaded from the processor external to the device, and wherein said SVP manager application is operable for configuring and controlling a specific hardware component within the device under development or manufacture.

35. The system according to claim 34, and further comprising a Bill of Material (BOM) to which the SVP file is added from the database.

36. The system according to claim 34, and further comprising a non-volatile memory on the device on which the SVP file is loaded.

37. The system according to claim 34, wherein said device includes predetermined register settings and said hardware configuration data is operative for changing the register settings.

38. The system according to claim 34, and further comprising an assembly line station for receiving the SVP file from the database and loading the SVP file onto a device during manufacturing.

39. The system according to claim 34, wherein said device includes operating system (OS) software and said SVP manager application is in said OS software.

40. The system according to claim 34, wherein said SVP file comprises an SVP header that comprises metadata of one of at least schema version, revision numbers, part numbers, creator and description.

41. The system according to claim 34, wherein said SVP file comprises an SVP trailer that comprises error checking data for data authentication.

42. The system according to claim 41, wherein said SVP trailer further comprises a cryptographic signature for authenticating SVP files.

43. A system for implementing configuration changes within a hardware component of a device when the device is under development or manufacture, comprising:

a processor external to the device and associated with an establishment that develops or manufactures the device, and an associated database that includes data related to manufacturing of the device, said processor operative for creating at least one binary standardized virtual part (SVP) file comprising hardware configuration data that comprises part-specific data for configuring the hardware component; and

a device comprising a memory, a specific hardware component that is under development or manufacture, an SVP manager application into which the SVP file is loaded from the processor external to the device, and wherein said SVP manager application is operable for loading SVP files as part-specific data for configuring a hardware component using serial transfer protocol (STP) commands.

44. The system according to claim 43, wherein said SVP file further comprises an SVP header that comprises metadata of one of at least schema version, revision numbers, part numbers, creator and description and said STP commands load data related to SVP file schema version and revision control on the device and upgrade/downgrade scenarios.

45. The system according to claim 43, and further comprising a Bill of Material (BOM) to which the SVP file is added from the database.

46. The system according to claim 43, and further comprising a non-volatile memory on the device on which the SVP file is loaded.

47. The system according to claim 43, wherein said device includes predetermined register settings and said hardware configuration data is operative for changing the register settings.

48. The system according to claim 43, and further comprising an assembly line station for receiving the SVP file from the database and loading the SVP file onto a device during manufacturing.

49. The system according to claim 43, wherein said device includes operating system (OS) software and said SVP manager application is in said OS software.

50. The system according to claim 43, wherein said SVP file further comprises an SVP trailer that comprises error checking data for data authentication.

51. The system according to claim 50, wherein said SVP trailer further comprises a cryptographic signature for authenticating SVP files.