USB superspeed peripherals Forum Discussions

Hi,

I'm using the 32-bit slave fifo sync interface and using the slfifosync example code.

When I do an IN transfer, the following OUT transfer has an extra word of zeros prepended to it.  Any ideas?  Is this expected?

I don't see the OUT direction GPIF flags asserted after the IN transfer.  Even so, when I try an OUT transaction, I get this extra word.  Any subsequent OUT transfer does not have the extra word.  If I perform another IN transfer, then the very next OUT transfer again has the extra word.

Second question:

On the OUT direction I'm using the partial flag to indicate when I can do a high speed burst.  This works fine, except that at power up this flag is incorrectly asserted.  After any transfer, the flag is correct.  To overcome this, I only do a high speed burst if both partial flag and the ready flag indicate that data is available.  I have both flags set to "initial value = low", "asserted polarity = low".  BTW, the ready flag does not have this behavior, only the partial flag.  Also the IN direction flags work as expected.  Anyway, is this incorrect initial polarity expected?

Thanks,

Joe

Has anyone successfully set up a CX3 chip to receive audio in addition to video data?

We're having trouble finding any electrical components that can work with the CX3.

1) i2s is a no go.  You can output i2s but not receive i2s.
2) spi is problematic.  It doesn't seem you can output a constant clock with spi.  There is a pause between SSN signal between word reads and even if there is a way to overcome that there is a larger pause when you switch DMA buffers. 

So in short, how do you get audio along with your video?

Using version 1.3.3 of the FX3 SDK and an explorer board. The USB control center will correctly allow me to write to the I2C eeprom, with the resulting firmware booting as expected.

Sadly if I try and use the cyfwprog utility it keeps failing. Once reset the FX3 board appears to go into USB boot programmer mode but the second stage where it should write the new firmware fails. 

The .img file is created using elf2img. Does this need any special options?

Any thoughts please? I need to get this process automated ASAP. Many thanks.

-------------------------------------snip--------------------------------------------

R:\src\cypress\fx3\gpiftousb>cyfwprog -v -fw BootGpifDemo.img -dest I2C_EEPROM Parsing the arguments Arguments: -------------------------------------------- Firmware Path: BootGpifDemo.img Destination  : I2C_EEPROM --------------------------------------------  Device detected with vid = 0x4b4 and pid = 0xf3  Downloading the R:\apps\cypress\EZ-USB FX3 SDK\1.3\\util\cyfwprog\CyBootProgrammer.img image for writing into EEPROM Reopening the USB device Device detected with vid = 0x4b4 and pid = 0x7 Downloading image BootGpifDemo.img Firmware download failed : Unknown error

Hello,

Can someone please advise on how we can get access to the source code and settings corresponding to CX3OV5640LIB libraries in CX3 OV5640 RDK.

Regards,

Subhasish Ghosh

actually we are using Cypress Streamer to get imaged data to pc .when we connected to fx3 board end pints are detecting but successful packets are not receiving by streamer only failure packets are receiving .can any one sort out of this problem

Every once in a while I get caught in the _tx_thread_schedule and can't recover unless I cycle the power to the CYUSB3014-BZXI device.  I'm wondering if you have a way to trouble shoot this? or an idea of what might cause this? (I don't have serial port available on this board)  This is a camera based on the AN75779 app note, using a MT9V034 Image sensor. 

Any help you could provide would be appreciated!
Brandon

I'm designing a stereo UVC device with the CYUSB3014 FX3 and two AS0260 CMOS sensors. I took the AN75779 as reference design, which allows to interface one MT9M114 with YUY2 output format directly to the GPIF-II port of the FX3. The AS0260 is actually similar to the MT9M114, but with higher resolution. It outputs in JPEG format, providing higher performances in terms of fps (thanks to the compression).

I'm wondering if it is possible to use the reference firmware to make it work with JPEG format.

JPEG has variable LV (line valid), that's my only concern. I'm afraid that the state machine can stuck.

I'm interested in know how to use UVC extension unit.

I  want to know how the UVC extension unit works

I noticed that the UVC Extension Unit is not supported in the AN75779 application note 

In the cyfxuvcdscr.c file,What changes should I make at the Extension Unit Descriptor when I want to communicate with

FX3 via UVC Extension Unit.

Thanks,  I appreciate the help.

FX3

I have a  complex GPIO set as a 1HZ timer with interrupt.  I get the interrupt until I start sending messages.

Below is the GIO configuration. 

    /* Configure GPIO 33 as 1PPS input */
    ppsGpioConfigComplex.outValue    = CyFalse;
    ppsGpioConfigComplex.inputEn     = CyFalse;
    ppsGpioConfigComplex.driveLowEn  = CyFalse;
    ppsGpioConfigComplex.driveHighEn = CyFalse;
    ppsGpioConfigComplex.intrMode    = CY_U3P_GPIO_INTR_TIMER_THRES; 
    ppsGpioConfigComplex.period      = 192000000; 
    ppsGpioConfigComplex.pinMode     = CY_U3P_GPIO_MODE_STATIC;
    ppsGpioConfigComplex.threshold   = 192000000; 
    ppsGpioConfigComplex.timer       = 0;           // Timer initial value
    ppsGpioConfigComplex.timerMode   = CY_U3P_GPIO_TIMER_HIGH_FREQ;
    apiRetStatus = CyU3PGpioSetComplexConfig(PPS_MONITOR, &ppsGpioConfigComplex);