[hpsdr] Metis, Mercury, Penelope Programming issues

Mon Oct 28 18:08:09 PDT 2013

Walter, 

Ozy v2.5 expects that the new protocol for the I2C bus will be used by all the boards.  If you are NOT using the latest firmware in the Penelope board and Mercury board then you should edit your initozy11.bat file in the PowerSDR folder to point to an earlier version of Ozy_Janus.rbf than v2.5.  You cannot mix and match firmware versions at will using old and new firmware interchangeably in the boards simultaneously; that’s why the latest firmware versions for Ozy, Metis, Penelope, and Mercury were released as a complete set, and specified as such.  Old firmware will not run properly with new firmware due to the major changes that have been made in the new I2C bus activity; as was explained in the release notification when the new firmware set was released.  

73,  Joe K5SO

On Oct 28, 2013, at 5:38 PM, Walter Holmes wrote:

> ***** High Performance Software Defined Radio Discussion List *****
> 
> Any clues as to why the Penelope board will complete the USB-blaster flash
> using the Ozy board, but still shows up as version 0.0 when starting
> PowerSDR ?
> 
> Since I can't seem to flash up to the later versions for Mercury and
> Penelope, I was hoping to at least go back to where I was to have a usable
> system again.
> 
> Thanks,
> 
> Walter/K5WH
> 
> -----Original Message-----
> From: Walter Holmes [mailto:Walterh at k5wh.net] 
> Sent: Sunday, October 27, 2013 12:43 PM
> To: 'hpsdr at lists.openhpsdr.org'
> Subject: RE: [hpsdr] Metis, Mercury, Penelope Programming issues
> 
> 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/

 1383008889.0