System and Method of Crosstalk Mitigation in Microstrip Serial Links in a Printed Circuit Board

CROSS-REFERENCE TO RELATED APPLICATION

Related subject matter is contained in co-pending U.S. patent application Ser. No. 15/______ (DC-107552) entitled “System and Method of Cancelling Floquet Mode Resonance and Far End Crosstalk, and Mitigating Crosstalk in a Printed Circuit Board,” filed of even date herewith, the disclosure of which is hereby incorporated by reference.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, and more particularly relates to crosstalk mitigation in microstrip serial links in a printed circuit board.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes. Because technology and information handling needs and requirements may vary between different applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software resources that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:

FIG. 1 is a cross-sectional view of a printed circuit board that utilizes a broadside coupled strip line stack-up according to an embodiment of the present disclosure;

FIG. 2 illustrates exemplary trace routings of circuit traces on the printed circuit board of FIG. 1;

FIG. 3 is a floquet coupling transmission diagram for angularly routed circuit traces of FIG. 2;

FIG. 4 a cross-sectional view of a printed circuit board that provides microstrip circuit traces according to an embodiment of the present disclosure;

FIG. 5 is a far end crosstalk (FEXT) diagram for strip line circuit traces of the printed circuit board of FIG. 2;

FIG. 6 is a response that includes a floquet mode coupling response of an angularly routed circuit trace and a FEXT of a strip line circuit trace according to an embodiment of the present disclosure;

FIG. 7 is a block diagram of a resonance estimating system according to an embodiment of the present disclosure;

FIG. 8 is a flow chart illustrating a method of cancelling floquet mode resonance and far end crosstalk according to an embodiment of the present disclosure; and

FIG. 9 is a cross-sectional view of a printed circuit board having microstrip trace pairs on a surface of the printed circuit board according to an embodiment of the present disclosure; and

FIG. 10 is a block diagram illustrating a generalized information handling system according to an embodiment of the present disclosure.

The use of the same reference symbols in different drawings indicates similar or identical items.

SUMMARY

A printed circuit board may include a core layer and a microstrip trace pair on a top surface of the core layer. The core layer may have a thickness (H). The microstrip trace pair may communicate serial data at a data transfer rate. The data transfer rate may be greater than or equal to 16 gigabits per second (Gbps). A separation (S1) between a first trace of the microstrip trace pair and a second trace of the microstrip trace pair may defined as S₁=XH. X may be less than or equal to 5.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The following discussion will focus on specific implementations and embodiments of the teachings. This focus is provided to assist in describing the teachings, and should not be interpreted as a limitation on the scope or applicability of the teachings. However, other teachings can certainly be used in this application. The teachings can also be used in other applications, and with several different types of architectures, such as distributed computing architectures, client/server architectures, or middleware server architectures and associated resources.

FIG. 1 illustrates a printed circuit board 100 that utilizes a broadside coupled stripline stack-up, including a core layer 110, a pre-impregnated composite fiber (pre-preg) layer 120, and a second core layer 130. Core layers 110 and 130 represent two-sided copper-clad laminate layers upon which circuit traces are etched. Pre-preg layer 120 represents a laminate layer that does not include circuit traces, and that provides separation between the circuit traces of core layers 110 and 130. An example of a laminate layer includes an epoxy laminate, a composite fiber laminate, a FR-2 laminate, a FR-4 laminate, or another laminate material, as needed or desired, and can include a composite fiber matrix such as fiberglass cloth, carbon fiber matrix, that is pre-impregnated with the laminate material. Core layer 110 includes a power plane 112 and a circuit trace 114. Core layers 110 and 130 have a dielectric constant, also referred to as a relative permeability, given by ε_core, and pre-preg layer 120 has a dielectric constant given by ε_pre-preg.

