[hpsdr] Magister USB driver for Windows 7 x64

Sun Aug 1 09:43:33 PDT 2010

Isaac,
Now you are beyond my skills (libusb0, winusb, KISS, C#), and into an area
where Bill is infinitely better than I am!

Maybe posting your current situation (if Bill doesn't respond) to the list
will help, as there are likely others out there who can help.  It may be
that you need a newer version of firmware on the Mercury or such before it
will work...  The 'byteblaster' code in Bill's USBBlaster-Binaries directory
on the SVN server would be required.  You should probably delete the
libusb0.dll from there and let Windows provide the proper one that it
installed.  You'll also need some Quartus software installed as well, I
think, to make the USBBlaster-Binaries work.

Vy 73,
George K9TRV 

-----Original Message-----
From: Isaac Weksler [mailto:iweksler at bezeqint.net] 
Sent: Saturday, July 31, 2010 12:57 PM
To: 'george byrkit'; 'Bill Tracey'
Subject: RE: [hpsdr] Magister USB driver for Windows 7 x64

Hi, guys.

Thank you, George, for replying so promptly.

At the moment I have Magister in slot J2 and Mercury in slot J5. I have a
Penelope board, but I thought that I first have the receiver working and
then integrate the Penelope and the Hercules which I still have to complete
assembling.

I am not sure about the JTAG jumpers since I am not familiar with the
boards. As far as I can see, the "Last JTAG" (JP7) in Mercury is not set. In
Magister I can see 2 jumpers that may be related to the JTAG sequence: JP6 -
set on the lower 2 pins (probably 2-3 (PS=0-FAS=1)) and JP7 - set on the
upper 2 pins (probably 1-2 (AS=0-PS=1)). I am looking at the board with the
Atlas connector down. Is this OK? I haven't found any instruction manual for
the Magister. What about other jumpers? In Ozy manual it says 3 jumpers have
to be set.

I just noticed that on the Mercury board the revision is not indicated, it
just says: Mercury DDC RX Rev A. And there is no S/N. Is this normal?

Vy 73

Isaac 4Z1AO

From: george byrkit [mailto:ghbyrkit at chartermi.net] 
Sent: Saturday, July 31, 2010 4:39 PM
To: 'Isaac Weksler'; 'Bill Tracey'
Subject: RE: [hpsdr] Magister USB driver for Windows 7 x64

Isaac,

It looks to me like both sets of WriteI2C calls are for the Penelope.  The
calls are duplicated, I think, from my examination.  Do you have a Penelope
board?  If not, those WriteI2C calls can and will fail, and I don't think
that's the problem.

It seems like the Ozy/Magister board is being found, as there are no
complaints from LoadFPGA and LoadFW.  It may be that the firmware in some of
the boards needs to be updated outside of PowerSDR.

What is the list of boards that you have, and which Atlas slots are they in?
Which board has the 'Last JTAG' jumper on it?

Bill, can you comment on what I've said, and maybe contribute the solution?
It's not obvious to me, and you have a lot more experience in this area.

Vy 73,

George K9TRV

________________________________

From: Isaac Weksler [mailto:iweksler at bezeqint.net] 
Sent: Saturday, July 31, 2010 3:01 AM
To: 'george byrkit'; 'Bill Tracey'
Subject: RE: [hpsdr] Magister USB driver for Windows 7 x64

Dear George and Bill,

As you suggested I deleted all the libusb0 stuff from PowerSDR directory,
leaving there only the files from Bill's bin\Release SVN directory. This
didn't help.

I looked at the bat files included in PowerSDR and as far as I understood,
it is the initozy11.bat that is executed when the start button is pressed.
So I restored the pause command at the end and thus succeeded in capturing
the messages from its run. Attached is the file. Looks like WriteI2C fails
to write the loaded firmware.

What could be the problem? Please advise.

Vy 73

Isaac 4Z1AO

P.S. As always I forgot to attach the file. Sorry. Here it is. Isaac

From: george byrkit [mailto:ghbyrkit at chartermi.net] 
Sent: Friday, July 30, 2010 8:36 PM
To: 'Isaac Weksler'
Cc: 'Bill Tracey'
Subject: RE: [hpsdr] Magister USB driver for Windows 7 x64

Dear Isaac,

The 'libusb0' stuff does NOT go in the PowerSDR directory.  The installation
of the driver puts the driver in the proper directory, and puts the proper
libusb0 dlls into the proper directories (under the Windows directory, most
likely C:\Windows, in various directories).  By placing the libusb0 stuff in
the PowerSDR directory, you have bypassed the Windows 7 64 bit mechanism for
loading the proper DLLs and such.

So remove all that libusb stuff from the PowerSDR directory and see if that
makes a difference.  And make sure that you have the latest version of
PowerSDR, please.

When you pressed 'start' on powersdr, did it open a DOS window?  If it did,
then it becomes important to try to watch what is happening in that window
to see if the firmware is getting loaded.  If it isn't then that explains
what's happening.  If you have all of Bill's stuff, the PennyMerge stuff
with the WriteI2C.exe and such, then the batch file would normally work.  If
you don't have it, then you don't have all the tools that are needed for the
batch file to run and work, so that would explain the firmware levels.

Once that is done, it either will work, or it's more up Bill Tracey KD5TFD's
alley...  I've included Bill so that he can add to what I've offered.

Vy 73,

George K9TRV

________________________________

From: Isaac Weksler [mailto:iweksler at bezeqint.net] 
Sent: Friday, July 30, 2010 12:46 PM
To: 'george byrkit'
Subject: RE: [hpsdr] Magister USB driver for Windows 7 x64

George,

Thanks very much for the driver - with your libusb0 the driver installed
without a hitch.

However, I do not succeed yet in setting up the radio. Maybe you can help. I
have the Magister and Mercury in the Atlas. I am using Bill's PowerSDR
version. I have put all the stuff from the libusb0 in the PowerSDR
directory. I run the PowerSDR and in the setup define everything as it says
in the Quick Startup Guide in the HPSDR Wiki. However The firmware versions
in HPSDR tab stay all 0 as you see below.

cid:image001.png at 01CB3096.046756A0

When I start the program it gives me the following message

cid:image002.png at 01CB3096.046756A0

Which, as I take it, means that it is unable to load the firmware.

What am I missing?

Thanks in advance.

73

Isaac 4Z1AO

-----Original Message-----
From: hpsdr-bounces at lists.openhpsdr.org
[mailto:hpsdr-bounces at lists.openhpsdr.org] On Behalf Of george byrkit
Sent: Wednesday, July 28, 2010 9:04 PM
To: hpsdr at lists.openhpsdr.org
Subject: Re: [hpsdr] Magister USB driver for Windows 7 x64

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

Dear Isaac,

I have signed libusb0 drivers in my KISS branch on the KISS SVN repository.

This is at:

svn://64.245.179.219/svn/repos_hpsdr_kiss/branches/K9TRV/libusb0-driver-sign

ed

Download and install.  This will work on Win7-64.  You will have to click
and approve in a dialog that says that the 'certificate' is unknown.

There are some other signed libusb drivers at:

http://home.ict.nl/~fredkrom/pe0fko/SR-V9-Si570/index.shtml#install<http://h
<http://home.ict.nl/~fredkrom/pe0fko/SR-V9-Si570/index.shtml#install<http://
h> 

ome.ict.nl/%7Efredkrom/pe0fko/SR-V9-Si570/index.shtml#install, but I don't
know if it's actually libusb0 or libusb1 (an updated version that KISS and
PowerSDR have NOT been tested against).  I do know that the Ozy/Magister VID
and PID are NOT mentioned in the pe0fko.inf file, so I don't think it will
work anyway.

Be aware that on 64 bit windows 7, you WILL (and MUST) be using a 32 bit
build of PowerSDR, as the various C DLLs that PowerSDR uses are only 32 bit
DLLs.  And you are prohibited from mixing bitsize (eg: 32 bit code and 64
bit code) under the same executable.  That's a Microsoft thing...

I think that Bill KD5TFD's latest build of PowerSDR has been marked as 32
bit.  Otherwise you'll get some message about 'cannot find dll' or 'sizes
mismatched' or something similar.

Let us know if you succeed...  Otherwise, let me know what the problem is
(exact error messages) and we'll see what we can do to help!

Vy 73,

George Byrkit, K9TRV

__________ Information from ESET Smart Security, version of virus signature
database 5326 (20100730) __________