<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Hi,<br><br>Since many of us we have Mercury-EU, I guess it would be a great idea if someone from the designers team (Gerd, Phil, etc...) could test any firmware release on both cards, Mercury-TAPR and Mercury-EU.<br><br>What you think?<br><br>Thanks.<br><br>73, Maximo - EA1DDO<br><br><br><br>> From: g.loch@nt-electronics.de<br>> To: hpsdr@lists.openhpsdr.org<br>> Date: Sat, 2 Apr 2011 09:47:28 +0200<br>> Subject: Re: [hpsdr] Flashing Mercury-EU with Metis<br>> <br>> ***** High Performance Software Defined Radio Discussion List *****<br>> <br>> Berndt,<br>> <br>> I did not know that C5 and C6 were going to be used for flashing with Metis.<br>> Did I miss any information about this?<br>> Was there a change in the coding for Mercury for this reason?<br>> Which are the signal names used for this purpose?<br>> <br>> Gerd, DJ8AY<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Sat, 2 Apr 2011 02:21:19 +1030<br>> From: Berndt Josef Wulf <wulf@ping.net.au><br>> To: hpsdr@lists.openhpsdr.org<br>> Subject: Re: [hpsdr] Cannot flash Mercury-EU with Metis and HPSDR<br>> Message-ID: <201104020221.19971.wulf@ping.net.au><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> G'day,<br>> <br>> Many thanks to all of you who responded to my email in support.<br>> <br>> Here an update and the conclusions to the above problem for the benefit of <br>> those who are facing the same dilemma:<br>> <br>> TAPR Mercury vs Mercury-EU FPGA pin assignments<br>> ================================<br>> The design of TAPR Mercury and Mercury-EU differ to the extend that some of <br>> the otherwise unused FPGA pins are assigned to different locations on the <br>> ATLAS bus, including signals C5 and C6 utilized by Metis to communicate with<br>> <br>> the target board. This caused HPSDRProgrammer to fail to flash the<br>> Mercury-EU <br>> card. lt will require a special version of Mercury_JTAG file to work around <br>> this problem. My feeling is that the purpose of unused pins of the FPGA were<br>> <br>> not part of the original design specifications of the Mercury board.<br>> <br>> As Mercury-EU is produced outside of TAPR, the problem remains of finding <br>> someone with the expertise and time to produce a modified version of the <br>> Mercury_JTAG file for Mercury-EU.<br>> <br>> My solution<br>> ========<br>> I rediscovered my old ByteBlaster and used the Altera programming<br>> application <br>> to upgrade the Mercury board to version 6.4. I've ordered a Mini USB<br>> Blaster, <br>> available for under US$13.00 on eBay including shipping, as PCs with<br>> parallel <br>> ports are getting harder to find.<br>> <br>> 73, Berndt<br>> VK5ABN<br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> HPSDR Discussion List<br>> To post msg: hpsdr@openhpsdr.org<br>> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org<br>> HPSDR web page: http://openhpsdr.org<br>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/<br> </body>
</html>