Core layer 130 includes a power plane 132 and a circuit trace 134. Power planes 112 and 132 represent the nodes of a power supply including a positive supply voltage (V+) associated with power plane 112 and a reference supply voltage (GND) associated with power plane 132. Circuit traces 114 and 134 represent signal carrying traces for different signals in an information handling system that is instantiated on printed circuit board 100. Circuit traces 114 and 134 will be understood to be viewed edge-on, and will extend into printed circuit board 100, passing to one or more surfaces of the printed circuit board to connect to devices which terminate the circuit traces. In a particular embodiment, one or more of circuit traces 114 and 134 are routed angularly, that is, in a zigzag pattern. Circuit trace 114 is illustrated as being a victim trace, and circuit trace 134 is illustrated as being an aggressor trace, however, the designation of victim and aggressor is arbitrary for the purpose of this disclosure.

FIG. 2 illustrates exemplary trace routings 200 of circuit traces on a printed circuit board similar to printed circuit board 100. Trace routing 200 illustrates a victim trace 202 that is a straight routing that has a unit cell length 204 (L_VICTIM) that is equal to L, as described below. Trace routing 200 also illustrates an aggressor trace 212 that is angularly routed, with a routing angle of θ. A unit cell 216 of aggressor trace 212 is shown as encompassing a single cycle of the trace layout and has a cell length of L. Thus, for convenience, the unit cell length of victim trace 202 is set to be the same as the unit cell length of aggressor trace 212. Thus, given a routing angle of θ, and a unit cell length of L, it will be understood that a unit cell length 214 of aggressor trace is given as:

L
_AGGRESSOR
=L*sec θ Equation 1

Other trace routings can be utilized as needed or desired. For example, a pair of trace routings can each be provided that utilize angular routing, where each trace has a different routing angle, such as θ_VICTIMand θ_AGGRESSOR, and where each trace has a different unit cell length, such as L_VICTIMand L_AGGRESSOR.

In a particular embodiment, the floquet mode coupling in trace routings 200 can be determined by applying a field solver that evaluates the electromagnetic interactions between traces 202 and 212. Such a field solver can analyze such factors including the geometry of traces 202 and 212, the spacings between the traces, the overall length of the traces, the dielectric constant of the laminate layers that make up the printed circuit board, and the like, to determine if the traces will meet a particular design specification. The design specification can include recommended or required values for maximum insertion loss, crosstalk, and the like. If traces 202 and 212 do not meet the design specification, then a designer can re-layout the traces to improve their performance. In a particular embodiment, an analysis of traces 202 and 212 can provide a floquet coupling transmission diagram such as is shown in FIG. 3, where the floquet frequency for an exemplary circuit trace is shown to be approximately 25 gigahertz (GHz). Here, if the operating frequency of the exemplary circuit trace is expected to be near to the floquet frequency, then the designer may consider redesigning the circuit trace in order to minimize the floquet coupling with the circuit trace.

FIG. 4 illustrates a microstrip printed circuit board 400 similar to stripline printed circuit board 100, including a prepreg layer 410 that includes one copper laminate layer upon which circuit traces are etched. Prepreg layer 410 includes a power plane 412 and a victim trace 414 and an aggressor trace 416. Prepreg layer 410 has a dielectric constant, also referred to as a relative permeability, given by ε_core. Power plane 412 represents the node of a power supply, such as a positive supply voltage (V+) or a reference supply voltage (GND). Circuit traces 414 and 416 represent signal carrying traces for different signals in an information handling system that is instantiated on printed circuit board 400. Circuit traces 414 and 416 will be understood to be viewed edge-on, and will extend into printed circuit board 400, and to be provided on the surface of the printed circuit board to connect to devices which terminate the circuit traces. Circuit trace 414 is similar to victim trace 202 of FIG. 2, in that the circuit trace is not necessarily routed angularly. Circuit trace 416 is similar to victim trace 212 of FIG. 2, in that the circuit trace is routed angularly. Other trace routings can be utilized as needed or desired. For example, a pair of trace routings can each be provided that utilize angular routing, where each trace has a different routing angle, such as θ_VICTIMand θ_AGGRESSOR, and where each trace has a different unit cell length, such as L_VICTIMand L_AGGRESSOR.

