<?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 &#187; DFT and JTAG test</title>
	<atom:link href="http://www.flynn.com/tag/dft-and-jtag-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flynn.com</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 20:19:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Properly Managing Common Tri-State Control Cells Boosts Fault Coverage</title>
		<link>http://www.flynn.com/jtag-blog/properly-managing-common-tri-state-control-cells-boosts-fault-coverage/</link>
		<comments>http://www.flynn.com/jtag-blog/properly-managing-common-tri-state-control-cells-boosts-fault-coverage/#comments</comments>
		<pubDate>Wed, 16 Dec 2009 20:16:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[onTAP Usage]]></category>
		<category><![CDATA[boundary scan]]></category>
		<category><![CDATA[Boundary Scan JTAG Turnkey Solution]]></category>
		<category><![CDATA[boundary scan test]]></category>
		<category><![CDATA[boundary scan test types]]></category>
		<category><![CDATA[DFT and JTAG test]]></category>
		<category><![CDATA[JTAG]]></category>
		<category><![CDATA[JTAG boundary scan test]]></category>
		<category><![CDATA[JTAG Test]]></category>
		<category><![CDATA[turnkey JTAG test]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2800</guid>
		<description><![CDATA[ We are constantly exposed to new situations in boundary scan test and new approaches to using boundary scan to achieve better test fault coverage. One item standing in the way of higher, more accurate fault coverage is common tri-state control cells.]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: small;">As the boundary scan community continues looking for new ways to improve test procedures and achieve higher and higher fault coverage, we expect the test tools to compensate for shortcomings in silicon devices or board design.&nbsp;We are constantly exposed to new situations in boundary scan test and new approaches to using boundary scan to achieve better test fault coverage.&nbsp;One item standing in the way of higher, more accurate fault coverage is common tri-state control cells.</span></p>
<p><span style="font-size: small;">  <span style="line-height: 115%;">Common tri-state control cells are groups of pins on a common net.&nbsp; Just as the name suggests, they are tri-state pins, grouped together by a common function, sharing a boundary scan cell.&nbsp;Though this is efficient for circuitry, it poses some issues during JTAG test.&nbsp;For example, when a single pin on the common cell drives or senses a value, all the pins associated with that cell are forced to perform the same function, simultaneously.&nbsp;This is represented in the following drawing.</span></span></p>
<p><img src="file:///C:/Users/Ryan/AppData/Local/Temp/moz-screenshot-4.png" alt="" /></p>
<p><img src="file:///C:/Users/Ryan/AppData/Local/Temp/moz-screenshot-5.png" alt="" /></p>
<p><img width="414" height="174" alt="Tri-State Control Cell diagram for JTAG test" src="/wp-content/uploads/image/PICS/Tri-State%20Control%20Cells.jpg" /><br />
Un-handled common tri-state cells can have a negative impact on boundary scan test, dramatically reducing accuracy and fault coverage of opens and shorts tests because multiple pins sharing a common net drive in the same test vector, as displayed in the screen capture below.&nbsp;</p>
<p><img width="541" height="170" alt="onTAP JTAG Test showing Common Tri-State Control Cell un-tested" src="/wp-content/uploads/image/PICS/BLOG%20POSTS/ProScan%20no%20TriState.jpg" /><br />
<var>In this image, you can see pins U23.AA14 and U36.AE30 are on net U23_AA14. This test is not accounting for the tri-state pins on the common control cell, ultimately compromising fault coverage. </var></p>
<div><span style="font-size: small;"><var>The yellow 0 and 1 characters show drive, or boundary register update, values at each test vector, and the green L and H values show expected boundary register capture values on the vectors following an update.</p>
<p></var></span></div>
<p><img width="605" height="197" alt="Mv64360 boundary scan device multiple pins sharing common tr-state cells" src="/wp-content/uploads/image/PICS/BLOG%20POSTS/Mv6430%20TriState.jpg" /><var><span style="font-size: small;"><br />
</span></var></p>
<p><var><span style="font-size: small;">This image shows the netlist view of the Mv6430 <strong>boundary scan</strong> device, while the following image displays the pins in an expanded view.</span></var></p>
<p><img width="621" height="241" alt="onTAP Netlist Browser displays common tristate control cells for JTAG device" src="/wp-content/uploads/image/PICS/BLOG%20POSTS/Mv6430%20TriState%20Netsview.jpg" /></p>
<p>&nbsp;</p>
<p><img width="624" height="117" alt="ProScan test view showing additional vectors added to JTAG test for tristate condition" src="/wp-content/uploads/image/PICS/BLOG%20POSTS/tristate%20fixed.jpg" /></p>
<p>&nbsp;</p>
<div><var><span style="font-size: small;"><em>This image shows how the test was revised to account for the tri-state pins on the common control cell. &nbsp;The result is a boost in fault coverage, with the added benefit of making the test more accurate.</em></span></var></div>
<div>&nbsp;</div>
<div>As explained in the text box in this screen shot, onTAP accounts for the shared cells and adds additional test vectors to ensure pins do not drive simultaneously, allowing for more comprehensive tests that deliver higher, and most importantly, more accurate, test fault coverage.&nbsp;</div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/jtag-blog/properly-managing-common-tri-state-control-cells-boosts-fault-coverage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JTAG.TECT Reviews onTAP JTAG System</title>
		<link>http://www.flynn.com/jtag-blog/russian-review-new-jtag-hardware/</link>
		<comments>http://www.flynn.com/jtag-blog/russian-review-new-jtag-hardware/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 20:10:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[onTAP Reviews]]></category>
		<category><![CDATA[DFT and JTAG test]]></category>
		<category><![CDATA[JTAG Russia]]></category>
		<category><![CDATA[onTAP Review]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2695</guid>
		<description><![CDATA[&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160; Written by: Dr. Ami Gorodetsky of JTAG.TECT Please follow this link for the original Russian:&#160; http://www.jtag-test.ru/JTAGUniversity/articles/12-PE_6_2009.php View Dr. Ami Gorodetsky&#8217;s blog: http://moodle.cs.huji.ac.il/cs08/course/view.php?id=67703 In the 7th paper of our &#8220;JTAG and DFT Basics Tutorial&#8221; series we had briefly examined the software basics of US based Flynn Systems&#8217; (www.flynn.com ) onTAP Boundary Scan system that is [...]]]></description>
			<content:encoded><![CDATA[<p><strong>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </strong></p>
<table cellspacing="1" cellpadding="1" border="0" style="width: 387px; height: 83px;">
<tbody>
<tr>
<td>Written by: <strong>Dr. Ami Gorodetsky of JTAG.TECT</strong></td>
<td><a href="http://www.jtag-test.ru"><img width="119" height="62" alt="Russian JTAG.TECT onTAP Boundary Scan Solutions Russian Distributor" src="/wp-content/uploads/image/JTAG%20TECT%20Logo%20copy.gif" /></a></td>
</tr>
</tbody>
</table>
<p><a href="http://www.jtag-test.ru"><br />
</a></p>
<p>Please follow this link for the original Russian:&nbsp; <br />
<a href="http://www.jtag-test.ru/JTAGUniversity/articles/12-PE_6_2009.php">http://www.jtag-test.ru/JTAGUniversity/articles/12-PE_6_2009.php</a></p>
<p>View Dr. Ami Gorodetsky&#8217;s blog: <br />
<a href="http://moodle.cs.huji.ac.il/cs08/course/view.php?id=67703">http://moodle.cs.huji.ac.il/cs08/course/view.php?id=67703 </a></p>
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">In the 7<sup>th</sup> paper of our &ldquo;JTAG and DFT Basics Tutorial&rdquo; series we had briefly examined the software basics of US based Flynn Systems&rsquo; (</span><a href="../../../../../../"><span style="font-size: 12pt;">www.flynn.com</span></a><span style="font-size: 12pt;"> ) onTAP Boundary Scan system that is intended for the JTAG test development, execution, and debugging, but the system hardware was not mentioned in the paper. In this sequential 12<sup>th</sup> paper of the series&nbsp;we will overview the hardware of this very popular JTAG test system that is in worldwide usage for the JTAG-based test and in-circuit programming and flash burn-in stations, both in the lab environment and on the production facilities.</span></div>
<div style="margin-bottom: 0.0001pt; line-height: normal;">&nbsp;</div>
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">One of the noticeable and special features of the onTAP, which fairly distinguishes it from the hardware of competitor&rsquo;s systems, is the surprising simplicity and mobility of the onTAP interface and, correspondingly, its low price. The onTAP hardware consists of the following three groups: two interface USB-adapters (the 6 MHz FS-9160 and the 30 MHz Dual Channel FS-9165), the FS-9180 TAP Serializer and GPIO Board, and a series of parallel JTAG-cables of different vendors (Xilinx, Altera, Lattice, etc.) that onTAP also supports. Designation of both USB-adapters, connected between a user&rsquo;s PC and the UUT, is to support the operating voltages in the range of 1.8V to 5V, to increase the loading capacity and noise protection of the JTAG bus, and therefore, notably increasing the permissible distance between the PC-based test station and the UUT without any additional TCK frequency constraints.</span></div>
<div style="margin-bottom: 0.0001pt; line-height: normal;">&nbsp;</div>
<div style="margin-bottom: 0.0001pt; line-height: normal;"><span style="font-size: 12pt;">The USB interface adapters together with the onTAP software allow for an easy and very mobile platform, without any noticeable limitations, to enlarge a quantity of JTAG chains utilized in the test, identical or different. In other words, the JTAG test preparation for a printed circuit board that contains <i>n</i> JTAG chains requires to have <i>n</i> FS-9160 adapters, or <i>n/2</i> FS-9165adapters. With the usage of the FS-9180 TAP Serializer and GPIO Board the number of adapters can be substantially reduced. The same hardware setup (with the FS-9180 TAP Serializer or without it) also supports the simultaneous testing of <i>n</i> identical printed circuit boards with one or several JTAG chains; this situation is frequently encountered during the testing of similar printed circuit boards in mass production.</span></div>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/jtag-blog/russian-review-new-jtag-hardware/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

