USB superspeed peripherals Forum Discussions

Hi,

I have a CX3 custom board and I try to program it via Linux using cyusb_linux.

I can see the device VID (04b4) and PID (00f3) but when trying to program the SPI I get "SPI sector erase failed: error.

Using Control Center using Windows works perfect on the same board.

Any ideas how to solve that issue?

Thanks,

Itay

Hello, I am using Streamer to test the read and write speed of USB. I have tested using two firmware versions (cyfxisosrcsink and cyfxisolpauto), and the speed is as follows. I have two questions

1. Why is there a significant difference in the USB speed between the two firmware.

2. For cyfxisosrcsink, its USB 2.0 speed reaches 192000KBps, which translates to over 100 MB/s, which does not match the actual 2.0 speed. May I ask if there is a problem with my understanding or if there are other misunderstandings

Thanks.

I bought a printer from China and the manufacture give me the driver of intel version (I think so, because its driver pack include .sys, .inf, .cat files and  they are only suitable for win 7/8/10, whenever I connect printer and try to choose "update driver" in "device manager" the windows says that they can not look the driver)

I think there is someone have been my shoes, so please help me if is there a version for ARM?

or is there a way that convert the driver to arm?

Thank you

Hi, I want to use FX3 SPI to program SPI Flash.

Read page seemed to be OK by CyU3PSpiReceiveWords function.

As I program 10 pages(256bytes per page) by CyU3PSpiTransmitWords API, I find randomly lost 3 bytes data at tail of page by capturing SPI signals with LA.

So... Is there any restrictions of CyU3PSpiTransmitWords  functions? Or just I cannot over 256 bytes in one write?

It all started with first LED Blinky for my FX3 explorer kit. The boot_fw was more elegant and readable than the recommended CyFx3 lib based Blinky and that was how the association started. Then went on to use the gpif example and was thrilled to hit near 400MB/s.

The time had come to build our firmware. Whether to take the bloated CyFx3 lib or the light weight boot_fw? The official recommendation was CyFx3 as it is multi threaded and has more features. As a hardware engineer, I was really sceptic about multi-thread. And it was also funny. A single core processor benefitting from a multithread capable OS!!

Went with boot_fw and built feature upon feature. Some key takeaways are 8 bit GPIF for FPGA configuration (wow never seen FPGA configured so fast) and 32bit GPIF for application streaming near 400MB/s in master mode with two GPIF threads and just a single tick gap between them. On top of it GPIF Ingress and Egress over control endpoint. Then some RS232 communications.

boot_fw never left me down during development. There were some missing functions. But so what. You could do a direct register access. Also, never faced any reliability issues.

So why is the boot_fw not that recommended. Really don't know.

But I can vouch that better performing systems with lower code size and more readable code can be built with boot_fw. 

May be some applications have a lengthy call, or they have to wait on a flag for too long. But such things can be easily from  handled from the main loop, without going for a bloated OS.

Finally, need more recommendation for boot_fw and definitely more examples.

Ravi

Could anyone point me to an example of how to define more than 31 controls on an extension unit descriptor?

I believe a second extension unit is required for that.

