Hello

The customer  is going to use the ControlCentor for FX2LP program writing, but The HOST PC is winodws10 x64.Is it possible to use the following Control Centor of SuiteUSB 3.4  for Windows10 x64?

https://www.cypress.com/documentation/software-and-drivers/suiteusb-34-usb-development-tools-visual-studio

Best Regards

MACNICA/Arai

Hi all,

Could you tell me where to find the drivers and application of CE95393.

My kit is CYCKIT-059(CY8C5888LTI-LP097).

Thanks

Boone

FIgure 2 of AN61345 shows this diagram, which indicates that IFCLK is generated by the FPGA and fed to the FX2LP component:

In the context of Slave FIFO mode, is it also valid to generate the IFCLK within the Cypress FX2LP chip, feed it through the FX2LP's output buffer, and use it directly in the FPGA for the synchronous state machine? Are there any timing considerations I'm not aware of? This seems straightforward enough to me.

Thank you!

If I open the USB Serial COM port in my terminal program and disconnect the USB, the USB Serial Port device will remain in the Windows Device Manager and the terminal program will not have any indication that the device is disconnected.  If I close the terminal program, then the USB Serial Port is removed from Device Manager.  This only happens with the Cypress driver.  I am using version 3.13.0.59.  If I change the VID to some unrecognized value in Windows and let it load the default Windows driver, I don't see this problem.  Once I disconnect USB, the port is gone from Device Manager and my terminal program shows an error.  I am using Windows 10 64-bit.  Does anyone know why this happens?  I prefer the behavior of the Windows driver.  Can I change something on the CYUSBS234 config or Cypress driver to make it behave like the Windows driver?

I am using a CY7C65215A as a USB - I2C bridge acting as the I2C master. If I power my system on without USB connected to the 215A, the 215A holds my I2C lines low.

After I connect USB to the 215A, I see some activity on the I2C lines for a few seconds (driven by 215A), and then it lets go of the lines and they are pulled high. After the lines are pulled high, I can disconnect the USB from the system and the I2C lines are still inactive (pulled high).

Any thoughts on why this is happening?

See my schematic below. There are 2 I2C slave devices: an FPGA and a TCA9406 I2C level shifter, and has a 10k ohm pullup resistor.

I have built a small evaluation board with the same configuration on the 215A and I2C pullups, but no I2C slave on the bus, and the 215A exhibits the same behavior.

Hi all,

I have two boards with CY7C68013A which fail to enumerate. When I attach the boards to USB on the PC I can not see

Bus 001 Device 003: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 EZ-USB FX2 USB 2.0 Development Kit

when running lsusb command on Linux.

In the dmesg I only see:

[root@ftrn-test-box chamber_test]# dmesg --follow

[22130.828634] usb 2-1.7: new full-speed USB device number 52 using ehci-pci

[22130.902630] usb 2-1.7: device descriptor read/64, error -32

[22131.077608] usb 2-1.7: device descriptor read/64, error -32

[22131.251608] usb 2-1.7: new full-speed USB device number 53 using ehci-pci

[22131.325604] usb 2-1.7: device descriptor read/64, error -32

[22131.500553] usb 2-1.7: device descriptor read/64, error -32

[22131.674549] usb 2-1.7: new full-speed USB device number 54 using ehci-pci

[22132.076527] usb 2-1.7: device not accepting address 54, error -32

[22132.149534] usb 2-1.7: new full-speed USB device number 55 using ehci-pci

[22132.551505] usb 2-1.7: device not accepting address 55, error -32

[22132.551630] usb 2-1-port7: unable to enumerate USB device

I see this response when I connect the board with USB cable or when I reset Cypress (once the board is connected via USB).

And it makes no difference if I2C EEPROM is connected or not.

Thing here is that that up until previous week I had no such issue with many boards in the past three years. Usually only one board would be connected to the PC, maybe two when test were done.

But I need to test many boards and for that I would like to connect 8-10 boards to one PC via USB hub.

Therefore I tried to connect 8 boards using two USB hubs. And after that inital test two boards fail to enumerate.

My questions are:

1. Could USB hub damage Cypress IC in a way that it would not enumerate even with default Cypress IDs?

2. Is there a way to restore IC back to factory settings?

Thanks!

Schematic (page 7, bottom left):

https://www.ohwr.org/projects/tr-pmc/repository/revisions/master/entry/PMC_REVB/FTRN_PMC_REVB_SCH/ftrn_pmc_revb.pdf

USB micro sources:

https://www.ohwr.org/projects/etherbone-core/repository/hdl/eb_usb_core?utf8=%E2%9C%93&rev=ba955bc&branch=master&tag=

Essentialy USB micro is erased by:

fxload -D "$dev" -tfx2lp -I erase_eeprom.ihx -v

and then flashed by

fxload -D "$dev" -tfx2lp -I cdc_acm.ihx -s vend_ax.hex -c 0x41 -v

I am using a CY7C65215A as a USB - I2C bridge acting as the I2C master. If I power my system on without USB connected to the 215A, the 215A holds my I2C lines low.

After I connect USB to the 215A, I see some activity on the I2C lines for a few seconds (driven by 215A), and then it lets go of the lines and they are pulled high. After the lines are pulled high, I can disconnect the USB from the system and the I2C lines are still inactive (pulled high).

Any thoughts on why this is happening?

In the document at table 3 there is a note [3] saying "Unused port DD+/DD– lines can be left floating. Leave the port power, amber, and green LED pins unconnected, and deassert the overcurrent pin. Do not leave the overcurrent pin floating; it is an input."

The OVR pin can have different polarity depending on the setting in EEPROM. Default is active low.

Question: Is there a difference in power consumption whether OVR active low and pulled up to VCC or OVR active high pulled to GND?

ハードウェアの接続はCY4615Bと同じで、Manufacturing Software のBLASTERにから

アドレス0x42,0x43と、0x49,0x4aをhigh-speedの0x0200に変えたのですが

転送速度がfull-speedのままです。

どうしたらhigh-speedになるでしょうか？

よろしくお願いいたします。