USB low-full-high speed peripherals Forum Discussions

 Dear Sirs

We are trying to implement a GPIF interface for a 8 Channel simultaneous sampling SAR ADC (TI ADS8568)     

The plan is to use the ADC in parallel interface mode (allow faster sampling) and stream data to a host PC via a FX2LP CY7C68013A-128.     

Although this is my first approach to USB micros, after reading some documentation available on the Cypress website, I was able to start a GPIF designer.     

The challenge appeared when trying to implement a single read, I run out of States.      

As it can be seems on the attached image (or ADS8568 datasheet) after a conversion signal the host must toggle the RD line eight times to gather the data from the 8 channel, but only 6 states are available.     

Any Ideas?     

Thanks in advance     

Hey,

When connecting up USB using the PSoC 5LP, can I leave VBUS floating if I am using self-poowered USB?  I dont need or want the VBUS connection, but I do want to communicate/debug through USB.  

I am using Cy3684 to test my code. I am writing following code to write some data on lg eeprom, but it doen't seem to work. i also tried tweaking function definition inside i2c.c provided by cypress. I am attaching my keil code here, and the edited i2c.c. I am checking SCL SDA lines using a DSO, but there is no fluctuation. Whereas when a burn iic file to lg eeprom using cyconsole i get fluctuations on SCL SDA lines.

//main code to write data to eeprom. The data is any dummy data, but it should write.

#include <fx2.h>
#include <fx2regs.h>
#include "i2c.c"

void main(void)
{

EZUSB_InitI2C();

EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x02);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x01);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x09);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x02);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x01);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x03);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x10);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x02);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x12);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x02);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x14);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x01);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0xe2);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x16);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x02);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x82);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x20);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0xd0);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0xC2);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x00);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x08);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x25);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x06);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x26);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x5B);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x27);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x9A);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x30);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x10);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x31);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x10);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x32);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x10);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x33);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x10);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x34);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x17);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x35);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x7F);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x40);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0xFF);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x41);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x7F);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x42);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x7F);EZUSB_WaitForEEPROMWrite(0xC2);

EZUSB_WriteI2C(0xC2,0x01,0x43);EZUSB_WaitForEEPROMWrite(0xC2);
EZUSB_WriteI2C(0xC2,0x01,0x7F);EZUSB_WaitForEEPROMWrite(0xC2);
}

Thanks !

 I have just purchased the CY3684 EZ-USB FX2LP Development Kit and I am trying to get the 'hid_kb' firmware example operational.

After downloading the firmware, I am unable to transfer characters from the development board to a Notepad window on the PC as described in the example text.  The device should be shown as part of the HID devices list in Device Manager (Windows 7). However, it actually appears as 'MFS100' in the Universal Serial Bus Controllers list. Could this be the problem? 

The Cypress USB Console displays the following ID codes...

VendorID: 0x04B4

ProductID: 0x1005

Manufacturer: MANTRA

Product: MFS100

hie everyOne,

I have one device having FX2LP for usb connectivity. and i have developed one code using CyUSB utility in Linux which displays the device descripotor of the device and logs it in log file.

but for this i have run the code. to get this. Actually i wanted to do like whenever i plug my device the code i have written should run automatically n logs the descriport in file.

i know this can be done with kind of daemon process i am trying  but i am not able to understand the things how to do this

please do rply i want to make it happen (i am working in linux)

Thanks & Regards

Rohan

 hello! 

I'm trying to use the synchronous Slave FIFO from the FPGA. 

FX2LP configuration is as follows: 

EP2 - AUTOIN 16bit 1k * 3x buff. 

EP8 - AUTOOUT 16bit 512b * 2x buff. 

I am sending data through CyConsole. The packet in EP8 - sent without errors (more than two packet). This means that the FIFO is emptied regularly (SLOE and SLRD - active, FIFOADDR = 11, SLCS # - not used). FlagB is configured as "empty fifo". When sending a packet - flagB changes. The packet comes in a FIFO. Then the FIFO is emptied again and FlagB changes again. 

However, I do not see any data sent on the bus FD [0-15]. 

 Instead, the bus exhibited values ​​0xFFFF. 

how to explain this situation???

P.S. FD [0-15] bus - working. I configured it as an IO-port and saw the correct values ​​on the chip legs FX2LP....