USB low-full-high speed peripherals Forum Discussions

Hi,

I have an Bulk IN endpoint with Auto-IN enabled that is constantly filled with data from the external master.

After a pause in data transfer I might want to discard the presumably old content of the endpoint buffers before I continue with the new transfer.

What do I have to write in which registers to declare the input buffers empty so that they can accept new data from the external master?

I assume this is an easy and silly question, but I have worked overnight on my previous problem and my brains feel like two soaked loafs of old bread.

Many thanks for any help!

Hello,

Maximum 18 mA is specified as the total power consumption of Vcc and Vccio in the data sheet of CY8C65213.

I want to know the power consumption Vcc and Vccio separately.

Please teach me the power consumption each power-pin.

Thanks,

Shimamura

Hi,

I tried to activate GPIO pins on PortA but to no avail.

My minimalistic firmware is this:

IFCONFIG = 0x03;

SYNCDELAY;

REVCTL = 0x03;

SYNCDELAY;

EP6CFG = 0xE0;

SYNCDELAY;

FIFORESET = 0x80;

SYNCDELAY;

FIFORESET = 0x86;

SYNCDELAY;

FIFORESET = 0x00;

SYNCDELAY;

EP6FIFOCFG = 0x0C;

SYNCDELAY;

PINFLAGSAB = 0x00;

SYNCDELAY;

while (1) {}

Now I want to activate PA1 and PA3 as GPIO outputs and inserted this before the while (1) {}:

OEA=0x0A;

SYNCDELAY;

CLR IOA.1

SYNCDELAY;

CLR IOA.3

SYNCDELAY;

I know, syncdelay is not really required here, but it should not do any harm.

The PA1 and PA3 pins are pulled to VCC by 22kOhm resistors and they stay high despite the GPIO pins being enabled as outputs (0x0A to OEA at SFR 0xB2) and cleared by the CLR commands.

Even if I write 0x00 to 0xB0, which should also set the output pins low, they stay at 3.3V.

What am I doing wrong?

API for the GPIO (CyGetGpioValue()/CySetGpioValue()) does not allow us to change the direction/drive of the GPIO pins on CY7C65211. In our system we may have a number of this USB-I2C bridge device and we want to be able to configure the GPIO direction/configuration individually on each of these bridge devices at least at system initialization. Is it possible achieve this with CY7C65211?

I see that you recommend to use the configuration utility to do so; in other posts. Do you have a Linux utility to do so? Even if there is one, it will be difficult to call it form our application. Can you please add APIs for this purpose?

Hi,

From this discussion FLAGC set to not empty after TD_Init , using the same firmware.

I have a problem with this firmware, reading from EP6 (from external master), greater than 1024 cause the last buffer data to be zero.

Let's say, I need 1050 number of data to read, the first 1024 is okay, but the next data is zero.

Please be inform that external master sends PKTEND.

Thank you for your support.

Best regards,

Livie

Hi,

I tried to build the Streamer example application from the USB Suite 3.4.7 with VS 2017 Community, but I get a lot of errors.

It does not recognize the System::Windows namespaces, expects or misses tons of declarations and so on.

Can anyone point me to a walk through guide for building these examples with VS 2017 Community?

I don't know if they are buildable with any other VS version, because I only have that one.

Thanks in advance

I only use  CY7C63813，didn't  have  SPI chip.Move the track ball.Light pulses into the CY7C63813 by IO pin.

The direction of the motion is calculated by different pulses.The  difficult is  how to calculate the distance???

Hi,

I want to use Slave FIFO Mode.

In this setup, I want to utilize all End Point (2,4,6,8).

EP2 & EP4 is AUTOOUT=1 while EP6 & EP8 is AUTOIN=0.

I set PINFLAGSAB = 0, and PINFLAGSCD = 0, so that all FIFO flags are indexed as pointed by FIFOADR[1:0]

My problem is after initialization of the firmware.

FLAGB is set to LOW

FLAGC is set to HIGH, therefore I cannot write to EP2, if selected by FIFOADR[1:0]. Why?

and at Vendor Command  returning EP2468STAT value is 0x5A.

that is: EP8E,EP6E & EP4F, EP2F.

Why EP4F and EP2F at initialization?

(I attached my code)

Thank you for your help.

When configured as USB-I2C bridge, there are 3 endpoints on CY7C65211. Please see below. Is it possible to get rid of Interrupt end-point? We are connecting a number of these devices to an xhci controller and we want to keep the number of endpoints to a minimum, since we don't want to run into resource constraints in the controller.

root@lsys:~# lsusb | grep -i cypress

Bus 001 Device 005: ID 04b4:000a Cypress Semiconductor Corp.

root@ls1043ardb:~#

root@ls1043ardb:~# lsusb -v -s 1:5

Bus 001 Device 005: ID 04b4:000a Cypress Semiconductor Corp.

Device Descriptor:

  bLength                18

  bDescriptorType         1

  bcdUSB               2.00

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass         0

  bDeviceProtocol         0

  bMaxPacketSize0         8

  idVendor           0x04b4 Cypress Semiconductor Corp.

  idProduct          0x000a

  bcdDevice            0.00

  iManufacturer           1 Cypress Semiconductor

  iProduct                2 USB-I2C (Dual Channel)

  iSerial                 0

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                 9

    bDescriptorType         2

    wTotalLength           48

    bNumInterfaces          2

    bConfigurationValue     1

    iConfiguration          0

    bmAttributes         0x80

      (Bus Powered)

    MaxPower              100mA

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        0

      bAlternateSetting       0

      bNumEndpoints           3

      bInterfaceClass       255 Vendor Specific Class

      bInterfaceSubClass      3

      bInterfaceProtocol      0

      iInterface              0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x01  EP 1 OUT

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval               0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x82  EP 2 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval               0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x83  EP 3 IN

        bmAttributes            3

          Transfer Type            Interrupt

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval              10

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        1

      bAlternateSetting       0

      bNumEndpoints           0

      bInterfaceClass       255 Vendor Specific Class

      bInterfaceSubClass      5

      bInterfaceProtocol      0

      iInterface              0

Device Status:     0x0000

  (Bus Powered)

root@sys:~#