USB low-full-high speed peripherals Forum Discussions

What is the address of I2C (SCB0) EEPROMS in CYUSBS236 USB-Serial (Dual Channel) Development Kit?

The sample code is as below.
cyI2CDataConfig.slaveAddress = 0x51;

Is it 0x51?

please answer about my question.

Access denied

Click the link below
A connection unavailable window appears.

https://www.cypress.com/file/123481/download

https://www.cypress.com/access-denied

Apologies for any inconvenience caused.

You are not authorized to access this page or it may have been removed from the site and is no longer available on Cypress.com. Please contact our webmaster support for more information.

Why?

i develope a firmware for dvb dongle using an fx2 board.

On a linux PC:

when i connect to PC USB and firmware is downloaded, strange things happen.

on the linux PC terminal  i get strange character input at random every once in a while.

Also screen resolution changes once in a while (due to strange key input).

The firmware is not functioning as it should.

On a linux LAPTOP:

plugin the dongle into my laptop, after firmware load, kernel panic.

On a raspberry pi:

it works.

This is so strange.

the firmware is processing a lot of "vendor-commands" through EP0. ?!

i am out of ideas....

I have asked the following questions in the past.
https://community.infineon.com/t5/USB-Low-Full-High-Speed/Win7-PC-does-not-recognized-CY7C65213/m-p/286786#M9839

I operated according to the KBA presented there. There was no problem with the Japanese version of Win7, but the Chinese version of Win7 did not show the COM port as shown in Figure 11.

Is KBA's solution dependent on the language version of the OS?

Thank you,
Tetsuo

Hello,

We are using the cygpio.exe script with the CY7C65215-32LTX on our boards.

Recently we have a new batch of boards and this command is failed to configure the gpio (see attached picture ''Cygpio_failed.PNG'), we compare on the same PC two boards one with old batch of devices (command succeeded) and one board with new batch (command failed).

We also tried manually using the ''USB serial configuration utility'' to configure the same gpio on both batch the gpio is working as expected.

We compare the version of both devices and its identical (see picture ''Cypress_device_configuration.png'').

The only difference we can see is the marking on the devices:

Old batch marking:
CY7C652
1532LTXI
2025 PHI
622477 C
103

New batch marking:
CY7C652
1532LTXI
2025 PHI
622477 C
311

Can you please advice what the last line at the marking refereeing to?
Can you please advice what can be the root cause for this behavior of the new batch of devices? do you have a solution?

Thank you

Best regards

Efi

Hello. I use cy7c68013a Mini Board.
I'm able to write any firmware for USB. And I have one trouble.
1) RAM UPLOAD(*.hex):
When I upload my firmware without EEPROM (hex. Directly to RAM through Cy Control utility), my device reconnects with new VID/PID and endpoint settings. Device works fine. It's OK.
2)EEPROM UPLOAD(*.i2c):
Then I convert hex to i2c, and load i2c file to EEPROM. I'm awaits that now my device will be recognized without any troubles (as it worked with RAM in step 1).. But nothing happens.  No Windows sound alert about new connection.
Main loop (thank to LEDs) is alive. But enumerates is failed. What is it?? 
What the reason of it?? I want that my device will enumerate as ordinary USB device.

Thanks.

Hello,

Can you tell me if there is a driver WIN10 for device cy7c68001

Best regards

Alain