cancel
Showing results for 
Search instead for 
Did you mean: 

USB Low-Full-High Speed Peripherals

Anonymous
Not applicable

Hi

   

I am trying to use a CYC7C68016A chip with fx2LP no EEPROM and I have problems when I first plug in it with the driver (at least I think)

   

I use Windows XP 32 bits and I have downloaded the CY3684 EZ USB FX2LP development kit.

   

 

   

When I plug in for the first time the FX2LP Windows detect an Unknown device so I try to update the driver with the Cypress->Manage->CyUSB->CYUSB.inf file but I've got the error: “the specified location does not contain information about your hardware”

   

I have, of course, modify the inf file with VID04B4 and PID8613 and even try to change the GUID.

   

Then I noticed that in Computer-> Manage->Unknown device->Detail   the Device Instance ID has a PID/VID of 0000.

   

I have seen it could come from a hardware problem (see Guide to Successful EZ-USB(R) FX2LP(TM) and EZ-USB FX1(TM) Hardware Design and Debug - AN15456 ) but it still does not work.

   

 

   

I really don’t know what to do next……

   

 

   

Here is my inf file :

   

; Installation INF for the Cypress Generic USB Driver for Windows 98ME/2000/XP
;

[Version]
Signature="$CHICAGO$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
provider=%PROVIDER%


[SourceDisksNames]
1=%CYUSB_INSTALL%,,,

[SourceDisksFiles]
CyUsbME.sys = 1
CyUsb.sys = 1
CyUsb.spd = 1

[Manufacturer]
%MFGNAME%=Cypress

[Cypress]
; Cypress FX2LP default ID
%VID_04B4&PID_8613.DeviceDesc%=CyUsb, USB\VID_04B4&PID_8613

; Cypress FX1 default ID
;%VID_04B4&PID_6473.DeviceDesc%=CyUsb, USB\VID_04B4&PID_6473

; Cypress FX2LP Example Device.  DVK firmware examples use this VID/PID
;%VID_04B4&PID_1004.DeviceDesc%=CyUsb, USB\VID_04B4&PID_1004

[DestinationDirs]
CyUsbME.Files.Ext = 10,System32\Drivers
CyUsb.Files.Ext = 10,System32\Drivers

[CyUsb]
CopyFiles=CyUsbME.Files.Ext
AddReg=CyUsbME.AddReg

[CyUsb.HW]
AddReg=CyUsb.AddReg.Guid

[CyUsb.NT]
CopyFiles=CyUsb.Files.Ext
AddReg=CyUsb.AddReg

[CyUsb.NT.HW]
AddReg=CyUsb.AddReg.Guid

[CyUsb.NT.Services]
Addservice = CyUsb, 0x00000002, CyUsb.AddService

[CyUsb.AddService]
DisplayName    = %CyUsb.SvcDesc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 3                  ; SERVICE_DEMAND_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %10%\System32\Drivers\CyUsb.sys
LoadOrderGroup = Base

[CyUsbME.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,CyUsbME.sys

[CyUsb.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,CyUsb.sys

[CyUsbME.Files.Ext]
CyUsbME.sys

[CyUsb.Files.Ext]
CyUsb.sys

[CyUsb.AddReg.Guid]
;HKR,,DriverGUID,,%CyUsb.GUID%

;---------------------------------------------------------------;

[Strings]
PROVIDER="Cypress"
MFGNAME="Cypress"
CYUSB_INSTALL="Cypress Generic USB Driver Installation Disk"
VID_04B4&PID_8613.DeviceDesc="Cypress EZ-USB FX2LP - EEPROM missing"
;VID_04B4&PID_6473.DeviceDesc="Cypress EZ-USB FX1 - EEPROM missing"
;VID_04B4&PID_1004.DeviceDesc="Cypress EZ-USB Example Device"
CyUsb.SvcDesc="Cypress Generic USB Driver"

CyUsb.GUID="{AE18AA60-7F6A-11d4-97DD-00010229B959}"

0 Likes
Reply
11 Replies
Anonymous
Not applicable

Hi lokas,

   

VID/PID coming as 0000 is suggestive of hardware issue. Did you follow the steps in AN15456 to check if the hardware design doesn't have any issues.

   

Regards,

   

Anand

0 Likes
Reply
Anonymous
Not applicable

Yes I followed this process

   

The process required to fix the DVB-T driver issue follows:
1. Disconnect your board from the PC’s USB port.
2. If you are inexperienced with registry editing, back up the registry before this step. Go to the registry (by typing ‘regedit’ in Start…Run) and find the HKEY_LOCAL_MACHINE/SYSTEM/ CurrentControlSet/Enum/USB folder. Locate the key or folder labeled ‘Vid_04b4&Pid_8613’. Right click on this key and set the security permissions to enable full control. Delete the key and any subkeys...

   

But there is no key or folder labeled ‘Vid_04b4&Pid_8613"

0 Likes
Reply
Anonymous
Not applicable

Hi lokas,

   

I'm talking about the process of observing the CLKOUT signal on the oscilloscope to find out if the design is right. Did you follow that.

   

Regards,

   

Anand

0 Likes
Reply
Anonymous
Not applicable

Sorry for the delay

   

 

   

There is no CLKOUT for the CY7C68016A (and neither  IFCLK). Those pins are just present on the 13A and 14A.

   

So I can't follow this process....

0 Likes
Reply
Anonymous
Not applicable

Can you please attach your schematic here? I would like to review it.

   

Regards,

   

Anand

0 Likes
Reply
Anonymous
Not applicable

Hi,

   

I attached my schematic

   

 

   

Regards

0 Likes
Reply
Anonymous
Not applicable

I don't see any issues in your schematic.

   

There are 2 possible reasons

   

1. The clock is not clean enough. Please check if the jitter is not able +/- 100ppm and has proper swing (VIH etc parameters available in datasheet). If possible please scope the signal and send across a screenshot of the waveform.

   

2. The USB line has lot of noise, in this case the layout has to be reviewed. Please look at http://www.cypress.com/?rID=12982 to see if you're meeting our layout guidelines.

   

Regards,

   

Anand

0 Likes
Reply
Anonymous
Not applicable

I don't think the problem come from the clock because I scoped the 24MHz clock that I use (pin 5 XTALIN) and it seem pretty clean.

   

 

   

About the USB line there is no noise and their  levels are 3V (D+) and 1.7V (D-)....

0 Likes
Reply
Anonymous
Not applicable

D- (1.7V)?? There will be a pull-up on D+ to indicate speed so the 3V on D+ is fine but D- should be 0V. Then there should be chirp sequence. Do you have the scoped signal of this 3V and 1.7V scenario.

   

Regards,

   

Anand

0 Likes
Reply
Anonymous
Not applicable

Hi

   

 

   

Indeed you were right I had a problem with the pin D- it should have been at 0V. 

   

My device is finally recognized.

   

 

   

Thank you

0 Likes
Reply
Anonymous
Not applicable

Hi Lokas,

   

What was the issue, how did you resolve it?

   

Regards,

   

Anand

0 Likes
Reply