{"id":2,"date":"2013-01-09T12:28:53","date_gmt":"2013-01-09T12:28:53","guid":{"rendered":"http:\/\/www.boundaryscan.org\/?page_id=2"},"modified":"2024-03-23T04:51:04","modified_gmt":"2024-03-23T04:51:04","slug":"sample-page","status":"publish","type":"page","link":"http:\/\/www.boundaryscan.org\/","title":{"rendered":"The History of Boundary Scan"},"content":{"rendered":"
\n
\n

The History of Boundary Scan<\/h1>\n
by<\/span>\u00a0admin<\/span><\/div>\n<\/div>\n

<\/h1>\n
\n

Boundary Scan was developed as a solution to\u00a0difficultly\u00a0in placing test points on modern circuit boards brought on by the ever increasing board complexity and decreasing size of modern electronic circuits.<\/p>\n

Systems Get Smaller<\/h3>\n

As technology advanced, chips got smaller, more tightly packed, and new package technologies, such as Ball Grid Arrays (BGAs),\u00a0were created to allow more and more devices to be placed on smaller and smaller footprints.<\/p>\n

These advances\u00a0made it increasingly difficult to place test points on a board, rendering traditional methods of testing \u00a0like\u00a0In-circuit Test<\/a>\u00a0or, ICT \u00a0less and less effective.<\/span><\/p>\n

To help deal with these problems, a group of US and\u00a0European\u00a0companies was formed to look at new ways to test these new boards and systems.<\/p>\n

Joint Test Access Group (JTAG)\u00a0 is Born<\/h3>\n

The\u00a0consortium\u00a0of companies came to be know as the\u00a0Joint Test Action Group<\/a>\u00a0or JTAG for short. This group created a specification for on-chip test that would later be known as IEEE 1149.1. \u00a0The specification was intended to provide a standard way to do \u201cpins out\u201d testing where each IC pin could become a\u00a0virtual\u00a0test point when the chip was placed in a special test mode. Using a published standard helped to enable multiple tools vendors to create\u00a0test products<\/a>\u00a0that could be used in all phases of board design and test.<\/p>\n

Evolution\u00a0of the JTAG\u00a0Specification<\/h4>\n

Later additions to the family of specifications included:\u00a01149.4 for\u00a0Analog testing \u00a0(not popular) and \u00a0IEEE\u00a01149.6 for AC\u00a0coupled\u00a0signals\u00a0(gaining popularity).<\/p>\n

Many modern IC Chips support Boundary Scan testing and as such adhere to the IEEE 1149.1 Specification. To meet the specification, vendors must include a Boundary Scan Definition Language File (BSDL) that describes the chip\u2019s support for the standard.<\/p>\n<\/div>\n

\n

Boundary SCAN Basics<\/h1>\n
by<\/span>\u00a0admin<\/span><\/div>\n<\/div>\n
\n

Boundary SCAN is a technology created to help improve test coverage on boards and they got smaller, had fewer test points and used more surface mount devices.<\/p>\n

Uses of Boundary SCAN<\/h2>\n

In addition to basic test coverage (manufacturing faults), modern Boundary SCAN systems can also be used for high speed in-circuit device programming and functional test. When integrated with other tools and technologies such as: In-circuit testers, flying probe testers, optical inspection tools and embedded diagnostics, Boundary SCAN becomes an integral part of your complete test solution.<\/p>\n

\"jtagpins\"Boundary SCAN helps improve test coverage by leveraging test circuitry built into modern ICs that supports the JTAG test standard: IEEE 1149.1.
\nTest cells are inserted on the IC between the external pins. When Boundary SCAN mode is enabled, and the internal logic of the device is isolated from the pins and the test cells can output and read signals on the chips pins.<\/p>\n

The TAP (Target Access Port)<\/h2>\n

The TAP or target access port is the interface to the on-chip Boundary SCAN test circuitry. The interface is comprised of 4 standard signals: TDI, TDO, TMS and TCK which allow access to the pins on the device is one long shift register.\u00a0 By clocking data into and out of the chip through this interface values at pins can be read and set to a logic one or zero.<\/p>\n

Basic Tests with Boundary SCAN<\/h2>\n

\"testing\"By setting pins on a Boundary SCAN enabled device to a high or low, and reading back the value from another device that is connected to the pin, basic tests can be accomplished.<\/p>\n

Typically opens, shorts and stuck-at faults are detected using these simple techniques.<\/p>\n

Boundary SCAN companies have created powerful tests that can be automatically generated based on how devices are connected and what each device can do.<\/p>\n

\u00a0Functional Test with Boundary SCAN<\/h2>\n

Boundary SCAN can be used to do functional tests on many devices such as: I2C and SPI based peripherals, RAM, DDR, FLASH and CPLDs and many others. Boundary SCAN companies include libraries for many popular devices that can be used to quickly test a device.<\/p>\n

\u00a0Functional and At-Speed Tests with Processor Emulation<\/h2>\n

Some Boundary SCAN tools support so called processor emulation mode for tests. This allows the tools to take control of a processor on a board and the load and run code. This technique allow you to run at speed (Burst Mode) RAM tests and high speed devices tests as well.<\/p>\n

Functional and At-Speed Tests with Programmable Logic<\/h2>\n

Some tools allow programmable devices like CPLDs and FPGAs to be programed to perform tests in real time. This method can allow maximum speed programming of FLASH devices as well as at-speed tests on hardware accessible from the programmable device.<\/p>\n

For More information please review our article on\u00a0applications<\/a>.<\/p>\n<\/div>\n

Comments on this entry are closed.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

The History of Boundary Scan by\u00a0admin Boundary Scan was developed as a solution to\u00a0difficultly\u00a0in placing test points on modern circuit boards brought on by the ever increasing board complexity and decreasing size of modern electronic circuits. Systems Get Smaller As technology advanced, chips got smaller, more tightly packed, and new package technologies, such as Ball […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-2","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/pages\/2","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2"}],"version-history":[{"count":4,"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions"}],"predecessor-version":[{"id":19,"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=\/wp\/v2\/pages\/2\/revisions\/19"}],"wp:attachment":[{"href":"http:\/\/www.boundaryscan.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}