1460724397-727e8563-137b-42c7-b9fc-dc4fd82d7c85

1. A method for creating diagnostic files, the method comprising:
receiving an error notification indicating that an error has occurred in a particular system section of a system having a plurality of system sections, the error notification including information about the error;
selecting one of:
creating a full image of the particular system section; and
creating a summarized error report of the particular system section without creating the full image of the particular system section,
the selecting based on the information in the error notification;

creating a diagnostic file comprising one of the full image of the particular system section and the summarized error report of the particular system section, wherein contents of the diagnostic file are based on the selecting; and
saving the diagnostic file.
2. The method of claim 1, further comprising:
determining another system section of the system that is associated with the error in the particular system section;
creating one of a full image of the other system section and a summarized error report of the other system section based on the information included in the error notification and a relationship between the particular system section and the other system section; and
including, in the diagnostic file, one of the full image and the summarized error report of the other system section.
3. The method of claim 2, wherein one or more of the plurality of system sections have a dedicated error engine associated with the respective system section to determine whether to create a full image or a summarized error report for the respective system section.
4. The method of claim 3, wherein the system includes a generic error engine associated with one or more of the plurality of system sections that are not associated with a dedicated error engine, said generic error engine for determining whether to create a full image or a summarized error report.
5. The method of claim 4, wherein the generic error engine is a master error engine for controlling the one or more dedicated error engines, wherein the dedicated error engines are slave error engines.
6. The method of claim 4, wherein the generic error engine and the one or more dedicated error engines have a peer-peer relationship, with any of the error engines detecting the error, acting as master error engine, and notifying other error engines.
7. The method of claim 1, wherein each of the plurality of system sections is a subset of system memory.
8. The method of claim 1, wherein each of the plurality of system sections is a unique system component.
9. The method of claim 1, wherein the information about the error includes information relating to the time the error occurred, the type of error that occurred, and the system section associated with the error occurrence.
10. The method of claim 1, further comprising dividing a memory address of the system into the plurality of system sections, each of the system sections a self-contained functional system section that includes one or more defined execution components.
11. A system for creating diagnostic files, the system comprising:
a plurality of system sections;
an error buffer configured to receive an error notification indicating that an error has occurred in a particular system section of the plurality of system sections, the error notification including information about the error; and
an error engine configured to:
select between one of:
create a full image of the particular system section; and
create a summarized error report of the particular system section without creating the full image of the particular system section,
the selecting based on the information in the error notification;

create a diagnostic file comprising one of the full image of the particular system section and the a summarized error report of the particular system section, wherein contents of the diagnostic file are based on the selecting; and
save the diagnostic file.
12. The system of claim 11, wherein the error engine is further configured to:
determine another system section of the system that is associated with the error in the particular system section;
create one of a full image of the other system section and a summarized error report of the other system section based on the information included in the error notification and a relationship between the particular system section and the other system section; and
include in the diagnostic file, one of the full image and the summarized error report of the other system section.
13. The system of claim 12, wherein the error engine includes one or more dedicated error engines associated with the respective system section, the one or more dedicated error engines configured to determine whether to create a full image or a summarized error report for the respective system section.
14. The system of claim 13, wherein the error engine further includes a generic error engine associated with one or more of the plurality of system sections that are not associated with a dedicated error engine, the generic error engine configured to determine whether to create a full image or a summarized error report.
15. The system of claim 14, wherein the generic error engine is configured as a master error engine to control the one or more dedicated error engines, and the dedicated error engines are configured as slave error engines.
16. The system of claim 14, wherein the generic error engine and the one or more dedicated error engines have a peer-peer relationship, with any of the error engines configured to detect the error, to act as master error engine, and to notify other error engines.
17. The system of claim 11, wherein each of the plurality of system sections is a subset of system memory.
18. The system of claim 11, wherein each of the plurality of system sections is a unique system component.
19. The system of claim 11, wherein the information about the error includes information relating to the time the error occurred, the type of error that occurred, and the system section associated with the error occurrence.
20. A computer program product for creating diagnostic files, the computer program product comprising:
a non-transitory computer readable storage medium having program code embodied therewith, the program code executable by a processor to:
receive an error notification indicating that an error has occurred in a particular system section of a system having a plurality of system sections, the error notification including information about the error;
select one of:
create a full image of the particular system section; and
create a summarized error report of the particular system section without creating the full image of the particular system section,
the selecting based on the information in the error notification;

