Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
The DFT structures are inserted usually by the synthesis tool, so Genus for Cadence and Design Compiler for Synopsys. The typical flow is to get a first synthesis to pass. Then you go adding the DFT commands until you get it like you want. This includes boundary scan, regular scan chain, MBIST, perhaps LBIST, and perhaps a JTAG IP. The tool does create some files that will be used by the P&R too.
Depends on the tool and the exact DFT features you are using. I never inserted the boundary scan, but from other DFT commands I have done I know you need to define the jtag instructions, define the JTAG registers, and create them using Genus commands. You might need to crea an iospec file. You can use add_jtag_boundary_scan -preview and write_dft_jtag_boundary_file can be used to get a template, modify and then use it.
Files generated, asside from the netlist, reports, and so on, Genus will also generate a BSDL file, for generating the sequences for testing the board and a final IO spec file which will have the exact order of the pins and some features used. Additionaly it is a good idea to let genus generate SDC files for innovus, with timing constraints for the functionality Genus added. The P&R will need some of these files, the BSDL is more for the testers.
You will have to go through the manual though for a complete list of files, but I think this is a starting point
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.