Understanding the JTAG Boundary Scan (BSCAN) Component

While reviewing the resource utilization report of the project, we discovered a special underlying hardwareBSCAN, as shown in 1. Let’s understand its uses and applications.

Understanding the JTAG Boundary Scan (BSCAN) ComponentFigure1.The resource report shows the number and usage ofBSCAN.

Understanding the JTAG Boundary Scan (BSCAN) ComponentFigure2.Finding the path ofBSCANin the code

Understanding the JTAG Boundary Scan (BSCAN) ComponentFigure3.Locating the project call to the underlying module

Understanding the JTAG Boundary Scan (BSCAN) ComponentFigure4.Finding the location and interconnections ofFPGAunderlyingBSCAN.

Understanding the JTAG Boundary Scan (BSCAN) ComponentFigure5.Finding where theMDMmodule inMBusesBSCAN.

Understanding the JTAG Boundary Scan (BSCAN) Component Understanding the JTAG Boundary Scan (BSCAN) Component

Figure6.It is found that inlanguagetemplatesit can also be found and called the underlyingBSCAN.

So what exactly is the underlying hardwareBSCAN?

Actually, it can be found thatBSCAN is used in two cases: the first is during traditionaldebug, for example, collecting data throughICON andILA VIO; the second is when users debug throughjtag insideMicroblaze.

This underlying module can be seen as an interface for users throughjtag and the boundary scan logic ofFPGA. In most application cases, tools will automatically call this underlying module, requiring engineers to care less about the underlying details, just a brief introduction^_^.

Note: Copyright belongs to the “FPGA That Thing” operation team, please indicate the source when reprinting.

We welcome you to scan the following QR code to follow “FPGA That Thing”!

Understanding the JTAG Boundary Scan (BSCAN) Component

Leave a Comment