topic Re: JTAG Digital Waveform Library in Components

JTAG Digital Waveform Library

Christian_L — Mon, 06 May 2024 20:16:42 GMT

Please post feedback, questions, and comments on the JTAG Digital Waveform Library in this thread.

- David

(posted by Christian on behalf of David)

Re: JTAG Digital Waveform Library

andrepereira — Mon, 04 May 2009 18:47:00 GMT

Hi Christian,

A customer of mine is looking into a low cost, efficient test platfform to deploy and test embedded systems through JTAG. Questions: is it really possible to implement such solution using one of our M Series device with clocked DIO? Is there any example showing the integration between this library and the DAQmx driver API?

I'm sort of new to JTAG, so any info would be really appreciated.

Thanks

Re: JTAG Digital Waveform Library

David S. — Mon, 06 May 2024 20:17:42 GMT

Hi all -

I've published a new Reference Application that should prove useful when working with the IDW, JDW, and SDW libraries: Serial Protocol Communication with Digital Waveform Devices. It explains how to configure an NI-HSDIO or NI-DAQmx based device to work with one of these libraries. Check it out, and please rate it!

Re: JTAG Digital Waveform Library

alevine — Wed, 17 Jun 2009 18:22:50 GMT

Hi,

My company has an NI PXI system with 2 PXI- 6509 DIO controllers. We would like to perform JTAG and SPI with these devices to test various systems.

The speed is not terribly important (we understand that the 6509 is has slower switching time), but would like a JTAG and SPI VI library that supports this 6509 board.

Can JTAG Digitial Waveform Library work in this environment, or can you recommend a different approach.

Thanks

Aaron

Re: JTAG Digital Waveform Library

David S. — Wed, 17 Jun 2009 18:32:06 GMT

Hi Aaron -

That exact same question -- using a 6509 for serial protocol communication -- was asked over in the SDW thread. You can read the dialogue I had with "sugeo" there. In short, the JDW library is designed to work with a hardware-clocked DIO device and can't be used with the 6509. You'll have to write code to toggle the I/O lines manually from your software application, similar to TomW [DE]'s SPI hack.

Re: JTAG Digital Waveform Library

0AintLifeGrand0 — Fri, 13 Nov 2009 19:26:38 GMT

Hello,

I'm wondering what speeds are reachable with this solution..

Let's say I use a NI-PCIe6535 (10MHz HDSIO), well it is in the HSDIO section but it actually uses DAQ drivers if I understood correctly.

What is the data/clock rate I can reach while using the JDW.

Is this the max clock speed of the 6535?

And for the SPI/I2C Waveform libs?

Re: JTAG Digital Waveform Library

David S. — Fri, 13 Nov 2009 19:55:19 GMT

Hi AintLifeGrand -

You can actually figure this out without needing any hardware. Just open up any JDW or SDW example program and enter the smallest delays possible in the "timing (ns)" cluster. (A 10 MHz sample clock has a period of 100 ns, so this is your smallest value.) Then step the serial clock (TCK or SCLK) frequency up to the maximum value you can get without throwing an error. I found that JDW can create a 5 MHz JTAG waveform with a 10 MHz sampling device.

You can't use IDW with the 6535. Only the 6547/8 and 6551/2 can be used with IDW. These devices support per-cycle tristating.

Remember also that you'll have to remove the "TDO" channel from the waveform when you use JDW with a 6535 device (or "MISO", in SDW).

Message Edited by David S. on 11-13-2009 01:55 PM

Re: JTAG Digital Waveform Library

0AintLifeGrand0 — Fri, 13 Nov 2009 20:12:59 GMT

Hmm, I am reading these pages for a couple of weeks now, and I believe that I previously did see examples of I2C 'emulated' with the 6535? Has the waveform library, or the "reference manual" been changed in the meantime?

PS. Can't I read in the TDO data? Or do I just have to remove from the waveform because it is using the hardware compare option?

