USB superspeed peripherals Forum Discussions
text.format{('custom.tabs.no.results')}
The original FX3 U3V sample only supports one format stream, so I tried to add the second format data(multi ROI) within it.
But what's the rule when different format?
It seems that the smaller iamge payload should add 4 bytes padding data when it works with two format?
Show LessHi All,
I believe we are experiencing a Silicon design problem with the CYUSB3064 chip. This is the second generation of the design. We noticed the same issue on the 1st generation, but never got to the bottom of it. This design appears to be worse (e.g. more leakage).
We have a CX3 design that runs VDDIO1 & VDDIO2 from 1.8V, VDDIO3, CVDDQ from 3.3 volts, TXVDD/RXVDD, AVDD, MIPI_VDD and VDD from 1.2V. The board contains four voltage regulators powered by USB's VBUS (5V) whose outputs are: 1.2, 1.8, 2.5 and 3.3V. All the regulator outputs are nominally correct except the 1.8V regulator is 2.7V and appears to be back-fed. The 1st generation boards supply was around 2.1 volts.
With all the components except the CX3 removed from the 2nd generation PCBA, including the 1.8V regulator, the 1.8V supply still sits at about 2.7V. If I connect an ammeter between the 1.8V supply and ground, I measure 15.7 mA, so this is not a dead-short. After removing the CX3 the 1.8V measures zero.
Are we misusing the CX3 in some manner to explain this leakage current?
Thanks,
Scott
Show LessHi all,
I have test setup which consist of Zedboard and SuperSpeed Explorer Kit.
Zedboard with Xilinx Zynq700 FPGA sends test pattern through the parallel interface (CLK/FV/LV/DATA(7 bit)) to FX3 GPIF input
FX3 is connected to PC USB3 port and running example SW from AN75779.
i'm trying to capture video from UVC device "FX3" with VLC/Virtualdub.
Problem is that there are no incoming frames at all.
Here is UART output:
UsbEventCB: Detected SS USB Connection
USBSetupCB:In SET_FTR 0::1
USBSetupCB:In SET_FTR 0::1
USBSetupCB:In SET_FTR 0::1
USBSetupCB:In SET_FTR 0::1
USBSetupCB:In SET_FTR 0::1
UVC: Completed 0 frames and 0 buffers
UsbEventCB: SUSPEND encountered...
Entering USB Suspend [00]S‹VVHרUSBSetupCB:In SET_FTR 0::1
Leaving Suspend Mode
UVC: Completed 0 frames and 0 buffers
Application Started
UVC: Completed 0 frames and 0 buffers
UVC: Completed 20 frames and 56 buffers
UVC: Completed 42 frames and 45 buffers
UVC: Completed 64 frames and 35 buffers
UVC: Completed 86 frames and 24 buffers
UVC: Completed 108 frames and 13 buffers
UVC: Completed 130 frames and 3 buffers
UVC: Completed 151 frames and 51 buffers
UVC: Completed 173 frames and 40 buffers
UVC: Completed 195 frames and 29 buffers
UVC: Completed 217 frames and 19 buffers
UVC: Completed 239 frames and 8 buffers
UVC: Completed 261 frames and 0 buffers
UVC: Completed 282 frames and 46 buffers
UVC: Completed 304 frames and 35 buffers
UVC: Completed 326 frames and 24 buffers
UVC: Completed 348 frames and 14 buffers
UVC: Completed 370 frames and 3 buffers
UVC: Completed 391 frames and 51 buffers
So video is definitely received by FX3, but is not forwarded to PC.
I appreciate any help
Show LessHi,
for my current FX3-Project I only need DQ0 to DQ11 and DQ16 to DQ27 of the 32 Bit GPIF as inputs. Can I use the remaining DQ-Pins (DQ12-15 and DQ28-31) as GPIO outputs?
Show LessAs the title states after striking our product containing an FPGA and FX3 chip vendor commands start sending corrupt data packets.
An example of expected data packet is 55, 33, 56, 43, 0, 0, 1, 8, 4, 0, 0, 0 but we are seeing 0, 0, 1, 8, 55, 33, 56, 43, d0, 1, 0, 0 it looks like each 4 bytes are getting swapped and random data is appended during the final 4 bytes.
We have seen this
We have added a simple vendor command that will return the character "A" when requested, no input from the FPGA, only the FX3.
<Code snip-it for the simple vendor command>
case 0xa1:
Ep0_Buf[0] = 0x41;
apiRetStatus = CyU3PUsbSendEP0Data(1, Ep0_Buf);
break;
After getting the FX3 into this weird state and asking for the character a random byte is returned.
All vendor commands seem to be working anything going into the device works as expected but data coming out of the FX3 seems to be wrong.
I would like to know if there is a way to reset memory or something inside the FX3 to try and get the data pointers working again.
We would perfer not to have to reset the FX3 with the command CyU3PDeviceReset due to it causing the product to disconnect from the PC.
Thanks for any assistance.
Show LessHi,
I am making a design based on the CYUSB3304-68LTXC USB3.0 hub. The reference document is the eval kit schematic. There is a discrepancy on the interfacing of the dwnstream ports to the USB Type A connectors. I have pasted a screen-shot below.
It shows the pins StdA_SSRX+ and StdA_SSRX- connected to DS1_RXM and DS1_RXP respectively in the IC. How is that possible ? Shouldnt the connections be swapped ? And what of the StdA_SSTX- and StdA_SSTX+ ? Should this also be so ?
Show LessHi all,
CYUSB3KIT-003 the kit is able to communicate Host to Host like
PC -USB- CYUSB3KIT-003 -USB- PC
I could not see any descriptions in any documents. please let me know.
Show Lesshi,
For my Ux testing I need an ability to control Ux features of FX3 device.
For default config I see:
wU2DevExitLat : 0x0000 (0 µs)
I need to change this latency. Is it possible?
Thanks,
Irena
Show LessHi,
I have been trying to work around and get to know the two programs usbbulksourcesink and bootledblink. So I what I wanted was to send hex codes like 0x74,0x75,etc and control GPIO pins that toggle LEDs.
So I have simply added my block of bootledblink to usbbulksourcesink without much changes to usbbulksourcesink program. All the initialization statements for gpio that were in bootledblink I have added to main() function of usbbulksourcesink . I only added a few more cases to bRequest and by using the cyfx3gpio.h set the state of GPIO by CyFx3BootGpioSetValue. But it does not seem to work.
First of all the program shows error even when I added "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\boot_lib\1_3_4\include" to "Path and Symbols". Commands like "CyFx3BootGpioSetValue", "CyFx3BootDeviceInit" that were in bootledblink show error.
And after Building the Project an image file was created. On programming the image file into EEPROM, the DataTransfers for "Bulk-In Endpoint" throws error "BULK IN transfer failed with Error Code:997".
I have attached the project file with the discussion.
Thanks
Show Less