中国保险汽车安全指数CIASI——正面25%偏置碰撞试验规程

合集下载

Intel芯片组大全

Intel芯片组大全

择CPU再选择其他的配件,当然这也没什么不对。

只是选择了CPU就应该选择与之相适应的主板,而其余的配件就必须与主板相配套,那么了解主板芯片组的特性就显得非常重要了。

本文的目的就是让那些购机、升级的菜鸟朋友们了解芯片组特性,再根据自己的需求确定主板,之后,有方向地去选择内存、显卡、硬盘等主要配件。

Intel芯片组:一、845系列芯片组包括:支持SDRAM的845芯片组、支持DDR266的845D芯片组、支持DDR266以及FSB533的845E/G/GL芯片组、支持DDR333以及FSB533的845PE/GE/GV 芯片组等诸多子产品。

845系列芯片组的82845E/82845GL/82845G/82845GV/82845GE/82845PE,除82845GL以外都支持533MHz FSB(82845GL只支持400MHz FSB),支持内存方面,所有845系列北桥都支持最大2GB内存。

82845GL/82845E支持DDR 266,其余都支持DDR 333。

除82845GL/82845GV之外都支持AGP 4X规范。

所有的533Mhz 外频芯片组都将支持Hyper-Threading(超线程技术)。

但对于845G 芯片组来说,即使升级BIOS也不能支持Hyper-Threading ,因为它的硬件架构不允许其支持Hyper-Threading。

而i845E 和850E就可以通过升级BIOS 来获得支持。

Intel将发布845G B-step以取代845G A-step芯片组,而且之后的845GV、GE、PE和Springdale都将支持Hyper-Threading。

845E芯片组对于845D芯片组来说,其实并没有重大改变,仅仅是使用了支持USB2.0的ICH4和支持FSB533而已,但845D芯片组也同样能够支持FSB533,而且经过超频之后内存子系统性能更高,整体甚至超过了845PE芯片组。

Z515中文资料(Intel)中文数据手册「EasyDatasheet - 矽搜」

Z515中文资料(Intel)中文数据手册「EasyDatasheet - 矽搜」

3.3 去耦指南................................................ ............................ 28
3.3.1 3.3.2
V CC 去耦................................................. ........................ 28 FSB AGTL +解耦............................................... ............... 28
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order. Copie s of docum ents which have an orde r num be r and are re fere nce d in this docum ent, or othe r Inte l lite rature , m ay be obtaine d
Hyper-Threading Technology requires a com puter system with a processor supporting Hyper-Threading Technology and HT Technology enabled chipset, BIO S and operating system . Perform ance will vary depending on the specific hardware and software

千元级游戏猛将 ROG STRIX B25OH GAMING主板

千元级游戏猛将 ROG STRIX B25OH GAMING主板
DDR 42 4 0 O )
显卡插槽
P C[ 县3 . 0x 1 6× 1 P Cf e3 . 0x 4 叫
扩展 接口
PC l e3 . 0x l x 4
3 2 Gb / sM . 2 x1
M. 2× 1 S A T A6 Gb p s x6
音频芯片
R OG Su p r eme F X S1 2 2 ( ) A
为用户提供了6 个SA T A接口 ,
3 . O) , 足够大部 分玩家使用 。
器、 DDR4 2 4 0 0内 存 , 通 过 F F T S进行 了半小 时满 载 烤机
r i me 9 5 l n - l o l a c e l a r g e 1 2 个USB接 口 ( 包含 6 个USB 运行 P
44 3
1 6 69
相供 电 。 B2 5 0H GAM i NG主 板 最 大 是 采用 了足够 多 的7 该主板 还搭 配了数颗5 K 的 变 化 是 采 用 了 B25 0芯 片 同时 ,
全 封 闭电 感 。 组。 与 Z2 7 O 相比 , B2 5 0 芯 片 军规 固态 电容 、 组缺 少处 理器 超 频能 力 , 但仍 我 们 采 用 Cor e j 5 - 7 50 0 处理
8 , ห้องสมุดไป่ตู้L a音频芯片
网络芯片
英特尔 } 2 1 g V 千兆网卡
背板 接口
U S B 2 . 0 + US B 3 . 0 + L AN+
模拟音频7 . 1 声道 接 口+ S I P DI F 光纤输出
+ HD Ml + Dp + DV 1 - 0 ) + P S / 2

Atmel AT25128B 256B 131K 16K 电池电源 EEPROM 数据手册说明书

Atmel AT25128B 256B 131K 16K 电池电源 EEPROM 数据手册说明书

