<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>All:</p>
<p>I have a Metis board and a Mercury board that came with "old"
firmware. (2.9 for Mercury)</p>
<p>I successfully used HPSDRProgrammer V 2.0.4.10 to update Meteis.
Although the title bar says it is a nopcap version, I had
previously installed WinPCAP on my Winders10 64-bit machine.</p>
<p>Although the HPSDR page <i>suggests</i> that HPSDRProgrammer can
be used to update Mercury,</p>
<p><img src="cid:part1.C07AFEB9.7DE21C37@wb4gcs.org" alt=""></p>
<p>I could not get it to recognize the Mercury board.</p>
<p>Following the instructions on pages 19 - 20 of the Metis manual
(V1.4), I used HPSDRBootloader version 2.0.4.4 to update Mercury.
It correctly detected Mercury and informed me that Mercury was at
firmware version 2.9. NOTE: Although the Mercury manual (v 1.0)
says I should see two of the 3 LEDs on the right hand of the
"horizontal" string of LEDs in the "upper-right-hand" quadrant of
the Mercury board (near the input BNC), I saw three, with the two
right-hand LEDs blinking. I could not find in any manual what
this means.</p>
<p>Following the update instructions in the Metis manual, I:</p>
<p>1. Powered off the ATLAS board.</p>
<p>2. Installed JP1 on the Metis board.</p>
<p>3. Installed JP7 (LAST JTAG) on the Mercury board.</p>
<p>4. Powered up the ATLAS board.</p>
<p>5. Ran HPSDRBootloader, which correctly detected the Mercury
board and reported firmware at version 2.9. (Latest is 3.4).
Note that the bootloader says I need Administrator priveleges,
which I have. (Windows10 does not give me a "run as
administrator" option, but I have verified that my account has
administrator priveleges.)<br>
</p>
<p>6. Updated the Mercury board with version 3.4 rbf file, which I
had years ago used to update other Mercury boards. The upgrade
appeared to go successfully, in terms of writing. I did see the
"erasing flash" message per the example on page 19 of the Metis
manual, then another set of "writing" reports, and finally a
message to remove jumper J1 on Metis and then power cycle. At
this point, the second LED from left on Mercury is flashing, the
next two are on solid, and the third from right is on solid.<br>
</p>
<p>7. Per the instructions on page 20 of the Metis manual, I shut
down power and removed JP1 on the Metis board. (Says nothing
about JP7 on Mercury.) I then reapplied power to the Atlas board,
expecting code to be written to the target board. I now see the
far left LED on Mercury on solid, the 2nd and 3rd LEDs from right
flashing at different rates, and the 4th from right on solid.</p>
<p>8. I then powered off the Atlas bus and removed the "last JTAG"
jumper on Mercury. Powering back up, I see the far left LED on
Mercury on solid, the 2nd and 3rd from LEDs from the right
flashing at different rates, and the 4th from the right on solid.
(In prior attempts, I would see ALL LEDs near the BNC connector
dimly lit and HPSDR would refuse to start, stating "bad firmware,
v0.0" for all boards.<br>
</p>
<p>9. This time, HPSDR starts and appears to work (I see noise with
no antenna connected.)</p>
<p>Notes:</p>
<p>1. This is a 2-slot Atlas board intended to be used for updating
other boards. Per instructions, Metis is farthest from the power
connector.</p>
<p>2. The Mercury TCXO is selected by jumper and in HPSDR seytup.
The Mercury 122 MHz clock is selected in HPSDR Setup.</p>
<p>3. I have audio (noise) output on both line and earphone
outputs.</p>
<p>4. I see a small 10MHz spur (-128dbm or so), which I expect
based on notes using the onboard TCXO.</p>
<p>5. A 9.9 MHz -60dbm signal from my HP 8657B sign gen shows up at
9.9 MHz and -54dbm -- probably a close as I can expect, given that
the sign gen is 2 years away from calibration.<br>
</p>
<p>So, questions:</p>
<p>1. Am I doing something wrong? I'm troubled by the LEDs acting
different than on page 4 of the Mercury manual, version 1.0.
(Green LEDs are lit as expected.) Yet, the receiver <i>appears</i>
to be working.<br>
</p>
<p>2. How can I tell what version of firmware I actually have in
Mercury? The HPSDRBootloader doesn't tell me, only that it
detected Mercury. The HPSDRProgrammer does not detect the
Mercury, only Metis. This <i>appears</i> correct, since
somewhere the documentation alludes to the Programmer detecting
"anything with an ethernet port".</p>
<p>3. Is there a way to update Mercury, Penny et al with the
HPSDRProgrammer and not messing with jumpers? The online
documentation <i>suggests</i> this, but does not explicitly so
state or tell me how.</p>
<p>Thanks & 73,</p>
<p>Jim</p>
<p><a class="moz-txt-link-abbreviated" href="mailto:wb4gcs@amsat.org">wb4gcs@amsat.org</a></p>
<p><br>
</p>
<p><br>
</p>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
<td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
</td>
</tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>