<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2900.2180" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial" bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document face=Arial color=#000000 size=2>
<DIV> </DIV>
<DIV>My Metis failed with the same symptoms as K5SO had. End result was</DIV>
<DIV>only the 4 power LEDs lit and no other activity and of course, I could
not</DIV>
<DIV>recover. Boot loader did not work.</DIV>
<DIV> </DIV>
<DIV>Previous to this failure, I was able to use HPSDRProgrammer to update</DIV>
<DIV>Metis code on XP 32 bit machine. It never worked on WIN 7-64 bit PC.</DIV>
<DIV> </DIV>
<DIV>At the time of failure, I was NOT updating Metis code, but attempting
to</DIV>
<DIV>load latest FPGA code in a spare Penelope board. I used the procedure</DIV>
<DIV>in the "How it is done" document "JTAG Programmer. I followed the 5</DIV>
<DIV>step process, which as I recall was missing reference to JP1, but
this</DIV>
<DIV>was displayed in the Programmer process. All went well and the
process</DIV>
<DIV>reported no errors and programing complete. Cycled power, and Metis </DIV>
<DIV>went dormant, nothing referenced in any of the documents would allow</DIV>
<DIV>recovery. No boot loader, no other activity. </DIV>
<DIV> </DIV>
<DIV>I am certain this was self inflicted, but I cannot see anywhere along the
</DIV>
<DIV>process that an error was either encountered or displayed. I believe
it</DIV>
<DIV>is related to JP1 function and/or sequence of when to use it! </DIV>
<DIV> </DIV>
<DIV>The only difference that I can tell you is that I was using a 3 slot
EU</DIV>
<DIV>Atlas board vs the 6 slot US board. I always keep this connected to</DIV>
<DIV>my XP PC for testing and FPGA upgrades, and keep the 6 slot Atlas</DIV>
<DIV>on the WIN 7-64 PC for on air operation.</DIV>
<DIV> </DIV>
<DIV>I am currently running Diversity 18 (K5SO) code with fantastic
results.</DIV>
<DIV>I have developed some hardware interface systems to integrate 3 RF</DIV>
<DIV>probe antennas (plus 2 horizontal antennas) with 2 Mercury boards,</DIV>
<DIV>and have phenomenal performance, especially at LF and VLF
frequencies.</DIV>
<DIV> </DIV>
<DIV>I am in the process of documenting the hardware that I have
incorporated</DIV>
<DIV>including software control of the antennas via the I2C buss from
Mercury</DIV>
<DIV>to the HiZ amplifiers at the RF probes. </DIV>
<DIV> </DIV>
<DIV>I have also encountered some issues with the transmit audio chain in
the</DIV>
<DIV>latest W5WC software, but not quite sure how to explain it, until
further</DIV>
<DIV>use. </DIV>
<DIV> </DIV>
<DIV>Thanks to ALL of you that have developed this great HPSDR project and</DIV>
<DIV>all the ongoing improvements, etc.</DIV>
<DIV> </DIV>
<DIV>73 de Joe</DIV>
<DIV>K1RQG</DIV>
<DIV> </DIV>
<DIV>
<DIV>In a message dated 2/22/2011 12:03:30 A.M. Eastern Standard Time,
scotty@tonks.com writes:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 10px; MARGIN-LEFT: 10px"><FONT style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>*****
High Performance Software Defined Radio Discussion List *****<BR><BR>Hi
Joe,<BR><BR>The reason that you could not recover from your "fault" is that
the <BR>bootloader code also resides in the PROM alongside the operating
<BR>code. If the PROM contents get scrambled (which they apparently
<BR>did), the FPGA does not load either of the two images from the PROM
<BR>and nothing works, not even the bootloader.<BR><BR>It is hard to imagine
what could have messed up the image in the <BR>PROM, but we'll all be looking
to see if this happens again or to anyone else.<BR><BR>Dan and I powered up
and down literally hundreds of Metis boards and <BR>never saw that
failure.<BR><BR>73,<BR>Scotty
WA2DFI<BR><BR></FONT></BLOCKQUOTE></DIV></FONT></BODY></HTML>