AT25128B and AT25256BSPI Serial EEPROM128K (16,384 x 8), 256K (32,768 x 8)DATASHEET Features●Serial Peripheral Interface (SPI) Compatible●Supports SPI Modes 0 (0,0) and 3 (1,1)Data Sheet Describes Mode 0 Operation●Low-voltage and Standard-voltage OperationV CC = 1.8V to 5.5V●20MHz Clock Rate (5V)●64-byte Page Mode and Byte Write Operation●Block Write ProtectionProtect 1/4, 1/2, or Entire Array●Write Protect (WP) Pin and Write Disable Instructions for Both Hardware andSoftware Data Protection●Self-timed Write Cycle (5ms max)●High ReliabilityEndurance: 1,000,000 Write CyclesData Retention: 100 Years●Green (Pb/Halogen-free/RoHS Compliant) Packaging Options●Die Sales: Wafer Form, Waffle Pack, and Bumped WafersDescriptionThe Atmel® AT25128B/256B provides 131,072/262,144 bits of Serial Electrically Erasable Programmable Read-Only Memory (EEPROM) organized as16,384/32,768 words of 8 bits each. The device is optimized for use in many industrial and commercial applications where low-power and low-voltage operation are essential. The AT25128B/256B is available in space saving JEDEC SOIC, TSSOP, UDFN, and VFBGA packages.The AT25128B/256B is enabled through the Chip Select pin (CS) and accessed via a 3-Wire interface consisting of Serial Data Input (SI), Serial Data Output (SO), and Serial Clock (SCK). All programming cycles are completely self-timed, and no separate erase cycle is required before write.Block Write protection is enabled by programming the status register with one of four blocks of Write Protection. Separate Program Enable and Program Disable instructions are provided for additional data protection. Hardware Data Protection is provided via the WP pin to protect against inadvertent write attempts. The HOLD pin may be used to suspend any serial communication without resetting the serial sequence.AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_01201521.Pin ConfigurationsTable 1-1.Pin Configurations 2.Absolute Maximum Ratings*Operating Temperature . . . . . . . . . . .-55︒C to +125︒C Storage Temperature. . . . . . . . . . . . .-65︒C to +150︒C Voltage on any pinwith respect to ground . . . . . . . . . . . . . -1.0V to +7.0V Maximum Operating Voltage . . . . . . . . . . . . . . . 6.25V DC Output Current. . . . . . . . . . . . . . . . . . . . . . .5.0mA*Notice:Stresses beyond those listed under “AbsoluteMaximum Ratings” may cause permanent damage to the device. This is a stress rating only and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of this specification is not implied. Exposure to absolute maximum rating conditions forextended periods may affect device reliability.Note: Drawings are not to scale.8-lead SOICCS SO WP GNDV CC HOLD SCK SI12348765Top ViewTop View8-lead TSSOP12348765CS SO WP GNDV CC HOLD SCK SIV CC HOLD SCK SICS SO WP GND123487658-ball VFBGABottom View8-pad UDFNBottom ViewV CC HOLD SCK SI CS SO WP GND123487653AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_0120153.Block DiagramFigure 3-1.Block DiagramV CCAT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_01201544.Electrical Characteristics4.1Pin Capacitance (1)Table 4-1.Pin CapacitanceNote:1.This parameter is characterized and is not 100% tested.4.2DC CharacteristicsTable 4-2.DC CharacteristicsNote:1.V IL min and V IH max are reference only and are not tested.Applicable over recommended operating range from T A = 25°C, f = 1MHz, V CC = +5V (unless otherwise noted).Applicable over recommended operating range from: T AI = -40︒C to +85︒C, V CC = +1.8V to +5.5V, (unless otherwise noted).5AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_0120154.3AC CharacteristicsTable 4-3.AC CharacteristicsApplicable over recommended operating range from T AI = -40 to +85°C, V CC = As Specified, CL = 1 TTL Gate and 30pF (unless otherwise noted).AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_0120156Note:1.This parameter is characterized and is not 100% tested.5.Serial Interface DescriptionMaster: The device that generates the serial clock.Slave: Because the Serial Clock pin (SCK) is always an input, the AT25128B/256B always operates as a slave.Transmitter/Receiver: The AT25128B/256B has separate pins designated for data transmission (SO) and reception (SI).MSB: The Most Significant Bit (MSB) is the first bit transmitted and received.Serial Opcode: After the device is selected with CS going low, the first byte will be received. This byte contains the opcode which defines the operations to be performed.Invalid Opcode: If an invalid opcode is received, no data will be shifted into the AT25128B/256B, and the serial output pin (SO) will remain in a high-impedance state until the falling edge of CS is detected again. This will reinitialize the serial communication.Chip Select: The AT25128B/256B is selected when the CS pin is low. When the device is not selected, data will not be accepted via the SI pin, and the SO pin will remain in a high-impedance state.Hold: The HOLD pin is used in conjunction with the CS pin to select the AT25128B/256B. When the device is selected and a serial sequence is underway, HOLD can be used to pause the serial communication with the master device without resetting the serial sequence. To pause, the HOLD pin must be brought low while the SCK pin is low. To resume serial communication, the HOLD pin is brought high while the SCK pin is low (SCK may still toggle during HOLD). Inputs to the SI pin will be ignored while the SO pin is in the high-impedance state.Write Protect: The Write Protect pin (WP) will allow normal read/write operations when held high. When the WP pin is brought low and WPEN bit is one, all write operations to the status register are inhibited. WP going low while CS is still low will interrupt a write to the status register. If the internal write cycle has already been initiated, WP going low will have no effect on any write operation to the status register. The WP pin function is blocked when the WPEN bit in the status register is zero. This will allow the user to install the AT25128B/256B in a system with the WP pin tied to ground and still be able to write to the status register. All WP pin functions are enabled when the WPEN bit is set to one.Table 4-3.AC Characteristics (Continued)Applicable over recommended operating range from T AI = -40 to +85°C, V CC = As Specified, CL = 1 TTL Gate and 30pF (unless otherwise noted).7AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_012015Figure 5-1.SPI Serial InterfaceMaster :MicrocontrollerSlave :AT25128B/256BAT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_01201586.Functional DescriptionThe AT25128B/256B is designed to interface directly with the synchronous Serial Peripheral Interface (SPI) of the 6800 series of microcontrollers.The AT25128B/256B utilizes an 8-bit instruction register. The list of instructions and their operation codes are contained in Figure 6-1. All instructions, addresses, and data are transferred with the MSB first and start with a high-to-low CS transition.Table 6-1.Instruction Set for the AT25010B/020B/040BWrite Enable (WREN): The device will power-up in the Write Disable state when V CC is applied. Allprogramming instructions must therefore be preceded by a Write Enable instruction. The WP pin must be held high during a WREN instruction.Write Disable (WRDI): To protect the device against inadvertent writes, the Write Disable instruction disables all programming modes. The WRDI instruction is independent of the status of the WP pin.Read Status Register (RDSR): The Read Status Register instruction provides access to the status register. The Read/Busy and Write Enable status of the device can be determined by the RDSR instruction. Similarly, the Block Write Protection bits indicate the extent of protection employed. These bits are set by using the WRSR instruction.Table 6-2.Status Register FormatTable 6-3.Read Status Register Bit Definition9AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_012015Write Status Register (WRSR): The WRSR instruction allows the user to select one of four levels of protection. The AT25128B/256B is divided into four array segments. None, one-quarter (¼), one-half (½), or all of the memory segments can be protected. Any of the data within any selected segment will therefore be read-only. The block write protection levels and corresponding status register control bits are shown in Table 6-4.Bits BP1, BP0, and WPEN are nonvolatile cells that have the same properties and functions as the regular memory cells (e.g., WREN, t WC , RDSR).Table 6-4.Block Write Protect BitsThe WRSR instruction also allows the user to enable or disable the write protect (WP) pin through the use of the Write Protect Enable (WPEN) bit. Hardware write protection is enabled when the WP pin is low and the WPEN bit is one. The hardware write protection is disabled when either the WP pin is high or the WPEN bit is zero. When the device is hardware write protected, writes to the Status Register including the Block Protect bits, the WPEN bit, and the block protected sections in the memory array are disabled. Writes are only allowed to sections of the memory which are not block-protected.Note:When the WPEN bit is hardware write protected, it cannot be changed back to zero as long as the WP pin is held low.Table 6-5.WPEN Operation Read Sequence (READ): Reading the AT25128B/256B via the SO pin requires the following sequence. After the CS line is pulled low to select a device, the Read opcode is transmitted via the SI line followed by the byte address to be read (Table 6-6). Upon completion, any data on the SI line will be ignored. The data (D7 – D0) at the specified address is then shifted out onto the SO line. If only one byte is to be read, the CS line should be driven high after the data comes out. The Read Sequence can be continued since the byte address isautomatically incremented and data will continue to be shifted out. When the highest address is reached, the address counter will roll-over to the lowest address allowing the entire memory to be read in one continuous read cycle.AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_01201510Write Sequence (WRITE): In order to program the AT25128B/256B, the Write Protect pin (WP) must be held high and two separate instructions must be executed. First, the device must be write enabled via the WREN instruction. Then a Write (WRITE) instruction may be executed. Also, the address of the memory location(s) to be programmed must be outside the protected address field location selected by the Block Write Protection level. During an internal write cycle, all commands will be ignored except the RDSR instruction.A Write instruction requires the following sequence. After the CS line is pulled low to select the device, the Write opcode is transmitted via the SI line followed by the byte address and the data (D7 D0) to be programmed (see Table 6-6 for the address key). Programming will start after the CS pin is brought high. The low-to-hightransition of the CS pin must occur during the SCK low time immediately after clocking in the D0 (LSB) data bit.The Ready/Busy status of the device can be determined by initiating a Read Status Register (RDSR)instruction. If Bit 0 is one, the write cycle is still in progress. If Bit 0 is zero, the write cycle has ended. Only the RDSR instruction is enabled during the write programming cycle.The AT25128B/256B is capable of an 64-byte Page Write operation. After each byte of data is received, the six low-order address bits are internally incremented by one; the high-order bits of the address will remain constant. If more than 64 bytes of data are transmitted, the address counter will roll-over, and the previously written data will be overwritten. The AT25128B/256B is automatically returned to the Write Disable state at the completion of a write cycle.Note:If the WP pin is brought low or if the device is not Write Enabled (WREN), the device will ignore the Write instruction and will return to the standby state, when CS is brought high. A new CS falling edge is required to reinitiate the serial communication.Table 6-6.Address Key7.Timing Diagrams — SPI Mode 0 (0,0)Figure 7-1.Synchronous Data Timing (for Mode 0)Figure 7-2.WREN TimingFigure 7-3.WRDI TimingSOSISCKCSV V ILV V ILV V ILV V SOSISCK CSWREN OpcodeHI-ZSOSISCK CSWRDI OpcodeHI-ZAT25128B/256B [DATASHEET]12Figure 7-5.WRSR TimingFigure 7-6.READ TimingSOSISCKCSSOSISCKCSInstruction76543210Data InHigh-impedanceMSBSOSI SCKCSFigure 7-8.HOLD TimingSOSISCKCSInstructionByte AddressData InHigh-impedance7654321015 14 13 (3)210HOLDSOSCKCSt HDAT25128B/256B [DATASHEET]148.Ordering Code DetailAtmel DesignatorProduct FamilyDevice DensityDevice RevisionShipping Carrier OptionOperating Voltage128 = 128 kilobit 256 = 256 kilobit25 = Standard SPI Serial EPPROMB or Blank = Bulk (Tubes)T = Tape and Reel, Standard Quantity Option E = Tape and Reel, Expanded Quantity OptionL = 1.8V to 5.5VPackage Device Grade or Wafer/Die ThicknessH = Green, NiPdAu Lead Finish, Industrial Temperature Range (-40°C to +85°C)U = Green, Matte Sn Lead Finish, Industrial Temperature Range (-40°C to +85°C)11 = 11mil Wafer ThicknessPackage OptionSS = JEDEC SOIC X = TSSOP MA = UDFN C = VFBGAWWU = Wafer UnsawnWDT = Die in Tape and ReelA T 25128B -S S H L -B9.Part MarkingsNote: 1.Contact Atmel Sales for Wafer sales.AT25128B/256B [DATASHEET]1611.18S1 — 8-lead JEDEC SOICAT25128B/256B [DATASHEET]1811.28X — 8-lead TSSOP11.38MA2 — 8-pad UDFNAT25128B/256B [DATASHEET]2011.48U2-1 — 8-ball VFBGA21AT25128B/256B [DATASHEET]Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_01201512.Revision HistoryX X X X X XAtmel Corporation 1600 Technology Drive, San Jose, CA 95110 USA T: (+1)(408) 441.0311F: (+1)(408) 436.4200| © 2015 Atmel Corporation. / Rev.: Atmel-8698E-SEEPROM-AT25128B-256B-Datasheet_012015.Atmel ®, Atmel logo and combinations thereof, Enabling Unlimited Possibilities ®, and others are registered trademarks or trademarks of Atmel Corporation in U.S. and other countries. Other terms and product names may be trademarks of others.DISCLAIMER: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN THE ATMEL TERMS AND CONDITIONS OF SALES LOCATED ON THE ATMEL WEBSITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS AND PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and products descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Unless specifically provided otherwise, Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel products are not intended,authorized, or warranted for use as components in applications intended to support or sustain life.SAFETY-CRITICAL, MILITARY, AND AUTOMOTIVE APPLICATIONS DISCLAIMER: Atmel products are not designed for and will not be used in connection with any applications where the failure of such products would reasonably be expected to result in significant personal injury or death (“Safety-Critical Applications”) without an Atmel officer's specific written consent. Safety-Critical Applications include, without limitation, life support devices and systems, equipment or systems for the operation of nuclear facilities and weapons systems.Atmel products are not designed nor intended for use in military or aerospace applications or environments unless specifically designated by Atmel as military-grade. Atmel products are not designed nor intended for use in automotive applications unless specifically designated by Atmel as automotive-grade.。

