Thanks for your answer.
The driver is similar to \Cypress\USB\Drivers\ezmon\ezusbsys.c
c0000001 is operation unsuccessful, but this information is still not enough for me to figure out the problem.
ezusb.sys was not tested with Vista/7 and from what I'm aware of it will need modification before you can get it to even load in Win 7..
When device manager says code 10 it means it doesn't have enough information to point the exact reason behind the error http://support.microsoft.com/kb/943104
Migrating to CyUSB.sys would be a good idea. Is it possible to migrate to CyUSB.sys or is the effort of migration significant?
I did some test. My driver is Xvpusb.sys.
If I rename Xvpusb.sys to cyusb.sys and overwrite \system32\drivers\cyusb.sys. It works in Win7. Cypress USB Console can find my device as "Cypress USB Generic Driver (3.4.7.000)".
If I rename cyusb.sys to Xvpusb.sys and overwrite \system32\drivers\Xvpusb.sys. It doesn't work in win7. Even in XP, it occasionally recognizes my device. Most of time shows "This device cannot start. (Code 10) ".
I don't know if you can show me what is the difference between ezusbsys.c and the souce cyusb.sys in those modules:
Ezusb_CallUSBD, Ezusb_ConfigureDevice, Ezusb_SelectInterfaces.
i am using USB3FPGA and successfully installed driver(cypress usb
generic driver 3.4.7000 ). i am using CYSUSB CONTROL CENTER & USB CONSOLE
for my communication with the USB3FPGA board and it works.
After i used
option " program FX2---->small EEPROM " of the USB control center and loaded
an example "cystream.iic " file in it. After loading it , the device is not anymore detected
by the control center.i have also reinstall the driver but then driver installation
wizard shows the error msg now as :
"cypress USB Generic Driver
This device cannot start.(Code 10) "
i have also checked the VID & PID which are correct.
1)Is anything happened to eeprom therefore its contents changed etc?
2) how can i access eeprom ,as device is not detected any more?
3)which file and changes i have to adopt to make the device detectable?solution?
did you find a solution? My device also can not be found after I program it with the example firmware.
Thanks for any reply.
You have mentioned that you have loaded the cystream.iic file into the small EEPROM. The small EEPROM is generally meant to have only 8 bytes of data containing the VID/PID/DID of the device. When the FX2LP comes out of reset and finds a valid EEPROM with the first byte as C0 in the address A2A1A0 - 000, it will copy only the first 8 bytes of data from the small EEPROM into the RAM.
In case you would want the entire firmware to be loaded into the EEPROM, kindly, consider using the large EEPROM (first byte as C2 and address A2A1A0 - 001).
Please let me know if you are using a custom board other than the Cypress CY3684 DVK.
In that case, please refer to the below thread for the solution.
We can face this problem on network adapter which is "this device cannot start. (code 10)". Actually, Code 10 is almost always a driver issue. You are probably using an outdated driver, or an incompatible driver (meant for a different operating system). You can follow the below methods to resolve this error.
Method#1: You can fix this error to update your device with the correct driver. Open PowerShell to write PowerShell on search bar then write Get-WmiObject win32_bios. After it, You will be shown your Serial Number/Service Tag. Then download the driver according to your serial number or service tag.
Method#2: Use Power Cycle your PC. If you'are using PC then remove all the power cables and if you're using the laptop then Off your laptop, remove your battery and after waiting around 10 minutes put it back and check error will be resolved. Hope, these 2 methods will work to fix this error.