<?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 test</title>
	<atom:link href="http://www.flynn.com/tag/boundary-scan-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>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>
		<item>
		<title>PC Based Parallel Test</title>
		<link>http://www.flynn.com/jtag-blog/pc-based-parallel-test/</link>
		<comments>http://www.flynn.com/jtag-blog/pc-based-parallel-test/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 17:03:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[onTAP JTAG Blog]]></category>
		<category><![CDATA[onTAP Usage]]></category>
		<category><![CDATA[boundary scan test]]></category>
		<category><![CDATA[JTAG boundary scan test]]></category>
		<category><![CDATA[parallel JTAG test]]></category>
		<category><![CDATA[Parallel test]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2707</guid>
		<description><![CDATA[Ontap_parallel.exe can be used to simultaneously run test suites on multiple PC boards using the onTAP DLL. Parallel board testing must be enabled for the DLL license. Testing is fastest on a multiple processor PC , particularly where one core processor is available for each board. For example if four PC boards are being tested in parallel, then a quad core processor is recommended so that the time to test four boards is about the same as that required to test one board.]]></description>
			<content:encoded><![CDATA[<p>Ontap_parallel.exe can be used to simultaneously run test suites on multiple PC boards using the onTAP DLL. Parallel board testing must be enabled for the DLL license. Testing is fastest on a multiple processor PC , particularly where one core processor is available for each board. For example if four PC boards are being tested in parallel, then a quad core processor is recommended so that the time to test four boards is about the same as that required to test one board.</p>
<p>&nbsp;</p>
<p><big><strong>Procedure for Running Tests in Parallel</p>
<p></strong></big>Create a separate folder for each board to be tested and in the folder place all of the tests that will be run for a board.</p>
<p>Launch an ontap_parallel.exe for each board to be tested, and for each instance of ontap_parallel.<br />
exe, browse to a folder with the tests for a designated board. In the SVF Files list, check the SVF files that will be run for the board.</p>
<p>Return to the first instance of ontap_parallel.exe and check the boards that you wish to run in the Board list.</p>
<p>Click Run Checked Board Folders to run the tests for one or more folders. Test results are left in the .test and .fail files for each test in each folder. The test and diagnostic messages can be seen on the screen by selecting, as opposed to checking, a board and then selecting an SVF file.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/jtag-blog/pc-based-parallel-test/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Flynn Systems Announces upgraded Boundary Scan Tools: onTAP Series 4000</title>
		<link>http://www.flynn.com/press-releases/flynn-systems-announces-upgraded-boundary-scan-tools-ontap-series-4000/</link>
		<comments>http://www.flynn.com/press-releases/flynn-systems-announces-upgraded-boundary-scan-tools-ontap-series-4000/#comments</comments>
		<pubDate>Sat, 15 Nov 2008 15:52:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Press Releases]]></category>
		<category><![CDATA[boundary scan]]></category>
		<category><![CDATA[boundary scan test]]></category>
		<category><![CDATA[free boundary scan/JTAG]]></category>
		<category><![CDATA[IEEE 1149.1]]></category>
		<category><![CDATA[JTAG]]></category>
		<category><![CDATA[JTAG Test]]></category>

		<guid isPermaLink="false">http://www.flynn.com/?p=2320</guid>
		<description><![CDATA[The goal is to exploit JTAG testing to achieve maximum fault coverage in addition to Flash programming and configuration tasks,” says Hank Flynn, CEO of Flynn Systems Corp. Like so many new features added to onTAP, Flynn’s introduction of the upgraded ATPG was a direct result of meeting customer needs. “Even if a tool has the capability to provide high fault coverage, when too much user intervention is required, chances are fault coverage goals will never be achieved. It’s clear that increased automation throughout the test prep experience is the key.” Says Flynn.]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<div><span style="font-size: 10pt;">Contact:</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">Wendy Harrison<br />
Flynn Systems Corp.<br />
74 Northeastern Blvd<br />
STE 16A<br />
Nashua, NH 03062-3192<br />
USA<br />
603-598-4444<br />
Sales@flynn.com</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">Navigating the Scan Path to Higher Fault Coverage</span></div>
<div>&nbsp;</div>
<div><strong><span style="font-size: 10pt;">NASHUA, NH</span></strong><span style="font-size: 10pt;"> August 15, 2008 &#8211; Flynn Systems Corp&rsquo;s onTAP Series 4000 featuring their newest tool, ProScan, boosts fault coverage and increases visibility for Boundary Scan/JTAG 1149.1 testing through increased automation and graphical interfaces. By tapping its roots as a leader in Automatic Test Pattern Generation, Flynn Systems has seamlessly integrated ATPG for boundary scan circuits with ATPG algorithms for complex networks of non-scan circuits, such as logic elements, buffers, transceivers, and resistor networks that often lie between boundary scan pins.</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">&ldquo;The goal is to exploit JTAG testing to achieve maximum fault coverage in addition to Flash programming and configuration tasks,&rdquo; says Hank Flynn, CEO of Flynn Systems Corp.&nbsp;Like so many new features added to onTAP, Flynn&rsquo;s introduction of the upgraded ATPG was a direct result of meeting customer needs. &ldquo;Even if a tool has the capability to provide high fault coverage, when too much user intervention is required, chances are fault coverage goals will never be achieved. It&rsquo;s clear that increased automation throughout the test prep experience is the key.&rdquo; Says Flynn.</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">&nbsp;&ldquo;When talking and meeting with customers, I recognized how easily fault coverage could be sacrificed in test preparation whenever the development software was not sufficiently helpful or too much user intervention was required. Development and test engineers are busy folks, so we had to make all aspects of boundary scan test development easy to use and understand and provide a software package that facilitates use of complex tools. This is where onTAP Series 4000 really opens doors.&rdquo; </span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">onTAP Series 4000 is a fully automated, netlist-based, boundary scan test, debug, and programming product.&nbsp;onTAP automatically initializes its ATPG algorithm to access a comprehensive library of models for non-scan devices, allowing it to manage and in effect to test through these devices.&nbsp;The user need only provide the BSDL files for the boundary scan/JTAG parts, and the netlist for the PCB.&nbsp;To make this process easier, Flynn Systems Corp. offers over 24 translators for popular CAD-based netlist formats, such as Allegro, EDIF, PADS, and OrCad. The test results are compiled into industry standard Serial Vector Format (SVF) files and supplementary diagnostic files used to provide pin-level diagnostic messages.&nbsp;</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">onTAP Series 4000 is part of a new series of testing and design tools from Flynn Systems offering greater flexibility, more automation and a more intuitive interface for novice boundary scan users and experts alike.&nbsp;Keep your eyes open for more advances in ease-of-use functionality from Flynn Systems this year. </span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">About Flynn Systems:</span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">Flynn Systems has provided test, debug, and programming solutions for the boundary scan test standard (JTAG IEEE 1149.1) for over ten years.&nbsp;Their onTAP software package is designed for completely automated boundary scan testing for devices of all levels of complexity on printed circuit boards (PCB) and non-boundary scan devices interacting with the scan enabled devices.&nbsp;onTAP&rsquo;s functionality also includes the capability to program FLASH enabled devices using only the onTAP USB Test and Programming Cable. Flynn Systems Corp. provides high level test suites and the highest fault coverage available with a powerful ATG engine: all backed by fast, responsive technical support. &nbsp;Its satisfied customers include Intel, Qualcom, Harris RF, Benchmark Electronics, Raytheon, L-3 Communications, Cadence Design, Stanford Linear Accelerator, Teradyne, Checkpoint Systems, Ulticom, and University of Arizona.&nbsp;Flynn Systems&rsquo; onTAP provides boundary scan services for university research, avionics, defense systems, consumer goods, and medical electronics.&nbsp;It is based in New Hampshire with distributors and partners in Europe. </span></div>
<div>&nbsp;</div>
<div><span style="font-size: 10pt;">Those interested are invited to download a free 30 day evaluation software package with full technical support available at <a href="http://www.flynnsystems.com/">www.flynnsystems.com</a>.</span></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.flynn.com/press-releases/flynn-systems-announces-upgraded-boundary-scan-tools-ontap-series-4000/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

