JTAG Testing with XJTAG Boundary Scan (newer version available, click top right corner)

Рет қаралды 15,187

XJTAG Boundary Scan

Күн бұрын

Пікірлер: 9

@agstechnicalsupport 2 жыл бұрын

Beautiful product !

@marioriley7209 2 жыл бұрын

What a great tool!

@ionelraul8228 3 жыл бұрын

Super tools!

@bennguyen1313 Жыл бұрын

If Jtag is a standard for all devices, why are different programmers needed? i.e. an Altera/Intel USB-Blaster won't program a Xilinx FPGA? I assume inside the debugger adapter is just a USB to I/O converter.. why would different hardware be needed for different FPGAs/CPLDs? Microcontrollers seem like they are more universal.. for example, a J-Link will program a Arm from STMicroelectronics as well as from Microchip/Atmel. Is that because Arm leverages a standard CMSIS-DAP that can be used by OpenOCD, whereas FPGAs don't have such a standard?

@XJTAG Жыл бұрын

Hi Ben, The JTAG standard defines a low level interface between JTAG controllers/programmers and JTAG devices. It also defines how devices should implement Boundary Scan for assisting with testing PCBs during manufacture, but it did not initially include anything about how to program devices. This meant different manufacturers created their own ways to program their devices built on top of the same low level JTAG interface. Only hardware that knows about the programming protocol created by a manufacturer can program those devices. For example, an Altera/Intel USB-Blaster would be able to transfer data to a Xilinx FPGA via JTAG, but because the Altera/Intel USB-Blaster and software don’t know about the programming protocol that Xilinx created for their devices then it can’t program a Xilinx device. Additionally, because the programmers use their own protocols over USB, then you can’t use one programmer with another manufacturers’ software. XJTAG can be used to program FPGAs from many different manufacturers. This is done by running SVF or STAPL files generated by the FPGA manufacturer that includes the programming algorithm. The difference with the microcontrollers you mention is that they are all ARM based, and so even though the ICs are manufactured by different companies there has been one company defining how to interact with all of them. Although there are some differences that the software needs to know about (e.g. address maps for different devices), the underlying protocol doesn’t change and this makes it easy to use the same software and hardware to program many different microcontrollers. If you would like any further details, please contact us at www.xjtag.com/contact