USB superspeed peripherals Forum Discussions

 Hi

In slave fifo mode, it's need windows apprication program. 

But i didn't know well about apprication program. 

Is xferdara() used in slavefifo sync mode operation?

If not, how can i translate data between fx3 and apprication programs in apprication programs?

Hii guys,

Is it possible to send data out from fx3 using two consumer sockets and I have two producer end points and  one producer socket mapped to one consumer end point. I have to perform a slave fifo interface 32 bit(burst read mode). Can I tranfer data out from one socket and when that buffer is empty can I transfer data out from the other socket is this design possible??

 Hello everyone 

The issue as follows:

Develop with SDKv1.2. 

I want to transfer data by USB3.0 with DMA mode. I create 3 DMA chanels.and two for data transfer the third for command transfer.

As we know just one DMA channel can work at the same time.But I want to transfer command during data transfer.Data transfer is not continue.So I want to transfer command in data transmission interval. So the DMA for command transfer must be CY_U3P_DMA_TYPE_MANUAL mode .Before command transfer I should check if other two DMA channels are busy or idle.

Is there any function to get the DMA status .Does somebody get me an sample .And does my scheme word?

thanks

ayi 

I have 3 endpoints 2 out bulk endpoints and 1 in endpoint. I want to implement a slavefifo interface.

 Is one consumer p-port socket is enough to transfer data from 2 out endpoints are should I create an other consumer p-port socket?

Thanks in advance

hi! all

I´m trying to compile my Examples for GPIO(LEDon/off)

but,a compilation error comes....

here message

----------------------------------------------------------------------------------------------------------------------------------------

in file included from C:\Cypress\EZ-USB FX3 SDK\1.2\firmware\u3p_firmware\inc/cyu3system.h:27:0,
                 from ../sdtech.c:47:
C:\Cypress\EZ-USB FX3 SDK\1.2\firmware\u3p_firmware\inc/cyu3dma.h:738:16: error: field 'lock' has incomplete type
C:\Cypress\EZ-USB FX3 SDK\1.2\firmware\u3p_firmware\inc/cyu3dma.h:739:16: error: field 'flags' has incomplete type
C:\Cypress\EZ-USB FX3 SDK\1.2\firmware\u3p_firmware\inc/cyu3dma.h:818:16: error: field 'lock' has incomplete type
C:\Cypress\EZ-USB FX3 SDK\1.2\firmware\u3p_firmware\inc/cyu3dma.h:819:16: error: field 'flags' has incomplete type
cs-make: *** [sdtech.o] Error 1

----------------------------------------------------------------------------------------------------------------------------------------

Doe get why this error?

Note That i'm using SDK1.2 and then the 1.2.1 upgrade.

 - default source -

#include <cyu3system.h>
#include <cyu3os.h>
#include <cyu3error.h>
#include <cyu3gpio.h>
#include <cyu3uart.h>

int
main (void)
{
    CyU3PIoMatrixConfig_t io_cfg;
    CyU3PReturnStatus_t status = CY_U3P_SUCCESS;

    /* Initialize the device */
    status = CyU3PDeviceInit (0);
    if (status != CY_U3P_SUCCESS)
    {
        goto handle_fatal_error;
    }

    /* Initialize the caches. Enable both Instruction and Data Caches. */
    status = CyU3PDeviceCacheControl (CyTrue, CyTrue, CyTrue);
    if (status != CY_U3P_SUCCESS)
    {
        goto handle_fatal_error;
    }

    /* Configure the IO matrix for the device. On the FX3 DVK board,
     * the COM port is connected to the IO(53:56). This means that
     * either DQ32 mode should be selected or lppMode should be set
     * to UART_ONLY. Here we are choosing UART_ONLY configuration. */
    CyU3PMemSet ((uint8_t *)&io_cfg, 0, sizeof(io_cfg));
    io_cfg.isDQ32Bit = CyFalse;
    io_cfg.useUart   = CyTrue;
    io_cfg.useI2C    = CyFalse;
    io_cfg.useI2S    = CyFalse;
    io_cfg.useSpi    = CyFalse;
    io_cfg.lppMode   = CY_U3P_IO_MATRIX_LPP_UART_ONLY;
    io_cfg.gpioSimpleEn[0]  = 0;
    io_cfg.gpioSimpleEn[1]  = 0;
    /* GPIOs 50, 51 and 52 are used as complex GPIO. */
    io_cfg.gpioComplexEn[0] = 0;
    io_cfg.gpioComplexEn[1] = 0x001C0000;
    status = CyU3PDeviceConfigureIOMatrix (&io_cfg);
    if (status != CY_U3P_SUCCESS)
    {
        goto handle_fatal_error;
    }

    /* This is a non returnable call for initializing the RTOS kernel */
    CyU3PKernelEntry ();

    /* Dummy return to make the compiler happy */
    return 0;

handle_fatal_error:
    /* Cannot recover from this error. */
    while (1);
}

/* [ ] */
 

Hello guys,

I am very new with USB Technology and I have been reading a lot about this from the manuals provided from cypress and also I have been following the forums.

I have read from the programmers manual that

"

A socket of a peripheral can be configured to either write to or read from buffers, not both. As a

convention, sockets used to write into system buffers are called 'Producers' " Does this mean that the data written over the socket  by an external processor(FPGA OR IMAGE SENSOR) so this socket is called a producer. But in the api libraries all the sockets and endpoints which are coming out I mean the data from (USB device to EXternal device) is called as producers. Please correct me if I am wrong

 Hi

I will going to make slave fifo sync mode of fx3.

Then i check FX3APIGuide.pdf in sdk. 

But i cannot any description of slavefifo sync mode. 

So  where can i find decription document? I mean that description is dscr member and firmware functions. 

The eeprom used on FX3 DVK is 24LC256, which is only 32KB, however, I found that even the minimum .img file size is over 120KB!! Is there a way to minimize the .img file size? If no, why Cypress used 24LC256 on the DVK board??

Hi Everybody

I search a way to put the SPI pins in high impedance mode. Does the function CyU3PSpiDeInit() put all SPI pins of the FX3 in high impedance mode or is there another way to do that?

Thank you

Chris

 Hi,

I am trying hard to understand the difference in the behavior between the bulk auto demo and one app where I set an auto dma between the uart rx and USB EP IN.

In the bulk auto demo, the bytes will be looped back onto the EP IN, no mather how few of them. No need to fill the DMA buffer before hitting the transfer data-IN button. There will be as many as sent, no padding (looked with some analyzer).

In the example I build, there is no way to get any bytes out of the EP before the DMA buffer is full. This seems to be the normal behavior when reading the doc, but I can not explain why the bulk loopback demo "seems" to be different.

My application is a simple DMA AUTO channel between UART (producer) and EP1 (consumer), 16-byte twin buffers (the smallest), infinite transfer, etc.

Any rational explanation for this behavior?

Thx for any help,

Martin