USB low-full-high speed peripherals Forum Discussions

I'm going off of these two examples:

Interfacing FX2LP™ with Image Sensor – KBA95736

USB2.0 Camera Interface Using FX2LP™ and Lattice CrossLink FPGA - KBA222479

I have the DVK installed. When I try to program either small EEPROM or 64kb EEPROM with the example *.iic file, using USB Control Center, I get a message after a few seconds that it failed. Programming the RAM works though.

The board I'm using is the super-common "WINGONEER EZ-USB FX2LP CY7C68013A USB Development Board Core Board Logic Analyzer". You take the jumper off and the board is recognized correctly as a "Cypress FX2LP No EEPROM Device". The EEPROM on the board is a 16kB I2C EEPROM: Atmel AT24C128A, according to https://sigrok.org/wiki/Lcsoft_Mini_Board

Anyway, my *guess* as to why the EEPROM programming fails is because the EEPROM that is on this board is a different size to what "USB Control Center" expects. If you agree that my guess is correct, what else can be used to program it?

Dear

I have a question about CY7C65211 Datasheet, Table 14 Serial Communication Block Configuration
Document Number: 001-82042 Rev. *J
http://www.cypress.com/file/139886/download

Question1:
Could you tell me the state all SCB pin while reset(nXRES=low) device?
I expect state Hi-Z at all SCB pin.
　　note:all SCB pin = pin1, 2, 20, 21, 22 and 23

Question2:
The Table 14 of the datasheet says as follows:
>> *Note: The device is configured in Mode 0 as the default. Other modes can be configured using the configuration utility provided by Cypress.

Please notify let me know if you know in a method other than using the configuration utility, about set other modes.
I am ok, if method don't exist about it.

The CY7C65211 allows to configure two GPIOs as TXLED# and RXLED#. According to the datasheet

• TXLED# Drives LED during USB transmit,
• RXLED# Drives LED during USB receive.

In its default configuration (according to the USB config tool) TXLED# is GPIO_0 (pin 18) and RXLED# is GPIO_1 (pin 19).

In a test it turns out that TXLED# and RXLED# are always on, even when USB is plugged into a dumb power bank, i.e. there certainly is not data on the data lines. That's not quite what I expected.

When I switch to I2C I see is that TXLED# and RXLED# is always on until some communication occurs - then RXLED# turns off and stays off.

What is the meaning of all this? There is no relation between a presumed TXLED#/ RXLED# status and the GPIO value.

(By the way, in the schematic of the CY8CKIT-049-42XX the headers are labeled J4,5,6 whereas the silk screen of the board says J5,6,7. @cypress Please fix.)

hi I have a problem with cannot find a driver with my usb which is controll a turntable and probes.

i had search "Software and Drivers" this page but still can't find a suitable driver.

my computer system is Win10.

(i already had WinXP driver but it can't work on Win10)

The pitcures are the details about my usb.

Hello,

In order to use the CYPRESS product, CYUSB 3. SYS driver can be used as a commercial base by modifying CYUSB.inf?  

If possible, where is the text?

Hi,

Please give me advises for the below queries.

1.

As description in datasheet, I understand that CY7C65211 can operate as SPI master but need to modify the configuration settings. Is my understanding correct?

2.

If #1 is yes, to modify the configurations, could you tell me appropriate technical information or any document? I could not find related specifications in datasheet.

3.

In my understanding, user will able to use the configuration utility S/W for the evaluation. But I think this tool is not appropriate for the manufacturing phase.

So, could you tell me suitable method or tool for programming the configuration data to device flash in manufacturing phase?

I'd like to understand that programming equipment, HW designs, whether Cypress can ship devices after programming (like CP parts) and so on.

If you need more information, please let me know.

Best regards,

Shohei

Starting Stage  USB Detecting on Device Manager

Select the *.hex File

After Flash the .hex File USB Device not Detecting

hi,

-I use the 68013a chip。To bulid a project ，I use the USBJmpTB.obj（size of 3kB） from the example project---bulkloop in my  uvision project,and it operates normally。

However，I exchange the USBJmpTB.obj  with the USBJmpTB.a51 in the example project(from AN78446_Interrupt_Handling_in_EZ-USB prj),and I buiasdfld the project.The

project   normally generates the   (prj name).hex file and the USBJmpTB.obj file(but its size is 2kB)。This new project can operates Its Endpoint normally，but it can‘’t operate some of 68013a‘s  IO，such as IOA---PA.0 ...

I wonder what's wrong with that.     I don't understand!!!  :the  Jmp Table should only have effect on the interruput,but it is normal. And It indeed has infuence on the IO??

Hello,

I use latest version of cyusbserial.dll downloaded from http://www.cypress.com/documentation/software-and-drivers/usb-serial-software-development-kit

My currently working setup is Win10 x64 and 2 versions of cyusbserial.dll

Selected is I2C communication.

Writing and reading works!

Logic analyzer

BUG:
Reading function CyI2cRead() reads more bytes than desired.

With latest library it reads 8+desired (example. when I want to read 1 byte, it reads 9 bytes)

See attached .zip file for contents.

DIFF:
There seems to be the difference between library versions. Older library reads 2 bytes when reading 1byte

INFO:

For further explanation I am more than happy to elaborate.

Kind regards,

Ziga

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

i know Linux implementation is Open Source.

Don't have working Linux setup, so I don't have time to debug *.so what is going wrong.