USB low-full-high speed peripherals Forum Discussions

I followed CyUSB3.pdf to add my own VID/PID pair to CyUSB3.inf file.

I did the following, none of them work.  No changes to CyUSB3.sys and CyUSB3.cat

1. Add my VID/PID to the .inf and change the strings. Remove all build in PID/VID and the strings, Keep the file name as CyUSB3.inf.

    But it never get work. The windows10 (64bits) always shows

2. Only add my VID/PID and strings, without changing any original data in cyusb3.inf. it can install successfully.

note: I have disable my computer Digital Signature.

Can tell me the difference is there?

Thank you.

Hello,

CY7C65211 SPI I/F is corresponding to 24 bits addressing? I'd like to use it to connect a 2Mb FRAM.

Hello,

I'm working with an EZ-USB FX3 development kit, connected to a Windows 7 64-bit machine, running my dll which uses the cyapi.lib library. My question is specifically to a failure with the XferData() method on the bulk-out endpoint.

My dll initializes the board (where the FX3 is connected) and programs both the RAM (.img file via CCyFX3Device.DownloadFw) and the FPGA (.bin file via BuilkOutEndPt.XferData) firmware; those two files are our own code. This board is connected to a windows 7 machine and both receive power to be turned on at the same time. After windows startup, I run my dll and the XferData() fails with error 997 (after checking LastError). This error is also seen even if Reset() and Abort() are issued before using XferData. However, if the board is NOT connected to the computer during startup, and then the board is turn on and plug in after windows is ready, everything works just fine (ie. no errors at all).

This behavior is really, really weird since it seems to be connected somehow to the windows startup sequence. We have also tried using a Windows 10 64-bit machine but with the same results.

If anybody has any ideas why we are seeing this error at startup only, or knows how to fix it, please let us know! We'd really appreciate any help.

Thanks,

-Stalin

I'm trying to use USB2.0 Camera Interface Using FX2LP™ and Lattice CrossLink FPGA - KBA222479 firmware with a Lcsoft CY7C68013A Mini Board connected to my existing FPGA design. I have the firmware uploaded, and the board is recognized as a generic USB video device. I'm specifically only trying to stream data into the FX2LP. I'm trying to figure out:

1. Specifically, what are the minimal set of pins on the CY7C68013A board need to be connected to the FPGA?

2. Which pins are active high/low and how will each pin need to be driven?

FX2LP

PIN       A.K.A.           Description

PA0      INT0#           ??

PA1      INT1#           ??

PA2      SLOE           This is the enable signal for the FIFO's output driver.

PA3      WU2             ??

PA4      FIFOADR0   These signals select the active endpoint.

PA5      FIFOADR1   These signals select the active endpoint.

PA6      PKTEND      ??

CTL0    FLAGA       These flags are used by the FIFO to indicate status (Full, Empty,and Programmable)

CTL1    FLAGB       These flags are used by the FIFO to indicate status (Full, Empty,and Programmable)

CTL2    FLAGC       These flags are used by the FIFO to indicate status (Full, Empty,and Programmable)

PA7       FLAGD       FIFO Full flag output from FX2LP. Active low

??         Sync           (PC0  of  FX2LP) ????

RDY0    SLRD         SLRD pin should be asserted by the master to read data from the FIFO

RDY1    SLWR        SLWR pin should be asserted by the master to write data to the FIFO.

IFCLK   IFCLK         48Mhz clock to FX2LP

PB[0:7] FD[0:7]       Lower 8 bits of 16-bit data bus.

PD[0:7] FD[8:15]     Upper 8 bits of 16-bit data bus.

1. What is PA0/INT0 used for and is it  active high or active low?

2. What is PA1/INT1 used for and is it  active high or active low?

3. Is PA2/SLOE active high or active low?

4. Does FIFOADR[0:1] always need to be "10" for my scenario, or "11"? Is it for some reason active low?

5. When does PKTEND need to be asserted and is it active high or active low?

6. What specifically are FLAGA, FLAGB, FLAGC for, and are they active high or active low?

