<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6001.18203" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><FONT size=3></FONT></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Hi All,</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Tnx for all the replies.</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Iam willing to program mercury via JTAG using
J7.</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Based on the code from Kirk iam able to load
very fast the new compiled code and use the internal logic analyser from altera
called signal tab; i like to use the debug option. </FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">To load it in prom i can use the blaster
(this works for my blaster with the wrong 220E resistor) by using J4; or using
OZY.</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS" size=4>The resistor R10 is only restricting the
programming via J4 of the PROM and does not interfer with the JTAG J7
connection.</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">I placed only the mercury board; now the
programming via JTAG was succesfull (only after hittng multiple times the start
button; several times iam getting the error CONF_DONE pin failed to go high in
device 1)</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">It seems that ozy does interfer with the mercury
board. Iam also using the ozy_janus.rbf of the project of Kirk. </FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Kirk is there a conflict with ozy (as described
by Phil)?</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">Hope i made the situation clear.</FONT></DIV>
<DIV><FONT face="Comic Sans MS"></FONT> </DIV>
<DIV><FONT face="Comic Sans MS">73 Johan PA3GSB</FONT></DIV>
<DIV><FONT face=Arial size=2><FONT size=3></FONT></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT size=3></FONT></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT size=3>Just to confirm Graham's
notes.<BR><BR>One other item to be aware of. The Ozy board is connected to
the JTAG <BR>chain on the Atlas bus so we can use it as a pseudo USBBlaster to
<BR>program other devices on the bus.<BR><BR>Hence, if you connect a JTAG
programmer to the JTAG header on a Penny <BR>or Mercury board it will be in
parallel with the one inside Ozy - and <BR>not work!<BR><BR>By adding the
facility to program devices over the Atlas bus using Ozy <BR>we remove the need
to purchase a JTAG programmer.<BR><BR>If you really have to program a board
using a JTAG programmer rather <BR>than Ozy let me know and I'll make you a
special version of <BR>Ozy_Janus.rbf that does not drive the JTAG
chain.<BR><BR>73's Phil...VK6APH<BR><BR><BR><BR>Quoting Graham / KE9H
<</FONT><A href="http://lists.hpsdr.org/listinfo.cgi/hpsdr-hpsdr.org"><FONT
size=3>KE9H at austin.rr.com</FONT></A><FONT
size=3>>:<BR><BR>></FONT><FONT size=3><I> ***** High Performance Software
Defined Radio Discussion List *****<BR></I>></FONT><I><BR></I><FONT
size=3>></FONT><FONT size=3><I> Several
Comments:<BR></I>></FONT><I><BR></I><FONT size=3>></FONT><FONT size=3><I>
If you are programming Mercury directly with a Byte Blaster, or
clone,<BR></I>></FONT><FONT size=3><I> you should jumper out R10, or replace
it with a 22 Ohm resistor <BR></I>></FONT><FONT size=3><I> (marked 220). It
shipped from the factory with a 220 Ohm resistor <BR></I>></FONT><FONT
size=3><I> (marked 221).<BR></I>></FONT><FONT size=3><I> Some will work, some
will not work with the 220 Ohm resistor in
place.<BR></I>></FONT><I><BR></I><FONT size=3>></FONT><FONT size=3><I> If
you are programming Mercury directly with a Byte Blaster, or clone, you
go<BR></I>></FONT><FONT size=3><I> in on the "PROM CONFIG" connector, J4,
because you are actually programming<BR></I>></FONT><FONT size=3><I> the
serial PROM. The FPGA will get the program from there at power
up.<BR></I>></FONT><I><BR></I><FONT size=3>></FONT><FONT size=3><I> If you
are programming Mercury directly with a Byte Blaster, or
clone,<BR></I>></FONT><FONT size=3><I> you should use the ".pof" file, and
set the "Mode" to "Active Serial <BR></I>></FONT><FONT size=3><I>
Programming,"<BR></I>></FONT><FONT size=3><I> NOT JTAG, because you are
actually programming an external serial PROM.<BR></I>></FONT><I><BR></I><FONT
size=3>></FONT><FONT size=3><I> The Files that reference a JTAG chain are for
programming the Serial PROM<BR></I>></FONT><FONT size=3><I> via the JTAG
chain using the FPGA and OZY configured as a Byte
Blaster,<BR></I>></FONT><FONT size=3><I> which is an entirely different
process, in which case you use the <BR></I>></FONT><FONT size=3><I> ".jic"
files.<BR></I>></FONT><I><BR></I><FONT size=3>></FONT><FONT size=3><I> It
is also possible to program the FPGA directly, but if you do that,
<BR></I>></FONT><FONT size=3><I> you will<BR></I>></FONT><FONT size=3><I>
loose the program every time that power is turned off, because it will not
be<BR></I>></FONT><FONT size=3><I> stored anywhere on the Mercury
card.<BR></I>></FONT><I><BR></I><FONT size=3>></FONT><I><FONT size=3> ---
Graham<BR></FONT></I></FONT></DIV>
<DIV><FONT face=Arial size=2><FONT size=3><FONT
size=2></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT size=3><FONT size=2> </FONT>
<DIV> </DIV>
<DIV>73 Johan PA3GSB</DIV></DIV></FONT></FONT></BODY></HTML>