Re: can't read device ID xcv200....what about the PROGRAM pin

Bob schrieb:

> "blisca" <blisca@tiscali.it> wrote in message
> news:44a93c14$0$3119$4fafbaef@reader1.news.tin.it...
> > for reading the device ID how should the PROGRAM pin be ?
> >
> > thank you all
> > (i'm still spending hours  and days trying to do it,no way....no activity
> > on
> > TDI or TDO)
> >
> >
>  [snip]
>
> TDI is the input and TDO is the output (at the FPGA). If you don't see
> activity (ever) on the FPGA's TDI pin then this is your problem. You may
> have the JTAG controller's TDI/TDO pins swapped. Are you using "flying
> leads" to connect the controller to your FPGA board? It's easy to get those
> wrong.
>
> I suggest you disconnect the controller from your board, and see which of
> the controller leads (TDI or TDO) wiggles when it attempts to communicate.
> The one that wiggles should be connected to the FPGA's TDI pin.
>
> Bob

good bob!

I was wondering that too in the original post but assumed it a typo
but assumptions are usually wrong.

testing TDI-TDO loop is one of the first things todo of course

Antti

blisca schrieb:

> > but assumptions are usually wrong.
> >
> > testing TDI-TDO loop is one of the first things todo of course
> >
> > Antti
> >
>
> can i do it with iMPACT?or only from line comands?thank you
>
> PS   sorry again because i forget to type the "E", xcv200E

sure you can use the impact "debug mode"

connected your cable TDI-TDO
and shoft some pattern and observer results, eg

Antti

> but assumptions are usually wrong.
>
> testing TDI-TDO loop is one of the first things todo of course
>
> Antti
>

can i do it with iMPACT?or only from line comands?thank you

PS   sorry again because i forget to type the "E", xcv200E

Bob <nimby1_NEEDSPAM@earthlink.net> wrote in message
X4dqg.2323$ye3.71@newsread1.news.pas.earthlink.net...
>
> "blisca" <blisca@tiscali.it> wrote in message
> news:44a93c14$0$3119$4fafbaef@reader1.news.tin.it...
> > for reading the device ID how should the PROGRAM pin be ?
> >
> > thank you all
> > (i'm still spending hours  and days trying to do it,no way....no
activity
> > on
> > TDI or TDO)
> >
> >
>  [snip]
>
> TDI is the input and TDO is the output (at the FPGA). If you don't see
> activity (ever) on the FPGA's TDI pin then this is your problem. You may
> have the JTAG controller's TDI/TDO pins swapped. Are you using "flying
> leads" to connect the controller to your FPGA board? It's easy to get
those
> wrong.
>
> I suggest you disconnect the controller from your board, and see which of
> the controller leads (TDI or TDO) wiggles when it attempts to communicate.
> The one that wiggles should be connected to the FPGA's TDI pin.
>
> Bob
>
>
Thank you Bob but no doubt about the wires of my jtag controller,they  have
different color,using the debug chain of iMPACT i can verify the toggling of
the signals until the ball pin on the FPGA itself