[hpsdr] Flashing Mercury-EU with Metis

[Maximo EA1DDO_HK1DX]

Hi,

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.

What you think?

Thanks.

73, Maximo - EA1DDO



> From: g.loch at nt-electronics.de
> To: hpsdr at lists.openhpsdr.org
> Date: Sat, 2 Apr 2011 09:47:28 +0200
> Subject: Re: [hpsdr] Flashing Mercury-EU with Metis
> 
> ***** High Performance Software Defined Radio Discussion List *****
> 
> Berndt,
> 
> I did not know that C5 and C6 were going to be used for flashing with Metis.
> Did I miss any information about this?
> Was there a change in the coding for Mercury for this reason?
> Which are the signal names used for this purpose?
> 
> Gerd, DJ8AY
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Sat, 2 Apr 2011 02:21:19 +1030
> From: Berndt Josef Wulf <wulf at ping.net.au>
> To: hpsdr at lists.openhpsdr.org
> Subject: Re: [hpsdr] Cannot flash Mercury-EU with Metis and HPSDR
> Message-ID: <201104020221.19971.wulf at ping.net.au>
> Content-Type: text/plain;  charset="us-ascii"
> 
> G'day,
> 
> Many thanks to all of you who responded to my email in support.
> 
> Here an update and the conclusions to the above problem for the benefit of 
> those who are facing the same dilemma:
> 
> TAPR Mercury vs Mercury-EU FPGA pin assignments
> ================================
> The design of TAPR Mercury and Mercury-EU differ to the extend that some of 
> the otherwise unused FPGA pins are assigned to different locations on the 
> ATLAS bus, including signals C5 and C6 utilized by Metis to communicate with
> 
> the target board. This caused HPSDRProgrammer to fail to flash the
> Mercury-EU 
> card. lt will require a special version of Mercury_JTAG file to work around 
> this problem. My feeling is that the purpose of unused pins of the FPGA were
> 
> not part of the original design specifications of the Mercury board.
> 
> As Mercury-EU is produced outside of TAPR, the problem remains of finding 
> someone with the expertise and time to produce a modified version of the 
> Mercury_JTAG file for Mercury-EU.
> 
> My solution
> ========
> I rediscovered my old ByteBlaster and used the Altera programming
> application 
> to upgrade the Mercury board to version 6.4. I've ordered a Mini USB
> Blaster, 
> available for under US$13.00 on eBay including shipping, as PCs with
> parallel 
> ports are getting harder to find.
> 
> 73, Berndt
> VK5ABN
> 
> 
> 
> 
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20110402/753790b8/attachment-0003.htm>