Method for coexistence and cooperation between system firmware and debug code

The present invention relates generally to the data processing field, and more particularly, relates to a method and apparatus for implementing coexistence and cooperation between system firmware and debug code.

During bring-up of a machine, such as an International Business Machines Corporation AS/400® or RS/6000®, typically multiple different tools for testing are required. For example, debug tools, such as a JTAG-base bring-up tools often are required for testing certain integrated circuit chips in the machine under test. System firmware of a host computer used for testing, typically provides a different set of tools.

Although the debug tools and the host computer system firmware may generally perform similar functions, the user interface, command syntax, and the capabilities of the debug tools and the host computer system firmware are generally different.

A need exists for a method to allow coexistence and cooperation between system firmware and debug tools for testing.

As used in the following description and claims, the term coexistence means a user can use either the system firmware or the debug tool at any time.

As used in the following description and claims, the term cooperation means that at a certain point in an operational sequence of a machine under test the system firmware might be used for certain operations and the debug tool for other functions that are not implemented in the system firmware. For example, during an initial power-on routine, system firmware might be used for certain operations and the debug code for other functions that are not implemented in the system firmware.

A principal object of the present invention is to provide a method and apparatus for implementing coexistence and cooperation between system firmware and debug code. Other important objects of the present invention are to provide such method and apparatus for implementing coexistence and cooperation between system firmware and debug code substantially without negative effect and that overcome many of the disadvantages of prior art arrangements.

In brief, a method and apparatus are provided for implementing coexistence and cooperation between system firmware and debug code. A service processor is coupled to a machine under test for sending system firmware test functions to the machine under test and receiving test data from the machine under test. A host computer is coupled to the service processor for sending bring-up tool debug test functions to the machine under test and receiving test data from the machine under test. The system firmware starts without user intervention on initial power-on routine of the machine under test. When the host computer receives a user request, the host computer notifies the service processor. The bring-up tool debug test functions are started responsive to the user request.

In accordance with features of invention, the system firmware can be used for certain operations to a certain point in an operational test sequence of the machine under test and then the debug tool debug test functions are used for other functions that are not implemented in the system firmware. A user can use either the system firmware or the bring-up tool debug test functions at any time.

The present invention together with the above and other objects and advantages may best be understood from the following detailed description of the preferred embodiments of the invention illustrated in the drawings, wherein:

FIG. 1 is a block diagram representation illustrating a computer system for implementing coexistence and cooperation between system firmware and debug code in accordance with the preferred embodiment; and

FIG. 2 is a block diagram illustrating a computer program product in accordance with the preferred embodiment.

Having reference now to the drawings, in FIG. 1, there is shown a test system of the preferred embodiment generally designated by the reference character 100 . As shown in FIG. 1, test system 100 includes a service processor 102 coupled to a machine under test 104 via a JTAG bus 106 . JTAG bus 106 provides a standardized interface for bi-directional data transfer to and from the machine under test 104 . A host computer 108 is coupled to the service processor 102 for bi-directional communications.

Service processor 102 includes a memory 110 for storing software including a system firmware 112 and a bring-up tool 114 . Service processor 102 includes a scan controller 116 coupled to the machine under test 104 via JTAG bus 106 . Scan controller 116 sends data to the machine under test 104 via JTAG bus 106 . The machine under test 104 returns data back to the scan controller 116 via JTAG bus 106 .

Various complex machines 104 can be tested in the test system 100 . For example, the machine under test 104 can be, such as, an International Business Machines Corporation AS/400® or RS/6000®, where multiple different tools for testing are required.

System firmware 112 of service processor 102 provides a large set of tools to perform predefined tests on the machine under test 104 using scan controller 116 . The system firmware 112 of service processor 102 includes a large code for extensive testing of the machine under test 104 using the scan controller 116 . Bring-up tool 114 of service processor 102 includes a relatively small code to control the scan controller 116 . Bring-up tool 114 of service processor 102 provides a server function for the host computer 108 .

Host computer 108 includes a system firmware 122 and a bring-up tool 124 . Host computer 108 is coupled to the service processor 102 , for example, via a parallel port 126 . Host computer 108 may be implemented using any suitable computer, such as an IBM personal computer running the OS/2® operating system. The bring-up tool 124 of host computer 108 provides a different, large set of tools than the system firmware 112 of service processor 102 for performing predefined debug tests on the machine under test 104 using scan controller 116 .

