USB low-full-high speed peripherals Forum Discussions
Hello. i am using my UVC device to connect esp32-s3 but it have only USB 1.1. my device code have only 2.0 for now. I have found one function to force the USB 2.0 device connection to full speed. But don't know how & where to add it.
CyBool_t enable /**< Whether to enable/disable the forced full speed operation. */
Cypress FX3 Core Library Header (cyu3usb.h).
And After using this function do i need to change DMA channel configuration?Show Less
I would like to know the standard value of VIL undershoot in CY7C65213-32LTXI.
In the datasheet, I found a description of VCCIO+0.2V as the standard value of overshoot for VIH,
but I could not find a description of the standard value of undershoot for VIL.
I've implemented a FIDO CTAP 2.1 interface on an FX3s but I am getting very strange behaviour with it... I've posted in the FIDO community google group but I don't think I'll get a response there... Any thoughts/ideas would be most appreciated!
1. Driver and report descriptors work as expected
2. HID Communication works
Situation 1 (working situation)
1. Load up a test page for FIDO (Chrome browser, webauthn.io or other tool, all have same behaviour)
2. Start a FIDO registration process, browser says "insert FIDO device"
3. Program FX3s with FIDO firmware, it registers and handles INIT and GETINFO steps correctly, and sends registration info
Situation 2 (not working situation)
1. Program FX3s with FIDO firmware
2. Load up test page
3. Start FIDO registration, gets stuck in a loop performing INIT and GETINFO until "device fail" message
The part that is really confusing me is during INIT stage, the FX3s must send a new CID value, which the webpage/host must use for future responses, which it DOES use for the getinfo request... This confirms that FX3s -> FIDO HID -> browser and back communication is working successfully in situation 2.....
Is this potentially an issue with chromes implementation of FIDO HID? Is there a way I can "trick" the host with the FX3s to do a reset on a specific USB interface? I do not want to disconnect USB via CyU3PConnectState since it is a composite device and other interfaces may be doing something.
I should also point out there's shouldn't be any real difference in timing between messages sent and received (approx 10~50ms), nor is the content of the replies different. I will be investigating this with wireshark shortly but I am doubtful that a message timeout is the problem since the host should be sending an error if there is one as well.
Edit: This only happens on USB3, works as expected on USB2 (Both scenario 1 and 2 work USB2), further edit, responses are always 64 byte in size which is the buffer size so there should be no issues with set wrap up (I think)
I am using a Android Stuio to program a USB to I2C. in fact, some body has help me. But he gave me an libs for armeabi(6t bit).
I need a a libCYUSBSerial.so for 32 bit ARMEABI-7a. can you urgent give me a reply and a lowver version?
I'm trying to send a signal from the ztex board USB-FPGA Module 2.13 using a USB 2.0 to the computer. From the side of the fpga, I'm using a fifo code, and from the computer side, I have a java code given by ZTex specific for communication with fpga. When I test if there is any informations received, i obtain this error that I don't really understand since this is the first time I test such programs:
Error: Error receiving data: Input/Output Error
Can you help me find a solution to this error so as I can send data from fpga to computer? Thanks in advance. Tell me if you need to see the java code and vhdl project. Thanks in advanceShow Less
I have a folder driver for printer which is used for win 10 (intel) and they include 3 files: cyusb3.sys, cyusb3.cat, cyusb3.inf. I tried to install them on windows 11 arm-based but it says unable to find these driver. I have been searching long while and found out there is way to convert them to arm-based (I am not giving the link cuz this come from another site)
Can anyone please help me if there is a document or tutorial of this topic?
Kindly thanks for your supportShow Less
Hi, I'm new to Fx2LP
I've been having this problem for days, I need help from everyone.
I have FX3SDKSetup_1.3.4 and sdcc-4.1.0-x64-setup installed.
I'm using 2 methods to build my program and facing a problem:
i) For method 1, download the project from github (https://github.com/matthiasbock/fx2lp-blinky) and add it to the EZ USB Suite as shown below:
The result was a .hex file, but loading it into FX2LP it didn't work.
The hex file when built using this method can be converted to .iic with hex2bix.
ii) With method 2, I used the available example of EZ USB Suite, the way to create is as shown below:
In fw.c, I modified main() to look like this:
__sfr __at (0xB2) OEA ;
__sfr __at (0x80) IOA ;
OEA=0x03; // port A as output
IOA = 0x00; // All leds ON
The result was a .hex file, loading into FX2LP worked, the light blinked.
However by this method I can't convert to iic, I get the error:
hex2bix -i -c 0x00 -f 0xC2 -o projectName.iic projectName.hex
Intel Hex file to EZ-USB Binary file conversion utility
Copyright (c) 2012-2013, Cypress Semiconductor Inc.
Error: Input image too big for output file size. Addr = 0xe000, len = 0x20.
I don't know where the error lies, if anyone can give me a perfect sample project, thanks.
I've a similar issue as described in thread:
Our Application/device is productive for several years now and running without any major issues using driver version 3.4.7.
We recently tried upgrading to the latest driver version(s) and run into connectivity problems:
The USB communication (mainly bulk transfer EP1) between uC and PC is working for several minutes upto a few hours with out any issues. Suddenly the device is removed and reattached within the same second, but of course the previous CyFX2Device object got invalid and the PC software stops/hangs. Debugging my software, it looks like the CyUSBEndpoint.XFerData routine never ends, waiting for the transfer to finish/abort. (More precisely: the thread is waiting in CyUSBEndpoint.WaitForIO)
Sometimes the device is also missing in the CyUSB.USBDeviceList after these "reenumeration events".
We tested several combinations of cyusb.sys and cyusb.dll with the same harware, firmware and PC-Software:
3.4.7 (sys) 3.4.7 (dll) -> working
126.96.36.199 (sys) 188.8.131.52 (dll) -> working
184.108.40.206 (sys) 220.127.116.11 (dll) -> fail
Since the above thread mentions a similar issue I was wondering if there
a) is a newer version of the cyusb.dll which should be used with 1.3.0.x version of the driver?
b) is there a newer version of the cyusb3.sys file?
Hello, now I test the SPI communication rate of cy7c65211A chip in the linux virtual machine environment. SPI has been adapted to 3Mhz, Master and Mode2 modes. It is found that the CySpiReadWrite function is used to read the time interval of 1-byte sensor data each time. The time required for payment is about 8ms, I am not sure why it takes so long. The CS chip selection signals here are all GPIO2. Please reply when you are free, thank youShow Less