Re: JTAG Digital Waveform Library

David S. — Mon, 06 May 2024 20:18:59 GMT

Hi AintLifeGrand-

The only edit was to remove the 6533/4 from the list of compatible devices after discovering that it lacks the necessary trigger/event routing capability. Other than that, only grammatical changes have been made to date. IDW relies wholly on per-cycle tristating to create an open-drain output. You can't have bidirectional communication on an I2C bus without it. The 6535 doesn't have this feature, so it can't be used with IDW.

P.S. You just have to remove the TDO channel from the waveform because it uses HWC bit states (X, L, H). You can still configure the DI task to read in the data, though parsing through it won't be as easy or as computationally efficient as it is with HWC. See the reference programs in Serial Protocol Communication for an example.

Message Edited by David S. on 11-13-2009 02:26 PM

Re: JTAG Digital Waveform Library

0AintLifeGrand0 — Fri, 13 Nov 2009 21:01:21 GMT

Hello David,

Thanks for the quick response.

The I2C functionality I was talking about was in the IDW forum topic (The following is your text) Quote :

You may be able to edit the IDW source code to work with a DAQmx-based device, but you'll have to work with only a subset of the functionality. Here are some pitfalls and workarounds I can see:

The only other clocked DIO device that supports open-collector outputs is the 6534. If you use a DAQ (E-, M-series, etc.) or another 653x device, you'll be stuck with actively driven outputs. This means that you won't be able to listen to the slave's responses (data and ACK) while the DO session is active.
No other device supports the compare and tristate states (L, H, X, Z, V, T) in a waveform. You'll have to either edit the IDW code to generate an active-drive waveform (1 and 0 only) or write a find-and-replace function that changes the Z's to 1's.
Without per-cycle tristating, you'll have to tell the DO session to tristate the buffers immediately after generating each segment of the waveform, so you don't interfere with the DUT's attempt to respond with an ACK bit or a data byte.
You can trigger the acquisiton (DI) task off the generation (DO) task to capture an ACK bit after you've sent data -- or to capture a data byte after the first ACK bit. Because of the above requirement of ending the DO session after generating the waveform though, this means that you'll have to stop-and-restart the sessions to transfer every byte. Some chips have a maximum limit to the amount of time between clock pulses; make sure you won't violate it waiting for the software to restart the sessions.
Without hardware compare, you'll have to write a bit-banging funciton to parse the acquired waveform and extract the valid bits that were sent by the slave.

It's not an impossible task, but it's largely simplified by the 655x's features.

So that is what I was talking about, so let's call it a glitch in my brains 'lookup table'.

Thnx for the quick response.

Kind Regards, Danny

Re: JTAG Digital Waveform Library

0AintLifeGrand0 — Mon, 04 Jan 2010 14:53:58 GMT

Hello David,

I'm now building a schematic for my new PCIe-6535. This testcase is a simple SPI bus expander, to test the SPI emulating. I still haven't looked in the programming/software behind the 6535 or behind the SDW/JDW lib's.

Can you tell me, when I use a device as the PCIe-6535 for emulating JTAG/SPI with the SDW JDW reference designs, should I then connect all lines (SCK,SI,SO,CS) to the Dig IO channels, or do I need to use the so called PFI channels as well?

Since your bit-banging I would guess you need only DIO?

Kind regards

Re: JTAG Digital Waveform Library

David S. — Mon, 04 Jan 2010 15:51:03 GMT

