Continue to Site

Welcome to EDAboard.com

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.

Register Log in

[SOLVED] JTAG TCK Speed Restriction

Status
Not open for further replies.
IanTrout

IanTrout

Newbie level 6
Joined
Apr 9, 2011
Messages
12
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
Israel
Activity points
1,371
Hi Everybody,

This is my first post on this forum, and I have a small question regarding JTAG...
The internal clock (TCK) of JTAG systems is restricted to several MHz, why is that?
Where's the bottle neck on the system? Has this bottle neck been addressed in the newer models of the standard (the IEEE 1149.7, or other draft standardizations)?

Ohh, and regarding the location of this post, I didn't know where to post it, so if one of the moderators has a better place for it, please just let me know for future reference...

Thanks in advance,
IanTrout
 

IanTrout said:
Hi Everybody,

This is my first post on this forum, and I have a small question regarding JTAG...
The internal clock (TCK) of JTAG systems is restricted to several MHz, why is that?
Where's the bottle neck on the system? Has this bottle neck been addressed in the newer models of the standard (the IEEE 1149.7, or other draft standardizations)?

Ohh, and regarding the location of this post, I didn't know where to post it, so if one of the moderators has a better place for it, please just let me know for future reference...

Thanks in advance,
IanTrout
Click to expand...

Ian,
There isnt a limitation on TCK in the 1149.1 standard itself. Like any synchronous data transmission there is a limit as to how much effort will be put into the IC design. Most devices top out at 50 or 60Mhz. This is fairly reasonable throughput for a full duplex ( 50mbits/sec of data going in two directions) protocol that is LVTTL based.
High speed links such as PCIe are based on LVDS, low voltage differential signaling. 1149.7 only advantage is the use of two pins, but this ends up being slower since it is half-duplex and has latency to turn the data stream around.
The other limit is due to routing TCK/TMS at the board level. Driving TCK/TMS with many end-points (inputs to each chip) over cable can limit frequency. A Scan Ring linker can give you more point-to-point routing and re-timing of the JTAG signals relative to TCK.
Hope it helps.
Cindy
 
Last edited by a moderator:
xilinx edk 750khz 1500khz .........24Mhz
 

treqer said:
xilinx edk 750khz 1500khz .........24Mhz
Click to expand...

To be clear, those are limitations of the Xilinx USB pod and not a limitation of all commercial JTAG pods nor the standard itself. Please note also that USB 2.0 is half-duplex and JTAG is full-duplex. Hence there is a lot of data transfer inefficiencies in USB 2.0 based pods since they must FIFO and hold the data every 256bytes or so and then turn the USB bus around.
The question was is there a TCK speed restriction in the standard and the answer to that is 'no'. There are limits in design, which brings around a 50Mhz/66mhz (some Xilinx parts) limitation.

Cindy
 

Oh! Can you explain why I am not running a chain of 32 units at the smallest frequency?
 

ckim said:
Ian,
There isnt a limitation on TCK in the 1149.1 standard itself. Like any synchronous data transmission there is a limit as to how much effort will be put into the IC design. Most devices top out at 50 or 60Mhz. This is fairly reasonable throughput for a full duplex ( 50mbits/sec of data going in two directions) protocol that is LVTTL based.
High speed links such as PCIe are based on LVDS, low voltage differential signaling. 1149.7 only advantage is the use of two pins, but this ends up being slower since it is half-duplex and has latency to turn the data stream around.
The other limit is due to routing TCK/TMS at the board level. Driving TCK/TMS with many end-points (inputs to each chip) over cable can limit frequency. A Scan Ring linker can give you more point-to-point routing and re-timing of the JTAG signals relative to TCK. Read more: JTAG linker

Hope it helps.
Cindy
Click to expand...

Thanks!
For some reason our teacher found it really hard to explain this to us, and basically dodged the question every time :)
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top