[hpsdr] Problems with PowerSDR software

[Chris Smith]

Hi Bill

Well! Curiouser & curiouser. I ran initozy11.bat with output to an  
error log and it ran to completion!!! (See attachment 1)

Next, I cycled power on the kit to ensure that the firmware had to be  
reloaded and ran PowerSDR. When I ticked the Janus/Ozy Control box in  
Setup/Hardware Config the command window appeared along with the usual  
errors.

I cycled power again and ran initozy11.bat with output to another  
error log and it failed on the next command (upload_fpgaV1.1 etc)  
after a successful firmware load and that is the current situation  
despite several reboots, power cycles etc. (See attachment 2).

I'm not a MS fan (I come from a UNIX background) but I'll try the  
monitor you suggest.

Cheers

Chris G4NUX

-------------- next part --------------
A non-text attachment was scrubbed...
Name: err.log
Type: application/octet-stream
Size: 5221 bytes
Desc: not available
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20081112/824e14f8/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: er2.log
Type: application/octet-stream
Size: 11195 bytes
Desc: not available
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20081112/824e14f8/attachment-0007.obj>
-------------- next part --------------



On 12 Nov 2008, at 06:01, Bill Tracey wrote:

> Well this should work -- I've got an Athlon and WinXP and it works  
> fine for me.
>
> Do you get anything more than "App has generated an exception".  If  
> there's a back trace for the exception that would be useful.   Or  
> can you run
>    initozy11.bat >err.log 2>&1 and
> send me the err.log file
>
> It is somewhat perplexing that if you init the boards from the Intel  
> machine all works well when running on the AMD machine.   It would  
> seem there's some difference between the machines -- wonder if  
> there's an older/different version of libusb running around on the  
> AMD box.  I'd suggest grabbing Process Monitor from SysInternals.com  
> and see if load_firmware11.exe looks to be loading things from  
> unexpected places.
>
> Regards,
>
> Bill  (kd5tfd)
>
>
> At 08:33 AM 11/11/2008, Chris Smith wrote:
>> ***** High Performance Software Defined Radio Discussion List *****
>>
>> Hi
>>
>> My apologies if this has been covered here already but I've searched
>> the archive and haven't found a similar reference.
>>
>> I've installed the PowerSDR software (the kt5tfd PennyMerge branch)
>> using Tortoise SVN plus the libusb driver (from the PowerSDR-163-  
>> OzyJanus-2007May11.zip) on an Intel based system running WinXP Home.
>> This is a test set-up and the load_firmwareV1.1.exe etc runs OK and I
>> can control my Ozy/Janus/Penny kit.
>>
>> The system I want to use in anger is AMD Athlon based running WinXP
>> Pro. I have followed the same installation procedure on this system
>> but the load_firmwareV1.1.exe  always fails with a Common Language
>> Runtime Debugging Services message: "Application has generated an
>> exception that could not be handled." Running the code manually  
>> causes
>> the same problem.
>>
>> If I load the firmware etc using the Intel based system then move the
>> USB cable to the AMD based system then PowerSDR runs OK and I can
>> control the hardware. So it seems that the libusb driver is installed
>> and running OK for this function but not the load function. Odd!
>>
>> Has anyone else found this problem? Before you say "reload the  
>> driver"
>> I have to point out that I've done that ad nauseam without any
>> observable change in the behaviour.
>>
>> I'd like to get this running properly before I take delivery of the
>> Mercury card. :-)
>>
>> Many thanks
>>
>> Chris
>>
>> G4NUX  _______________________________________________
>
>