In a particular embodiment, because circuit traces 414 and 416 are routed on a top or bottom surface of printed circuit board 400, the circuit trace experiences frequency dependent losses that are related to the fact that the circuit trace is not routed between power or ground planes, and so the circuit trace is said to be inhomogeneous. As such, circuit traces 414 and 416 are microstrip circuit traces. The loss characteristics of circuit traces 414 and 416 are dependent upon the geometry of the circuit trace, the geometry of the circuit board, the relative permeability, ε_core, of prepreg layer 410, and the relative permeability of the air or a soldering layer over the circuit trace. The loss characteristics of circuit traces 414 and 416 can be determined by applying a field solver that evaluates the electromagnetic interactions between the circuit trace and power plane 412. Such a field solver can analyze such factors including the geometry of circuit traces 414 and 416, the overall length of the circuit trace, the dielectric constant of prepreg layer 410, and the like, to determine if the traces will meet a particular design specification. The design specification can include recommended or required values for maximum insertion loss, crosstalk, and the like. If circuit trace 414 does not meet the design specification, then a designer can re-layout the circuit trace to improve the performance. In a particular embodiment, an analysis of circuit trace 414 can provide a far end crosstalk (FEXT) diagram such as is shown in FIG. 5, where the FEXT frequency for an exemplary circuit trace is shown to be worse at approximately 6 and 11 GHz. Here, if the operating frequency of the exemplary circuit trace is expected to be near to the FEXT frequency, then the designer may consider redesigning the circuit trace 416 in order to minimize the FEXT of circuit trace 414 at the design operating frequency. Other trace parameters can be utilized in specifying and creating the design, other than the FEXT of the circuit trace. For example, a circuit trace can be specified in terms of near end crosstalk (NEXT), insertion loss, reflection loss, or other parameters, as needed or desired.

In a particular embodiment, the designer compares the floquet mode frequency of an angularly routed circuit trace with the FEXT of a nearby strip line circuit trace, and the circuit traces are designed such that the floquet mode frequency coupling loss of the angularly routed circuit trace offsets the FEXT of the strip line circuit trace at a particular frequency of interest, such as at the operating frequency of the angularly routed circuit trace or the operating frequency of the strip line circuit trace. In this way, the overall response at the frequency of interest is flattened out, rendering the signal received at the receiver more easily compensated, and increasing the eye margins at the receiver. FIG. 6 shows a response 600 that includes a floquet mode coupling response 612 of an angularly routed circuit trace and a FEXT 614 of a strip line circuit trace, and a resultant response 616 of the received signal at a receiver end of the strip line circuit trace. The circuit traces associated with responses 612 and 616 have been designed to flatten response 616 for a 6 GHz signal frequency. In a particular embodiment, response 616 is considered to be flattened if there is 5 dB or less of change in the frequency response within 1 GHz of the operating frequency.

FIG. 7 illustrates an embodiment of a resonance estimating system 700 including a printed circuit board design input module 710, a propagation delay input module 740, a floquet/strip line frequency estimator module 742, a frequency comparison module 744, and a trace re-layout module 746. Design input module 710 represents a design depiction of a printed circuit board layout for an information handling system, and can include information related to circuit layout, device placement, and trace routing for the information handling system. As such, design input module 710 can include information regarding multiple circuit traces, in addition to the traces that are designated as victim and aggressor. Thus, the victim trace and the aggressor trace can be selected as being typical of a larger group of similarly designed traces on the printed circuit board. Design input module 710 includes a victim trace design 712, an aggressor trace design 722, and an equivalent dielectric constant value 730.

Victim trace design 712 includes a trace routing 714, a unit cell length 716, and an interface frequency 718. Similarly, Aggressor trace design 212 includes a trace routing 724, a unit cell length 726, and an interface frequency 728. Equivalent dielectric constant value 730 represents an equivalent dielectric constant value for the printed circuit board design that accounts for the differences in the dielectric constant of a core material of the printed circuit board and a pre-preg material of the printed circuit board. In a particular embodiment, equivalent dielectric constant value 730 is determined by taking an average of the dielectric constant of the core material of the printed circuit board and the dielectric constant of the pre-preg material of the printed circuit board. In another embodiment, equivalent dielectric constant value 730 is determined as a byproduct of a field solver analysis of the printed circuit board design, and can yield a more accurate value for the equivalent dielectric constant of the printed circuit board. In yet another embodiment, equivalent dielectric constant value 730 is further determined based upon interface frequencies 718 and 728, in order to yield a yet more accurate value for the equivalent dielectric constant of the printed circuit board. The skilled artisan will recognize that the dielectric constant of many common printed circuit board laminate materials are found to be in the range of 3.5 to 4.5. Thus, for the purpose of further illustration, equivalent dielectric constant value 730 will be assumed to be 4.

