USB superspeed peripherals Forum Discussions

Here is the thing that I 've bought an CYUSB3KIT-003,and I used it in slave fifo mode.  I used FLAGA and set it to gpio_21. As I understand it, gpio_21 is connected to the CTL_4 pin of the board so it should be logic 0 after the board is booted, however , its voltage was about 0.9V.

 How is it happen? 

Hello,

I'd like to test a custom module which is CSI-2 serial data output (MIPI 2lnae 960 Mbps/lane, D-PHY spec. ver. 1.2 compliant).

is it possible to test it using CX3?

If more information is needed to check it, let me know what it is.

Regards,

Philip

Dear Sirs,

Attached is part of my FX3 state machine when doing READing Data and the interface timing I suppose FX3 would be.

State machine will go from READ state to RD_WAIT state triggered by rfifo_empty(from external device:FPGA).

my question is :

If I just want to read 4 times, but state machine will go to RD_WAIT(slcs/slrd/sloe==HIGH) after it samples rfifo_empty==HIGH at positive edge of PCLK. If the interface timing is like what I draw, there will exist 5 read transfers.

How to avoid this situation? (Or maybe my assumption about interface timing is not correct)

Best regards,

james

Hello,

I would like to put the XRST pin in high with the following function: CyU3PMipicsiSetSensorControl (CY_U3P_CSI_IO_XRES, CyTrue); but when I call any function that contains Mipi I get the following error: 

Does anyone have any idea why? thank you

Dear sir,

When I was learning and using the CYAPI library, I found a problem.

About BeginDataXfer and FinishDataXfer. In these 2 functions, they all need a buffer paramemter.

So I checked the source code. In BeginDataXfer function, the buffer will be memcpy into pXmitBuf.

And in FinishDataXfer, the buffer will be memcpy out from pXmitBuf.

So why do we need such a weird repetitive operation?

Thanks

Chad

Hi,

I am actually working with 13MPx CMOS Image Sensor. this sensor has 10 bits accuracy in his dynamic range. So, for this reason has the possibility to sending both 8 bits per pixel either 10 bits per pixel (using full dynamic range).

As I am currently working with the CX3, using RGB888 as data input and 24 bits size as data output. I have to use The the 8 bits per pixel profile from the sensor,knowing that I am lossing accuracy which is esential in order to quantize the analog value.

So, I have the following question: Is it possible to send 10 bits per pixel from the sensor, using a CX3's configuration based on RGB888 as data input and holding the same output size of 24 bits?. Because if I do it, we will not have to do zero padding as with the RAW10 format. (Please, see the attached picture).

What code sections will have to change in order to get this profile?.

Thanks so much.

Hello,

I'm trying to develop a custom module.

The module has embedded data but I cannot receive the data that I expected.

In order to check EMB data, I modified a BulkLoop example to print some logs as below.

I expected "Phase Idx" 0, 1, 2, and 3 should be repeated but they didn't.

At first, I thought I'm able to use "CyU3PDebugPrint()" function.

However when I added that function to DMA callback function which names CyCx3UvcAppDmaCallback(), the firmware didn't work.

I want to check the DMA buffer to make sure that the firmware is no problem.

In this case, how can I access the DMA buffer to check values?

or Is there any way to check the EMB data?

Thank you.

Hello,

We want to use CyU3PMipicsiSetSensorControl(CY_U3P_CSI_IO_XRES,CyTrue); in the BootLedBlink example main.c line 83.

We attached also the source code .The result when compile is: 

*** Incremental Build of configuration Debug for project BootLedBlink ****
cs-make all
'Building target: BootLedBlink.elf'
'Invoking: Cross ARM C Linker'
arm-none-eabi-gcc -mcpu=arm926ej-s -marm -mthumb-interwork -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall -g3 -T "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_build/boot_fw/cyfx3.ld" -nostartfiles -Xlinker --gc-sections -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/boot_lib/1_3_3/lib" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\ARM GCC\/lib/gcc/arm-none-eabi/4.8.1" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\ARM GCC\/arm-none-eabi/lib" -Wl,-Map,"BootLedBlink.map" -Wl,-d -Wl,-elf -Wl,--no-wchar-size-warning -Wl,--entry,Reset_Handler -o "BootLedBlink.elf" ./I2C.o ./cyfx_gcc_startup.o ./main.o -lcyfx3boot -lcyu3mipicsi -lc -lgcc
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiRegisterRead':
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterRead+0x54): undefined reference to `CyU3PI2cReceiveBytes'
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterRead+0x68): undefined reference to `_tx_thread_sleep'
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiRegisterWrite':
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterWrite+0x50): undefined reference to `CyU3PI2cTransmitBytes'
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterWrite+0x64): undefined reference to `_tx_thread_sleep'
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiSetSensorControl':
cyu3mipicsi.c:(i.CyU3PMipicsiSetSensorControl+0xbc): undefined reference to `_tx_thread_sleep'
c:/program files (x86)/cypress/ez-usb fx3 sdk/1.3/arm gcc/bin/../lib/gcc/arm-none-eabi/4.8.1/../../../../arm-none-eabi/bin/ld.exe: BootLedBlink.elf: hidden symbol `CyU3PI2cReceiveBytes' isn't defined
c:/program files (x86)/cypress/ez-usb fx3 sdk/1.3/arm gcc/bin/../lib/gcc/arm-none-eabi/4.8.1/../../../../arm-none-eabi/bin/ld.exe: final link failed: Bad value
collect2.exe: error: ld returned 1 exit status
cs-make: *** [BootLedBlink.elf] Error 1

12:55:48 Build Finished (took 2s.213ms)

How can we use this function in bootledblink example?What do we have to include or to configure?

Thanks in advance!