7. What pin is "Sync" on the FX2LP? Is it  active high or active low? ( Pin diagram on page 22 https://www.cypress.com/file/138911/download )

8. Can you confirm that SLRD and SLWR are active low?

I've already looked at these references:

USB2.0 Camera Interface Using FX2LP™ and Lattice CrossLink FPGA - KBA222479

https://www.cypress.com/documentation/application-notes/an61345-designing-ez-usb-fx2lp-slave-fifo-interface

https://www.cypress.com/file/44551/download

https://www.cypress.com/file/138911/download

http://blog.malcom.pl/wp-content/uploads/2015/02/CY7C68013A_schematic.png

Thanks

We sell several devices which uses Cyprus USB FX2 chips. We have always used the CyUSB.sys driver (which we signed ourselves) but are now running into problems installing these drivers on Windows 10. The upshot is that we need to migrate to using CyUSB3.sys and get the drivers properly signed by Microsoft. I have looked at the ‘Driver Resell’ information and am in the process of generating the necessary information.

I have a question regarding CyUSB3 driver installation (as I was not the developer who developed the CyUSB communications):

At the moment we install specific “.spt” configuration/firmware files at the same time as we install the CyUSB3.sys driver. These files are (very occasionally) updated during product improvements. Is it necessary for us to include these in the CyUSB3 driver installation? If so then would changing the file invalidate the driver certification (assuming the driver already installed)?

Hello!

A  few  years  ago, I wrote an C++ application for Windows - use CY68013, CyAPI-based, and it work good.

And now, after migrating from Visual Studio 2015 to Visual Studio 2017, my application (for CY68013, CyAPI-based) can not build anymore!

I've got the error message:

1>CyAPI.lib(CyAPI.obj) : error LNK2019: unresolved external symbol _sprintf referenced in function "public: void __thiscall CCyUSBDevice::UsbdStatusString(unsigned long,char *)" (?UsbdStatusString@CCyUSBDevice@@QAEXKPAD@Z)

It seems that problem is into CyAPI.lib.

How can I fix it?

Thnx.

Hello,

Any gaudiness in how connect a keypad with fx3. I am planning to interface it with I2C . Any similar examples?    

Thanks in advance.

Hi,

I am using CYUSBS236 USB-serial development Kit.
When I run the example UART code given in the ISO file from "www.cypress.com/go/CYUSBS236" the function "CyGetDeviceInfoVidPid" returns a device type "5" which corresponds to a device in "Manufacturing mode"

typedef enum _CY_DEVICE_TYPE {

    CY_TYPE_DISABLED = 0,               /*Invalid device type or interface is not CY_CLASS_VENDOR*/

    CY_TYPE_UART,                       /*Interface of device is of type UART*/

    CY_TYPE_SPI,                        /*Interface of device is of type SPI */

    CY_TYPE_I2C,                        /*Interface of device is of type I2C */

    CY_TYPE_JTAG,                       /*Interface of device is of type JTAG*/

    CY_TYPE_MFG                         /*Interface of device is in Manufacturing mode*/

} CY_DEVICE_TYPE;

I would like to configure the development board (CY7C65215) in UART mode (I have already configured SCB0 in UART mode) to be able to use UART specific functions.

/*

   Summary

   This API is used to retrieve the information of all devices with specified Vendor ID and Product ID.

   Description

   For a given VID and PID, the API returns deviceIdList and deviceInfoList.

   The deviceIdList contains the device numbers of all the devices with specified VID and PID.

   Using deviceInfoList application can identify the device of interest.

   Information that is provided includes interface number, string descriptor, deviceType and deviceClass.

   Return Value

   * CY_SUCCESS on success else error codes as defined in the enumeration CY_RETURN_STATUS.

   * CY_ERROR_REQUEST_FAILED on if library is not initialized (Only for Linux and Mac)

   * CY_ERROR_INVALID_PARAMETER if the input parameters are invalid.

   * CY_ERROR_DEVICE_INFO_FETCH_FAILED if failed to fetch device information.

   * CY_ERROR_ACCESS_DENIED if access is denied by operating system.

   * CY_ERROR_DEVICE_NOT_FOUND if specified device number is invalid.

   See Also

   * CY_DEVICE_INFO

   * CY_DEVICE_CLASS

   * CY_DEVICE_TYPE

   * CyGetListofDevices

   * CyGetDeviceInfo

   * CyOpen

   * CyClose

*/

CYWINEXPORT CY_RETURN_STATUS CyGetDeviceInfoVidPid ( 

    CY_VID_PID vidPid,                          /*VID and PID of device of interest*/

    UINT8 *deviceIdList,                        /*Array of device ID's returned*/   

    CY_DEVICE_INFO *deviceInfoList,             /*Array of pointers to device info list*/

    UINT8 *deviceCount,                         /*Count of devices with specified VID PID*/

    UINT8 infoListLength                        /*Total length of the deviceInfoList allocated

                                                 (Size of deviceInfoList array)*/  

    );

Thank you for your help.

Hello,

In my company, we are producing keyboards using CY7C63413C controler.

Until now, we programmed them with CYPRESS USB PROGRAMMER FOR STARTER (CY3649). Unfornately it seems to don't work anymore and I can't find where to buy a new one online.

Do you know if I can buy a new one ? Or maybe which new programmer can I use ?

Many thanks for your quick reply, we are actually blocked du to this failure,

Best Regards,

Benjamin Recoules

Hello

After programming the program using the USB "Control Center",
Could you tell me how to check that the program was correctly rewritten by Control Centor?

Best Regards

Arai