FPGA Central - World's 1st FPGA / CPLD Portal

FPGA Central

World's 1st FPGA Portal

 

Go Back   FPGA Groups > NewsGroup > FPGA

FPGA comp.arch.fpga newsgroup (usenet)

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 09-25-2003, 02:01 PM
T. Irmen
Guest
 
Posts: n/a
Default chipscope pro and jtag

Hi ,

my question is about using/modifiying ChipScope Pro:

I have a direct access to the jtag pins through my own device driver. Now I
wanna use this pins with the chipscope pro software. I thought about adding
a filter driver ontop of the xilinx driver and redirect all access to my pci
card.

But before I try this workaround, I wanna ask some guys who might have been
done such crazy things.

thanks in advance,
thomas


Reply With Quote
  #2 (permalink)  
Old 09-25-2003, 06:49 PM
Antti Lukats
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

"T. Irmen" <[email protected]> wrote in message news:<[email protected]>...
> Hi ,
>
> my question is about using/modifiying ChipScope Pro:
>
> I have a direct access to the jtag pins through my own device driver. Now I
> wanna use this pins with the chipscope pro software. I thought about adding
> a filter driver ontop of the xilinx driver and redirect all access to my pci
> card.
>
> But before I try this workaround, I wanna ask some guys who might have been
> done such crazy things.


crazy things are fun, but in your case it want help
xilinx uses kernel driver that bypasses IO virtualization, so request
from
chipscope are executed to hardware directly (executing at x86 ring 0)
you can not intercept that.

choices are:
1 external hardware that wraps Xilinx Cable III to your hardware
2 internal PCI board that emulates a LPT device and Cable III and
rewraps to you adapter
3 fake kernel driver that you use to replace xilinx driver, you need
full disassembly and RE for that
4 fake communication DLL again full disassembly and RE needed.
5 intercept dll, it exposes xilinx DLL entry points and call xilinx
dll
(that you have renamed) part of the calls are re routed to your dll
that then talks to your hardware
6 you install windows in BOCHS PC simulator, install chipscope in
windows that runs in bochs, and you use customized BOCHS (rewrite and
recompile!) to reroute the hardware access to your device.

FUN!
antti
Reply With Quote
  #3 (permalink)  
Old 09-25-2003, 09:59 PM
T. Irmen
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

Hi Antti,

> 5 intercept dll, it exposes xilinx DLL entry points and call xilinx
> dll
> (that you have renamed) part of the calls are re routed to your dll
> that then talks to your hardware


that sounds good to me.

I never thought of that way. Isnīt it possible to stack a filter onto xilinx
kernel driver?

Do you know which Xilinx DLL I have to deal with? :-)

thomas


Reply With Quote
  #4 (permalink)  
Old 09-26-2003, 06:21 AM
Antti Lukats
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

"T. Irmen" <[email protected]> wrote in message news:<[email protected]>...
> Hi Antti,
>
> > 5 intercept dll, it exposes xilinx DLL entry points and call xilinx
> > dll
> > (that you have renamed) part of the calls are re routed to your dll
> > that then talks to your hardware

>
> that sounds good to me.
>
> I never thought of that way. Isnīt it possible to stack a filter onto xilinx
> kernel driver?


stupid, me, yes it would. its just that I havent written such drivers

> Do you know which Xilinx DLL I have to deal with? :-)


not hard to find, check out whitch one talks the xpc4drvr.sys

antti
Reply With Quote
  #5 (permalink)  
Old 10-27-2003, 10:04 PM
T. Irmen
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

Hi to all interested in,

Xilinx support respondet, that in the future it will be possible to redirect
the jtag signals to
custom registers. The developer agreed that it is a very useful feature. Not
only for us...

today, there is no way to make reuse of the parallel III / IV driver ...

thomas

"Antti Lukats" <[email protected]> schrieb im Newsbeitrag
news:[email protected] om...
> "T. Irmen" <[email protected]> wrote in message

news:<[email protected]>...
> > Hi Antti,
> >
> > > 5 intercept dll, it exposes xilinx DLL entry points and call xilinx
> > > dll
> > > (that you have renamed) part of the calls are re routed to your dll
> > > that then talks to your hardware

> >
> > that sounds good to me.
> >
> > I never thought of that way. Isnīt it possible to stack a filter onto

xilinx
> > kernel driver?

>
> stupid, me, yes it would. its just that I havent written such drivers
>
> > Do you know which Xilinx DLL I have to deal with? :-)

>
> not hard to find, check out whitch one talks the xpc4drvr.sys
>
> antti



Reply With Quote
  #6 (permalink)  
Old 10-28-2003, 05:37 AM
Antti Lukats
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

"T. Irmen" <[email protected]> wrote in message news:<[email protected]>...
> Hi to all interested in,
>
> Xilinx support respondet, that in the future it will be possible to redirect
> the jtag signals to
> custom registers. The developer agreed that it is a very useful feature. Not
> only for us...


well the jtag signals can be used with custom registers today, no problems
with that!!

> today, there is no way to make reuse of the parallel III / IV driver ...


you can reuse Cable III, no problems with that, just write your own
logic analyzer core, write the custom registers, connect them to
BSCAN primitive, and then use JAM player to talk to your custome
logic analyzer and custom registers.

this cant be used with Cable IV, because the API and documentation
about Cable IV are kept as secret.

antti
Reply With Quote
  #7 (permalink)  
Old 10-28-2003, 01:07 PM
Henk van Kampen
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

> this cant be used with Cable IV, because the API and documentation
> about Cable IV are kept as secret.


I have successfully used a Cable IV assuming it is a Cable III. The
only problem is that iMPACT leaves the cable and your port in an
undefined state, so you have to reset the ECP mode and reset the cable
(reset printer). Of course you will not benefit from the ECP speed
possible with the Cable IV.

Henk van Kampen
www.mediatronix.com
Reply With Quote
  #8 (permalink)  
Old 10-31-2003, 01:26 PM
Antti Lukats
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

[email protected] (Henk van Kampen) wrote in message news:<[email protected] om>...
> > this cant be used with Cable IV, because the API and documentation
> > about Cable IV are kept as secret.

>
> I have successfully used a Cable IV assuming it is a Cable III. The
> only problem is that iMPACT leaves the cable and your port in an
> undefined state, so you have to reset the ECP mode and reset the cable
> (reset printer). Of course you will not benefit from the ECP speed
> possible with the Cable IV.
>
> Henk van Kampen
> www.mediatronix.com


do you want to say that Cable IV is Cable III backward compatible in
non-ECP mode?

if it so then it very good information
antti
Reply With Quote
  #9 (permalink)  
Old 11-02-2003, 02:44 PM
Henk van Kampen
Guest
 
Posts: n/a
Default Re: chipscope pro and jtag

>
> do you want to say that Cable IV is Cable III backward compatible in
> non-ECP mode?
>
> if it so then it very good information
> antti


Yes, see also the datasheet of the IV cable. It says that the cable
will go to 'compatability' mode if the ECP mode of your parallel port
is not enabled. This compatability mode appears to be cable III
functionality.

Henk van Kampen
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 04:11 AM.


Powered by vBulletin® Version 3.8.0
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Copyright 2008 @ FPGA Central. All rights reserved