Yes, the DIO channels are used for the bus signals. (The PFI lines are all static, so they can't be used.)

Re: JTAG Digital Waveform Library

cous — Mon, 06 May 2024 20:19:34 GMT

In the Serial Protocol Communication Reference Design for Digital Waveform Devices document, it mentions, "During the Initialization sequence, configure the device's Hardware Compare engine to operate in "Stimulus and Expected Response" mode." There is a graphic showing the niHSDIO property node with the attribute "HardwareCompare.Mode" and there is an enum feeding it set to "Stimulus and Expected Result". Where is that attribute? I can't find it. I'm using LV 2009 and NI HSDIO 1.7.2.

I do see an attribute for "Supported Data States" which I can set to HWC mode which allows for 0, 1, Z, L, H, and X on the stimulus and response. Is that the same as setting the Hardware.Compare.Mode?

thx,

-marcus

Re: JTAG Digital Waveform Library

David S. — Tue, 05 Oct 2010 23:43:25 GMT

Hi marcus -

Yes, they're the same thing. It looks like the properties were changed in a recent version. You can see in the context help for that property that it's used to configure the device for Hardware Compare mode.

Since it looks like you work at NI too -- you have a blue icon next to your name -- just call my extension or email me if you have any more questions.

Re: JTAG Digital Waveform Library - incorrect comment in example VI

illini — Mon, 15 Nov 2010 22:07:07 GMT

In the LV 8.6 package, the JDW Get IDCODE.vi example has an error in comment text on the block diagram.

It says: "1. Initialize the waveform, preallocating samples in memory. If desired, begin by clocking in five 0's on the TMS line to initialize the device to the TEST-LOGIC-RESET state"

Clocking five 1's will reset to TEST-LOGIC-RESET. This is what the example actually does - so the '0' should simply be replace with a '1'.

Re: JTAG Digital Waveform Library

nxb — Tue, 04 Jan 2011 18:25:48 GMT

Hi all

I was wondering if there is a way to send JTAG Digital Waveforms generated by LabVIEW into a parallel port or USB port. I know that there is a way to use DAQmx devices with JTAG Digital Waveforms where DAQmx drivers take JTAG Digital Waveforms and transfer that into physical signals which is then send to UUT. I really am in a need to try to mimic whatever a DAQmx can do to make that happen with a parallel port or usb port. I would really appreciate if you can help me it is very urgent. Also I would really appreciate if there is another cheaper device or a way that can replace DAQmx so I can send those JTAG signals to my UUT. By the way I am using LV8.6.

Thanks

Re: JTAG Digital Waveform Library

moderator1983 — Wed, 16 Mar 2011 08:35:31 GMT

Hi Everyone,

I wanna know, if "JTAG Digital Waveform Reference Library" cna be used with R-Series cards (specifically PXI-78XXR series).

And the main concern is to implement/establish communication using JTAG interface (IEEE 1149.1).

Please help me with the issue.

Thanx and Regards

Re: JTAG Digital Waveform Library

David S. — Wed, 16 Mar 2011 14:53:19 GMT

Hi moderator -

As explained in the Serial Protocol Communication whitepaper, JDW is designed to work only with vector waveform devices like NI DAQ and HSDIO. It does not work with RIO (R-series, FlexRIO, cRIO) devices.

Re: JTAG Digital Waveform Library

moderator1983 — Wed, 16 Mar 2011 17:21:03 GMT

Thank you David for your reply....

Could you guide me, I've PXI 7833R and want to implement JTAG interface to perform 'Boundary Scanning', is there any knowledge base or example or case study.....?

Re: JTAG Digital Waveform Library

ravirmsp — Tue, 24 May 2011 15:33:03 GMT

Hi Christian,

Thanks for the JTAG Digital Waveform Library. Really it reduces the protocol development time drastically.

I am using your example VI called HSDIO JTAG - Core Features.vi to generate JTAG signals TCK, TMS, TDI and TRST and acquire JTAG signals TCK, TMS, TDI, TDO and TRST with HSDIO PXI 6552 card. I have the following question in the above example.

What is the meaning of the following control JTAG channels in the example.

Can I expect TCK in channel 0, TMS in channel 1, TDI in channel 2, and TDO in channel 3 of the HSDIO card. Otherwise please suggest me how to map the JTAG channels with HSDIO channels.

I am using the same JTAG channels configuration for my program but I am getting