Mellanox -ib驱动安装手册linux

Mellanox -ib驱动安装手册linux

Mellanox OFED for Linux Installation GuideRev 1.5.1Mellanox Technologies350 Oakmead Parkway, Suite 100Sunnyvale, CA 94085U.S.A.Tel: (408) 970-3400Fax: (408) 970-3403Mellanox Technologies, Ltd.PO Box 586 Hermon Building Yokneam 20692Israel Tel: +972-4-909-7200Fax: +972-4-959-3245© Copyright 2010. Mellanox Technologies, Inc. All Rights Reserved.Mellanox®, BridgeX®, ConnectX®, InfiniBlast®, InfiniBridge®, InfiniHost®, InfiniPCI®, InfiniRISC®, InfiniScale®, andVirtual Protocol Interconnect are registered trademarks of Mellanox Technologies, Ltd.CORE-Direct , FabricIT, and PhyX are trademarks of Mellanox Technologies, Ltd.All other marks and names mentioned herein may be trademarks of their respective companies.Document Number: 2914Rev 1.5.1Mellanox Technologies 2NOTE:THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PRO-VIDED BY MELLANOX TECHNOLOGIES “AS-IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUS-TOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO(S) AND/OR THE SYSTEM USING IT. THEREFORE, MELLANOX TECHNOLOGIES CAN-NOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY . ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING , BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-CHANTABILITY , FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEM-PLARY , OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING , BUT NOT LIMITED TO, PAYMENT FOR PROCURE-MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY , WHETHER IN CONTRACT, STRICT LIABILITY , OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Mellanox OFED for Linux User’s Manual Rev 1.5.1 InstallationThis chapter describes how to install and test the Mellanox OFED for Linux package on a singlehost machine with Mellanox InfiniBand and/or Ethernet adapter hardware installed. The chapterincludes the following sections:•“Hardware and Software Requirements” (page 3)•“Downloading Mellanox OFED” (page 4)•“Installing Mellanox OFED” (page 4)•“Uninstalling Mellanox OFED” (page 15)Hardware and Software RequirementsHardware RequirementsPlatforms• A server platform with an adapter card based on one of the following Mellanox Technologies’InfiniBand HCA devices:-MT25408 ConnectX®-2 (VPI, IB, EN, FCoE) (firmware: fw-ConnectX2)-MT25408 ConnectX® (VPI, IB, EN, FCoE) (firmware: fw-25408)-MT25208 InfiniHost® III Ex (firmware: fw-25218 for Mem-Free cards, and fw-25208 for cards withmemory)-MT25204 InfiniHost® III Lx (firmware: fw-25204)-MT23108 InfiniHost® (firmware: fw-23108)Note For the list of supported architecture platforms, please refer to the Mellanox OFEDRelease Notes file.Required Disk Space for Installation•400MBSoftware RequirementsOperating System•Linux operating systemNote For the list of supported operating system distributions and kernels, please refer to the Mellanox OFED Release Notes file.Installer Privileges•The installation requires administrator privileges on the target machineMellanox Technologies3Rev 1.5.1Mellanox Technologies 4Downloading Mellanox OFEDStep 1.Verify that the system has a Mellanox network adapter (HCA/NIC) installed by ensuringthat you can see ConnectX or InfiniHost entries in the display.The following example shows a system with an installed Mellanox HCA:host1# lspci -v | grep Mellanox02:00.0 InfiniBand: Mellanox Technologies MT25418 [ConnectX IB DDR, PCIe 2.0 2.5GT/s] (reva0)Step 2.Download the ISO image to your host.The image’s name has the format MLNX_OFED_LINUX-<ver>-<OS label>.iso. You candownload it from > Products > IB SW/Drivers.Step e the md5sum utility to confirm the file integrity of your ISO image. Run the followingcommand and compare the result to the value provided on the download page.host1$ md5sum MLNX_OFED_LINUX-<ver>-<OS label>.isoInstalling Mellanox OFEDThe installation script, mlnxofedinstall , performs the following:•Discovers the currently installed kernel•Uninstalls any software stacks that are part of the standard operating system distribution oranother vendor's commercial stack•Installs the MLNX_OFED_LINUX binary RPMs (if they are available for the current kernel)•Identifies the currently installed InfiniBand and Ethernet network adapters and automatically 1upgrades the firmwarePre-installation Notes•The installation script removes all previously installed Mellanox OFED packages and re-installsfrom scratch. You will be prompted to acknowledge the deletion of the old packages.Note Pre-existing configuration files will be saved with the extension “.conf.saverpm”.•If you need to install Mellanox OFED on an entire (homogeneous) cluster, a common strategy isto mount the ISO image on one of the cluster nodes and then copy it to a shared file system suchas NFS. To install on all the cluster nodes, use cluster-aware tools (such as pdsh).•If your kernel version does not match with any of the offered pre-built RPMs, you can add yourkernel version by using the “mlnx_add_kernel_support.sh ” script located under the docs/directory.Usage:mlnx_add_kernel_support.sh -i|--iso <mlnx iso>[-t|--tmpdir <local work dir>][-v|--verbose]1.The firmware will not be updated if you run the install script with the ‘--without-fw-update’ option.Mellanox OFED for Linux User’s Manual Rev 1.5.1 ExampleThe following command will create a MLNX_OFED_LINUX ISO image for RedHat 5.4 underthe/tmp directory.MLNX_OFED_LINUX-1.5.1-rhel5.4/docs/mlnx_add_kernel_support.sh -i/mnt/MLNX_OFED_LINUX-1.5.1-rhel5.4.isoAll Mellanox, OEM, OFED, or Distribution IB packages will be removed.Do you want to continue?[y/N]:yRemoving OFED RPMs...Running mkisofs...Created /tmp/MLNX_OFED_LINUX-1.5.1-rhel5.4.isoInstallation ScriptMellanox OFED includes an installation script called mlnxofedinstall. Its usage is describedbelow. You will use it during the installation procedure described in Section , “Installation Proce-dure,” on page 6.Usage./mlnxofedinstall [OPTIONS]Note If no options are provided to the script, then all available RPMs are installed.Options-c|--config <packages config_file>Example of the configuration file can be found under docs -n|--net <network config file>Example of the network configuration file can be foundunder docs-p|--print-available Print available packages for the current platform and cre-ate a corresponding ofed.conf file. The installation scriptexits after creating ofed.conf.--with-fc Install FCoE support — Available on RHEL5.2 ONLY--with-32bit Install 32-bit libraries (default). This is relevant forx86_64 and ppc64 platforms.--without-32bit Skip 32-bit libraries installation--without-ib-bonding Skip ib-bonding RPM installation--without-depcheck Skip Distro's libraries check--without-fw-update Skip firmware update--force-fw-update Force firmware update--force Force installation (without querying the user)--all Install all kernel modules, libibverbs, libibumad, librd-macm, mft, mstflint, diagnostic tools, OpenSM, ib-bonding,MVAPICH, Open MPI, MPI tests, MPI selector, perftest, sdp-netstat and libsdp srptools, rds-tools, static and dynamiclibrariesMellanox Technologies5Rev 1.5.1Mellanox Technologies6--hpc Install all kernel modules, libibverbs, libibumad, librd-macm, mft, mstflint, diagnostic tools, OpenSM , ib-bonding,MVAPICH, Open MPI, MPI tests, MPI selector, dynamic librar-ies--basic Install all kernel modules, libibverbs, libibumad, mft,mstflint, dynamic libraries--msmInstall all kernel modules, libibverbs, libibumad, mft,mstflint, diagnostic tools, OpenSM , ib-bonding, dynamiclibrariesNOTE: With --msm flag, the OpenSM daemon is configured torun upon boot.-v|-vv|-vvvSet verbosity level -q Set quiet - no messages will be printed mlnxofedinstall Return CodesTable 1 lists the mlnxofedinstall script return codes and their meanings.Installation ProcedureStep 1.Login to the installation machine as root.Step 2.Mount the ISO image on your machine host1# mount -o ro,loop MLNX_OFED_LINUX-<ver>-<OS label>.iso /mntNote After mounting the ISO image, /mnt will be a Read Only folder.Step 3.Run the installation scripthost1# /mnt/mlnxofedinstallThis program will install the MLNX_OFED_LINUX package on your machine.Note that all other Mellanox, OEM, OFED, or Distribution IB packages will be removed.Do you want to continue?[y/N]:yUninstalling the previous version of OFEDTable 1 - mlnxofedinstall Return CodesReturn CodeMeaning 0The Installation ended successfully 1The installation failed 2No firmware was found for the adapter device 3Failed to start the mst driverMellanox OFED for Linux User’s Manual Rev 1.5.1 Starting MLNX_OFED_LINUX-1.5.1-rc6 installation ...Installing kernel-ib RPMPreparing... ########################################### [100%]1:kernel-ib ########################################### [100%]Installing kernel-ib-devel RPMPreparing... ########################################### [100%]1:kernel-ib-devel ########################################### [100%]Installing mft RPMPreparing... ########################################### [100%]1:mft ########################################### [100%]Installing mpi-selector RPMPreparing... ########################################### [100%]1:mpi-selector ########################################### [100%]Install user level RPMs:Preparing... ########################################### [100%]1:libibumad ########################################### [100%]Preparing... ########################################### [100%]1:libibumad ########################################### [100%]Preparing... ########################################### [100%]1:libibmad ########################################### [100%]Preparing... ########################################### [100%]1:libibmad ########################################### [100%]Preparing... ########################################### [100%]1:libibumad-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibumad-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibmad-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibmad-devel ########################################### [100%]Preparing... ########################################### [100%]1:ofed-scripts ########################################### [100%]Preparing... ########################################### [100%]1:libibverbs ########################################### [100%]Preparing... ########################################### [100%]1:libibverbs ########################################### [100%]Preparing... ########################################### [100%]1:libibverbs-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibverbs-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibverbs-devel-static########################################### [100%]Preparing... ########################################### [100%]1:libibverbs-devel-static########################################### [100%]Preparing... ########################################### [100%]1:libibverbs-utils ########################################### [100%]Preparing... ########################################### [100%]1:libmthca ########################################### [100%]Mellanox Technologies7Rev 1.5.1Mellanox Technologies8Preparing... ########################################### [100%]1:libmthca ########################################### [100%]Preparing... ########################################### [100%]1:libmthca-devel-static ########################################### [100%]Preparing... ########################################### [100%]1:libmthca-devel-static ########################################### [100%]Preparing... ########################################### [100%]1:libmlx4 ########################################### [100%]Preparing... ########################################### [100%]1:libmlx4 ########################################### [100%]Preparing... ########################################### [100%]1:libmlx4-devel ########################################### [100%]Preparing... ########################################### [100%]1:libmlx4-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibcm ########################################### [100%]Preparing... ########################################### [100%]1:libibcm ########################################### [100%]Preparing... ########################################### [100%]1:libibcm-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibcm-devel ########################################### [100%]Preparing... ########################################### [100%]1:libibumad-static ########################################### [100%]Preparing... ########################################### [100%]1:libibumad-static ########################################### [100%]Preparing... ########################################### [100%]1:libibmad-static ########################################### [100%]Preparing... ########################################### [100%]1:libibmad-static ########################################### [100%]Preparing... ########################################### [100%]1:ibsim ########################################### [100%]Preparing... ########################################### [100%]1:librdmacm ########################################### [100%]Preparing... ########################################### [100%]1:librdmacm ########################################### [100%]Preparing... ########################################### [100%]1:librdmacm-utils ########################################### [100%]Preparing... ########################################### [100%]1:librdmacm-devel ########################################### [100%]Preparing... ########################################### [100%]1:librdmacm-devel ########################################### [100%]Preparing... ########################################### [100%]1:libsdp ########################################### [100%]Preparing... ########################################### [100%]1:libsdp ########################################### [100%]Preparing... ########################################### [100%]1:libsdp-devel ########################################### [100%]Preparing... ########################################### [100%]1:libsdp-devel ########################################### [100%]Mellanox OFED for Linux User’s Manual Rev 1.5.1Preparing... ########################################### [100%]1:opensm-libs ########################################### [100%]Preparing... ########################################### [100%]1:opensm-libs ########################################### [100%]Preparing... ########################################### [100%]1:opensm ########################################### [100%]opensmd 0:off 1:off 2:off 3:off 4:off 5:off 6:offPreparing... ########################################### [100%]1:opensm-devel ########################################### [100%]Preparing... ########################################### [100%]1:opensm-devel ########################################### [100%]Preparing... ########################################### [100%]1:opensm-static ########################################### [100%]Preparing... ########################################### [100%]1:opensm-static ########################################### [100%]Preparing... ########################################### [100%]1:compat-dapl ########################################### [100%]Preparing... ########################################### [100%]1:compat-dapl ########################################### [100%]Preparing... ########################################### [100%]1:compat-dapl-devel ########################################### [100%]Preparing... ########################################### [100%]1:compat-dapl-devel ########################################### [100%]Preparing... ########################################### [100%]1:dapl ########################################### [100%]Preparing... ########################################### [100%]1:dapl ########################################### [100%]Preparing... ########################################### [100%]1:dapl-devel ########################################### [100%]Preparing... ########################################### [100%]1:dapl-devel ########################################### [100%]Preparing... ########################################### [100%]1:dapl-devel-static ########################################### [100%]Preparing... ########################################### [100%]1:dapl-devel-static ########################################### [100%]Preparing... ########################################### [100%]1:dapl-utils ########################################### [100%]Preparing... ########################################### [100%]1:perftest ########################################### [100%]Preparing... ########################################### [100%]1:mstflint ########################################### [100%]Preparing... ########################################### [100%]1:sdpnetstat ########################################### [100%]Preparing... ########################################### [100%]1:srptools ########################################### [100%]Preparing... ########################################### [100%]1:rds-tools ########################################### [100%]Preparing... ########################################### [100%]1:rnfs-utils ########################################### [100%]Preparing... ########################################### [100%]Mellanox Technologies9Rev 1.5.1Mellanox Technologies 10 1:ibutils ########################################### [100%]Preparing... ########################################### [100%]1:ibutils2 ########################################### [100%]Preparing... ########################################### [100%]1:ibdump ########################################### [100%]Preparing... ########################################### [100%]1:infiniband-diags ########################################### [100%]Preparing... ########################################### [100%]1:qperf ########################################### [100%]Preparing... ########################################### [100%]1:mlnxofed-docs ########################################### [100%]Preparing... ########################################### [100%]1:mvapich_gcc ########################################### [100%]Preparing... ########################################### [100%]1:mvapich_pgi ########################################### [100%]Preparing... ########################################### [100%]1:mvapich_intel ########################################### [100%]Preparing... ########################################### [100%]1:openmpi_gcc ########################################### [100%]Preparing... ########################################### [100%]1:openmpi_pgi ########################################### [100%]Preparing... ########################################### [100%]1:openmpi_intel ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_mvapich_gcc ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_mvapich_pgi ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_mvapich_intel ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_openmpi_gcc ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_openmpi_pgi ########################################### [100%]Preparing... ########################################### [100%]1:mpitests_openmpi_intel ########################################### [100%]Device (15b3:634a):02:00.0 InfiniBand: Mellanox Technologies MT25418 [ConnectX IB DDR, PCIe 2.0 2.5GT/s] (rev a0)Link Width: 8xLink Speed: 2.5Gb/sInstallation finished successfully.Programming HCA firmware for /dev/mst/mt25418_pci_cr0 deviceRunning: mlxburn -d /dev/mst/mt25418_pci_cr0 -fw /tmp/MLNX_OFED_LINUX-1.5.1/MLNX_OFED_LINUX-1.5.1-sles11/firmware/fw-25408/2_7_000/fw-25408-rel.mlx -dev_type 25408 -no-I- Querying device ...-I- Using auto detected configuration file: /tmp/MLNX_OFED_LINUX-1.5.1/MLNX_OFED_LINUX-1.5.1-sles11/firmware/fw-25408/2_7_000/MHGH28-XTC_A4-A7.ini (PSID = MT_04A0140005)-I- Generating image ...Current FW version on flash: 2.6.0New FW version: 2.7.0Burning FW image without signatures - OKRestoring signature - OK-I- Image burn completed successfully.Please reboot your system for the changes to take effect.warning: /etc/infiniband/openib.conf saved as /etc/infiniband/openib.conf.rpmsaveNote In case your machine has the latest firmware, no firmware update will occur and the installation script will print at the end of installation a message similar to the following:...Installation finished successfully.The firmware version 2.7.000 is up to date.Note: To force firmware update use '--force-fw-update' flag.Note In case your machine has an unsupported network adapter device, no firmware update will occur and the error message below will be printed. Please contact your hardwarevendor for help on firmware updates.Error message:-I- Querying device ...-E- Can't auto detect fw configuration file: ...Step 4.In case the installation script performed firmware updates to your network adapter hard-ware, it will ask you to reboot your machine.Step 5.The script adds the following lines to /etc/security/limits.conf for the userspace components such as MPI:* soft memlock unlimited* hard memlock unlimitedThese settings unlimit the amount of memory that can be pinned by a user space application.If desired, tune the value unlimited to a specific amount of RAM.Step 6.For your machine to be part of the InfiniBand/VPI fabric, a Subnet Manager must be run-ning on one of the fabric nodes. At this point, Mellanox OFED for Linux has alreadyinstalled the OpenSM Subnet Manager on your machine. For details on starting OpenSM,see Chapter 12, “OpenSM – Subnet Manager”.Step 7.(InfiniBand only) Run the hca_self_test.ofed utility to verify whether or not the InfiniBand link is up. The utility also checks for and displays additional information suchas•HCA firmware version•Kernel architecture•Driver version•Number of active HCA ports along with their states•Node GUIDNote For more details on hca_self_test.ofed, see the file hca_self_test.readme under docs/.host1# /usr/bin/hca_self_test.ofed---- Performing InfiniBand HCA Self Test ----Number of HCAs Detected (1)PCI Device Check ....................... PASSKernel Arch ............................ x86_64Host Driver Version .................... MLNX_OFED_LINUX-1.5.1 (OFED-1.5.1-mlnx9) 1.5.1-2.6.9_89.ELlargesmpHost Driver RPM Check .................. PASSHCA Firmware on HCA #0 ................. 2.7.000HCA Firmware Check on HCA #0 ........... PASSHost Driver Initialization ............. PASSNumber of HCA Ports Active 0Port State of Port #0 on HCA #0 ........ INITPort State of Port #0 on HCA #0 ........ DOWNError Counter Check on HCA #0 .......... PASSKernel Syslog Check .................... PASSNode GUID on HCA #0 .................... 00:02:c9:03:00:00:10:e0------------------ DONE ---------------------Note After the installer completes, information about the Mellanox OFED installation such as prefix, kernel version, and installation parameters can be retrieved by running the com-mand /etc/infiniband/info.Installation ResultsSoftware•The OFED and MFT packages are installed under the /usr directory.•The kernel modules are installed under:-InfiniBand subsystem:/lib/modules/`uname -r`/updates/kernel/drivers/infiniband/-mlx4 driver:Under /lib/modules/`uname -r`/updates/kernel/drivers/net/mlx4you will find mlx4_core.ko, mlx4_en.ko, mlx4_ib.ko (and mlx4_fc ifyou ran the installation script with --with-fc)-RDS:/lib/modules/`uname -r`/updates/kernel/net/rds/rds.ko-Bonding module:/lib/modules/`uname -r`/updates/kernel/drivers/net/bonding/bonding.ko •The package kernel-ib-devel include files are placed under /usr/src/ofa_kernel/include/. These include files should be used when building kernel modules that use the stack. (Note that the include files, if needed, are “backported” to your kernel.)•The raw package (un-backported) source files are placed under/usr/src/ofa_kernel-<ver>•The script openibd is installed under /etc/init.d/. This script can be used to load and unload the software stack.•The script connectx_port_config is installed under /sbin. This script can be used to con-figure the ports of ConnectX network adapter cards to Ethernet and/or InfiniBand. For details on this script, please see Section 3.1, “Port Type Management”.•The directory /etc/infiniband is created with the files info and openib.conf and con-nectx.conf. The info script can be used to retrieve Mellanox OFED installation information. The openib.conf file contains the list of modules that are loaded when the openibd script is used. The connectx.conf file saves the ConnectX adapter card’s ports configuration to Ether-net and/or InfiniBand. This file is used at driver start/restart (/etc/init.d/openibd start) .•The file 90-ib.rules is installed under /etc/udev/rules.d/•If OpenSM is installed, the daemon opensmd is installed under /etc/init.d/ and opensm.conf is installed under /etc.•If IPoIB configuration files are included, ifcfg-ib<n> files will be installed under:-/etc/sysconfig/network-scripts/ on a RedHat machine-/etc/sysconfig/network/ on a SuSE machine•The installation process unlimits the amount of memory that can be pinned by a user space application. See Step 5.•Man pages will be installed under /usr/share/man/Firmware•The firmware of existing network adapter devices will be updated if the following two condi-tions are fullfilled:1. You run the installation script in default mode; that is, without the option‘--without-fw-update’.2. The firmware version of the adapter device is older than the firmware version includedwiththe Mellanox OFED ISO imageNote If an adapter’s Flash was originially programmed with an Expansion ROM image, the automatic firmware update will also burn an Expansion ROM image.•In case your machine has an unsupported network adapter device, no firmware update will occur and the error message below will be printed. Please contact your hardware vendor for help on firmware updates.Error message:。