Design input module 710 is utilized to determine a propagation delay for signals associated with the victim trace and the aggressor trace through a unit cell, as:

$\begin{matrix} t_{delay} = \frac{l_{avg}}{v} & Equation 2 \end{matrix}$

where t_delayis the propagation delay, l_avgis the average of the unit cell lengths of the victim trace and the aggressor trace, that is:

$\begin{matrix} l_{avg} = \frac{l_{victim} + l_{aggressor}}{2} & Equation 3 \end{matrix}$

as can be determined using Equation 1, above, and v is the propagation speed of the printed circuit board material. The propagation speed v is given as:

$\begin{matrix} v = \frac{C}{\sqrt{ɛ_{eq}}} & Equation 4 \end{matrix}$

where C is the speed of light in a vacuum, and ε_eqis equal to equivalent dielectric constant value 730. For example, where the victim trace has unit cell length 716 is 8 millimeters (mm) and the aggressor trace has unit cell length 726 is 4 mm, l_avgis determined by Equation 3 to be 6 mm. Further, assuming equivalent dielectric constant value 730 is 4, the propagation speed v is determined by Equation 4 to be 1.5*10⁸m/sec. Substituting these values into Equation 3 yields a t_delayof 40 picoseconds (ps).

In another embodiment, the propagation delay can be directly measured on an exemplary printed circuit board that has the victim trace and the aggressor trace laid out as specified by design input module 710, using a time domain reflectometer on the traces, and operating at the designated interface frequencies 718 and 728. In this way, an actual measurement for the propagation delay of the unit cells of the victim trace and the aggressor trace can be determined, as needed or desired. In another embodiment, the calculated determination of the propagation delay, as described in Equations 2-4, above, is made, and the measurement using the time domain reflectometer is used as a check on the accuracy of the modeled propagation delay.

Floquet frequency/strip line estimator module 742 receives the one or more of the calculated propagation delay from design input module 710 and from propagation delay input module 740. Floquet frequency/strip line estimator module 742 determines an estimate of the floquet frequency for the victim and aggressor traces as:

$\begin{matrix} f_{floquet} = \frac{n}{2 t_{delay}}, where n = 1, 2, \dots & Equation 5 \end{matrix}$

and where f_floquetis the estimated floquet frequency and n is an integer that identifies the harmonics of the estimated floquet frequency. Floquet frequency/strip line estimator module 742 determines an estimate of the resonance frequency for the victim and aggressor traces as:

$\begin{matrix} f_{FEXT - trough} = \frac{n}{\frac{l}{v_{E}} - \frac{l}{v_{O}}}, where N = 1, 2, \dots & Equation 6 \\ and where : \\ \frac{l}{v_{E}} - \frac{l}{v_{O}} = l (\frac{1}{\sqrt{(L_{11} + L_{12}) (C_{11} - C_{12})}} - \frac{1}{\sqrt{(L_{11} - L_{12}) (C_{11} + C_{12})}}) & Equation 7 \end{matrix}$

and where L₁₁and C₁₁are the equivalent input inductance and input capacitance, and L₁₂and C₁₂are the equivalent reverse inductance and reverse capacitance.

Frequency comparison module 444 operates to compare the estimated floquet frequency and the estimated FEXT frequency with interface frequencies 418 and 428. If the estimated floquet frequency and the estimated FEXT frequency are not complimentary to one another, then the configuration is likely to result in undesirable insertion loss and crosstalk, and one or more of the victim trace and the aggressor trace is redesigned in trace re-layout module 446.

