USB superspeed peripherals Forum Discussions

A DEV PC has the FX3 SDK installed on Ubuntu 18.04 LTS since Feb'20 (currently 18.04.04). ControlCenter (aka cyusb_linux), download_fx3, and my app "X2", are all running fine.

On Thursday, 18.04.05 was installed on a **new PC** along with the same FX3 SDK install process.

cybusb_linux and download_fx3 detect the FX3 and images can be downloaded from either.

However at this point, it seems  that re-enumeration fails as cybusb_linux cannot detect the loaded FX3 (?!).

The recompiled X2 app also fails at

1) Is it a re-enumeration issue? All the files setup in the install.sh script are located where they need to be.

2) Is it an SDK install issue? Quite a few packages were deleted during "sudo apt-get remove libusb-1.0-0" prior to the "sudo apt-get install libusb-1.0-0-dev"...
    Running apt-get update and another package was required to get ubuntu login/desktop running......

3) The fallback is to revert to 18.04.01 (or whatever is available) given the DEV pc works; albeit reversion to Ubuntu 16 would be the next step.

Thanks

John

Hello,

I am new to FX3 chip.

I am using cyfxmscdemo that comes within the FX3 SDK. My goal is to connect the FX3(master) to FPGA(slave) using gpif port.

In the demo, there is a dma channel between uib-socket and cpu socket and the on-chip ram space is allocated for read/write purposes.

I want to transfer the data to gpif port. The question is,

1) Can I create another dma channel between another cpu socket and gpif socket to transfer the data?

(As far as I see in the manual, there is only cpu socket(?) and it is already in use by this demo)

2) Should I read/write to gpif using register access by CyU3pGpifWriteDataWords()-CyU3pGpifReadDataWords() functions?. But this must be slower than dma access.

Thanks in advance,

  HI：      in   C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\application\cpp\streamer  project  ,how to get every frame  data and  display it..

Hi,

I'm working with an FX3 and I would like to combine BULK and ISOCHRONOUS endpoints (a pair of bulk endpoints and a pair of Isochronous endpoints). I've tried to modify the descriptor but I don't get the USB recognised. Also added code for a proper initialisation. If I use only the BULK interface it works just fine and I can see the device normally listed and its descriptors.

My question is: Can I mix in the same interface BULK and ISOCHRONOUS endpoints?

Kind regards

Hello

From AN76405, I2C EERPOM specifications are below.
ROM size: Up to 128kB(1024kb)×4, 128kB is recommended for microchip 24LC1025.
Q)
Are there any restrictions on the operating specifications?
1.Page write size (128LC for 24LC1025)
2. Writing time
3. Other

Best Regards

Arai

I'm using FX3 with FPGA instead of Image sensor. To debug some issue, I am trying to get UART logs, but not able to.

Any pointer that would help.

How  hexa decimal value assigned for below in cyfxuvcdscr.c?  Is reference available?

/* Interface Association Descriptor */

/* Standard Video Control Interface Descriptor */

/* Class specific VC Interface Header Descriptor */

/* Input (Camera) Terminal Descriptor */

/* Processing Unit Descriptor */

/* Extension Unit Descriptor */

/* Output Terminal Descriptor */

/* Video Control Status Interrupt Endpoint Descriptor */

/* Super Speed Endpoint Companion Descriptor */

/* Standard Video Streaming Interface Descriptor (Alternate Setting 0) */

/* Class specific Uncompressed VS format descriptor */

/* Class specific Uncompressed VS frame descriptor */

Thanks

Esakki

Hi All,

I am looking for a MJPEG firmware example with the OV5640 sensor,  please share the example.

Please refer to Cypress 001-90369_AN90369_How_to_Interface_a_MIPI_CSI-2_Image_Sensor_With_EZ-USB_CX3.pdf pp.28

thanks

Akeem

Hi

we have used an FX3 and Type a Male connector before, There we have swapped an RX and TX lines in the connector to Fx3.

This time we have used a Type A receptacle (Female), Here we have to swap the RX and TX pins or not?

This Type A receptacle is connected to the PC (Like UVC output) by male to male Cable.

Thanks.