Inetr芯片组发展历程

Inetr芯片组发展历程

从430FX到X58——大话INTEL主板芯片组发展历史2008-06-17 04:25:57 分类:intel英特尔| 业界| 评论(10) | 浏览(8055)- 序 -主板是电脑中最为重要的硬件之一。

CPU、内存、显卡等都基于其上,硬盘、光驱、电源等都与其连通,显示器、键盘、鼠标、音箱等都同其衔接。

主板连接并控制着其它硬件之间的数据传输,是其它硬件的中心枢纽。

而主板芯片组则是主板的心脏,决定着主板的功能和特性。

世界上存在多家拥有自主设计能力研发生产主板芯片组的公司,分别是Intel(英特尔)、NVIDIA(英伟达)、VIA(威盛)、SIS(矽统)、ALI(扬智)、AMD(2006年7月24日AMD收购了ATI)等。

这些厂商的历代多款主板芯片组,在性能、价格和CPU的支持上都各有特色,而Intel的主板芯片组,经过多年发展,久历市场考验,凭借着其在电脑使用人群中绝对优势的主板芯片组占有率,毫无悬念理所当然的成为众多主板芯片组厂商中的领军品牌。

电脑技术发展飞快,回望这些年Intel主板芯片组走过的历程,我们能够从历史的脚印中未来Intel主板芯片组发展的可能方向和规律。