FIG. 8 illustrates a method of cancelling floquet mode resonance and far end crosstalk, starting at block 802, where trace length information and PCB material information for a strip line circuit trace are provided. The FEXT trough frequency of the strip line circuit trace is computed in block 804. For example, a floquet frequency/strip line estimator module can calculate a FEXT trough frequency as described above. Periodicity information for an angularly routed circuit trace that is coupled to the strip line circuit trace in block 806. The floquet mode resonance frequency of the angularly routed circuit trace is computed in block 808. For example, a floquet frequency/strip line estimator module can calculate a floquet mode resonance frequency as described above. The FEXT trough frequency from block 804, and the floquet mode resonance frequency from block 808 are compared with the operating frequency of one or more of the strip line circuit trace and the angularly routed circuit trace in block 810, and the FEXT trough frequency and the floquet mode resonance frequency are evaluated to determine if the resulting frequency profile is flattened in block 812.

FIG. 9 illustrates a printed circuit board 900 that utilizes microstrip serial links on the surface of the printed circuit board. Printed circuit board 900 includes a core layer 910, a ground trace layer 912, microstrip trace pairs 920 and 930 on the surface of core layer 910. Microstrip trace pairs 920 and 930 represent differential signal trace pairs that are associated with a particular serial data communication interfaces. In a particular embodiment, microstrip trace pairs 920 and 930 represent individual serial data communication lanes. For example, microstrip trace pairs 920 and 930 may represent serial data communication lanes of one or more PCIe serial links, serial ATA (SATA) data communication lanes, USB interfaces, or the like. In a particular embodiment, microstrip trace pairs 920 and 930 are associated together for the transmission of data signals on a common serial communication interface. For example, microstrip trace pairs 920 and 930 may be individual data transmission lanes of a PCIe serial link, such as a PCIe serial link with four lanes (×4), with eight lanes (×8), or with 16 lanes (×16). Note that microstrip trace pairs 920 and 930 are described as transmitting data signals, however, one or more of the microstrip trace pairs may be considered as for receiving data signals, and the attribution as for transmitting or receiving of data signals is arbitrarily ascribed with respect to data flow direction between circuit devices, and the teachings as disclosed herein are applicable equally to pairs of data transmission lanes, to pairs of data receiving lanes, and to one data transmission lane and one data receiving lane.

Printed circuit board 900 is characterized by the fact that core layer 910 has a particular thickness (H) 940 between ground trace layer 912 and the top surface of the printed circuit board. Thickness 940 can be selected based upon various design criteria for the printed circuit board, as described further, below. Printed circuit board 900 is further characterized by an intra-microstrip trace separation (S₁) 942 that represents a minimum spacing for distances between the individual traces that make up the differential signal pair associated with microstrip trace pairs 920 and 930. Intra-microstrip trace separation 942 is defined based upon various design rules, as described further, below. Finally, printed circuit board 900 is characterized by inter-microstrip trace separation (S₂) 944 that represents a minimum spacing for distances between microstrip trace pairs 920 and 930. Inter-microstrip trace separation 944 is also defined based upon various design rules, as described further, below.

Typically, as the speed of serial data communication interfaces increases, design recommendations for printed circuit boards call for wider separations between microstrip trace pairs in order to reduce the crosstalk between the microstrip trace pairs. For example, serial interfaces that operate at 12 gigabits per second (Gbps) may be constrained by a design rule that calls for separation between the microstrip trace pairs of greater than 15H, and serial interfaces that operate at 25 Gbps may be constrained by a design rule that calls for separation between the microstrip trace pairs of greater than 21H. Thus, where a printed circuit board has a typical core layer thickness of 3 mils, the separation between microstrip pairs may be specified to be greater than 45 mils for a 12 Gbps serial data communication interface, and to be greater than 63 mils for a 25 Gbps serial data communication interface. As such, a typical design goal for printed circuit board 900 is to provide for a thinner core layer thickness in order to reduce the absolute value of the inter-microstrip trace separation. However, by providing a thin core layer thickness of, for example, 3 mils, energy from the microstrip trace pairs is strongly coupled to the ground layer, resulting in greater signal crosstalk between the microstrip trace pairs.

