Fast initialization of medical device system having multiple operating systems

• US 7,529,921 B2
• Filed: 10/18/2005
• Issued: 05/05/2009
• Est. Priority Date: 12/17/2004
• Status: Expired due to Fees

• Current Assignee: Cardiac Pacemakers Incorporated (Boston Scientific Corporation)
• Original Assignee: Cardiac Pacemakers Incorporated (Boston Scientific Corporation)
• Inventors: Sinha, Binita, Shehadeh, Firass, Khenson, Eugene, Barton, Michael W., Hidem, Steve, Cao, Lihong, Stein, Richard E.
• Primary Examiner(s): Lee; Thomas
• Assistant Examiner(s): TRAN, VINCENT HUY
• Application Number:
  US11/253,000
• Publication Number:
  US 20060133362A1
• Time in Patent Office: 1,295 Days
• Field of Search: 713/1, 713/2, 719/310
• US Class Current: 713/1
• CPC Class Codes: G06F 9/441 Multiboot arrangements, i.e. selecting an operating system to be loaded

Abstract

A system including a communication circuit and a microprocessor operable to execute instruction code associated with at least a first operating system and a second operating system. The system also includes a volatile system memory to store executable code, a nonvolatile memory to store executable startup code, and nonvolatile image storage to store at least one captured state image. The captured state image includes an image of system memory in a captured state associated with a non-executing operating system. The system further includes a system transition routine to transition between the executing operating system and the non-executing operating system when an application to be run on the microprocessor requires the non-executing operating system. The system transition routine converts content of volatile memory and microprocessor registers to a captured state in accordance with the non-executing operating system captured state image stored in the nonvolatile image storage.

Claims

1. A medical device system comprising:

a communication circuit;

a microprocessor coupled to the communication circuit, the microprocessor having registers, and the microprocessor operable to execute instruction code associated with at least a first operating system and a second operating system, where only one operating system executes at a time, a portion of the instruction code executed to communicate with a medical device;

a volatile system memory in communication with the microprocessor, the volatile system memory to store executable code, including code of an executing operating system;

a nonvolatile memory to store executable startup code;

nonvolatile image storage to store at least one captured state image, wherein the captured state image includes an image of memory and microprocessor registers in a captured state, the captured state associated with a non-executing operating system;

a system transition routine to transition the system between the executing operating system and the non-executing operating system when an application to be run on the microprocessor requires the non-executing operating system, wherein the system transition routine converts content of volatile memory and microprocessor registers to a captured state in accordance with the non-executing operating system captured state image stored in the nonvolatile image storage; and

wherein the image storage includes at least a first captured state image associated with the first operating system and at least a second captured state image associated with the second operating system, and wherein the second captured state image is stored within the first captured state image.

2. The system of claim 1, wherein the system transition routine transitions the system between the executing operating system and the non-executing operating system without saving a state of the executing operating system.

3. The system of claim 1, wherein the first captured state image is associated with a first software application that uses the first operating system, and the second captured state image is associated with a second software application that uses the second operating system.

4. The system of claim 1, wherein the captured state image comprises a reduced copy of contents of system memory in the captured state.

5. The system of claim 1, wherein the captured state image excludes contents of a portion of the system memory.

6. The system of claim 1, wherein the image storage includes flash memory, or EPROM, or both.

7. The system of claim 1, wherein the image storage includes disk memory and a captured state image is transferred from the disk memory to volatile system memory.

8. The system of claim 1, further comprising:

code in the system transition routine to retrieve a memory image and a captured state data structure from the image storage, wherein the memory image corresponds to pages in a linear address space that are mapped in the captured state into page frames of physical address space by a paging mechanism, and wherein the captured state data structure comprises values of microprocessor registers in the captured state; and

code in the system transition routine to load microprocessor registers with values in the captured state data structure and to store the memory image in the volatile system memory in a manner that restores the page frames of the captured state.

9. The system of claim 1, wherein the system is capable of transitioning from an assertion of power-on-reset to the first operating system to the second operating system in less than seven seconds.

10. The system of claim 1, wherein the first and second operating systems include QNX and Linux.

11. The system of claim 10, wherein the image storage includes a captured state image associated with a QNX operating system within a captured state image associated with a Linux operating system, and the system transition routine converts contents of the volatile system memory to a QNX captured image by first retrieving the Linux captured image from thenonvolatile image storage.

12. The system of claim 10, wherein the image storage includes a captured state image associated with a QNX operating system stored as a file associated with a Linux memory partition, and the system transition routine converts contents of the volatile system memory to a QNX captured image by first retrieving the Linux captured image from the nonvolatile image storage.

13. The system of claim 10, wherein the image storage includes a captured state image associated with a QNX operating system, and the system transition routine converts contents of the volatile system memory to a QNX captured state image by loading the QNX image directly from the nonvolatile image storage.

14. The system of claim 1, wherein the captured state image in the image storage

15. The system of claim 1, wherein the captured state image contained in the image storage includes contents to initialize the communication circuit.

