[hpsdr] Cypress USB Problem

[Lyle Johnson]

Hello Chris!

> What's telling you that the Cypress is enumerating as PID 0000 and VID
> 0000?

When Windows complains about the fact that the USB device is not working 
properly, I go to device manager, click on the "unknown device" and 
bring up properties, then details, and Windows then tells me these IDs 
are 0000 and 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.

And fail it does.

So, either I have a bad FX2 chip, or ???

I have verified all pins for shorts and opens, traced the USB and EEPROM 
wiring, verified the pull-ups are pulling up on the I2C bus, verified no 
shorts to adjacent pins, verified power supply, verified the reset 
circuit is not stuck and that it goes to the right pin on the FX2...

> 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.

I have no Xylo board or anything related to it.

I also removed the EEPROM so it is just the Cypress chip, and Windoze 
reports the same IDs of all 0s.

> 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 tried this, get the same error message:

"The specified location does not contain information about your hardware."

For both with and without the EEPROM attached.  And on two different 
computers.

> 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.

Hope so.  Or just someone who knows how to fire up a Cypress CY7C68013A 
device on a Windoze computer.  Or how to tell conclusively if the chip 
is bad before all 128 pins get unsoldered...

Now you know why I like embedded DSP, not things attached to desktop and 
laptop computers :-)

73,

Lyle KK7P


 1152057091.0