<!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>Phil</DIV>
<DIV> </DIV>
<DIV>I will pay very close attention when I try that again. Did you look at the
</DIV>
<DIV>instructions in "How it is done" compared to the complete user manual.
</DIV>
<DIV>I started reading at the heading "JTAG Programmer" and followed the</DIV>
<DIV>5 step process, but never saw in the written instructions any
reference</DIV>
<DIV>to JP1. Indeed when I tried to interrogate the JTAG, the
HPSDRProgrammer</DIV>
<DIV>said you must have JP1 installed and this is where I think I screwed
up!</DIV>
<DIV> </DIV>
<DIV>I am just not sure, but I will certainly try it again when I am confident I
can </DIV>
<DIV>recover from any disasters!</DIV>
<DIV> </DIV>
<DIV>Thanks for your comments</DIV>
<DIV> </DIV>
<DIV>73 de Joe</DIV>
<DIV> </DIV>
<DIV>
<DIV>In a message dated 2/28/2011 9:44:21 P.M. Eastern Standard Time,
phil@pharman.org writes:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 10px; MARGIN-LEFT: 10px"><FONT style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>Hi
Joe,<BR><BR>Thanks for your feedback regarding using Metis to program other
HPSDR boards.<BR><BR>I've just re-read the instructions in the Metis User
Manual regarding the<BR>procedure to use, in particular to JP1, and it seems
correct to me.<BR><BR>With JP1 installed, and the power cycled, then Metis
will start in<BR>BootLoader mode. This uses a different, fixed, MAC address to
that<BR>normally assigned to the board.<BR><BR>In which case I can't see how
it would be able to erase or corrupt its own<BR>flash memory.<BR><BR>You can
check that the board is in BootLoader mode since the indicator<BR>LEDs have a
different pattern.<BR><BR>Perhaps when you re-program you board you could run
through the steps<BR>again and see if you can reproduce the problem.<BR><BR>73
Phil...VK6APH<BR><BR><BR><BR><BR><BR>> ***** High Performance Software
Defined Radio Discussion List *****<BR>><BR>><BR>> My Metis failed
with the same symptoms as K5SO had. End result was<BR>> only the 4 power
LEDs lit and no other activity and of course, I could<BR>> not<BR>>
recover. Boot loader did not work.<BR>><BR>> Previous to this failure, I
was able to use HPSDRProgrammer to update<BR>> Metis code on XP 32 bit
machine. It never worked on WIN 7-64 bit PC.<BR>><BR>> At the time of
failure, I was NOT updating Metis code, but attempting to<BR>> load
latest FPGA code in a spare Penelope board. I used the procedure<BR>> in
the "How it is done" document "JTAG Programmer. I followed the 5<BR>> step
process, which as I recall was missing reference to JP1, but
this<BR>> was displayed in the Programmer process. All went well and
the process<BR>> reported no errors and programing complete. Cycled
power, and Metis<BR>> went dormant, nothing referenced in any of the
documents would allow<BR>> recovery. No boot loader, no other
activity.<BR>><BR>> I am certain this was self inflicted, but I cannot
see anywhere along the<BR>> process that an error was either encountered or
displayed. I believe it<BR>> is related to JP1 function and/or
sequence of when to use it!<BR>><BR>> The only difference that I can
tell you is that I was using a 3 slot EU<BR>> Atlas board vs the 6
slot US board. I always keep this connected to<BR>> my XP PC for testing
and FPGA upgrades, and keep the 6 slot Atlas<BR>> on the WIN 7-64 PC for on
air operation.<BR>><BR>> I am currently running Diversity 18 (K5SO) code
with fantastic results.<BR>> I have developed some hardware interface
systems to integrate 3 RF<BR>> probe antennas (plus 2 horizontal antennas)
with 2 Mercury boards,<BR>> and have phenomenal performance, especially at
LF and VLF frequencies.<BR>><BR>> I am in the process of
documenting the hardware that I have incorporated<BR>> including
software control of the antennas via the I2C buss from Mercury<BR>>
to the HiZ amplifiers at the RF probes.<BR>><BR>> I have also
encountered some issues with the transmit audio chain in the<BR>>
latest W5WC software, but not quite sure how to explain it, until
further<BR>> use.<BR>><BR>> Thanks to ALL of you that have developed
this great HPSDR project and<BR>> all the ongoing improvements,
etc.<BR>><BR>> 73 de Joe<BR>> K1RQG<BR>><BR>><BR>> In a
message dated 2/22/2011 12:03:30 A.M. Eastern Standard Time,<BR>>
scotty@tonks.com writes:<BR>><BR>> ***** 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<BR>> 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>><BR>>
_______________________________________________<BR>> HPSDR Discussion
List<BR>> To post msg: hpsdr@openhpsdr.org<BR>> Subscription
help:<BR>>
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></FONT></BLOCKQUOTE></DIV></FONT></BODY></HTML>