<div dir="ltr">HPSDR'ers,<div><br></div><div>OK - here's something interesting:</div><div><br></div><div>I was able to put version 2.6a rbf onto Metis - however, when connecting to PowerSDR v3.4.9 - it would disconnect in about 10 seconds. Just about the time I was checking the board revs and then disconnects.</div><div><br></div><div>I put version 2.6b rbf onto Metis - and now it's running OK. I see the board ID's were updated - how they were checked that is - via I2C vs. 1Wire - so, that seems to be working, but I still get the occasional time out when pinging.</div><div>Note JP2 is 'ON' (connected) right now - I'll try it with JP2 off.</div><div><br></div><div>So, this begins to beg the question - my shack computer is a little old - Vista-64 but still runs; has all of the 'protocol-1' HPSDR stuff on it, amongst other things... (Altera vintage tools, etc) - but has the computing requirements of PowerSDR</div><div>gone up; or maybe using some combinations of firmware/PowerSDR is maybe not working so well with my older machine?</div><div><br></div><div>Interesting I see such a difference with Metis version 2.6a and 2.6b.</div><div><br></div><div>If I look at the release notes - they say this (what I found, anyway):</div><div><br></div><div><div>May 3 - changes by Joe K5SO: replaced i2c comm module with new i2c interface and master modules </div><div><span style="white-space:pre"> </span>to pass firmware version numbers, Penny output power, FWD, REV, and ADC overload status </div><div><span style="white-space:pre"> </span>signals via the i2c bus (Atlas A20/A21)instead of via NWire comm lines. Re-configured </div><div><span style="white-space:pre"> </span>Atlas A3, A4, A5, A8, A9, and A10 to receive Rx1 I data on A10, Rx1 Q data on A5, Rx2 I data on A9, </div><div><span style="white-space:pre"> </span>Rx2 Q data on A4, Rx3 I data on A8, and Rx3 Q data on A3, in order to support 384ksps Rx sampling rates</div><div><span style="white-space:pre"> </span>for up to three receivers on a single Mercury or three Mercury boards. </div><div><span style="white-space:pre"> </span>- Changed version number to v2.6.</div><div><br></div><div><span style="white-space:pre"> </span> 27 - Increased wideband FIFO to 16k words, released as V2.6a</div><div><br></div><div><span style="white-space:pre"> </span> Jun 5 - Added mic boost, released as V2.6b.</div></div><div><br></div><div>73's,</div><div>John</div><div>AJ6BC</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 23, 2018 at 4:54 PM, John C. Westmoreland, P.E. <span dir="ltr"><<a href="mailto:john@westmorelandengineering.com" target="_blank">john@westmorelandengineering.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">OK - a few edits:<div><br></div><div>Metis only responds if I use the HPSDR Programmer if version 3.0 rbf is loaded - it won't respond to anything else - no activity lights.</div><div><br></div><div>I made a build - version 1.7 - loaded that with the HPSDR Programmer - and that works - getting activity LEDs no matter what position JP2 is in. </div><div>USB Blaster can't successfully program - and maybe the board really isn't designed to support the USB Blaster - I'm just trying to remember all of this right now.</div><div><br></div><div>If I put version 2.9 back on - which is what was there previously - I get the same result - no LED activity.</div><div><br></div><div>So, any help/clues appreciated.</div><div><br></div><div>I using Protocol-1 on the Atlas backplane.</div><div><br></div><div>73's,</div><div>John</div><div>AJ6BC</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 23, 2018 at 4:38 PM, John C. Westmoreland, P.E. <span dir="ltr"><<a href="mailto:john@westmorelandengineering.com" target="_blank">john@westmorelandengineering.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello HPSDR'ers,<div><br></div><div>I upgraded my Metis board with the version 3.0 rbf that's on the Github site and now it doesn't respond.</div><div><br></div><div>It will only respond when using the HPSDR Programmer with the version 3.0 rbf loaded.</div><div><br></div><div>I have an older version of Quartus v13.x installed on my shack computer, and I put version 1.7 back onto Metis using the USB Blaster and after making that build Metis will work no matter what position I have JP2 in.</div><div><br></div><div>If I try and put v2.9 back on - which is what I had previously, no matter what position I put JP2 on, it won't connect (no ethernet activity - won't respond to ping, etc.) - but of course the power LEDs are fine.</div><div><br></div><div>So, anyone know what's going on?</div><div><br></div><div>Metis is working in this mode OK - it'll connect to v3.4.9 of PowerSDR, but it's just limping along right now.</div><div><br></div><div>Is there a way to program Metis using the USB Blaster connection on the JTAG port?</div><div><br></div><div>Thanks In Advance.</div><div><br></div><div>73's,</div><div>John</div><div>AJ6BC</div><div><br></div><div><br></div><div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>