Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Contributor
elharrach
Posts: 41
Registered: ‎04-07-2009
0

Re: spartan3

and when i use a 5 pin jtag that exist in this card ,i will buy an simple jtag ,because the jtag is standard ,or for each card there must a special jtag ?
Expert Contributor
bassman59
Posts: 4,673
Registered: ‎02-25-2008
0

Re: spartan3


elharrach wrote:
and when i use a 5 pin jtag that exist in this card ,i will buy an simple jtag ,because the jtag is standard ,or for each card there must a special jtag ?

Duh! All you need is a USB cable!

 

-a


----------------------------------------------------------------
Yes, I do this for a living.
Xilinx Employee
barriet
Posts: 2,439
Registered: ‎08-13-2007
0

Re: spartan3

And the USB cable in question is included in the S3ESK kit.

Using your existing resources (S3ESK documentation and those provided in your other threads) - this should be clear.

Should you elect to not use the on-board JTAG programming cable and supply another one to connect to the JTAG chain (why, I'm not sure), you'll want a Xilinx programming cable adaptor. While JTAG is standardized (e.g. IEEE1149.1) the software interface to the cables is not. Chipscope/XMD/iMPACT/etc. are expecting a Xilinx cable like the PC4 or Platform USB.

 

bt

Contributor
elharrach
Posts: 41
Registered: ‎04-07-2009
0

Re: spartan3

then if you can RECONFIGURE rom with a simple cable usb , why is there jtags  pin ,and all this complexity ,because there is a pin in the card that can be no used!!!,

 

 

THANK YOU VERY MUCH

Xilinx Employee
barriet
Posts: 2,439
Registered: ‎08-13-2007
0

Re: spartan3

The alternate JTAG header (J28) is provided for applications that can't use the embedded Platform USB, e.g.

-your computer doesn't have a USB port (and you need to use a Parallel-IV cable)

-you are using a version of ISE prior to introduction of support for the Platform USB

It is also likely a tradition to provide JTAG access via a header and some users would expect it.

 

The SPI header (J12) is provided to program the SPI Flash - which is a different interface and protocol.

 

From the S3EK User Guide (ug230.pdf):

/*

The starter kit board also includes an on-board USB-based JTAG programming interface.
The on-chip circuitry simplifies the device programming experience. In typical
applications, the JTAG programming hardware resides off-board or in a separate
programming module, such as the Xilinx Platform USB cable.

 

Download FPGA designs directly to the Spartan-3E FPGA via JTAG, using the onboard
USB interface. The on-board USB-JTAG logic also provides in-system
programming for the on-board Platform Flash PROM and the Xilinx XC2C64A CPLD.
SPI serial Flash and StrataFlash programming are performed separately.

*/

 

Embedding this circuitry saves the average user from having to purchase a cable that is roughly the same cost as the board itself.

 

Since customers expect an evaluation board with a lot of configuration flexibility, our boards likely have more configuration circuitry than the average FPGA board.

 

bt

 

Contributor
elharrach
Posts: 41
Registered: ‎04-07-2009
0

Re: spartan3

can i store program of keyboard with jtag ?
on the occasion ,is there a program of keyboard ps/2?

THANK YOU
Contributor
elharrach
Posts: 41
Registered: ‎04-07-2009
0

Re: spartan3

can i store program of keyboard with jtag ? on the occasion ,is there a program of keyboard ps/2? THANK YOU
Visitor
praveenk
Posts: 21
Registered: ‎03-19-2013
0

Re: spartan3

hi,i am trying to use the picoblaze implemented frequency counter using KCPSM3...............its the same program given on xilinx frequence counter which is for Spartan 3E XC500E . but i am having a spartan 3 kit and i am trying to program it on spartan 3 ,i am getting some errors which i am unable to solve ...can some one help me with the errors............ the errors are:- Pack:679 - Unable to obey design constraints (LOC=SLICE_X8Y29) which require the combination of the following symbols into a single SLICEM component: MUXCY symbol "processor/sel_shadow_muxcy" (Output Signal = processor/sel_carry) MUXCY symbol "processor/zero_cymux" (Output Signal = processor/zero_carry) The carry muxes are not connected in the required manner. Please correct the design constraints accordingly.