USB superspeed peripherals Forum Discussions
Hi,
I am trying to send data from USB to GPIF in Serial mode (Serial interface using GPIF II ) . serial data is going to FPGA. But i have data loss in FPGA.
I think my problem is that there is a gap during buffer change. so I tried to do something like the configuration in UVC example in reversing(FROM FX3 to GPIF II)
I change the state machine for reading from 2 threads in DR_data (The image is attached) and also used multi channel DMA to with 2 consumer sockets (CY_U3P_DMA_TYPE_AUTO_ONE_TO_MANY). But now I get this error: BULK OUT transfer failed with Error Code:997 when i try to send a file which its size is more than DMA_Buff_size.
Should I do any other changes in code? I appreciate if there is any suggestion and help.
Thanks
Hi,
I'm using fx2lp in cyusb linux, but i'm geeting error in data transfer. The following errors are shown below.
I program the FX2LP using the cyusb_linux, getting the error in sending and receiving the data.
Regards,
Show LessDear all,
I am using the CX-3 controller interfaced to a ToF Image-Sensor using CSI-2. If the sensor sends the image data(which consists of a variable length of several same-sized sub-frames(640x480, RAW12)) as a superframe(=all the image data of a raw frame is transferred between a single "Start of Transmission" and "End of Transmission" on CSI-2 level) there is a limitation regarding the data-size. It is able to transfer 8 consecutive sub-frames having 640x480 resolution and 12bit per pixel. When transfering 9 consecuitve frames it stops working. However, if each sub-frame is transferred packed between "Start of Transmission" and "End of Transmission" packets, the image data can be transferred without a problem. I am somehow suspecting that the GPIFII interface causes these problems by maybe loosing track of data-counters due to an internal overflow. The firmware is mostly identical to the AN75779 UVC Firmware. Any help is kindly appreciated!
Show LessQ1.
Do you have information about the MIPI CSI2 output data format and timing of the image sensor (OV5640)?
Q2.
Cusotmer want to perform an experiment to operate another camera by customizing the firmware sample cycx3_uvc_ov5640.
The camera configuration is not changed, but is there a way to unlock it?
=>
I think as follows.
Once, select "Save" at the top right of the window to save as a custom configuration, then select "User Defined Configuration" to change the settings.
Is it correct?
Q3.
Is there any file that has a description specific to the camera OV5640 other than the file that is changed by the configuration tool?
=>
I understand that there is an I2C initialization file. Please let me know if you have any other.
Best Regards,
Harukawa
------------------------------------------
Q1.
キットに添付のイメージセンサ(OV5640)のMIPI CSI2出力データフォーマット、タイミングに関する情報はございますか。
Q2.
ファームウェアサンプルのcycx3_uvc_ov5640をカスタムして別のカメラを動作させる実験をしようとしております。
カメラコンフィグレーションが変更できないようになっていますが、解除する方法はありますでしょうか
=>
一度、ウィンドウ右上にある「保存」を選択して、カスタム構成として保存したあと、「User Defined Configuration」を選択して設定を変更すれば良いと思います。
この理解で正しいでしょうか。
Q3.
コンフィグレーションツールで変更するファイル以外に、カメラOV5640に固有の記述があるファイルはあるでしょうか。
=>
I2Cによる初期化用ファイルがあることは理解しています。それ以外にもありましたらご教示ください
Show LessHello,
How to integrate FATFS to firmware inorder to read data in PC/Mobile from SD Card?I went through the default FATFS firmware and wanted to integrate that into my firmware.Anyone did the same application please let me know.
Regards,
Dhanuja.
Show LessIf one kit is connected to USB and another still not connected (or one host PC is down), then some pins on GPIF II bus may be driven by the powered kit onto the unpowered kit which may be harmful unless the firmware and the GPIF II state machine can be sure that this doesn't happen.
A potential solution is remove VBUS jumper of one kit and connet USB3_VBUS between the kits by not cutting that pin. Potential problem is this may drive VBUS_IN on the unpowered kit trough U11 to 4.x Volts.
Show LessHello dear Cypress community,
I'm currently trying to use a JTAG SEGGER J link probe to debug the CX3RDK_OV5640 firmware. I have the known error of bad JTAG communication while passing over the CyU3PDeviceInit(NULL) :
ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x3 (TAP Command : 15) @ Off 0x1053.
I have found the fix topic and followed the recommended configuration to change the CPU clock :
But unfortunately, even with this correction I'm still getting the same error message in the end :
ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x3 (TAP Command : 15) @ Off 0x1053.
I tried both CPU clock configurations (0x00080014 and 0x00080015) and it still results with the same error message.
Am i missing something in the configuration steps ?
Thank you in advance for helping me solving this bug.
Best regards,
Vivien