[hpsdr] Metis, Mercury, Penelope Programming issues

Sun Oct 27 19:08:16 PDT 2013

Many thanks Dave..

F4 was the only one not already shorted out from years ago.

I'll give that one a try..

Thanks,

Walter/K5WH

-----Original Message-----
From: hpsdr-bounces at lists.openhpsdr.org
[mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of David McQuate
Sent: Sunday, October 27, 2013 8:40 PM
To: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Metis, Mercury, Penelope Programming issues

***** High Performance Software Defined Radio Discussion List *****

I suspect that LPU is not able to supply enough current.
First step is to short out the resettable fuses, because their current
rating is too low-- their resistance goes up when they get hot, reducing the
current available to Metis, Ozy, etc.
It may be that LPU simply cannot supply enough current, even with the
resettable fuses shorted out.
You'll need a power supply with higher current capability.
73,
Dave
WA8YWQ

On 10/27/2013 10:42 AM, Walter Holmes wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
> More on this issue, that may be related..
>
> It seems that there is some type of oscillation taking place, when I 
> attempt to start PowerSDR..(of course I have to select the  bypass 
> firmware check to get this far)
>
> Whether I use the 2.6 Metis, or the Ozy board at 2.5, there is a 
> squealing sound being resonated from what sounds like the LPU area.
>
> If I unplug the Ethernet cable from Metis, it stops. Back in, and it 
> restarts. Oddly, it does this when Ozy is used as well.
>
> At least with Ozy, it shows the firmware for Mercury to be at 3.3 now. 
> But Penelope still at 0.0.
>
>   
>
> Walter/K5WH
>
> -----Original Message-----
> From: hpsdr-bounces at lists.openhpsdr.org 
> [mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of Walter Holmes
> Sent: Saturday, October 26, 2013 6:00 PM
> To: 'Phil Harman'; hpsdr at lists.openhpsdr.org
> Subject: [hpsdr] Metis, Mercury, Penelope Programming issues
>
> ***** High Performance Software Defined Radio Discussion List *****
>
> I am not sure if I am experiencing the same thing here myself, but 
> here's something strange I am seeing.
>
> After not being able to update my existing Metis board for months, I 
> decided to buy a NEW one. (have not tried the JTAG cable yet)
>
> It's currently on version 2.6 from TAPR.
>
> The Metis bootloader seems to go through the motion to program it to 
> 2.6, completes the programming successfully.
> But yet it never seems to change the version. It's still on 2.6
>
> So I decided to update the Mercury and Penelope boards using the
Bootloader.
> It completed all the programming just fine, and shows on the screen 
> that it completed.
>
> But if I check them with the Interrogate function, the Hex code is 
> still the same, so not sure if it really changed the firmware version
after all.
>
> Since I wasn't completely sure, I installed my Ozy board, and used the 
> USB-Blaster, and flashed both Mercury and Penelope just fine. Again, 
> no errors, completed successfully.
>
> However, here's where it seems VERY strange.
>
> If I load PowerSDR 3.1.5,with Metis, it shows the Metis as v2.6,  but 
> Mercury and Penelope as 0.0, and of course it doesn't start PowerSDR.
>
> If I use Ozy instead of Metis, I get the same message about Mercury 
> and Penelope as being 0.0.
>
> Any ideas on what may not be correct ?
>
> I removed the 2 jumpers for I2C and Bypass on Penelope, but could not 
> find them on Mercury, in case this was related the message attached 
> here.. But no difference.
>
> Many thanks for any insight..
> Walter/K5WH
>
> -----Original Message-----
> From: hpsdr-bounces at lists.openhpsdr.org 
> [mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of Phil Harman
> Sent: Wednesday, October 23, 2013 6:45 AM
> To: hpsdr at lists.openhpsdr.org; Kjell Karlsen
> Subject: Re: [hpsdr] Problems programming Mercury and Penny with new 
> firmware.
>
> ***** High Performance Software Defined Radio Discussion List *****
>
> Hi Kjell,
>
> Apologies, this should have been included in the user guide and 
> release notes.
>
> The latest versions of Mercury, Penny and Metis FPGA code no longer 
> use the Atlas bus to transfer some low speed, or one time only, data.
>
> We did this in order to free up some Atlas bus lines so we could 
> increase the Mercury sampling rate to 384ksps.
>
> In which case the FPGA code versions in Mercury and Penny(lane) are 
> transferred  to Metis via the I2C bus.
>
> This means that the I2C bypass jumpers on Mercury and Penny(lane) need 
> to be removed.
>
> I'll update the relevant user guides shortly.
>
> 73 Phil...VK6PH
>
>
>
> -----Original Message-----
> From: Kjell Karlsen
> Sent: Tuesday, October 22, 2013 6:54 PM
> To: hpsdr at lists.openhpsdr.org
> Subject: [hpsdr] Problems programming Mercury and Penny with new firmware.
>
> ***** High Performance Software Defined Radio Discussion List *****
>
> Hi All.
>
> At last I found what the problems installing new firmware in Mercury 
> and specially in  Penny was. Programming Mercury went through after 
> using the USB-Blaster but doing the same with Penelope did not work. 
> It seemed as Penny blocked the communication over the Atlas Bus. Phil, 
> VK6AP suggested that I should check the I2C jumpers on the Penny card. 
> They were both installed and when removed, everything worked OK. On 
> Mercury, the two jumpers were not installed.
>
> I did not know that some of the communication between Metis and 
> Mercury/Penny over the Atlas Bus was modified. In the description of 
> the Penelope card, the two jumpers should be installed. I can not 
> remember anything mentioned on the reflector about this?
>
> I still have problems when trying to use HPSDRBootloader to program 
> Mercury and Penelope. After loading *_JTAG.rbf, the Erasing Flash 
> reports timeout, try again? But trying once more does not help.
>
> 73, Kjell
>
> --
> Sendt med Operas e-postklient: http://www.opera.com/mail/ 
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: 
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
>

_______________________________________________
HPSDR Discussion List
To post msg: hpsdr at openhpsdr.org
Subscription help:
http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
HPSDR web page: http://openhpsdr.org
Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/

 1382926096.0