那么,就让我们一起走进“时间隧道”,共同来回顾一下Intel主板芯片组发展的光辉历史。

- 前言 -Intel主板芯片组历史上,曾有440BX、810、815、845、865、915、945、965、P35等诸多型号的经典产品,以及最近在台北Computex2008电脑展上刚刚发布的P45,还有Intel未来将要发布的搭配下一代Nehalem处理器的X58,让我们看的眼花缭乱晕乎其晕。

主板芯片组分为北桥芯片和南桥芯片(NVIDIA有部分IGP整合主板产品将北桥主板对和南桥主板对集成到一个主板芯片中)。

本文所讲的主要是主板的北桥芯片,它通常靠近CPU插槽一端,负责主板对CPU、内存、显卡等硬件的控制,我们平时所说的“845”主板就是指的使用845北桥芯片的主板。

PCI9054详细资料

PCI9054详细资料

本文介绍近期工程用到了CPCI,便上网搜集了一下PCI的资料,CPCI是PCI的子集,所用桥接芯片分主从两种,在此不赘述了。

至于PCI,本人整理介绍如下:随着Windows图形用户界面的迅速发展,以及多媒体技术的广泛应用,要求系统具有高速图形处理和I/O吞吐能力,这使原有的ISA、EISA总线远远不能适应而成为整个系统的主要瓶颈。

