USB low-full-high speed peripherals Forum Discussions

Cypress recently introduced a new family of USB parts. The first part in our USB-Serial family is the USB-UART Bridge controller. This is a fully integrated controller that allows connectivity to devices with a UART interface. The device includes a USB 2.0 Full-Speed Controller, Voltage Regulator and internal EEPROM in a 28-pin SSOP package. These features make the product ideal for upgrading legacy peripherals to USB interface.

For more information, please visit www.cypress.com/

Thanks,

Anup

Hi,

I am working on slave FIFO intereface for FX2LP usb controller.  I am configuring the FIFO in auto mode. 

Once the master gives the 8bit data to the slave FIFO bus (FD0-FD7), I am expecting the data to be commited to the USB endpoint buffer with the following code segment : 

I am using EP2 as bulk in endpoint and I am disabling all other endpoints

SYNCDELAY;                    // 

EP2CFG = 0xE0;                // bulk endpoint and quad buffering

SYNCDELAY;                    //

EP6CFG &= 0x7F;          //clear valid bit 

SYNCDELAY;

EP4CFG &= 0x7F;                // clear valid bit

SYNCDELAY;                    // 

EP8CFG &= 0x7F;                // clear valid bit

SYNCDELAY;

FIFORESET = 0x80;             // activate NAK-ALL to avoid race conditions

SYNCDELAY;                    // see TRM section 15.14

FIFORESET = 0x02;             // reset, FIFO 2

SYNCDELAY;                    // 

FIFORESET = 0x04;             // reset, FIFO 4

SYNCDELAY;                    // 

FIFORESET = 0x06;             // reset, FIFO 6

SYNCDELAY;                    // 

FIFORESET = 0x08;             // reset, FIFO 8

SYNCDELAY;                    // 

FIFORESET = 0x00;             // deactivate NAK-ALL

SYNCDELAY;                    // 

EP2FIFOCFG = 0x08;            // AUTOIN=1, WORDWIDE=0

SYNCDELAY;                    // 

I just finished converting a working bulk design to use an isochronous endpoint and I think I may be misunderstanding what CCyIsoPktInfo.Length is trying to tell me.  Here's what I am observing:

1)  I fill my data buffer with a magic pattern before reading into it (host side--IN transfer).
2)  I read data from the isochronous endpoint using beginDataXfer / WaitForXfer / FinishDataXfer.  The endpoint is configured for 3 1K transfers per microframe. 
3)  All of the calls return success.  The bus analyzer indicates that all of the data was transmitted.  I iterate over the CCyIsoPktInfo structures to see how much of my data came through as expected.  A cleaned up code snippet:

int packets;
CCyIsocEndPoint *ep = ... // this is my endpoint
CCyIsoPktInfo *pktInfos = ep->CreatePktInfos(l, packets);
memset(pktInfos, 0, sizeof(CCyIsoPktInfo) * packets);

ret = ep ->FinishDataXfer(buf, l, c->Overlapped(), c->m_ptr, pktInfos);
for(int i = 0; i < packets; i++)
{
    if(pktInfos.Status != 0)
        break;       
               
    len += pktInfos.Length;
}
delete [] pktInfos;

At this point, I expect "len" to contain the length of data successfully sent through up to the first dropped packet (if there are any).  However, if I iterate over the first "len" bytes of the buffer, I find "holes" in the buffer where the original magic pattern still exists.  The holes always begin and end on 1K boundaries. 

I expected to see the CCyIsoPktInfo status return nonzero any time data wasn't copied into my buffer.  Am I doing something obviously wrong with the SDK or should I look elsewhere in my code for the bug?

Thanks!

Hi,

I am looking for doc on the vendor specific commands (0x40) that work with alternate interfaces. I believe they are 0x33, 0x35 and 0x36.

Our firmware has some alternate interfaces defined to reserve bandwidth and I need to set them to simulate inadequate bandwidth to test our device's driver.

I have the EZ USB TRM, but I don't see a list of the commands and their calling packet?

Thanks

We have used the 68013A 56pins in a design and are having problems to get it to work. I am now working on the CY6384 to try to understand how to use this circuit. Unfortunately the examples included in the documentation does not give much help. I find it hard to believe that looping data from one endpoint back to another endpoint inside the chip is a typical application for anyone. 

Does anybody know of some examples that read og write data from endpoint to ports?

Our application is quite simple. We have two 16 bits ADCs multiplexed to port B and D. When output are ready from the ADC we read the port and put the data in the endpoint fifo. The plan was to used Endpoint 2 and 6, the configuration 9 in figure 1.17 in TRM. From the Users Guide this should be an easy task, the only thing we would need to do is to write the TD_Init and TD_Poll to initialize the ports and registers. In the TD_Poll we check the Output Ready from the ADC connected to RDY0, and read the port. Any examples doing something like this?

Best regards

 Hi, 

I am working on Cy7C68013A-56pin cypress USB controller. I am not using a development board, instead made a custom design for my own application. Later, I read somewhere that 56-pin doesn't support debugging. Is that right. ? Is there any way that I can do any USB based debugging on  Cy7C68013A-56pin cypress USB controller. ? Or, should I use a 100-pin  Cy7C68013A cypress USB controller for debugging purpose ? 

I am using uvision keil IDE. 

Hi,

I am working on Cypress usb high speed controller Cy7c68013A. I need to interface I2C lines with a I2C slave device (a cmos camera sensor). The example code for I2C read uses EZUSB_ReadI2C from EZUSB  library. 

My cmos camera slave address is 0x60 and the device ID is present in the sub address 0x1D. Here is the sequence I implemeted to read the device ID in a linux based system. 

1. i2c_start()

2. i2c_write_byte(0x60)

3. i2c_ack()

4. i2c_write_byte(0x1D)

5. i2c_ack()

6. i2c_write_byte(0x61)

7. i2c_ack()

8. value = i2c_read_byte ()

The variable value gives the device ID. How can I implement this sequence with a EZUSB library ? 

Thank You

Hi,

I'm using this uC to control a RS232 port. I enabled the interrupt

and I can read a received payload of 3 bytes by a vendor command and an interrupt routine.

I have problem when I try to write because I suppose the interrupt routine is triggered, something goes wrong and the 

uC won't answer. Could you help me?

How do I manage the writing operation skipping the interrupt?

This in the TD_Init:

 CPUCS = ((CPUCS & ~bmCLKSPD) | bmCLKSPD1) ; //Setting up the clock frequency

SYNCDELAY;

 T2CON = 0x34 ;

RCAP2H  = 0xFF ;

RCAP2L = 0xD9;

SCON0 = 0x5A ;

 Cont=0;

IE|= bmBIT4;

The interrupt routine:

#include "fx2.h"

#include "fx2regs.h"

#include "fx2sdly.h"            // SYNCDELAY macro

extern BYTE Cont;

extern BYTE rbuf[10];

void IRS_USART0(void) interrupt 4

{

if (RI != 0)

  {

  RI = 0;

  *(rbuf+Cont)=SBUF0;

  Cont++;

  if(Cont==3)

  Cont=0;

 }

else if(TI!=0)

     TI=0;

}

while (TI == 0) ;

TI = 0 ;

SBUF0 = ch ;

break;