<?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; Boundary Scan JTAG Turnkey Solution</title>
	<atom:link href="http://www.flynn.com/tag/boundary-scan-jtag-turnkey-solution/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>Accepting New Turnkey JTAG Projects</title>
		<link>http://www.flynn.com/product-news/turnkey-jtag-projects/</link>
		<comments>http://www.flynn.com/product-news/turnkey-jtag-projects/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 20:58:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[Product News]]></category>
		<category><![CDATA[Boundary Scan JTAG Turnkey Solution]]></category>
		<category><![CDATA[boundary scan test]]></category>
		<category><![CDATA[JTAG Test]]></category>
		<category><![CDATA[pre-developed tests]]></category>
		<category><![CDATA[turnkey boundary scan test]]></category>
		<category><![CDATA[turnkey JTAG test]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2747</guid>
		<description><![CDATA[We insure that your boundary scan tests are maximized for the highest possible fault coverage, are completely debugged, and are ready to put in the hands of test engineers on the manufacturing floor, so all they have to do is “press a button.”
We support our tests and we will support your manufacturer by answering questions and bringing them up-to-speed with boundary scan test and onTAP. ]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: small;"><span style="line-height: 115%;">Flynn Systems wants to let our users know that we are accepting new JTAG / Boundary Scan projects for Q1-2/10</span></span></p>
<div><span style="font-size: small;">While our standard Technical Support provides assistance with test and development issues, our boundary scan test development services go beyond onTAP&nbsp;technical support services by taking the<strong> boundary scan / JTAG test development and debugging</strong> off your plate, allowing you to focus your undivided attention on your core business issues as you move through development and prototyping into manufacturing.&nbsp;</span></div>
<div><span style="font-size: small;">&nbsp;</span></div>
<div><span style="font-size: small;"><span style="line-height: 115%;">Our Boundary Scan Test Development Service is very popular with both existing and new customers.</span>&nbsp; In fact, 4 out of 5 customers who have used onTAP boundary scan test development services once, immediately recognize the cost and time savings, and return within 4 months with another project.&nbsp; By turning over your JTAG / Boundary Scan test developm</span>ent to Flynn Systems, you are able focus on other aspects of your project without being distracted by developing and debugging boundary scan tests.</div>
<div>&nbsp;</div>
<div>We ensure that your boundary scan tests are maximized for the highest possible fault coverage, are completely debugged, and are ready for the manufacturing floor, so the end user only has to &ldquo;press a button.&rdquo;</div>
<div>&nbsp;</div>
<div>We support our tests and we will support you and/or your contract manufacturer by answering questions and bringing all parties involved up-to-speed with boundary scan test and onTAP procedures and reports.&nbsp;</div>
<div>&nbsp;</div>
<div>Our test development features:</div>
<ul>
<li>&nbsp;JTAG TAP infrastructure tests.</li>
<li>Interconnect tests including detection of opens, shorts, stuck-at, bus-wire, pull-up/down related faults.</li>
<li>Memory tests</li>
<li>Cluster tests of non-JTAG components</li>
<li>Flash programming</li>
<li>In-system programming configuration</li>
<li>Pin-level diagnostics</li>
<li>On-going support</li>
</ul>
<div style="margin-left: 0.5in; text-indent: -0.25in;">&nbsp;</div>
<div>All of our tests are comprehensive, accurate, supported and reliable.</div>
<div>&nbsp;</div>
<div>Call us today to get started.</div>
<p><a href="http://www.flynn.com/boundary-scan-products-and-services/ontap-turn-key-service/"><strong>Click here to learn more about onTAP Turnkey Service</strong></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/product-news/turnkey-jtag-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