create a diagnostic file comprising one of the full image of the particular system section and the summarized error report of the particular system section, wherein contents of the diagnostic file are based on results of the determining; and
save the diagnostic file.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A contact system for a semiconductor component having a plurality of terminal contacts comprising:
a board comprising a plurality of contacts in electrical communication with external circuitry;
a substrate configured to slide on the board comprising a plurality of flexible segments configured to move independently of one another and a plurality of contactors on the flexible segments configured to simultaneously electrically engage the contacts and the terminal contacts;
each contactor comprising a first contact on a flexible segment configured to electrically engage a terminal contact on the component, and a conductive polymer layer on a second opposing side of the flexible segment in electrical communication with the first contact configured to electrically engage a contact on the board.
2. The contact system of claim 1 wherein the substrate comprises a plurality of grooves separating the contractors and the flexible segments.
3. The contact system of claim 1 further comprising a test handler configured to place and hold the component on the substrate.
4. The contact system of claim 1 wherein the substrate slides in a z-direction on pins attached to the board.
5. The contact system of claim 1 wherein the terminal contacts comprise an element selected from the group consisting of leads, bumps and pads.
6. The contact system of claim 1 wherein the external circuitry comprises test circuitry.
7. A contact system for a semiconductor component having a plurality of terminal contacts comprising:
a board comprising a plurality of contacts in electrical communication with external circuitry and a plurality of pins;
a substrate slidably mounted on the pins having a plurality of flexible segments configured to move independently of one another;
a plurality of contactors on the flexible segments configured to simultaneously electrically engage the contacts and the terminal contacts;
each contactor comprising a first contact on a first side of a flexible segment configured to electrically engage a terminal contact, a second contact on a second side of the flexible segment in electrical communication with the first contact, and a conductive polymer layer configured to electrically engage the second contact and a contact.
8. The contact system of claim 7 wherein the substrate comprises a plurality of grooves on either side of the contactors forming the flexible segments.
9. The contact system of claim 7 wherein the conductive polymer layer comprises an elastomeric base material and a plurality of conductive particles in the base material configured to electrically engage the contact.
10. The contact system of claim 7 wherein the terminal contact comprises a lead and the first contact comprises a pad configured to physically engage the lead.
11. The contact system of claim 7 wherein the terminal contact comprises a bump and the first contact comprises an indentation for the bump.
12. The contact system of claim 7 wherein the terminal contact comprises a pad and the first contact comprises a bump for engaging the pad.
13. The contact system of claim 7 wherein the component comprises an element selected from the group consisting of packages, ball grid array devices, and modules.
14. A contact system for a semiconductor component having a plurality of terminal contacts comprising:
a board comprising a plurality of contacts in electrical communication with an external circuitry;
a substrate slidably mounted to the board for movement in a z-direction and having a first side, an opposing second side, and a plurality of grooves from the first side to the second side forming a plurality of flexible segments;
a plurality of contactors on the flexible segments configured to move independently of one another and to simultaneously electrically engage the contacts and the terminal contacts;
each contactor comprising a first contact on the first side of a flexible segment configured to electrically engage the terminal contact, a second contact on the second side of the flexible segment in electrical communication with the first contact, and a conductive polymer layer configured to electrically engage the second contact and a contact.
15. The contact system of claim 14 wherein the first contact and the second contact comprise an element selected from the group consisting of gold and platinum.
16. The contact system of claim 14 wherein the conductive polymer layer comprises an elastomeric base material and a plurality of conductive particles in the base material.
17. The contact system of claim 14 wherein the conductive polymer layer comprises a plurality of particles configured to penetrate the second contacts.
18. A contact system for a semiconductor component having a plurality of terminal contacts comprising:
a test circuitry configured to apply test signals to the component;
a test handler configured to move and support the component;
a board comprising a plurality of contacts in electrical communication with the test circuitry;
a substrate on the board comprising a plurality of independent flexible segments and a plurality of contactors on the flexible segments configured under a force applied by the test handler to the component to simultaneously electrically engage the contacts and the terminal contacts;
each contactor comprising a first contact on a first side of a flexible segment configured to electrically engage a terminal contact on the component, and a second contact on a second opposing side of the flexible segment in electrical communication with the first contact, and a conductive polymer layer configured to electrically engage the second contact and a contact on the board.
19. The contact system of claim 18 wherein the substrate is configured to float in a Z-direction on the board.
20. The contact system of claim 18 wherein the substrate comprises a plurality of grooves electrically isolating the contactors and forming the flexible segments.