If the boundary scan software that runs your production test has just been discontinued — the vendor sunset the product, dropped support for your controller, or was absorbed and the tool quietly disappeared — the honest answer to “what now?” is this: your test programs are an asset you can carry forward, not something you have to rebuild from scratch. The netlist, BSDL libraries, and fault-graded vectors that took months to validate still describe your board. The job is migrating that intellectual property onto a supported JTAG boundary scan platform before an end-of-life tool strands a running line. After thirty years of moving customers off obsolete test systems, here is the migration path we walk them through.
What “End of Life” Actually Puts at Risk on Your Line
A discontinued boundary scan tool rarely stops working the day it is announced. The risk is slower and more expensive than a dead application. The controller hardware ages with no replacement path, so one failed interface unit can idle a test station. Newer devices ship with BSDL models the frozen software will never learn to parse. And when a board spins — an engineering change order, a component substitution, a new revision — you discover the tool that can regenerate the program no longer exists.
That is the real exposure of an end-of-life JTAG test tool: not today’s throughput, but the first change order you cannot service and the first controller you cannot buy. Planning the move while the old system still runs is far cheaper than reacting after it fails.
Your Test Program Is Portable — Here Is What Carries Over
The reason migration is a project measured in days rather than months is that the inputs to a boundary scan program are open, standardized descriptions of your hardware, not proprietary secrets locked inside the old tool. When you move to onTAP, this is the material that comes with you:
- The board netlist — your connectivity is the ground truth a new automatic test generator reads to build interconnect and shorts tests.
- Device BSDL files — the IEEE 1149.1 boundary register descriptions are standard, so the same models the old tool used are re-used directly.
- Fault coverage intent — the nets you needed to guarantee do not change because the software did; the coverage target moves with the board.
- Flash and programming payloads — the images you program in-system are your data, independent of whichever tool drives the JTAG chain.
- Fixturing and access points — the four-wire JTAG connection that reached your board still reaches it; often no hardware change is needed at all.
Because these inputs are standards-based, re-targeting them is a software task. That is the same principle behind custom test development in automated JTAG testing — the program is generated against your netlist, so it can be regenerated on a supported platform.
How the Migration to onTAP Works
The practical sequence is straightforward. You send the board netlist and the device list; the toolchain resolves BSDL for each part and generates a fault-graded interconnect, memory-cluster, and flash-programming program against the new controller. The result is a program you own and can regenerate — not a black box. For teams without spare test-engineering hours to run the port, our FS-ATG test vector generation service produces the graded program for you, and the full onTAP turnkey service takes it all the way to a running station on the floor.
The hardware side is deliberately low-drama. onTAP drives the same IEEE 1149.1 chain your old tool did through supported JTAG controllers for test and programming, and the platform carries a published onTAP support policy — the thing your discontinued tool no longer offers. If you are weighing options, our guide to choosing the right JTAG test solution for your line lays out the criteria that matter past price.
What You Gain by Not Waiting for a Forced Migration
Migrating on your schedule, while the old line still runs, means you validate the new program against known-good boards in parallel, keep both systems live through the cutover, and never ship untested product. Migrating after a failure means doing all of that under pressure with a station down. The difference is entirely in the timing — the technical work is the same either way, so the only variable you control is whether it happens calmly or in a crisis.
A supported platform also reopens the doors the frozen tool had closed: new BSDL for the parts you are designing in now, current controllers you can actually purchase, and a path to newer capability such as the onTAP Series 4000 for modern PCB manufacturing.
Frequently Asked Questions
Do I lose my existing test coverage when I switch boundary scan tools? No. Coverage is defined by your board’s netlist and the IEEE 1149.1 devices on it, not by the software brand. Regenerating the program against the same netlist on onTAP reproduces — and often improves — the fault coverage you had.
Can I reuse the BSDL files from my discontinued tool? Yes. BSDL is an IEEE standard describing each device’s boundary register, so the same files carry directly into the new toolchain. Where a part’s model is missing, current BSDL is available for devices the frozen tool never supported.
Do I have to replace my JTAG controllers and fixtures? Usually not the fixtures — the four-wire JTAG access to your board is unchanged. You move to supported controllers, but the connection point on the board and much of your test setup stay as they are.
How long does a migration take? Because it is a software re-targeting rather than a rebuild, a graded program is typically turned around in days once the netlist and device list are in hand, not the months the original development took.
Move Before the Deadline Moves You
A discontinued boundary scan tool is a countdown, not an emergency — as long as you act while it is still running. Your netlist, BSDL, and vectors are portable, the JTAG access to your board does not change, and a supported platform ends the obsolescence spiral for good. To scope your migration, contact Flynn Systems with your board and device list for a coverage assessment, or review the full onTAP products and services line to see the supported path off your end-of-life tool.
0 Comments