Category: Boundary Scan

Boundary Scan devices must be capable of executing all Boundary Scan instructions specified by the IEEE 1149.1 standard. If the Boundary Scan devices are not capable of executing these instructions correctly, the ScanWorks test actions that is built, when applied to the UUT, will return incorrect data. This blog goes into details for how to build the ScanPath Verify action using ScanWorks.
Itโ€™s been great to reconnect with our Boundary Scan customers across the United States and Europe over the last several months discussing the new and exciting projects they have in the works. Itโ€™s also exciting to learn how our Boundary Scan product, ScanWorks, will play an integral role in the test, debug, validation, and deployment of these products. During one of these recent visits to a company that I consider a real power user of ScanWorks, the engineering manager who was participating in the meeting asked, โ€œWhat is the best way for our new engineers to learn Boundary Scan?โ€
In addition to the BC_1 Boundary Scan cell type, there are more Boundary Scan cell types that can be used to create a Boundary Scan Register and implement the IEEE 1149.1 operations within a Boundary Scan device. The type(s) of Boundary Scan cell(s) implemented within a device are listed in the BSDL. Basic Cell (BC)_0 through BC_7 are the standard Boundary Scan cell types commonly found in an IEEE 1149.1 compliant Boundary Scan device. You may ask the question, โ€œAre there more Boundary Scan cells than BC_0 through BC_7?โ€
Boundary Scan Description Language (BSDL) provides a description of testability features within ICs that comply with the IEEE 1149.1 Standard (hereinafter used interchangeably with the term โ€œJTAGโ€). Having a good understanding of the BSDL leads to a deeper knowledge of JTAG, that in turn grants insight into the technology behind IEEE 1687, also known as IJTAG.
Archives