[hpsdr] Metis quit working

[Mike F]

Hi All

Thanks for the help.

Following Jeremy's input I have got Metis back to fully operational 
status.  However, the next step now has a problem.  In order to upgrade 
Mercury to rev 6.4, HPSDRProgrammer wants two file locations.  One is 
the one I downloaded, Mercury.rbf, from k5so site.  The other is 
Mecury_jtag.rbf.

I can't find this file on the web.

I don't have it on my computer.

It isn't in the HPSDRProgrammer (ver 1.4) directory.

Metis manual ver 1.1 has no additional clue.

Most likely I have overlooked something.  Could someone help.

Thanks.

Mike, K7SR



> [hpsdr] Metis quit working
> Joe Martin K5SO k5so at valornet.com
> Tue Apr 26 05:47:48 PDT 2011
>
>     * Previous message: [hpsdr] Metis quit working
>     * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
> Very good.  Thanks for that detailed explanation, Jeremy!  Hopefully
> that will allow Mike to get up and running again.
>
> However Mike, should Metis/HPSDR Programmer NOT work exactly as
> explained by Jeremy, your system may exhibit some "non_standard"
> behavior  as mine does.  On my particular system (Win XP x64) only
> HPSDR Programmer v1.0 can discover and program a Metis board, none of
> the later versions of HPSDR Programmer will do it on my system.
> However, on my system, only HPSDR Programmer v1.4 can successfully
> interrogate a Mercury/Penelope board and program them using the JTAG
> Bootloader mode (v1.4 will not discover a Metis board in normal Metis
> programming mode on my system).   Thus, it is necessary for me to run
> HPSDR Programmer v1.0 to program a Metis board and v1.4 to program
> Mercury/Penelope.  I mention this in case your system behaves weirdly
> as mine does, not that this situation is something that exists
> generally with everyone's system; clearly it does not.
>
> One other note, Mike.  Check to see which LEDs are lit on your Metis
> board when you power it up.  A detailed explanation of what each LED
> means is given in the documentation.  If NONE of the status LEDs are
> lit (as happened to me and a few others now) then the programming in
> the EPROM has become corrupted or erased and it will be necessary for
> you to re-program the EPROM on Metis with a blaster cable in order to
> recover.
>
> Good luck!   Thanks again Jeremy for straightening me out!
>
> 73,  Joe K5SO
>
>

 1303832711.0