<div dir="ltr"><div>I download the docs and utilities from Phil's site --</div>
<div> </div>
<div>Step 1.2.3 instructs me to "load_firmware".</div>
<div> </div>
<div>This command fails -- here is the output from the cmd window: I have confirmed that I have .net 2.0 and 1.0 installed. I<strong> get the same error even w/ Ozy unplugged from the USB connection</strong>. Do I have some version problems? I have previously gone thru several installations and removals of drivers and SDR software packages</div>
<div> </div>
<div>Microsoft Windows XP [Version 5.1.2600]<br>(C) Copyright 1985-2001 Microsoft Corp.</div>
<div>C:\Documents and Settings\Greg>cd desktop</div>
<div>C:\Documents and Settings\Greg\Desktop>cd ozyu</div>
<div>C:\Documents and Settings\Greg\Desktop\ozyu>load_firmware 0x4b4 0x813 OZYV1FW.he<br>x</div>
<div>Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl<br>y 'HPSDR_USB_LIB_V1, Version=<a href="http://1.0.0.0">1.0.0.0</a>, Culture=neutral, PublicKeyToken=null' or o<br>ne of its dependencies. The located assembly's manifest definition does not matc h the assembly reference. (Exception from HRESULT: 0x80131040)<br>
File name: 'HPSDR_USB_LIB_V1, Version=<a href="http://1.0.0.0">1.0.0.0</a>, Culture=neutral, PublicKeyToken=n<br>ull'<br> at load_firmware.Program.Main(String[] args)</div>
<div>WRN: Assembly binding logging is turned OFF.<br>To enable assembly bind failure logging, set the registry value [HKLM\Software\M<br>icrosoft\Fusion!EnableLog] (DWORD) to 1.<br>Note: There is some performance penalty associated with assembly bind failure lo<br>
gging.<br>To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus<br>ion!EnableLog].</div>
<div><br>C:\Documents and Settings\Greg\Desktop\ozyu><br><br></div>
<div class="gmail_quote">On Mon, Aug 11, 2008 at 10:21 PM, Greg Clark <span dir="ltr"><<a href="mailto:greg@bigredbee.com">greg@bigredbee.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Hi Bill,</div>
<div> </div>
<div>thanks for the quick reply -- this is a TAPR built board. </div>
<div> </div>
<div>ID's are: USB\VID_04B4&PID_8613\5&9345ECD&0&2<br> </div>
<div>I'll try what you report below, and follow up. I kinda thought the device ID's were weird.....</div>
<div> </div><font color="#888888">
<div>-- Greg <br><br> </div></font>
<div>
<div></div>
<div class="Wj3C7c">
<div><span class="gmail_quote">On 8/11/08, <b class="gmail_sendername">Bill Tracey</b> <<a href="mailto:bill@ewjt.com" target="_blank">bill@ewjt.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Greg,<br><br>From the attachment it looks like Device Manager is showing Ozy as EEPROM missing -- that leads me to think the EEPROM is not programmed or not working. Is this a TAPR produced board or one you homebrewed? If you look at the Details tab for your device does it show a VID of 0x4b4 and PID of 0x8613 ? Those are the VID and PID for an FX2 w/o an EEPROM specifying a VID/PID.<br>
<br>Regardless it looks like you need to program the EEPROM -- sectino 1.2 of <a href="http://www.philcovington.com/HPSDR/OZY/UTILS/HPSDR%20PROJECT%20LIBUSB.pdf" target="_blank">http://www.philcovington.com/HPSDR/OZY/UTILS/HPSDR%20PROJECT%20LIBUSB.pdf</a> explains how to do that. The tools needed to do it are at: <a href="http://www.philcovington.com/HPSDR/OZY/UTILS/" target="_blank">http://www.philcovington.com/HPSDR/OZY/UTILS/</a> (as well as in SVN)<br>
<br>Regards,<br><br>Bill (kd5tfd)<br><br>At 10:31 AM 8/11/2008, Greg Clark wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">***** High Performance Software Defined Radio Discussion List *****
<div><span><br><br><br>Inspired after upgrading my ticket, I starting working on my Atlas/Ozy/Penelope setup this weekend, but couldn't get past the "initozy" step.<br><br>I installed the USB drivers, and PowerSDR, but can't get the ozy firmware to load -- I think it's something basic, as I get the same failure whether or not I have the USB cable connected.<br>
<br>Here's the error I get<br><br><br>C:\Program Files\FlexRadio Systems\PowerSDR v1.10.4>initozy11<br><br>C:\Program Files\FlexRadio Systems\PowerSDR v1.10.4>load_firmwareV1.1 0xfffe 0x0<br>007 ozyfw-sdr1k.hex<br>
finding busses...<br>finding devices...<br>usb_get_busses...<br>bus location: 0<br>Checking for VID PID...<br><br>Unhandled Exception: System.NullReferenceException: Object reference not set to<br>an instance of an object.<br>
at HPSDR_USB_LIB_V1.USB.FindDevice(usb_bus bus, Int32 VID, Int32 PID)<br> at load_firmware.Program.Main(String[] args)<br><br>C:\Program Files\FlexRadio Systems\PowerSDR v1.10.4>sleep 3000<br>Sleeping: 3000<br>Here's the screen shots of the process showing the device manager, etc.<br>
</span></div><<a href="http://bigredbee.com/tmp/ozyerror.pdf" target="_blank">http://bigredbee.com/tmp/ozyerror.pdf</a>><a href="http://bigredbee.com/tmp/ozyerror.pdf" target="_blank">http://bigredbee.com/tmp/ozyerror.pdf</a><br>
<br>Regards, Greg K7RKT<br></blockquote><br><br></blockquote></div><br></div></div></blockquote></div><br></div>