<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Flynn Systems</title>
	<atom:link href="http://www.flynn.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.flynn.com</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 15:20:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Using onTAP to test a board</title>
		<link>http://www.flynn.com/using-ontap-to-test-a-board</link>
		<comments>http://www.flynn.com/using-ontap-to-test-a-board#comments</comments>
		<pubDate>Tue, 12 Feb 2013 09:00:05 +0000</pubDate>
		<dc:creator>Flynn Systems</dc:creator>
				<category><![CDATA[onTAP]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[onTAP Usage]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=4023</guid>
		<description><![CDATA[What Does onTAP Test?   As boundary scan technology grows in popularity, more JTAG compliant devices (1149.1 and 1149.6) are now being included in board design, along with more JTAG chains that often require simultaneous testing. The great advantage to using onTAP, is that there are no restrictions on the number of devices in a [...]]]></description>
				<content:encoded><![CDATA[<p style="text-align: left;" align="center"><strong><em>What Does onTAP Test? </em></strong><strong> </strong></p>
<p>As boundary scan technology grows in popularity, more JTAG compliant devices (1149.1 and 1149.6) are now being included in board design, along with more JTAG chains that often require simultaneous testing.</p>
<p>The great advantage to using onTAP, is that there are no restrictions on the number of devices in a chain that it can test. Using just one onTAP TAP CONNECT JTAG Cable, onTAP can test two chains simultaneously. Testing more than two chains in parallel can be achieved in one of two ways:</p>
<ol start="1">
<li>Multiple TAP CONNECT JTAG cables may be used to test chains simultaneously.</li>
<li>Serializing chains can be accomplished using the onTAP GPIO Serializer, a single TAP CONNECT Cable, and merged netlists (a task performed by onTAP).</li>
</ol>
<p>onTAP will perform several critical tests on your board such as:</p>
<ul>
<li>TAP Infrastructure/ID Code Test</li>
<li>Interconnect Test</li>
<li>Mid-state/Resistive Shorts</li>
<li>Incorporating Multi-die devices</li>
<li>Opens and Shorts Tests</li>
<li>Pull Up/Pull Down</li>
<li>I2C Bus Control and Test</li>
<li>Memory/Flash Test &amp; Programming</li>
<li>Cluster tests</li>
<li>1149.6 – AC Coupled Circuit/Differential Pairs</li>
</ul>
<p>onTAP requires just three items to begin developing a test:</p>
<ul>
<li>BSDL Files for all JTAG compliant devices on the board</li>
<li>Board Netlist</li>
<li>An onTAP- TAP CONNECT JTAG Cable</li>
</ul>
<p><strong><em>An Overview of Some Tests Performed with onTAP</em></strong></p>
<p>The first test is the TAP (Test Access Port) test. Since JTAG Boundary Scan is essentially a test instrument built into your board, it is important to check the test instrument before beginning a test. Any infrastructure test through device TAPs (Test Access Ports) accomplishes this and in the case of a fault, alerts where a boundary scan chain is broken.</p>
<p style="text-align: center;"><a href="http://www.flynn.com/wp-content/uploads/2013/01/JTAG-Tap.png"><img class="aligncenter size-full wp-image-4024" title="JTAG Tap - onTAP - Flynn Systems" alt="Flynn Systems provides their onTAP solution for your boundary scan needs." src="http://www.flynn.com/wp-content/uploads/2013/01/JTAG-Tap.png" width="470" height="287" /></a></p>
<p>Once the TAP has been verified, the next test is the <strong>Interconnect Test.</strong></p>
<p>A connectivity test, or <strong>Interconnect Test</strong>, is the foundation of any boundary scan test solution. This test verifies that devices are properly connected to your board with no opens or shorts, especially common with BGAs. onTAP’s automatic test pattern generator (ATPG) generates test patterns to ensure that boards are free of defects including opens, stuck-ats-shorts and mid-state/resistive shorts.</p>
<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/Interconnect-Test.png"><img class="aligncenter size-full wp-image-4025" title="Interconnect Test - onTap - Flynn Systems" alt="Interconnect issue being resolved with Flynn Systems onTAP system" src="http://www.flynn.com/wp-content/uploads/2013/01/Interconnect-Test.png" width="447" height="253" /></a></p>
<p><strong>Mid-State / Resistive Shorts &#8211; Nasty, Tough to Isolate, Show Stoppers</strong></p>
<p>A major problem that often goes undetected by typical boundary scan connectivity tests are mid-state/resistive shorts. While the typical connectivity tests will locate the short between nets 3 and 4 in the example below, they cannot locate the resistive short which exists between nets 1 and 2. This type of short is a mid-state condition, and is recognized and diagnosed. (See our application note on Interconnect testing for more information.)</p>
<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/Mid-State-Break.png"><img class="aligncenter size-full wp-image-4026" title="Mid-State Break - onTAP - Flynn Systems" alt="Mid State Resistive Short beig recognized by Flynn Systems onTAP software" src="http://www.flynn.com/wp-content/uploads/2013/01/Mid-State-Break.png" width="278" height="128" /></a></p>
<p><strong>Bus Wire &#8211; Managing Multiple Outputs on a Net</strong></p>
<p>The onTAP-Specific Interconnect test manages bus wires when multiple outputs are connected to a net. onTAP verifies each pin has the chance to drive the output high and low while all inputs capture values.</p>
<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/Bus-Wire.png"><img class="aligncenter size-full wp-image-4027" title="Bus Wire - onTAP - Flynn Systems" alt="Flynn Systems onTAP verifies each pin has the chance to drive the output high and low while all inputs capture values." src="http://www.flynn.com/wp-content/uploads/2013/01/Bus-Wire.png" width="546" height="109" /></a></p>
<p><strong>Cluster Testing &#8211; Accessing, Testing, Programming and Controlling non-JTAG Devices</strong><strong> </strong></p>
<p><a title="onTAP Series 4000 Overview" href="http://www.flynn.com/boundary-scan-products-and-services/"><span style="text-decoration: underline;">onTAP</span></a> uses the high-level DTS test language (see application note and DTS Programming Manual to learn more about this dynamic, C-Like, reusable language) to develop reusable test models for testing connectivity between scan devices and non-scan devices such as DDR2, SRAM, SDRAM, and FLASH. onTAP’s Cluster Test also provides a means to program FLASH memory and configure logic.</p>
<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/Cluster-Testing.png"><img class="aligncenter size-full wp-image-4028" title="Cluster Testing - onTAP - Flynn Systems" alt="Flynn Systems onTAP’s Cluster Test also provides a means to program FLASH memory and configure logic." src="http://www.flynn.com/wp-content/uploads/2013/01/Cluster-Testing.png" width="631" height="192" /></a></p>
<p><strong> </strong></p>
<p>For more information regarding onTAP or Boundary Scan, contact Flynn</p>
<p>systems at (603)-598-4444 or visit the website at <a href="http://www.flynn.com/">www.flynn.com</a>.</p>
<p><strong> </strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/using-ontap-to-test-a-board/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New to Boundary Scan Test?</title>
		<link>http://www.flynn.com/new-to-boundary-scan-test</link>
		<comments>http://www.flynn.com/new-to-boundary-scan-test#comments</comments>
		<pubDate>Tue, 05 Feb 2013 09:00:42 +0000</pubDate>
		<dc:creator>Flynn Systems</dc:creator>
				<category><![CDATA[onTAP JTAG Blog]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=4016</guid>
		<description><![CDATA[Many newcomers to JTAG start their first projects knowing only that boundary scan testing is a requirement for new board design. The specifics of boundary scan, details of test strategy, or expected results are for many, an uncharted territory. In fact, most newcomers to boundary scan testing don’t know what questions to ask or how [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/BoundaryScan.png"><img class="alignright size-medium wp-image-4017" title="BoundaryScan - JTAG - Flynn Systems" alt="Flynn Systems provides the best JTAG suite of tools for your company's boundary scan needs." src="http://www.flynn.com/wp-content/uploads/2013/01/BoundaryScan-300x231.png" width="300" height="231" /></a></p>
<p>Many newcomers to JTAG start their first projects knowing only that boundary scan testing is a requirement for new board design. The specifics of boundary scan, details of test strategy, or expected results are for many, an uncharted territory. In fact, most newcomers to boundary scan testing don’t know what questions to ask or how to get started.</p>
<p>If you find that you are in a similar predicament, with a deadline for completing a boundary scan project looming ahead, help is just a phone call away. Flynn Systems is always available to discuss boundary scan in general, your project in particular, and how onTAP® can help you reach your goals. Flynn Systems offers a comprehensive suite of JTAG tools to meet your boundary scan testing needs, and we are always available to answer your questions, concerns, and inquiries regarding what <strong>JTAG</strong> is and how it can help you<em> </em></p>
<h2><strong><em>A Brief History of Boundary Scan Testing</em></strong></h2>
<p>Boundary scan or the boundary scan test is also known as JTAG test or 1149.1. <strong>J</strong>oint <strong>A</strong>ccess <strong>T</strong>est <strong>G</strong>roup (commonly referred to as JTAG) is a consortium of engineers from a multitude of electronics companies worldwide that formed over twenty years ago to meet the cries and pleas of standardization that the market was lacking. JTAG developed a standardized architecture for testing surface-mount devices applied to denser PCBs (Printed Circuit Boards), a test system commonly dubbed as <em>JTAG</em> or JTAG testing.</p>
<p>In the early 1980s, most PCB testing was achieved using the in-circuit bed-of-nails testers, which generally required physical access to all the devices on the board. This in-Circuit (IC) bed-of-nails technique, provided an efficient and affordable method of testing boards. However, to meet the growing demands of miniaturization, denser (or layered) printed circuit boards began to dominate the market. This posed a huge problem for testing the electrical connectivity between devices, because board density and complex layering prevented the IC pins from being physically probed. Adding to this initial problem was the fact that real estate on boards was becoming a premium: the demand called for more devices with more information on smaller boards. Chip manufacturers met that demand with surface-mount technology.</p>
<p>As good as that was for shrinking technology, surface-mount packaging added complexity to the whole test process, not to mention board layout. Board design layout now had to provide test points for the bed-of-nails fixtures. Adding test points added noise to the board being tested, which created more complexity, more headaches, more delays and more financial cost. Without adding costly test points, access to IC pins could no longer be counted on and engineers as well as chip manufacturers had no set of standards by which to design, build and test. Enter the JTAG consortium.</p>
<p>The Joint Test Action Group originally began with participation from just European electronics companies in the mid-80s. As they sought to devise a specification for boundary scan testing, North American companies joined in the effort and the consortium gained sponsorship from the IEEE.</p>
<p>By 1990, that specification was ready to become the standard for boundary scan test. It was published as IEEE Std 1149.1 and remains the foundation for boundary scan architecture. In 1994, an addition to the standard was made, which contained the <strong>B</strong>oundary <strong>S</strong>can <strong>D</strong>escription <strong>L</strong>anguage, more commonly known as BSDL. The BSDL IEEE supplement to 1149.1 describes the logic content of boundary scan compliant devices.</p>
<h2><strong><em>An Overview of What Boundary Scan does</em></strong></h2>
<p>The boundary scan test architecture provides a way to test interconnects between integrated circuits (ICs) on a board without using physical test probes. It contains cells within a device that can capture data from pin or core logic signals or force data onto pins. The captured data is shifted out and externally compared to other results. Forced test data is shifted into the boundary scan cells. This is all controlled from a data path called the <strong>scan path</strong> or <strong>scan chain</strong>.</p>
<p>By allowing direct access to nets, boundary scan can eliminate the need for a large number of test vectors. These test vectors are normally needed to properly initialize sequential logic. The benefits of boundary scan technology were quickly realized through shorter test times, higher test coverage, increased diagnostic capability and lower equipment cost.</p>
<h2><strong><em>Flynn Systems</em></strong></h2>
<p>Flynn Systems Corporation, a boundary scan vendor, offers onTAP, a dynamic PC-based boundary scan test software suite. onTAP Boundary Scan provides a cost-effective test solution which encompasses the entire life cycle of a product from development through production. onTAP Boundary Scan technology offers solutions to handle problems such as:</p>
<p>•    Boards that include components assembled on both sides, burying most of the through-holes, thus making them inaccessible</p>
<p>•    Small-size products that do not have test points, making it difficult or impossible to probe suspected nodes</p>
<p>•    Loss of physical access to fine pitch components, making it complicated to distinguish between manufacturing and design issues</p>
<p>&nbsp;</p>
<p>For more information regarding our offers our comprehensive set of <span style="text-decoration: underline"><a title="Home" href="http://www.flynn.com/">JTAG</a></span> tools, onTAP or Boundary Scan, contact Flynn systems at (603)-598-4444</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/new-to-boundary-scan-test/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Boundary Scan Works</title>
		<link>http://www.flynn.com/how-boundary-scan-works</link>
		<comments>http://www.flynn.com/how-boundary-scan-works#comments</comments>
		<pubDate>Tue, 29 Jan 2013 17:43:01 +0000</pubDate>
		<dc:creator>Flynn Systems</dc:creator>
				<category><![CDATA[Boundary Scan]]></category>
		<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=4034</guid>
		<description><![CDATA[A Brief Overview The boundary scan test architecture provides a way to test interconnects between integrated circuits (ICs) on a board without using physical test probes. It contains cells within a device that can capture data from pin or core logic signals or force data onto pins. The captured data is shifted out and externally [...]]]></description>
				<content:encoded><![CDATA[<h2><strong>A Brief Overview</strong></h2>
<p>The <strong>boundary scan</strong> test architecture provides a way to test interconnects between integrated circuits (ICs) on a board without using physical test probes. It contains cells within a device that can capture data from pin or core logic signals or force data onto pins. The captured data is shifted out and externally compared to other results. Forced test data is shifted into the boundary scan cells. This is all controlled from a data path called the <strong>scan path</strong> or <strong>scan chain</strong>.</p>
<p><a href="http://www.flynn.com/wp-content/uploads/2013/01/BoundaryScanRegister.png"><img class="aligncenter size-full wp-image-4035" title="Boundary Scan - Flynn Systems" alt="Flynn Systems provides the best in JTAG Boundary Scan solutions for you and your company" src="http://www.flynn.com/wp-content/uploads/2013/01/BoundaryScanRegister.png" width="578" height="365" /></a></p>
<p>By allowing direct access to nets, boundary scan can eliminate the need for a large number of test vectors. These test vectors are normally needed to properly initialize sequential logic. The benefits of <em>boundary scan</em> technology were quickly realized through shorter test times, higher test coverage, increased diagnostic capability and lower equipment cost.</p>
<p>While boundary scan testing is frequently used in the production phase of a product, this technology is also extremely beneficial when applied to product design, prototype debugging and field service. Thus, the cost can be incorporated over the entire life cycle of the product.</p>
<p>JTAG defines test logic through an integrated circuit, which provides applications to perform five basic duties:</p>
<ul>
<li>Chain integrity testing</li>
<li>Interconnection testing between devices</li>
<li>Core logic testing (BIST)</li>
<li>In-system programming (FLASH Programming)</li>
<li>Functional testing (DDR, SRAM, FLASH, UART, etc.)</li>
</ul>
<p>Flynn Systems Corporation, offers onTAP, a dynamic PC-based boundary scan test software suite. onTAP Boundary Scan provides a cost-effective test solution which encompasses the entire life cycle of a product from development through production. onTAP Boundary Scan technology offers solutions to handle problems such as:</p>
<p>•    Boards that include components assembled on both sides, burying most of the through-holes, thus making them inaccessible</p>
<p>•    Small-size products that do not have test points, making it difficult or impossible to probe suspected nodes</p>
<p>•    Loss of physical access to fine pitch components, making it complicated to distinguish between manufacturing and design issues</p>
<p>An example of some of the device types typically tested using boundary scan technology are:</p>
<ul>
<li> CPLDs, FPGAs, processors chained together in a boundary scan path</li>
<li>Non-boundary scan components such as SRAM, SD-RAM, DDR2, DDR3</li>
<li>Programmable FLASH</li>
<li>Series resistors or buffers—making them transparent</li>
<li>I2C devices</li>
</ul>
<p>There are critical tests that should be performed to test these devices, such as:</p>
<ul>
<li>TAP Infrastructure/ID Code Test</li>
<li>Interconnect Test</li>
<li>Mid-state/Resistive Shorts</li>
<li>Incorporating Multi-die devices</li>
<li>Opens and Shorts Tests</li>
<li>Pull Up/Pull Down</li>
<li>I2C Bus Control and Test</li>
<li>Memory/Flash Test &amp; Programming</li>
<li>Cluster tests</li>
<li>1149.6 – AC Coupled Circuit/Differential Pairs</li>
</ul>
<p>&nbsp;</p>
<p>For more information regarding onTAP or <a title="Boundary Scan Products &amp; Services" href="http://www.flynn.com/boundary-scan-products-and-services"><span style="text-decoration: underline;">Boundary Scan</span></a>, contact Flynn systems at</p>
<p>(603)-598-4444 or visit the website at <a href="http://www.flynn.com/">www.flynn.com</a>.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/how-boundary-scan-works/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>onTAP Gets a New Look for the New Year!</title>
		<link>http://www.flynn.com/ontap-gets-a-new-look-for-the-new-year</link>
		<comments>http://www.flynn.com/ontap-gets-a-new-look-for-the-new-year#comments</comments>
		<pubDate>Tue, 18 Dec 2012 19:39:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[onTAP]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=3979</guid>
		<description><![CDATA[&#160; Our Development team has been busy at work on a new UI for onTAP. We’re all excited about the new look and we’re sure you will like it as much as we do. We expect to introduce our new and improved onTAP mid-to-late Q1 2013, so stay tuned for updates. In the meantime, all [...]]]></description>
				<content:encoded><![CDATA[<h1 align="center"></h1>
<p>&nbsp;</p>
<p style="text-align: center;"><a href="http://www.flynn.com/wp-content/uploads/2012/12/coming_soon.png"><img class="aligncenter  wp-image-3983" title="onTAP - Flynn Systems" alt="Flynn Systems's onTAP boundary scan software delivers the best value, and best service." src="http://www.flynn.com/wp-content/uploads/2012/12/coming_soon-276x300.png" width="198" height="216" /></a></p>
<p>Our Development team has been busy at work on a new UI for onTAP. We’re all excited about the new look and we’re sure you will like it as much as we do.</p>
<p>We expect to introduce our new and improved <a title="onTAP Series 4000 Overview" href="http://www.flynn.com/boundary-scan-products-and-services/ontap-series-4000-overview"><span style="text-decoration: underline;">onTAP</span></a> mid-to-late Q1 2013, so stay tuned for updates.</p>
<p>In the meantime, all of us at Flynn Systems wish to thank our customers for all the great suggestions and for sending us your wish list items. We have incorporated many of your requests into onTAP’s new UI.</p>
<p>We wish you all a Happy Holiday Season and we look forward to working with you on your boundary scan projects next year!</p>
<p>The Flynn Systems Team</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/ontap-gets-a-new-look-for-the-new-year/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Quick Reference Guide to Boundary Scan Terms</title>
		<link>http://www.flynn.com/a-quick-reference-guide-to-boundary-scan-terms-2</link>
		<comments>http://www.flynn.com/a-quick-reference-guide-to-boundary-scan-terms-2#comments</comments>
		<pubDate>Fri, 14 Dec 2012 17:10:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Boundary Scan]]></category>
		<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[JTAG Boundary Scan]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=3952</guid>
		<description><![CDATA[While not all boundary scan terminology is contained in the guide, there are enough terms to at least acquaint you with some of the most commonly used expressions. BIST: Built-In Self-Test, sometimes controllable via boundary scan BOARD NETLIST: Files that show the connections between devices on a circuit board and the probe access to circuit [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.flynn.com/central-and-eastern-european-distributorship-reaffirmed/ontap-logo-bscan-copy-2" rel="attachment wp-att-4059"><img class="aligncenter size-full wp-image-4059" alt="Flynn Systems provides the best JTAG boundary scan test software with their onTAP series 4000 with ProScan" src="http://www.flynn.com/wp-content/uploads/2008/08/onTAP-LOGO-BSCAN-copy.jpg" width="422" height="189" /></a></p>
<p>While not all boundary scan terminology is contained in the guide, there are enough terms to at least acquaint you with some of the most commonly used expressions.</p>
<p><strong>BIST:</strong><br />
<strong>B</strong>uilt-<strong>I</strong>n <strong>S</strong>elf-<strong>T</strong>est, sometimes controllable via boundary scan</p>
<p><strong>BOARD NETLIST:</strong><br />
Files that show the connections between devices on a circuit board and the probe access to circuit nets. Many formats are available, including PADS. CADENCE, EDIF, ALLEGRO, etc.</p>
<p><strong>BOUNDARY REGISTER: </strong><br />
A network of register cells linking the TDI and TDO TAP pins. This network provides access to package pins and to system circuits.</p>
<p><strong>BOUNDARY SCAN: </strong><br />
A test and access method for electronic devices based on IEEE. Std 1149.1a –2001 specification. Boundary Scan employs scan registers which may operate in system or test mode at each system pin. The boundary scan circuit is controlled by a test access port (TAP) which has four required pins and one optional pin (see TAP).</p>
<p><strong>BSDL</strong>:<br />
<strong>B</strong>oundary <strong>S</strong>can <strong>D</strong>escription <strong>L</strong>anguage is based on the IEEE 1149.1 standard. BSDL files provide a hardware description language of boundary scan circuits, and most contain the filename extension .bsd or .bsdl. BSDL is a subset of VHDL (Verilog Hardware Description Language).</p>
<p><strong>BYPASS: </strong><br />
A boundary scan instruction that allows test data to go through a device and to bypass the boundary register.</p>
<p><strong>CHAINS:</strong><br />
Configuration of multiple boundary scan devices.</p>
<p><strong>CLUSTER TEST:</strong><br />
An onTAP method of applying test vectors through JTAG-capable devices to non-JTAG devices.</p>
<p><strong>DISABLE:</strong><br />
An in-circuit test technique of electrically isolating a device under test (DUT) by applying input signal patterns that turn off the devices that interact with the DUT.</p>
<p><strong>EDIF NETLIST</strong>:<br />
<strong>E</strong>lectronic <strong>D</strong>ata <strong>I</strong>nterchange <strong>F</strong>ormat, is a netlist for a circuit within a device or between devices.</p>
<p><strong>EXTEST:</strong><br />
A boundary scan instruction for interconnect test.</p>
<p><strong>GUARDS:</strong><br />
Used with constraints, such as forcing a value on a net, to “guard” or limit interaction between boundary scan and non-boundary scan circuits.</p>
<p><strong>HIGHZ:</strong><br />
Output high impedance condition.</p>
<p><strong>ICT:</strong><br />
<strong>I</strong>n-<strong>C</strong>ircuit <strong>T</strong>esting is a type of automatic test equipment in digital electronic board manufacturing. ICT accesses digital devices on a PCB through a bed-of-nails test fixture. This access allows ICT to test one device at a time while disabling any devices that interact and might cause test conflicts with the device under test.</p>
<p><strong>IEEE 1149.1:</strong><br />
The standards established by the Joint Action Test Group (JTAG) for boundary scan architecture that incorporates TAP for boundary scan testing of complex ICs. As a whole, these standards have become synonymous with “JTAG test” and “boundary scan test” (<a href="http://http://www.ieee.org/index.html">http://www.ieee.org/index.html</a>).</p>
<p><strong>IEEE 1149.6:</strong><br />
An additional IEEE standard that provides for A/C testing (<a href="http://http://www.ieee.org/index.html">http://www.ieee.org/index.html</a>).</p>
<p><strong>INTERCONNECT TEST:</strong><br />
A boundary scan test between multiple devices that uses scan patterns, typically Wagner patterns, to check pin to pin connections and shorts.</p>
<p><strong>INTEST:</strong><br />
An instruction that allows parallel test vectors to functionally test through a device and to be transported via boundary scan.</p>
<p><strong>ISP:</strong><br />
<strong>I</strong>n <strong>S</strong>ystem <strong>P</strong>rogramming is a technique of configuring programmable logic devices via boundary scan.</p>
<p><strong>JTAG:</strong><br />
The Joint Test Action Group was a test standards committee that established the current IEEE 1149.1 standards for boundary scan architecture, incorporating the TAP (Test Access Port). The acronym is now synonymous with the group’s output. The terms “JTAG”, “boundary scan” and “IEEE 1149.1” are used interchangeably.</p>
<p><strong>JUMPERS:</strong><br />
When circuit elements, such as resistors and bus transceivers, residing between boundary scan pins are made transparent so that the boundary scan pins are effectively joined together.</p>
<p><strong>onTAP:</strong><br />
Flynn Systems’ Automatic Test Generation suite of Boundary Scan tools.</p>
<p><strong>TAP:</strong><br />
<strong>T</strong>est <strong>A</strong>ccess <strong>P</strong>ort. Each <em>boundary scan</em> device has a TAP that contains the TAP pins, state machine controller circuit, boundary register, and optional BIST and ISP circuits. All conform to the IEEE 1149.1 standards  (<a href="http://http://fiona.dmcs.pl/~cmaj/JTAG/JTAG_IEEE-Std-1149.1-2001.pdf">http://fiona.dmcs.pl/~cmaj/JTAG/JTAG_IEEE-Std-1149.1-2001.pdf</a>)</p>
<p>TAP pins are:<br />
<strong>TDI</strong> (test data in)<br />
<strong>TDO</strong> (test data out)<br />
<strong>TMS</strong> (test mode select)<br />
<strong>TCK</strong> (test clock)<br />
and optionally<br />
<strong>TRST</strong> (test reset)</p>
<p><strong>TEST PATTERN:</strong><br />
A sequence of applied input values and expected output values related to a device’s I/O pins over a series of test steps.</p>
<p><strong>Transparent Devices:</strong><br />
Circuit elements such as resistors and bus transceivers that reside between <a title="Boundary Scan Products &amp; Services" href="http://www.flynn.com/boundary-scan-products-and-services"><span style="text-decoration: underline;">boundary scan</span></a> pins may be made “transparent” so that the boundary-scan pins are effectively joined or “jumpered” together.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/a-quick-reference-guide-to-boundary-scan-terms-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New To JTAG Boundary Scan Test? You&#8217;re not alone&#8230;</title>
		<link>http://www.flynn.com/new-to-jtag-boundary-scan-test-youre-not-alone</link>
		<comments>http://www.flynn.com/new-to-jtag-boundary-scan-test-youre-not-alone#comments</comments>
		<pubDate>Fri, 14 Dec 2012 13:38:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Boundary Scan]]></category>
		<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[JTAG Boundary Scan]]></category>
		<category><![CDATA[onTAP]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=3941</guid>
		<description><![CDATA[Many newcomers to JTAG test start their first projects knowing only that boundary scan testing is a requirement for new board design. The specifics of boundary scan, details of test strategy, or expected results are, for many, uncharted territory. In fact, most newcomers to boundary scan testing are uncertain as to what questions to ask [...]]]></description>
				<content:encoded><![CDATA[<p>Many newcomers to JTAG test start their first projects knowing only that boundary scan testing is a requirement for new board design. The specifics of boundary scan, details of test strategy, or expected results are, for many, uncharted territory. In fact, most newcomers to boundary scan testing are uncertain as to what questions to ask or how to get started.</p>
<p>If you find that you are in a similar predicament, with a deadline for completing a boundary scan project looming ahead, help is just a phone call away. Flynn Systems is always available to discuss boundary scan in general, your project in particular, and how onTAP® can help you reach your goals. Flynn Systems offers a comprehensive suite of JTAG tools to meet your boundary scan testing needs, and we are always available to answer your questions, concerns, and inquiries regarding what JTAG is and how it can help you. But, first&#8230;</p>
<h2><span style="color: #000080;"><em><strong> What Boundary Scan Does<br />
</strong></em></span></h2>
<p>The boundary scan test architecture provides a way to test interconnects between integrated circuits (ICs) on a board without using physical test probes. It contains cells within a device that can capture data from pin or core logic signals or force data onto pins. The captured data is shifted out and externally compared to other results. Forced test data is shifted into the boundary scan cells. This is all controlled from a data path called the <strong>scan path</strong> or <strong>scan chain</strong>.</p>
<p>By allowing direct access to nets, boundary scan can eliminate the need for a large number of test vectors. These test vectors are normally needed to properly initialize sequential logic. The benefits of boundary scan technology were quickly realized through shorter test times, higher test coverage, increased diagnostic capability and lower equipment cost.</p>
<h3><span style="color: #000080;"><strong><em>A Brief History of JTAG Boundary Scan Testing</em></strong></span></h3>
<p>Boundary scan or the boundary scan test is also known as JTAG test or 1149.1. <strong>J</strong>oint <strong>T</strong>est <strong><strong>A</strong>ccess G</strong>roup (commonly referred to as JTAG) is a consortium of engineers from a multitude of electronics companies worldwide that formed over twenty years ago to meet the cries and pleas of standardization that the market was lacking. JTAG developed a standardized architecture for testing surface-mount devices applied to denser PCBs (Printed Circuit Boards), a test system commonly dubbed as JTAG or JTAG testing.</p>
<p>In the early 1980s, most PCB testing was achieved using the in-circuit bed-of-nails testers, which generally required physical access to all the devices on the board. This In-Circuit bed-of-nails technique provided an efficient and affordable method of testing boards. However, to meet the growing demands of miniaturization, denser (or layered) printed circuit boards began to dominate the market. This posed a huge problem for testing the electrical connectivity between devices, because board density and complex layering prevented the IC pins from being physically probed. Adding to this initial problem was the fact that real estate on boards was becoming a premium: the demand called for more devices with more information on smaller boards. Chip manufacturers met that demand with surface-mount technology.</p>
<p>As good as that was for shrinking technology, surface-mount packaging added complexity to the whole test process, not to mention board layout. Board design layout now had to provide test points for the bed-of-nails fixtures. Adding test points added noise to the board being tested, which created more complexity, more headaches, more delays and more financial cost. Without adding costly test points, access to IC pins could no longer be counted on and engineers as well as chip manufacturers had no set of standards by which to design, build and test. Enter the JTAG consortium.</p>
<p>The Joint Test Action Group originally began with participation from just European electronics companies in the mid-80s. As they sought to devise a specification for boundary scan testing, North American companies joined in the effort and the consortium gained sponsorship from the IEEE.</p>
<p>By 1990, that specification was ready to become the standard for boundary scan test. It was published as IEEE Std. 1149.1 and remains the foundation for boundary scan architecture. In 1994, an addition to the standard was made, which contained the <strong>B</strong>oundary <strong>S</strong>can <strong>D</strong>escription <strong>L</strong>anguage, more commonly known as BSDL. The BSDL IEEE supplement to 1149.1 describes the logic content of boundary scan compliant devices.</p>
<p>While the JTAG consortium remains active, adding more standards for boundary scan testing, the IEEE 1149.1 standard is the foundation upon which additional standards was built.</p>
<p><span style="color: #000080;"><strong><em>Flynn Systems</em></strong></span></p>
<p>Flynn Systems Corporation, a boundary scan vendor, offers onTAP, a dynamic PC-based boundary scan test software suite. onTAP Boundary Scan provides a cost-effective test solution which encompasses the entire life cycle of a product from development through production. onTAP Boundary Scan technology offers solutions to handle problems such as:</p>
<ul>
<li>Boards that include components assembled on both sides, burying most of the through-holes, thus making them inaccessible</li>
<li>Small-size products that do not have test points, making it difficult or impossible to probe suspected nodes</li>
<li>Loss of physical access to fine pitch components, making it complicated to distinguish between manufacturing and design issues</li>
</ul>
<p>For more information regarding onTAP or <a title="Boundary Scan Products &amp; Services" href="http://www.flynn.com/boundary-scan-products-and-services"><span style="text-decoration: underline;">Boundary Scan</span></a>, contact Flynn systems at</p>
<p>(603)-598-4444 or visit the website at <a href="http://www.flynn.com">www.flynn.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/new-to-jtag-boundary-scan-test-youre-not-alone/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boundary Scan Test Fault Insertion</title>
		<link>http://www.flynn.com/boundary-scan-test-fault-insertion</link>
		<comments>http://www.flynn.com/boundary-scan-test-fault-insertion#comments</comments>
		<pubDate>Sun, 10 Jun 2012 08:04:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Boundary Scan]]></category>
		<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[JTAG Boundary Scan]]></category>
		<category><![CDATA[onTAP]]></category>

		<guid isPermaLink="false">https://www.flynn.com/newsite/?p=1831</guid>
		<description><![CDATA[Use this function to: Check the fault coverage of your test for a specific fault condition. Insert an open fault without modifying your board or test fixture. Validate that your test is working as expected. How to Insert Faults 1. Create a file FaultInsert.txt in your test project directory. 2. Add fault declarations to the [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.flynn.com/central-and-eastern-european-distributorship-reaffirmed/ontap-logo-bscan-copy-2" rel="attachment wp-att-4059"><img class="aligncenter size-full wp-image-4059" alt="Flynn Systems provides the best JTAG boundary scan test software with their onTAP series 4000 with ProScan" src="http://www.flynn.com/wp-content/uploads/2008/08/onTAP-LOGO-BSCAN-copy.jpg" width="422" height="189" /></a></p>
<div style="line-height: normal;"><b><span style="font-size: 12pt;">Use this function to: </span></b></div>
<ul>
<li><span style="font-size: 12pt;">Check the fault coverage of your test for a specific fault condition.</span></li>
<li><span style="font-size: 12pt;">Insert an open fault without modifying your board or test fixture. </span></li>
<li><span style="font-size: 12pt;">Validate that your test is working as expected.</span></li>
</ul>
<div style="line-height: normal;"><b><span style="font-size: 12pt;">How to Insert Faults </span></b></div>
<div style="line-height: normal;"></div>
<div style="line-height: normal;"><span style="font-size: 12pt;">1. Create a file<b> FaultInsert.txt</b> in your test project directory.</span></div>
<div style="line-height: normal;"></div>
<div style="line-height: normal;"><span style="font-size: 12pt;">2. Add fault declarations to the <b>FaultInsert.txt</b> file as shown below. A sample file with syntax examples can be found in the /<strong>onTAP</strong> program directory.</span></div>
<div style="line-height: normal;"></div>
<table style="width: 381pt;" width="508" border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="padding: 0in; width: 30pt;" width="40">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in; width: 105pt;" width="140">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">open u6.15;</span></div>
</td>
<td style="padding: 0in; width: 262.5pt;" width="350">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// pin will be open to all signals</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">open u9.12,u12.8; </span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// multiple pins will fail to capture other pins&#8217; signals </span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">stucklow u6.18; </span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// pin and net are stuck low</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">stucklow u20.a5;</span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// all pins on net ADDR14 will be measured low</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">short u3.8 u2.10; </span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// shorts nets of pins in list, low values prevail.</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">drivelow u17.6;</span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// always drive pin to a low value</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">drivehigh u13.18;</span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// always drive pin to a high value</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">drivez u7.a2; </span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">// always drive pin to a high impedance</span></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">measurelow u20.9; </span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">measurehigh u67.3;</span></div>
</td>
<td style="padding: 0in;">
<div style="margin-bottom: 0.0001pt; line-height: normal;"></div>
</td>
</tr>
</tbody>
</table>
<div style="line-height: normal;"></div>
<div style="line-height: normal;"><span style="font-size: 12pt;">3. Run the project&#8217;s SVF file from the <a title="onTAP Series 4000 Overview" href="http://www.flynn.com/boundary-scan-products-and-services/ontap-series-4000-overview"><span style="text-decoration: underline;">onTAP</span></a> Test Screen.</span></div>
<div style="line-height: normal;"><span style="font-size: 12pt;">When onTAP detects a <b>FaultInsert.txt</b> file in your project folder, it posts a message so that when you run the the test, diagnostic messages corresponding to the inserted fault expressions are displayed.</span></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/boundary-scan-test-fault-insertion/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boundary Scan Software Evaluation Download</title>
		<link>http://www.flynn.com/boundary-scan-software-evaluation-download</link>
		<comments>http://www.flynn.com/boundary-scan-software-evaluation-download#comments</comments>
		<pubDate>Sun, 20 May 2012 14:00:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Boundary Scan]]></category>
		<category><![CDATA[Boundary Scan Test]]></category>
		<category><![CDATA[JTAG Boundary Scan]]></category>
		<category><![CDATA[Messages]]></category>
		<category><![CDATA[onTAP]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2536</guid>
		<description><![CDATA[Thank you for your interest in onTAP Boundary Scan software.  Please download and install onTAP Boundary Scan Software on your target machine.  Once you install onTAP, open and run the software.  This will generate a license.txt file.  Please copy this file and e-mail it to license@flynn.com.  We will activate your license and return a complete onTAP Boundary [...]]]></description>
				<content:encoded><![CDATA[<p>Thank you for your interest in onTAP Boundary Scan software.  Please download and install onTAP Boundary Scan Software on your target machine.  Once you install <em>onTAP</em>, open and run the software.  This will generate a license.txt file.  Please copy this file and e-mail it to<a href="javascript:location.href='mailto:'+String.fromCharCode(108,105,99,101,110,115,101,64,102,108,121,110,110,46,99,111,109)+'?'"> license@flynn.com</a>.  We will activate your license and return a complete <strong>onTAP</strong> Boundary Scan Software Evaluation.  We will also e-mail you with instructions on how to install and start developing tests with <a title="onTAP Series 4000 Overview" href="http://www.flynn.com/boundary-scan-products-and-services/ontap-series-4000-overview"><span style="text-decoration: underline;">onTAP</span></a> Boundary Scan Software.</p>
<p>Please click the &#8220;<strong>Download Now</strong>&#8221; button below to continue with the download.</p>
<p><big><strong>Current build 4393. Updated May 17, 2013. </strong></big></p>
<p><big><strong><em>Featuring: </em></strong></big></p>
<p><span style="font-size: medium;"><strong><em>Drag and Drop for cluster model association (Flash, Memory, and other non-JTAG devices)!</em></strong></span></p>
<p><big><strong><em>ShowMe! </em>Finally, accurate pin-level diagnostics for memory cluster test debugging!<br />
</strong></big></p>
<p><a href="http://flynn.com/files/downloads/ontap_setup.exe"><img alt="Download onTAP Boundary Scan Software, begin testing today!" src="/wp-content/uploads/image/PICS/download.gif" width="127" height="24" /></a><a href="http://flynn.com/files/downloads/ontap_setup.exe"><br />
</a></p>
<p>&nbsp;</p>
<p><span style="font-size: larger;"><strong>IMPORTANT NOTE: </strong></span></p>
<div style="text-indent: -0.25in; margin-right: 1.5pt;"><span style="font-size: 11pt;">·<span style="font: 7pt 'Times New Roman';">        </span></span><span style="font-size: 11pt;">onTAP builds 4217 and later include Microsoft Visual Studio redistributable DLLs in installation package so that onTAP should run without the MS redistributable. However, if there are DLL complaints when loading onTAP, please run the MS redistributable at this link:</span></div>
<div style="text-indent: -0.25in; margin-right: 1.5pt;"></div>
<div style="text-indent: -0.25in; margin-right: 1.5pt;"><span style="font-size: 11pt;">     <a href="http://www.microsoft.com/downloads/en/details.aspx?familyid=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&amp;displaylang=en">http://www.microsoft.com/downloads/en/details.aspx?familyid=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&amp;displaylang=en</a></span></div>
<p>&nbsp;</p>
<p><a href="/wp-content/uploads/file/onTAP%20Installation%20instructions.pdf" target="_blank"><span style="color: #000080;"><strong>VIEW INSTALLATION INSTRUCTIONS</strong></span></a> <img class="alignnone size-medium wp-image-253" title="pdf_symbol" alt="" src="/wp-content/uploads/2008/09/pdf_symbol.gif" width="16" height="16" /></p>
<p>&nbsp;</p>
<p><a href="http://www.flynn.com/boundary-scan-products-and-services/ontap-turn-key-service/"><strong>Please click here to learn more about our Turnkey Boundary Scan Solutions</strong></a></p>
<p><strong>&#8220;This [BLADE Network Research] is the second company I’ve used onTAP at, I’ve been using it for 3 or 4 years. Other vendors I’ve used tended to dismiss my problems or suggest a work around that just hides the problem. Lately I’ve been letting Flynn develop our applications because I just don’t have the time.  That’s another option if you need a boundary scan test but have way too many other testing details to sort out.&#8221; F. Roberts &#8216;Test Engineer&#8217; Blade Network Research<em><br />
</em></strong></p>
<p><a href="http://flynn.com">Continue browsing</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/boundary-scan-software-evaluation-download/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xilinx Download</title>
		<link>http://www.flynn.com/xilinx-download</link>
		<comments>http://www.flynn.com/xilinx-download#comments</comments>
		<pubDate>Mon, 09 Apr 2012 14:21:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Messages]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=3514</guid>
		<description><![CDATA[Thank you for your interest in onTAP Boundary Scan/JTAG solutions and XILINX compatibility. Once we receive your e-mail, we will e-mail you the documents you have requested.  Please be patient. Feel free to contact info@flynn.com with any questions about the software and JTAG solutions. Sincerely, Flynn Systems Continue browsing]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.flynn.com/central-and-eastern-european-distributorship-reaffirmed/ontap-logo-bscan-copy-2" rel="attachment wp-att-4059"><img class="aligncenter size-full wp-image-4059" alt="Flynn Systems provides the best JTAG boundary scan test software with their onTAP series 4000 with ProScan" src="http://www.flynn.com/wp-content/uploads/2008/08/onTAP-LOGO-BSCAN-copy.jpg" width="422" height="189" /></a></p>
<p>Thank you for your interest in onTAP Boundary Scan/JTAG solutions and XILINX compatibility.</p>
<p>Once we receive your e-mail, we will e-mail you the documents you have requested.  Please be patient.</p>
<p>Feel free to contact <a href="javascript:location.href='mailto:'+String.fromCharCode(105,110,102,111,64,102,108,121,110,110,46,99,111,109)+'?'">info@flynn.com</a> with any questions about the software and <a title="onTAP Series 4000 Overview" href="http://www.flynn.com/boundary-scan-products-and-services/ontap-series-4000-overview"><span style="text-decoration: underline;">JTAG</span> </a>solutions.</p>
<p>Sincerely,</p>
<p>Flynn Systems</p>
<p><a href="http://www.flynn.com/boundary-scan-products-and-services/">Continue browsing</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/xilinx-download/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>onTAP&#8217;s Mention in SMT Magazine</title>
		<link>http://www.flynn.com/ontaps-mention-in-smt-magazine</link>
		<comments>http://www.flynn.com/ontaps-mention-in-smt-magazine#comments</comments>
		<pubDate>Wed, 21 Mar 2012 18:53:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[onTAP]]></category>
		<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[onTAP Reviews]]></category>
		<category><![CDATA[Product News]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=3496</guid>
		<description><![CDATA[SMT Magazine: "onTAP Software includes every feature necessary to develop tests for complex multi-board assemblies without expensive add-ons. Apart from performing interconnect or CPLD/FLASH programming, this software also has the capability of developing custom cluster tests."]]></description>
				<content:encoded><![CDATA[<p><a href="http://www.flynn.com/central-and-eastern-european-distributorship-reaffirmed/ontap-logo-bscan-copy-2" rel="attachment wp-att-4059"><img class="aligncenter size-full wp-image-4059" alt="Flynn Systems provides the best JTAG boundary scan test software with their onTAP series 4000 with ProScan" src="http://www.flynn.com/wp-content/uploads/2008/08/onTAP-LOGO-BSCAN-copy.jpg" width="422" height="189" /></a></p>
<p><strong>&#8220;onTAP Software includes every feature necessary to develop tests for complex multi-board assemblies without expensive add-ons. Apart from performing interconnect or CPLD/FLASH programming, this software also has the capability of developing custom cluster tests.&#8221; </strong>A Barnai, SMT Magazine, March 2012. onTAP user since March, 2010</p>
<p>Last week, one of our valued onTAP Software users wrote an article for SMT Magazine describing his past five years of experience using boundary scan as a fundamental and critically important test and programming method.  The article is very much worth reading for the insight into his <em>boundary scan</em> application.  We think the best part, though, is when he outlines how his switch to onTAP  <strong>Boundary Scan</strong> Software has enabled him to improve his test development strategy and implementation.  According to him, onTAP&#8217;s full featured <span style="text-decoration: underline;"><a title="Boundary Scan Products &amp; Services" href="http://www.flynn.com/boundary-scan-products-and-services">boundary scan</a></span> solutions have facilitated better, more flexible tests because the software is so robust, and the technical support is responsive and helps him adapt the software to meet his needs.</p>
<p><input type="image" alt="onTAP mentioned in SMT Magazine" height="874" src="http://www.flynn.com/wp-content/uploads/image/for%20News/SMT%20Article.png" width="754" /></p>
<p>link to full article &#8211; March 2012, pp 40 &#8211; 46 <a href="http://www.smtonline.com/pages/smtmagazine.cgi">http://www.smtonline.com/pages/smtmagazine.cgi</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/ontaps-mention-in-smt-magazine/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
