[hpsdr] Metis Protocol-1 Question

[John C. Westmoreland, P.E.]

HPSDR'ers,

OK - here's something interesting:

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.

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.
Note JP2 is 'ON' (connected) right now - I'll try it with JP2 off.

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
gone up; or maybe using some combinations of firmware/PowerSDR is maybe not
working so well with my older machine?

Interesting I see such a difference with Metis version 2.6a and 2.6b.

If I look at the release notes - they say this (what I found, anyway):

May 3 - changes by Joe K5SO: replaced i2c comm module with new i2c
interface and master modules
to pass firmware version numbers, Penny output power, FWD, REV, and ADC
overload status
signals via the i2c bus (Atlas A20/A21)instead of via NWire comm lines.
Re-configured
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,
Rx2 Q data on A4, Rx3 I data on A8, and Rx3 Q data on A3, in order to
support 384ksps Rx sampling rates
for up to three receivers on a single Mercury or three Mercury boards.
- Changed version number to v2.6.

     27 - Increased wideband FIFO to 16k words, released as V2.6a

Jun  5 - Added mic boost, released as V2.6b.

73's,
John
AJ6BC


On Mon, Jul 23, 2018 at 4:54 PM, John C. Westmoreland, P.E. <
john at westmorelandengineering.com> wrote:

> OK - a few edits:
>
> 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.
>
> 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.
> 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.
>
> If I put version 2.9 back on - which is what was there previously - I get
> the same result - no LED activity.
>
> So, any help/clues appreciated.
>
> I using Protocol-1 on the Atlas backplane.
>
> 73's,
> John
> AJ6BC
>
>
> On Mon, Jul 23, 2018 at 4:38 PM, John C. Westmoreland, P.E. <
> john at westmorelandengineering.com> wrote:
>
>> Hello HPSDR'ers,
>>
>> I upgraded my Metis board with the version 3.0 rbf that's on the Github
>> site and now it doesn't respond.
>>
>> It will only respond when using the HPSDR Programmer with the version 3.0
>> rbf loaded.
>>
>> 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.
>>
>> 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.
>>
>> So, anyone know what's going on?
>>
>> Metis is working in this mode OK - it'll connect to v3.4.9 of PowerSDR,
>> but it's just limping along right now.
>>
>> Is there a way to program Metis using the USB Blaster connection on the
>> JTAG port?
>>
>> Thanks In Advance.
>>
>> 73's,
>> John
>> AJ6BC
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20180723/bfa420ef/attachment.html>