16. The system of claim 1, wherein the system further includes an electrocardiogram subsystem, and wherein the captured state image contained in the image storage includes contents to initialize the electrocardiogram subsystem.

17. The system of claim 1, wherein the system further includes a pacing system analyzer, and wherein a captured state image contained in the image storage includes contents to initialize the pacing system analyzer.

18. The system of claim 1, wherein the system transition routine includes a system capture routine, wherein the system capture routine captures an image of system memory corresponding to a quiescent state of an operating system, and wherein the system capture routine stores a captured state image on the image storage.

19. The system of claim 18, wherein the system capture routine includes code to unmount a root file system and store the root file system in the captured state image.

20. The system of claim 18, wherein the system capture routine is configured to divide the root file system into a plurality of root file domains including a domain that is read-only, a domain that remains open in volatile memory, and a domain that is unmountable and writeable, and wherein the captured state image includes files in the domain that remains open.

21. The system of claim 20, wherein the read-only root domain includes meta-data files that are included in the captured state image.

22. The system of claim 1, wherein the system transition routine includes code to remount a root file system associated with the second operating system.

23. The system of claim 1, wherein the system further includes a disk drive, and wherein the system transition routine includes code to prevent the disk drive from spinning down.

24. A method comprising:

loading a first captured state image from non-volatile memory into volatile memory, wherein the first captured state image is associated with a first operating system and includes a second captured state image within the first captured state image, wherein the second captured state image is associated with a second operating system and is loaded into volatile memory with the first captured state image;

interrupting a first operating system executing on a microprocessor-based medical device system when an application associated with a second non-executing operating system is selected for execution on the system;

retrieving a captured memory image and a captured state data structure associated with the second operating system from volatile image storage; and

transferring system control to the second operating system.

25. The method of claim 24, further including:

retrieving a captured memory image and a captured state data structure associated with the first operating system from the volatile image storage without first saving a state of the first operating system; and

transferring system control to the first operating system.

26. The method of claim 25, wherein retrieving a captured memory image and a captured state data structure associated with the first operating system from an image storage medium includes retrieving when the application associated with the second operating system is exited.

27. The method of claim 25, wherein retrieving a captured memory image and a captured state data structure associated with the first operating system from an image storage medium includes retrieving when an application associated with the first operating system is selected.

28. The method of claim 24, wherein retrieving the captured memory image includes retrieving a memory image corresponding to at least one page in linear address space that is mapped in the captured state into at least one page frame of physical address space by a paging mechanism, and wherein storing the retrieved memory image in volatile memory includes storing the retrieved memory image in volatile memory in a manner that restores the at least one page frame in accordance with information derived from paging tables in active memory.

29. The method of claim 28, wherein retrieving a memory image includes restoring memory pages from a file in nonvolatile memory.

30. The method of claim 28, wherein retrieving a memory image includes restoring memory pages from a file on a disk memory partition.

31. The method of claim 24, wherein retrieving a captured memory image and a captured state data structure includes retrieving a captured memory image and a captured state data structure corresponding to a captured state of one or more user processes held in a suspended state by an operating system.

32. The method of claim 24, wherein transferring system control to the second operating system includes:

enabling memory paging;

initializing peripheral hardware devices;

running integrity tests; and

running the processes held in a suspended state by the operating system.

33. The method of claim 24, wherein storing the retrieved memory image in volatile memory includes executing retrieval and store processes in parallel.

34. The method of claim 33, wherein executing retrieval and store processes in parallel includes transferring the retrieved memory image into pages of system memory based on a RAM bitmap using direct memory access (DMA).

35. The method of claim 24, further including:

creating the captured memory image and captured state data structure; and

storing the captured memory image and captured state data structure in the image storage medium.

36. The method of claim 35, wherein creating the captured memory image includes reducing an amount of memory used by the captured state image.

37. The method of claim 36, wherein reducing an amount of memory used by the captured state image includes reducing to fit within a size of system flash memory.

38. The method of claim 36, wherein reducing an amount of memory used by the captured state image includes using memory page laundering.

39. The method of claim 35, wherein creating and storing the captured memory image and the captured state data structure includes:

creating the captured memory image and the captured state data structure by executing a system capture routine on a development system;

transferring the captured memory image and the captured state data structure on the image storage medium to a system under production.

40. The method of claim 35, wherein creating and storing the captured memory image and the captured state data structure includes:

creating the captured memory image and the captured state data structure by executing a system capture routine on a system under production; and

storing the captured memory image and the captured state data structure on the image storage medium on the system under production.

41. The method of claim 35, wherein creating and storing the captured memory image and the captured state data structure includes:

creating the captured memory image and the captured state data structure by executing a system capture routine on a system under repair; and

storing the captured memory image and the captured state data structure on the image storage medium on the system under repair.

42. The method of claim 35, wherein creating the captured memory image includes unmounting a root file system, and wherein the method further includes mounting a root file system associated with the second operating system before transferring processor execution to the second operating system.