In accordance with features of the preferred embodiment, service processor 102 is a converged service processor for implementing coexistence and cooperation between system firmware and debug code. Both system firmware 112 and the bring-up tool 124 run on the converged service processor 102 . The user is enabled to easily use either tool set of system firmware 112 or the bring-up tool 124 at any time.

In accordance with features of the preferred embodiment, commands executed on the host machine 108 attached to the service processor 102 via parallel port 126 may communicate with code loads of either the system firmware 112 or the bring-up tool 114 . System firmware 112 or the bring-up tool 114 running on the converged service processor 102 may include semaphores to determine which code is being asked to carry out the user's instructions. Program semaphores in the system firmware 112 and the debug tool 114 control access to the scan controller 116 of the converged service processor 102 .

Each bring-up tool 114 and 124 is a JTAG-based bring-up tool for implementing debug functions that run on the service processor 102 . Bring-up tool 124 of host computer 108 is user driven or runs responsive to a user request. Bring-up tool 114 of service processor 102 provides a server function for performing predefined debug tests of bring-up tool 124 on the machine under test 104 using scan controller 116 .

Bring-up tool 114 sends debug tests from bring-up tool 124 to the machine under test 104 via the scan controller 116 . Bring-up tool 114 returns debug test data from the machine under test 104 to the bring-up tool 124 of host computer.

System firmware 112 of service processor 102 runs on the service processor 102 independently without user intervention. In general there is no interaction between the system firmware 112 and the bring-up tools 114 and 124 . System firmware 112 of service processor 102 communicates with the system firmware 122 of host computer 108 to provide information to a user. For example, system firmware 112 communicates with the system firmware 122 to provide a failure notice of an identified failure in the machine under test 104 . System firmware 122 of host computer 108 provides a graphical user interface (GUI) for receiving user requests or commands. Bring-up tool 124 of host computer 108 also includes a small user interface code.

In accordance with features of the preferred embodiment, cooperation between system firmware and debug code is provided. For example, during an initial power-on routine of the machine under test 104 , system firmware 112 might be used for certain operations to a certain point and then the debug code of the bring-up tools 124 is used for other functions that are not implemented in the system firmware 112 . Then the initial power-on routine of the machine under test 104 continues using the system firmware 112 after the debug functions of the bring-up tool 124 are completed.

In typical operation of test system 100 , system firmware 112 starts without user intervention on initial power-on routine of the machine under test 104 . When the user selects debug functions of the bring-up tool 124 , system firmware 112 is notified and stops its testing. Then the bring-up tool 124 controls the scan controller 116 via bring-up tool 114 to perform the user selected debug functions of the bring-up tool 124 . When the system firmware 112 identifies a failure during testing of the machine under test 104 , system firmware 112 stops its testing and sends a failure notice to the host computer 108 . For example, system firmware 112 sends the failure notice to the system firmware 122 of the host computer 108 . The user can select debug functions of the bring-up tool 124 responsive to the failure notice from system firmware 112 . Then the user selected debug functions of the bring-up tool 124 or system firmware 112 are used to efficiently identify the cause of the failure in the machine under test 104 .

Referring now to FIG. 2, an article of manufacture or a computer program product 200 of the invention is illustrated. The computer program product 200 includes a recording medium 202 , such as, a floppy disk, a high capacity read only memory in the form of an optically read compact disk or CD-ROM, a tape, a transmission type media such as a digital or analog communications link, or a similar computer program product. Recording medium 202 stores program means 204 , 206 , 208 , 210 on the medium 202 for carrying out the methods for implementing coexistence and cooperation between system firmware and bring-up tool debug code of the preferred embodiment in the system 100 of FIG. 1 .

A sequence of program instructions or a logical assembly of one or more interrelated modules defined by the recorded program means 204 , 206 , 208 , 210 , direct the system 100 for implementing coexistence and cooperation between system firmware and bring-up tool debug code of the preferred embodiment.

While the present invention has been described with reference to the details of the embodiments of the invention shown in the drawing, these details are not intended to limit the scope of the invention as claimed in the appended claims.