[hpsdr] FW: Cypress USB Problem

[Christopher T. Day]

Sorry, this was meant to go to the mailing list directly.


	Chris - AE6VK


-----Original Message-----
From: Christopher T. Day 
Sent: Tuesday, July 04, 2006 3:58 PM
To: 'Lyle Johnson'
Subject: RE: [hpsdr] Cypress USB Problem

Lyle,

What's telling you that the Cypress is enumerating as PID 0000 and VID
0000? Presumably, when the FX2 powers up, it first looks for a working
I2C EEPROM, which I presume it finds. It then checks if the first byte
in the EEPROM is 'C0'; if so, it reads the next four bytes as the PID
and VID. If the first byte is 'C2', it attempts to load a program from
the EEPROM. Assuming there is nothing in the EEPROM, the FX2 presumably
gets back 'FF' and then enumerates with the built-in, Cypress-exclusive
PID='0x04B4' => Cypress and VID='0x8613' => EZUSB. Windows then takes
these values and searches among its INF files for a match to decide what
driver to load. If there is no match, the device installation will fail.

According to the Cypress documentation, _no_one_ who distributes a
product should let the FX2 enumerate with the default Cypress-exclusive
values; they are for development and debugging purposes only. The
Flex-Radio USB-to-Parallel Port Adapter has followed this rule and has
its own values. Unfortunately, the Xylo has _not_ followed this rule. It
you have the Xylo software installed, there may be a corresponding INF
file that is confusing things and trying to turn Ozy into a Xylo with
unpredictable results.

Meanwhile, you might look at 
<
http://www.cypress.com/portal/server.pt?space=CommunityPage&control=SetC
ommunity&CommunityID=285&PageID=552&shortlink=DA_293822 >

for Cypress' own development tools. It has a USB Console that might be
helpful.

I wish I could be more helpful, or even more certain that I'm not
spouting nonsense, but if we keep going on this thread, we ought to be
able to coax a real Windows USB expert out of the woodwork.


	Chris - AE6VK


-----Original Message-----
From: Lyle Johnson [mailto:kk7p at wavecable.com] 
Sent: Tuesday, July 04, 2006 1:37 PM
To: hpsdr at hpsdr.org
Subject: [hpsdr] Cypress USB Problem

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

Thought I'd start a new thread...

Background: PC running Windows XP Pro SP2 doesn't recognize the Cypress 
USB chip.  It enumerates as PID 0000 and VID 0000.  Windows insists any 
driver I try to install doesn't match the hardware and refuses to load
it.

Verified part is installed, oscillator is running, etc.  Part is 
CY7C68013A in 128-pin package.  Application is Ozy alpha board.

Same symptom on three different computers.  Unknown device, and can;t 
load a driver for it.

1) Plugged in Flex USB adapter.  Not recognized.  Went to Cypress 
website and discovered... not much.  One technical reply said to put the

right drivers in the right directories!  Yes, didn't state what the 
drivers were, where to get them, or suggest what the right directories 
might be !!!

2) Rooted around the web some more (TAPR VNA site, and USB adapter for 
N2PK VNA) and found I needed EZUSB stuff installed on the computer.

Found and loaded ezusbw2k.inf in windows\inf directory.  This is generic

cypress USB stuff, dated 4/9/2006.  From the N2PK VNA USB widget files.

Found and loaded cyusb.inf in windows\inf directory.  This is from the 
Cypress download page associated with the development kit for the chip 
in use.  Note that the file in the zip from cypress had this as 
cyusb.inf.bak. I had to manually rename it.

Put ezusb.sys in windows\system32\drivers directory. This is generic 
cypress USB stuff, dated 9/16/2002.

Put cyusb.sys in windows\system32\drivers directory. This is from the 
Cypress download page associated with the development kit for the chip 
in use.

3) Now the Flex USB adapter is recognized.

4) Ozy's Cypress USB chip is still an "unknown device" and Windows still

refuses to allow me to associate any *.inf I can find with it.

***

I have new parts on order, but I seriously doubt I have a parts problem.

I strongly suspect it is a driver or setup problem of some sort.

If anyone here is familiar with this chip and how to install the drivers

for it, please let me know.  I suspect it will help anyone dealing with 
Ozy in the future...

73,

Lyle KK7P

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