Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method and System for Remote, in situ Debugging and Control of uEFI/BIOS in a BladeCenter Environment

IP.com Disclosure Number: IPCOM000202203D
Publication Date: 2010-Dec-08
Document File: 2 page(s) / 45K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for remote, in situ debugging and control of uEFI/BIOS in a BladeCenter* environment is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method and System for Remote , in situ Debugging and Control of uEFI/BIOS in a BladeCenter Environment

Disclosed is a method and system for in situ debugging and control of uEFI/BIOS in a BladeCenter* environment.

The method and system disclosed herein, eliminates the need for expensive cables and devices for uEFI/BIOS debugging. At a remote site, the equipment is replaced by software that performs the same processing. Instead of attaching expensive cables and equipment to the motherboard, the Integrated Test Processor (ITP) hooks in the processors that are instead sent to an integrated Management Module (iMM) in order to be packetized for Ethernet transport over a Network Controller Sideband Interface (NCSI). At a remote location, this information is received, de-packetized and processed for uEFI/BIOS development using a software.

In another instance, the method and system enables intensive uEFI/BIOS development or debugging to be performed remotely. Thus, problems may be debugged in the original customer environment without modifying the hardware, for example, adding dongles. In other words, without adding hardware to the motherboard, other than traces, full uEFI/BIOS debug from a remote site is attained. The blade or Information Technology element (ITE) does not need to be retrieved from the customer site. The blade or ITE remains in the failing condition and the uEFI/BIOS developer need to log only into the Advanced Management Module (AMM) or equivalent in order to gain full access to the blade or ITE for debugging. Lastly, the uEFI/BIOS developer can develop uEFI/BIOS at a remote location for a piece of new hardware attached to the blade or ITE. In this way, the uEFI/BIOS developer does not need to fly on-site to do development nor have the equipment flown to the developer. The remote developer has full access to the AMM or equivalent and, thus, has full control of the blade for development.

For debugging the uEFI/BIOS, the data from the debug that interface into the processor is brought to the iMM to be packetized and then sent to the iMM network layer to be converted to TCP packets. These TCP packets are sent over the NCSI bus to the Ethernet controller. The Ethernet controller is configured to forward the packets to the Ethernet switches. The TCP packets have the destination IP address and, eventually, reach the remote uEFI/BIOS developer's debug application. The remote uEFI/...