USB superspeed peripherals Forum Discussions

Dear Supplier,

Could you please provide the TSCA statement for our customer request? Thank you very much.

Hi Cypress

We need CYUSB3035-BZXI SPI overshoot and undershoot spec for signal quality test , Can you help to get the spec for verifying , Thank !!

Hi:

   Now, i Can correct  read Sensor ID ,but  i Can not Writer register config in Register.   can call me ? my phone 18911808268

hello，

    I want to use cyusb3065 to transfer the frame by dma. So I want to get the point of the frame start. Wherher the GPIFII state machine can be modified? And how can I modify the GPIFII state machine？

When can we expect to see Cypress' support for USB 4.0.

The spec is expected to be released in late 2019.

Cypress as a USB leader, is likely well aligned.

Is Cypress able to update the USB Controllers Roadmap with their plans for various USB 4.0 products?

https://www.cypress.com/cypress-product-roadmaps

Greg

Hello,

I am using Fx3S microcontroller for my application. I noticed that standard FaTFS can support the filenames of the format 8.3 and to use the filenames of length>8, we have to change the value of _USE_LFN to 1(2 or 3 based on the need). This macro can be found in ffconf.h header.

If I define change the value of this macro to other than 0, then there are errors in the ff.c file.

Please help in solving this issue, so that I can use Long File Names(LFN) in my application.

Regrads,

Raghavendra.T.R

Hello,

in my CX3-based application I enabled the 'PIB interrupt' callback, by registering my CyU3PPibIntrCb_t-compliant function with the CyU3PPibRegisterCallback API: I don't need this for any purpose apart checking for unexpected conditions while I'm in a debug phase for the entire application.

Surprisingly I'm having my callback called many times during apparently normal operation, with cbType == CYU3P_PIB_INTR_ERROR and CYU3P_GET_GPIF_ERROR_TYPE(cbArg) == CYU3P_GPIF_ERR_INVALID_STATE.

Even if I'm not sure that it is legal to do so, in those circumstances I'm trying to understand which GPIF SM state is considered 'invalid', by calling the CyU3PGpifGetSMState from inside the callback. According to that procedure the states that seem to trigger the error are: CX3_IDLE_SCK0/1, CX3_WAIT_FOR_FRAME_START_SCK0/1, CX3_PARTIAL_BUFFER_IN_SCK0/1 and undocumented states 131 and 132.

Since I'm working on the CX3 device, I'm using the 'fixed'function' GPIF configuration that results from the call to CyU3PMipicsiGpifLoad(CY_U3P_MIPICSI_BUS_24, buffer_size).

Is the described behavior normal/expected ? If not, what could be causing the triggering of those errors ?

Please note that my application is currently a bit peculiar because I'm programming a custom D-PHY/CSI-2 sensor for image frames composed of a single line: as a result I'm currently keeping the line/frame rate quite low (compared to what supported by the sensor HW) in order to be able, on the CX3 side, to keep up with the corresponding interrupt rate.

Thanks in advance and best regards, Nicola.

I want to design a USB to SD card bridge using SD3. Is there an example project and reference schematic which I can refer to?

-> You can refer to cyfx3s_msc and cyfx3s_raid0 example projects provided in EZ-USB FX3 SDK

    You can refer to the attached FX3S USB RAID Dongle schematic for your design.

Hi,

I am working as a software Engineer and I'm quite new to the CY7C6801a / 128 pin and keil uvision. I already have working firmware program and chip is on our own circuit.  We haven't change the firmware since very very long time so I don't know how to connect the chip with keil uvision 3 and debug on the board.If it is able to debug with this chip, I would like to know how to do it.

On our circuit board , there is a 6 pin debug connector . Pin connections are as follow:

Pin 1 -> TX0, Pin2 -> RX0, Pin3 ->TX1, Pin4 ->RX1, Pin5 -> Gnd, Pin6->3.3V.

To be able to debug the program, how should i connect ?Do i need the Ulink2 adapter to connect ? How can I convert the 10 pin Jtag to 6 pin connection that I currently have on board?

Many Thanks

Su