In a particular embodiment of printed circuit board 900, core layer thickness (H) 940 is increased and intra-microstrip trace separation (S₁) 942 is reduced, so that a greater portion of the energy in microstrip trace pairs 920 and 930 is coupled within the respective microstrip trace pairs, and the signals are not as strongly coupled to ground trace layer 912. In this way, inter-microstrip trace separation 944 can be significantly decreased without incurring excessive crosstalk. For example, where thickness 940 is provided at 6 mils, and intra-microstrip trace separation 942 is lowered to 0.5H, or 3 mils, inter-microstrip trace separation (S₂) 944 can be reduced to 6H for serial data communication interfaces operating at up to 32 Gbps, without suffering excessive crosstalk. Thus the microstrip trace density on the top surface of printed circuit boards can be successfully increased, thereby making surface routing of serial data links more desirable.

Tables 1-4 illustrate exemplary performance data for various configurations of microstrip trace pairs in printed circuit boards with different core layer thicknesses. Each of tables 1-4 show signal degradation of microstrip trace pairs on exemplary printed circuit boards with core layer thicknesses (H) of 3 mils, 4 mils, 5 mils, and 6 mils. Each exemplary printed circuit board is further provided with microstrip trace pairs that are configured with intra-microstrip trace separations (S₁) that are defined as a ratio of the intra-microstrip trace separation to the core layer thickness (S₁/H). Exemplary ratios of 0.5, 1.0, 2.0, and 10 are provided. Each exemplary printed circuit board is further provided with inter-microstrip trace separations (S₂) that are defined as a ratio of the inter-microstrip trace separation to the core layer thickness (S₂/H). Exemplary ratios of 5 and 10 are provided. Each of tables 1-6 show the signal degradation for each configuration in terms of an output signal percentage of the input signal for near end crosstalk (NEXT) and for far end crosstalk (FEXT). Shaded entries represent configurations which were not modeled. Tables 1 and 4 show the signal degradation for 16 Gbps signaling, tables 2 and 5 show the signal degradation for 25 Gbps signaling, and tables 3 and 6 show the signal degradation for 32 Gbps signaling.

Note that, utilizing a 5H inter-microstrip trace separation ratio (S₂/H), as seen in tables 1-3, an intra-microstrip trace separation ratio (S₁/H) of 2.0 or less provides for acceptable signal degradation of less than 33% for all core layer thicknesses for 16 Gbps signaling, but for 25 and 32 Gbps signaling, an intra-microstrip trace separation ratio (S₁/H) of 0.5 and a core layer thicknesses of 6 mils provides for acceptable signal degradation. Utilizing a 10H inter-microstrip trace separation ratio (S₂/H), as seen in tables 4-6, an intra-microstrip trace separation ratio (S₁/H) of 10 or less provides for acceptable signal degradation for all core layer thicknesses for 16 Gbps signaling, for 25 Gbps signaling, an intra-microstrip trace separation ratio (S₁/H) of 2.0 or less provides for acceptable signal degradation for all core layer thicknesses, and for 32 Gbps signaling, an intra-microstrip trace separation ratio (S₁/H) of 1.0 or less provides for acceptable signal degradation for all core layer thicknesses.

FIG. 10 illustrates a generalized embodiment of information handling system 1000. For purpose of this disclosure information handling system 1000 can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, information handling system 1000 can be a personal computer, a laptop computer, a smart phone, a tablet device or other consumer electronic device, a network server, a network storage device, a switch router or other network communication device, or any other suitable device and may vary in size, shape, performance, functionality, and price. Further, information handling system 1000 can include processing resources for executing machine-executable code, such as a central processing unit (CPU), a programmable logic array (PLA), an embedded device such as a System-on-a-Chip (SoC), or other control logic hardware. Information handling system 1000 can also include one or more computer-readable medium for storing machine-executable code, such as software or data. Additional components of information handling system 1000 can include one or more storage devices that can store machine-executable code, one or more communications ports for communicating with external devices, and various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. Information handling system 1000 can also include one or more buses operable to transmit information between the various hardware components.