43. The method of claim 24, wherein the microprocessor-based system is configured as an external programmer for an implantable cardiac rhythm management device, and storing the retrieved memory image in volatile memory includes storing initialization information for the external programmer.

44. A system comprising:

a communication circuit;

a microprocessor coupled to the communication circuit, the microprocessor having registers, and the microprocessor operable to execute instruction code associated with at least first and second operating systems, where only one operating system executes at a time, a portion of the executable code for communicating with a medical device;

a volatile system memory in communication with the microprocessor, the volatile system memory to store executable code, including code of an executing operating system;

a nonvolatile memory to store executable startup code;

nonvolatile image storage to store at least a first captured state image associated with the first operating system and at least a second captured state image associated with the second operating system, wherein the second captured state image is stored within the first captured state image, and wherein a captured state image includes an image of memory and microprocessor registers in a captured state; and

a system transition routine to transition between the executing and the non-executing operating systems when an application to be run on the microprocessor requires the non-executing operating system, wherein the system transition routine includes code to cause the microprocessor to execute instructions in system management mode (SMM) to convert contents of volatile memory and microprocessor registers to a captured state in accordance with the non-executing operating system captured state image.

45. The system of claim 44, wherein the system transition routine transitions the system between the executing operating system and the non-executing operating system without saving a state of the executing operating system.

46. The system of claim 44, wherein the system includes an system management interrupt (SMI) handler, wherein the system transition routine generates an SMI to be processed by the interrupt handler when an application to be run on the system requires the non-executing operating system, and wherein an SMI causes the microprocessor to execute instructions in SMM.

47. The system of claim 44, wherein the instructions executed in SMM cause the microprocessor to convert contents of volatile system memory to a captured state by transferring a captured state image from the nonvolatile image storage to the volatile system memory in a manner that restores page frames of the captured state image.

48. The system of claim 44, wherein the system further includes an interface to transfer data between a primary operating system and a secondary operating system.

49. The system of claim 44, wherein the interface includes a data structure, and wherein the instructions executed in SMM cause the microprocessor to transfer memory contents to a data structure accessible by both the first and second operating systems.

50. The system of claim 44, wherein the instructions executed in SMM cause the microprocessor to load a system management random access memory (SMRAM) area with at least a portion of a captured state image, and wherein the instructions executed in SMM include a resume instruction that loads the captured state from the SMRAM area into the microprocessor.

51. The system of claim 50, wherein the resume instruction further causes the microprocessor to return to the operating switching routine and restore an additional portion of a captured state image stored outside of the SMRAM area.

52. The system of claim 44, wherein the first and second operating systems include QNX and Linux.

53. The system of claim 44, further including an electrocardiogram subsystem coupled to the microprocessor and wherein the captured state image in the image storage includes contents to initialize the electrocardiogram subsystem.

54. A system comprising:

a communication circuit;

a microprocessor coupled to the communication circuit, the microprocessor having registers, and the microprocessor operable to execute instruction code associated with at least a first operating system and a second operating system, where only one operating system executes at a time, a portion of the instruction code executed to communicate with a medical device;

a volatile system memory in communication with the microprocessor, the volatile system memory to store executable code, including code of an executing operating system;

a nonvolatile memory to store executable startup code;

nonvolatile image storage to store a plurality of captured state images, wherein a captured state image includes an image of memory and microprocessor registers in a captured state, the captured state associated with one of the plurality of operating systems;

a direct memory access (DMA) controller operable to store information in the volatile system memory and retrieve information from the nonvolatile system memory, the DMA controller operable to interpret the contents of a RAM bitmap and a zero bitmap; and

a system transition routine to transition the system between an executing operating system and a non-executing operating system when an application to be run on the microprocessor requires the non-executing operating system, the transition routine including;

a DMA controller initialization routine to load the Ram bitmap and the zero bitmap into the DMA controller and start a DMA operation, the DMA operation to convert content of volatile memory to a captured state in accordance with the non-executing operating system captured state image stored in the nonvolatile image storage;

a operating system switching routine to convert content of microprocessor registers and to transition control of the system to the non-executing operating system; and

a system capture routine to create captured state images of volatile system memory and store the non-executing operating system captured state image within an executing operating system captured state image on the nonvolatile image storage.

55. The system of claim 54, wherein a captured state image of a first operating system includes a captured state image of the second operating system, wherein the DMA controller initialization routine converts content of volatile system memory to a captured state in accordance with a first operating system captured state image and stores a second operating system captured state image in volatile system memory.

56. The system of claim 55, wherein the DMA controller initialization routine converts content of volatile system memory to a captured state in accordance with the second operating system captured state image stored in the volatile system memory when an application to be run on the microprocessor requires the second operating system.

57. The system of claim 56, wherein the first operating system is a primary operating system and wherein the DMA controller initialization routine converts content of volatile system memory to a captured state in accordance with a primary operating system captured state image upon system power-up.

58. The system of claim 57, wherein the system transition routine converts content of microprocessor registers to a captured state prior to executing the first or second operating system.