I tried adding it in the following way, but it did not work.

    /* Processing Unit Descriptor */
    0x0D,                               /* Descriptor size */
    CX3_CS_INTRFC_DESCR,                /* Class specific interface desc type */
    0x05,                               /* Processing Unit Descriptor type: VC_PROCESSING_UNIT*/
    0x02,                               /* ID of this unit */
    0x01,                               /* Source ID: 1: Connected to input terminal */
    0x00, 0x40,                         /* Digital multiplier */
    0x03,                               /* Size of controls field for this terminal: 3 bytes */
                                        /* A bit set to 1 indicates that the mentioned */
                   						/* Control is supported for the video stream. */
    0b0111'1111,						/* D0: Brightness
                                         * D1: Contrast
                                         * D2: Hue
                                         * D3: Saturation
                                         * D4: Sharpness
                                         * D5: Gamma
                                         * D6: White Balance Temperature 
                                         * D7: White Balance Component */

    0b0001'0011,                        /* D8: Backlight Compensation
                                         * D9: Gain
                                         * D10: Power Line Frequency
                                         * D11: Hue, Auto
                                         * D12: White Balance Temperature, Auto
                                         * D13: White Balance Component, Auto
                                         * D14: Digital Multiplier
                                         * D15: Digital Multiplier Limit */

    0b0000'0000,                         /* D16: Analog Video Standard 
                                         * D17: Analog Video Lock Status
                                         * D18..(n*8-1): Reserved. Set to zero */
    0x00,                               /* String desc index: Not used */
    0x00,                               /* Analog Video Standards Supported: None */

    /* Extension Unit Descriptor */
    //0x1C,                               /* Descriptor size */
    0x1D,                               /* Descriptor size (4 control bytes) */    
    CX3_CS_INTRFC_DESCR,                /* Class specific interface desc type */
    0x06,                               /* Extension Unit Descriptor type */
    0x03,                               /* ID of this terminal */
    0x0C, 0x89, 0xB6, 0xAC,             /* GUID specific to AN75779 firmware. Obtained from Visual studio */
    0xB3, 0xA3, 0x60, 0x40,             /* static const GUID <<name>> = */
    0x8B, 0x9A, 0xDF, 0x34,             /* { 0xacb6890c, 0xa3b3, 0x4060,{0x8b, 0x9a, 0xdf, 0x34, 0xee, 0xf3, 0x9a, 0x2e} };*/
    0xEE, 0xF3, 0x9A, 0x2E,
    //0x01,                               /* Number of controls in this terminal */
    //0x1F,                               /* Number of controls in this terminal */ 1F = 31
    0x01,                               /* Number of input pins in this terminal */
    0x02,                               /* Source ID : 2 : Connected to Proc Unit */
    //0x03,                               /* Size of controls field for this terminal : 3 bytes */
    0x04,                               /* Size of controls field for this terminal : 4 bytes */
    0b1111'1111,                        /* Controls supported */
    0b1111'1111,                        /* Controls supported */
    0b1111'1111,                        /* Controls supported */
    0b0111'1111,                        /* Controls supported */
    0x00,                               /* String descriptor index : Not used */
#if true
    /* 2nd Extension Unit Descriptor */
    0x1C,                               /* Descriptor size 28 bytes*/
    CX3_CS_INTRFC_DESCR,                /* Class specific interface desc type */
    0x06,                               /* Extension Unit Descriptor type */
    0x04,                               /* ID of this terminal */    
    0xAF, 0x80, 0x74, 0x32,             /* GUID specific to AN75779 firmware. Obtained from Visual studio */
    0x25, 0x17, 0x49, 0x27,             /* static const GUID <<name>> = */
    0x9E, 0x71, 0xAB, 0x4D,             /* { 0xacb6890c, 0xa3b3, 0x4060,{0x8b, 0x9a, 0xdf, 0x34, 0xee, 0xf3, 0x9a, 0x2e} };*/
    0xD9, 0x82, 0x91, 0x95,
    0x18,                               /* Number of controls in this terminal */
    0x01,                               /* Number of input pins in this terminal */
    0x03,                               /* Source ID : 3 : Connected to Ext. Unit */
    0x03,                               /* Size of controls field for this terminal : 3 bytes */
    0b1111'1111,                        /* Controls supported */
    0b1111'1111,                        /* Controls supported */
    0b1111'1111,                        /* Controls supported */
    0x00,                               /* String descriptor index : Not used */
#endif
    /* Output Terminal Descriptor */
    0x09,                               /* Descriptor size */
    CX3_CS_INTRFC_DESCR,                /* Class specific interface desc type */
    0x03,                               /* Output Terminal Descriptor type */
    0x05,                               /* ID of this terminal */
    0x01, 0x01,                         /* USB Streaming terminal type */
    0x00,                               /* No association terminal */
    0x04,                               /* Source ID : 3 : Connected to Extn Unit */
    0x00,                               /* String desc index : Not used */

Hello, I am using cyusb3014 chip, now I want to test the usb read and write speed through soft, but the speed I got has not been ideal, limited to 30MB/s, the following is my test logic, I want to know if I have a better way to send data, thank you.

I call the usb_write API multiple times, timing before and after the call.