为此,1991年下半年,Intel公司首先提出PCI概念,并联合IBM、Compaq、AST、HP Apple、NCR、DEC 等100多家公司共谋计算机总线发展大业,成立了PCI集团。

PCI:Peripheral Component Interconnect,外围设备互联总线,是一种局部总线,已成为局部总线的新标准,广泛用于当前高档微机、工作站,以及便携式微机。

主要用于连接显示卡、网卡、声卡。

PCI总线是32位同步复用总线。

其地址和数据线引脚是AD31~AD0。

PCI的工作频率为33MHz。

一PCI总线特性1.PCI总线特点(1)传输速率高最大数据传输率为132MB/s,当数据宽度升级到64位,数据传输率可达264MB/s。

这是其他总线难以比拟的。

它大大缓解了数据I/O瓶颈,使高性能CPU的功能得以充分发挥,适应高速设备数据传输的需要。

(2)多总线共存采用PCI总线可在一个系统中让多种总线共存,容纳不同速度的设备一起工作。

通过HOST-PCI桥接组件芯片,使CPU总线和PCI总线桥接;通过PCI-ISA/EISA 桥接组件芯片,将PCI总线与ISA/EISA总线桥接,构成一个分层次的多总线系统。

高速设备从ISA/EISA总线卸下来,移到PCI总线上,低速设备仍可挂在ISA/EISA总线上,继承原有资源,扩大了系统的兼容性。

(3)独立于CPU PCI总线不依附于某一具体处理器,即PCI总线支持多种处理器及将来发展的新处理器,在更改处理器品种时,更换相应的桥接组件即可。

(4)自动识别与配置外设用户使用方便。

PCIE检测卡代码

PCIE检测卡代码

PCIE检测卡代码PCIEPCIE主板测试卡测试卡无中文显示,可参照以下代码。

一般来说:FF、00、C0、DO、CF、F1或什么也没有表示CPU没通过C1、C6、C3、D3、D4、D6、D8、BO、A7、E1 表示内存不过24、25、26、01、0A、OB、2A、2B、31 表示显卡不过某些集成显卡主板23、24、25表示可以正常点亮,某些VIA芯片组显示13则表示可以点亮,某些品牌机里的主板显示0B则表示正常,某些主板显示4E表示正常点亮,某些INTEL 芯片组的主板显示26或16则表示可以正常点亮。

C1、C6、C3、01、02这个组合循环跳变大部分是I/O坏或刷BIOS如显示05、ED、41则直接刷BIOS 00 .已显示系统的配置;即将控制INI19引导装入。

? 01处理器测试1,处理器状态核实,如果测试失败,循环是无限的。

处理器寄存器的测试即将开始,不可屏蔽中断即将停用。

CPU寄存器测试正在进行或者失败。

02确定诊断的类型(正常或者制造)。

如果键盘缓冲器含有数据就会失效。

停用不可屏蔽中断;通过延迟开始。

CMOS写入/读出正在进行或者失灵。

03清除8042键盘控制器,发出TESTKBRD 命令(AAH )通电延迟已完成。

ROM BIOS 检查部件正在进行或失灵。

04使8042键盘控制器复位,核实TESTKBRD。

键盘控制器软复位/通电测试。

可编程间隔计时器的测试正在进行或失灵。

05如果不断重复制造测试1至5,可获得8042控制状态。

已确定软复位/通电;即将启动ROM。

DMA初如准备正在进行或者失灵。

06使电路片作初始准备,停用视频、奇偶性、DMA电路片,以及清除DMA电路片,所有页面寄存器和CMOS停机字节。

已启动ROM计算ROM BIOS检查总和,以及检查键盘缓冲器是否清除。

DMA初始页面寄存器读/写测试正在进行或失灵。

07处理器测试2,核实CPU寄存器的工作。

ROM BIOS检查总和正常,键盘缓冲器已清除,向键盘发出BAT (基本保证测试)命令。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

C-IASI 中国保险汽车安全指数规程编号:C I A S I-S M.P I.S O T-A0第2部分:车内乘员安全指数正面25%偏置碰撞试验规程Part 2:Vehicle Occupant Safety IndexSmall Overlap Frontal Crash Test Protocol(2017版)目次前言 (III)1 简介 (1)2 车辆准备 (1)2.1 车辆检查 (1)2.2 车辆准备 (1)2.3 乘员舱调整 (3)3 假人准备及设置 (3)4 试验照片 (4)5 高速摄像 (4)6 试验条件 (5)6.1 试验壁障 (5)6.2 试验质量 (6)6.3 车辆宽度 (6)6.4 碰撞速度 (6)6.5 重叠率 (6)7 试验测量 (7)7.1 测试仪器 (7)7.2 侵入量测量 (8)7.3 假人空间位置测量 (11)7.4 假人运动和接触位置 (12)7.5 侧面头部保护气囊向前覆盖范围 (13)7.6 燃料系统完整性 (13)7.7 高压系统完整性 (13)附录A 乘员前倾量测量 (14)附录B 侧面头部保护气囊向前覆盖范围分析程序 (17)附录C 样品信息参数表 (20)前言长期以来,车型保险安全分级作为车型定价的最重要因子,在中国一直未能建立系统的体系,极大地制约了车型定价的精细化发展。

为此,在中国保协行业协会的指导下,中国汽车工程研究院与中保研汽车技术研究院,在充分研究并借鉴国际先进经验的基础上,结合中国汽车保险与车辆安全技术现状,经过多轮论证、形成中国保险汽车安全指数(简称C-IASI)测试评价体系。

C-IASI从消费者立场出发,从汽车保险视角,围绕车险事故中“车损”、“人伤”,开展耐撞性与维修经济性、车内乘员安全、车外行人安全、车辆辅助安全四项指数的测试评价。

最终评价结果为汽车保险保费厘定提供数据支撑,为汽车安全研发、消费者购车用车提供参考。

正面25%偏置碰撞试验为车内乘员安全指数的一个试验工况,本试验规程参考IIHS中“Small Overlap Frontal Crashworthiness Evaluation Crash Test Protocol”(Version Ⅲ)编制。

试验车辆以64.4 km/h±1km/h 的速度、25%±1%的重叠率(驾驶员侧)正面撞击固定刚性壁障,采集假人伤害数据、车体结构变形数据、假人运动状态数据。

中国保险汽车安全指数(C-IASI)规程是在中国保险行业协会的指导下,中国汽车工程研究院股份有限公司和中保研汽车技术研究院有限公司共同制定。

随着中国道路交通安全、汽车保险数据以及车辆安全技术水平的不断发展和相关标准的不断更新,我们保留对试验项目和评价方法进行变更升级的权利,积极助推车辆安全技术成果与汽车保险的融汇应用,有效促进中国汽车安全水平整体提高和商业车险健康持续发展,更加系统全面地为消费者、汽车行业及保险行业服务。

中国保险行业协会、中国汽车工程研究院股份有限公司、中保研汽车技术研究院有限公司三方保留对中国保险汽车安全指数(C-IASI)的全部权利。

未经三方同时授权,除企业自行进行技术开发的试验外,不允许其他机构使用中国保险汽车安全指数(C-IASI)规程对汽车产品进行公开性或商业目的的试验或评价。

正面25%偏置碰撞试验规程1 简介正面25%偏置碰撞试验为车辆以64.4km/h±1km/h的速度、25%±1%的重叠率(驾驶员侧)正面撞击固定刚性壁障。

试验车辆驾驶员位置放置一个Hybrid III 50%假人,用于测量碰撞过程中驾驶员的损伤情况。

2 车辆准备2.1 车辆检查车辆抵达试验室后,首先检查和确认车辆状态是否完好(如车辆零部件是否完整、是否存在漏油现象、车辆状态指示灯是否正常等),如有异常则详细记录异常状态和部位。

若这些异常状态与试验直接相关,则应对其进行修复或更换车辆。

2.2 车辆准备2.2.1调整车辆至正常运行状态,即没有驾驶员、乘客和货物,排空燃油箱中的燃油,向燃油箱中加入占总容量90%~95%的Stoddard溶液或其他等质量的燃油替代物,以充满整个燃油系统,并带有随车工具和备胎(如果由车辆制造厂商作为标准装备提供)。

测量和记录此时的车辆质量和前后轴轴荷,该车辆质量即为整备质量。

2.2.2排除发动机和变速箱液体、蓄电池电解液、空调系统制冷剂,去除左前轴轴套和油脂。

2.2.3若车辆为混合动力或纯电动车辆,在制造厂商建议的最大充电状态下对混合动力和纯电动车辆的高压系统进行测试。

若制造厂商无建议,则在不低于最大容量95%的带电状态下对高压系统进行测试。

保险丝不拆除,并遵循车辆制造厂商规定的撞击前和撞击后的注意事项。

此外,按照GB/T 31498-2015《电动汽车碰撞后安全要求》将相关设备安装到高压系统上。

2.2.4车辆上安装4台车载高速相机。

1台安装在右前门,1台安装在右后门,另外2台安装在后排座椅车顶区域,在车内合适位置安装车载补光灯。

2.2.5在车辆前端合适位置(副车架或发动机支架等位置)安装牵引挂绳(不得安装在车C I A S I-S M.P I.S O T-A0辆悬架相关部件上)。

2.2.6车辆行李箱区域安装用于固定测试设备的支架。

如有必要,可移除该区域地毯、备胎、千斤顶、随车工具以及第三排座椅等。

以下测试设备安装在行李箱区域的支架上:●车载紧急制动系统:系统启动后,作用于车辆后轮。

车载紧急制动系统启动时间为碰撞后1.5s。

●12V电源系统:该系统为车辆供电。

●数据采集系统:该系统采集试验过程中各传感器的数据。

●车载高速相机和车载补光灯电源系统:该系统为车载高速相机和车载补光灯供电。

2.2.7移除车辆内的脚垫,若脚垫是标配或选装,则仅保留驾驶员处脚垫。

2.2.8断开日间行车灯(若配备)的保险丝或继电器以减少车载电源的消耗。

2.2.9在车辆外部和内部合适位置分别安装T0时刻指示灯,并在车辆上与壁障最先接触点处粘贴带状开关。

2.2.10在车辆表面粘贴摄影标识,用于视频分析(见图1、图2)。

摄影标识位置如下:●4个61cm标识:引擎盖表面、左前门表面、右前门表面、穿过驾驶员座椅中心线的垂直面。

●车身上加速度传感器对应车顶表面位置。

●车辆重心对应车顶表面位置。

●前后门门锁(车辆左右侧)和驾驶员安全带上固定点位置对应的车身侧表面位置。

●从A柱底部开始,沿着A柱在X向上每10cm贴一个圆标,直至贴满A柱。

●在驾驶员侧门上标记出方向盘中心纵向的最前位置(转向管柱若可伸缩,则为压缩最前位置)。

●方向盘和仪表板前缘用摄影标识标记,用白漆喷涂左前轮胎。

2.2.11移除前排座椅头枕,屏蔽右前乘员侧正面和侧面气囊(可以在气囊线路中接入阻值和功率合适的电阻),以避免气囊展开影响相机拍摄。

图1 车辆外表面标记(俯视)C I A S I-S M.P I.S O T-A0图2 车辆外表面标记(主视)2.3 乘员舱调整2.3.1座椅及转向管柱(若可调)调整的详细程序参见《前排假人及座椅调节规程》。

2.3.2可手动调节的驾驶员内侧扶手(若配备)调整到最低位置;对于多级调节扶手,调整到最接近水平位置。

2.3.3驾驶员安全带上固定点调整到制造厂商推荐位置或最上固定位置。

2.3.4关闭所有车门,但不锁止。

若车辆已配备自动落锁装置,车门无法在车辆向前运动时保持在非锁止状态,则门锁保持其自动状态。

2.3.5在测试之前,所有侧窗玻璃都降到最低位置,点火开关处于接通位置(ON状态),变速器处于空挡位置。

3 假人准备及设置3.1将Hybrid III 50%假人放置在驾驶员座椅上,按照《前排假人及座椅调节规程》进行定位。

3.2安装假人颈部护套。

3.3假人经过5次试验后,根据49 CFR 572(E)对假人进行标定。

若某部位的测量值超过了所发布的伤害参考值或假人标定测试中的数值(以较高者为准),或在碰撞后检查发现有受损部位,则对这些部位进行重新标定。

假人再次使用前,对所有的损坏部位进行修复。

3.4试验前,将假人和车辆放置在温度为20.0℃~22.2℃、相对湿度为10%~70%的环境中至少16小时。

3.5假人系好安全带,并且消除腰带上的松弛量。

从卷收器中拉出肩带织带,再使之卷回,重复操作4次。

3.6假人头部、膝盖和小腿涂不同颜色油彩,以便识别碰撞中假人与车辆内饰的接触位置。

在假人头部两侧用摄影标识标示出头部重心位置。

C I A S I-S M.P I.S O T-A04 试验照片记录测试车辆在碰撞前后的状态,包括测试前后车辆侧面视图和左前四分之一视图。

记录驾驶员假人在碰撞前后的位置,包括假人腿部的特写照片,详细拍摄视角见表1。

表1 试验照片图3 地面高速相机摆放位置图C I A S I-S M.P I.S O T-A0表2 车载高速相机—视角图4 车载高速相机位置6 试验条件6.1 试验壁障试验壁障为刚性壁障,其结构尺寸见图5和图6。

壁障固定于车辆牵引方向驾驶员侧地面上。

图5 壁障顶部和轴侧视图C I A S I-S M.P I.S O T-A0图6 壁障侧面和正面视图6.2 试验质量车辆试验质量在安装好所有的测试设备后测量,车辆试验质量包括所有的测试设备和假人的质量。

车辆试验质量应比所测得的整备质量大125kg~175kg。

若车辆试验质量未达到此范围,则在车辆行李箱内进行配重。

若车辆试验质量超过此范围,则将车辆后部不重要的、不影响车身结构的部件拆除(如消音器、排气管等)。

通过前后轴荷确定测试车辆重心的纵向位置。

6.3 车辆宽度车辆宽度按照SAE J1100《汽车尺寸》进行确定和测量,其定义为车辆最宽部分之间的最大尺寸,不包括后视镜、柔性挡泥板和标志灯,但包括保险杠、车身装饰件、金属钣金件凸起或双排轮(若为标准配置)。

6.4 碰撞速度车辆的碰撞速度为64.4 km/h±1km/h。

碰撞速度通过测速仪测量得到,牵引系统自身的速度测量值作为碰撞速度的备份。

试验车辆由牵引装置以≤0.3g加速度进行加速,直到其达到测试速度。

6.5 重叠率测试车辆与刚性壁障对准,驾驶员侧重叠部分占车辆宽度的25%±1%(见图7),实际的重叠率根据顶部高速摄像进行确认(见图3中的A位置高速相机)。

C I A S I-S M.P I.S O T-A0图7 车辆与壁障碰撞位置示意图区域的地毯或座垫,也可以在该区域焊接传感器安装平台。

表4 车身加速度传感器7.1.2 假人测试仪器Hybrid III 50%假人安装以下传感器:表5 假人测量参数和测试要求7.2 侵入量测量试验前后在同一坐标系下用三坐标测量仪测量驾驶员侧车辆内外部的18个标记点。

7.2.1 坐标系定义使用右手法则定义三维坐标系:X向(从前向后为正)、Y向(从左向右为正)、Z向(从下向上为正)。

相关文档
最新文档