Information handling system 1000 can include devices or modules that embody one or more of the devices or modules described above, and operates to perform one or more of the methods described above. Information handling system 1000 includes a processors 1002 and 1004, a chipset 1010, a memory 1020, a graphics interface 1030, include a basic input and output system/extensible firmware interface (BIOS/EFI) module 1040, a disk controller 1050, a disk emulator 1060, an input/output (I/O) interface 1070, and a network interface 1080. Processor 1002 is connected to chipset 1010 via processor interface 1006, and processor 1004 is connected to the chipset via processor interface 1008. Memory 1020 is connected to chipset 1010 via a memory bus 1022. Graphics interface 1030 is connected to chipset 1010 via a graphics interface 1032, and provides a video display output 1036 to a video display 1034. In a particular embodiment, information handling system 1000 includes separate memories that are dedicated to each of processors 1002 and 1004 via separate memory interfaces. An example of memory 1020 includes random access memory (RAM) such as static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NV-RAM), or the like, read only memory (ROM), another type of memory, or a combination thereof.

BIOS/EFI module 1040, disk controller 1050, and I/O interface 1070 are connected to chipset 1010 via an I/O channel 1012. An example of I/O channel 1012 includes a Peripheral Component Interconnect (PCI) interface, a PCI-Extended (PCI-X) interface, a high-speed PCI-Express (PCIe) interface, another industry standard or proprietary communication interface, or a combination thereof. Chipset 1010 can also include one or more other I/O interfaces, including an Industry Standard Architecture (ISA) interface, a Small Computer Serial Interface (SCSI) interface, an Inter-Integrated Circuit (I²C) interface, a System Packet Interface (SPI), a Universal Serial Bus (USB), another interface, or a combination thereof. BIOS/EFI module 1040 includes BIOS/EFI code operable to detect resources within information handling system 1000, to provide drivers for the resources, initialize the resources, and access the resources. BIOS/EFI module 1040 includes code that operates to detect resources within information handling system 1000, to provide drivers for the resources, to initialize the resources, and to access the resources.

Disk controller 1050 includes a disk interface 1052 that connects the disc controller to a hard disk drive (HDD) 1054, to an optical disk drive (ODD) 1056, and to disk emulator 1060. An example of disk interface 1052 includes an Integrated Drive Electronics (IDE) interface, an Advanced Technology Attachment (ATA) such as a parallel ATA (PATA) interface or a serial ATA (SATA) interface, a SCSI interface, a USB interface, a proprietary interface, or a combination thereof. Disk emulator 1060 permits a solid-state drive 1064 to be connected to information handling system 1000 via an external interface 1062. An example of external interface 1062 includes a USB interface, an IEEE 1394 (Firewire) interface, a proprietary interface, or a combination thereof. Alternatively, solid-state drive 1064 can be disposed within information handling system 1000.

I/O interface 1070 includes a peripheral interface 1072 that connects the I/O interface to an add-on resource 1074, to a TPM 1076, and to network interface 1080. Peripheral interface 1072 can be the same type of interface as I/O channel 1012, or can be a different type of interface. As such, I/O interface 1070 extends the capacity of I/O channel 1012 when peripheral interface 1072 and the I/O channel are of the same type, and the I/O interface translates information from a format suitable to the I/O channel to a format suitable to the peripheral channel 1072 when they are of a different type. Add-on resource 1074 can include a data storage system, an additional graphics interface, a network interface card (NIC), a sound/video processing card, another add-on resource, or a combination thereof. Add-on resource 1074 can be on a main circuit board, on separate circuit board or add-in card disposed within information handling system 1000, a device that is external to the information handling system, or a combination thereof.

Network interface 1080 represents a NIC disposed within information handling system 1000, on a main circuit board of the information handling system, integrated onto another component such as chipset 1010, in another suitable location, or a combination thereof. Network interface device 1080 includes network channels 1082 and 1084 that provide interfaces to devices that are external to information handling system 1000. In a particular embodiment, network channels 1082 and 1084 are of a different type than peripheral channel 1072 and network interface 1080 translates information from a format suitable to the peripheral channel to a format suitable to external devices. An example of network channels 1082 and 1084 includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernet channels, proprietary channel architectures, or a combination thereof. Network channels 1082 and 1084 can be connected to external network resources (not illustrated). The network resource can include another information handling system, a data storage system, another network, a grid management system, another suitable resource, or a combination thereof.

Although only a few exemplary embodiments have been described in detail herein, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.

The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover any and all such modifications, enhancements, and other embodiments that fall within the scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

System and Method of Crosstalk Mitigation in Microstrip Serial Links in a Printed Circuit Board

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims