Slide 1 ITC 2005 Gunnar Carlsson 1, David Bäckström 2, Erik Larsson 2 2) Linköpings Universitet Department of Computer Science Sweden 1) Ericsson Radio Network Development Sweden Remote Boundary-Scan System Test Control for the ATCA Standard

Slide 2 ITC 2005 Outline Remote Boundary-Scan System Test Control for the ATCA Standard  Introduction  System Environment  Approach  Demonstration Board  Conclusions

Slide 3 ITC 2005 Introduction  Boundary Scan (BScan) not only used for production interconnect test of boards  In multiboard systems the test controller and the target devices may be located on different boards  How to link BScan between controller and target devices?  Natural solution: BScan control and data must be routed through backplane Boundary Scan in Modern Systems

Slide 4 ITC 2005 Introduction Multiboard Systems Shelf Management Board Application specific boards Backplane

Slide 5 ITC 2005 Introduction BScan Multidrop Central Processor Local Processor Local Processor Local Processor System Management Application Boards Control Path Boundary Scan ATEATE Local BScan Master/Slave System BScan Master/Slave

Slide 6 ITC 2005 Introduction Related Work  Several commercial solutions exist how to link BScan in a backplane environment  National Semiconductor: SCAN Bridge  Based upon: [D.Bhavsar, ITC´91]  Addressing boards and modules by using the instruction scan  Texas instruments: Addressable Shadow Port (ASP)  [L.Whetsel, ITC´92]  Added shadow protocol used to access boards and modules

Slide 7 ITC 2005 Introduction Problem Definition  However, some system architectures do not include BScan in the backplane  The emerging ATCA standard is an example, which will be increasingly deployed  The purpose of this project is to find a way to manage remote BScan control in ATCA based systems

Slide 8 ITC 2005 System Environment ATCA Overview  Advanced Telecommunications Computing Architecture (ATCA)  Contain design specifications and requirements in the following areas:  Mechanical and Dimensions  Power Distribution  Thermal Dissipation  Interfacing and Interconnections  System Management

Slide 9 ITC 2005 System Environment  Intelligent Platform Management Interface (IPMI)  Exposing HW management functions to OS and Management SW  Provides interface and communications for:  Monitoring and Logging  Inventory  Recovery Control  Allows implementation of additional management applications within the IPMI framework System Management (IPMI)

Slide 10 ITC 2005 System Environment System Management (IPMI) SM Shelf Management Board BMC Application Board BMC Application Board Management SW/OS SM = Shelf Manager BMC = Baseboard Management Controller Management Bus (IPMB)

Slide 11 ITC 2005 Synch & Clock I/F Update Channel I/F IPMB-0 Buffers Temperature Sensor Payload Interface Point-to-Point E-Keying Enables Hardware Address [7:0] Power Supply Monitoring Payload Power Enable Management Power DC/DC Converter Monitor/ Controller Enable Blue LED Handle Switch FRU LEDs Bussed E-Keying Enables Bussed E-Keying Enables Payload Fabric I/F Base I/F Metallic Test Bus IPMB-0 Hardware Address Dual – 48V Power BMC to scale BMC Controller

Slide 12 ITC 2005 System Environment  Intelligent Platform Management Bus (IPMB)  Based on the two wire serial I 2 C Bus  Data transfers up to: 100 kbit/s  Maximum message size: 32 bytes  All IPMI messaging, including IPMB, uses a request/response protocol  All IPMB requests must be answered with an IPMB response  Requests and Responses are not automatically paired Management Bus (IPMB)

Slide 13 ITC 2005 Approach  Propose a way to transport BScan data and control using the IPMB  Propose means how to manage embedded tests in IPMI  The solution should fit in the ATCA/IPMI context  Build a demonstration board to validate the proposed solution Project Goals

Slide 14 ITC 2005 Approach New Functionality in IPMI IPMB BMC Application Board Components under test Memory Operator/ Test Program SM Shelf Management Board Memory

Slide 15 ITC 2005 Approach  Command set to interface and control the onboard tests:  Test management commands: oLIST, SEND, RECEIVE, DELETE  Test execution commands: oRUN  Test setup commands: oLINK, OPTIONS  Embedded test data format  National Semiconductor EVF is an example  Based on the Serial Vector Format (SVF) Commands and Data Format

Slide 16 ITC 2005 Approach  IPMB designed to carry short control and status messages  Extended the IPMB protocol to enable transport of BScan control and data  Still follows the rules and requirements set by the standard IPMB protocol  The SM unit is the requester (master) and the BMC units are the responders (slaves)  Mechanisms for dividing larger test files into smaller IPMB packages and re- assembling of packages back into test files has been specified and implemented Transport of BScan Control and Data

Slide 17 ITC 2005 Approach Transport of BScan Control and Data  Transport times of a 77 kB EVF file on IPMB DescriptionMax. packet size P o + P d I 2 C Speed S Total transport time T 3 Standard IPMB restrictions32 B100 kbit/s11.7 s Increased max packet size64 B100 kbit/s8.44 s Fast I 2 C mode32 B400 kbit/s2.94 s I 2 C High speed mode32 B3.4 Mbit/s0.35 s I 2 C High speed mode and Increased max packet size 64 B3.4 Mbit/s0.25 s

Slide 18 ITC 2005 Demonstration Board Shelf Manager Board BackplaneApplication Board SM Operator Interface IPMB SM Operator Interface BMC BSC UUT

Slide 19 ITC 2005 Demonstration Board Operators interface SM-unit BScan controller BMC-unit UUT

Slide 20 ITC 2005 Conclusions  Easy to add BScan functionality to the ATCA/IPMI context  IPMB suitable to carry BScan control and status  IPMB less suitable to carry large tests due to the limitations of the standard.  Can be solved using the higher available I 2 C data transfer speeds and larger IPMB packet sizes