USB low-full-high speed peripherals Forum Discussions
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E4%BD%8E%E5%99%AA%E5%A3%B0%E6%94%BE%E5%A4%A7%E5%99%A8/BF776%E4%B8%8EBFP760%E6%9C%AC%E8%B4%A8%E5%8C%BA%E5%88%AB/td-p/732149
Show LessHi, Support.
I obtained a file named "files for command line utility.zip " from the forum, which includes a method for generating firmware and programming for CY7C65211. In the Decryption Utility directory, using the tool provided, I managed to generate default_CY7C65213-32LTXI_decrypted.cyusbd
from default_CY7C65213-32LTXI.cyusb
.However, after programming this firmware into the CY7C65211 device under Linux, the device can no longer be recognized by Linux.
My goal is to enable USB to SPI functionality support on the CY7C65211 chip. I am unable to generate the corresponding firmware version on Windows in my current situation. Could you provide me with a .cyusb
file that supports USB to SPI functionality for the CY7C65211 chip? Thank you very much.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E4%BD%8E%E9%80%9F-%E5%85%A8%E9%80%9F-%E9%AB%98%E9%80%9F-USB-%E5%A4%96%E8%AE%BE/CY7C65211-Generate-Firmware/td-p/734070
Show LessHi! Just wanted to let people know about a new tool that I have released for CY7C652xx serial bridge devices: the cy_serial_bridge Python package. I developed this package for a project that requires some advanced features of the CY7C65211 chip: namely, being able to switch it between SPI/UART/I2C mode at runtime rather than having to provision it manually via the configuration utility.
To that end, this driver package implements a new system which can dynamically read the configuration out of the chip, edit it to change the device type (and other settings too), and then write it back. This finally lets the CY7C65211 fulfill its full promise of being a multi-interface I2C/SPI/UART bridge rather than just being locked into one mode until manually changed.
This driver also implements a number of other useful features with the configuration, such as being able to edit the VID, PID, and serial number from the command line (even on Linux/Mac where the standard configuration utility isn't supported). I suspect that this could be very useful for those looking to provision CY7C652xx devices on a production line.
Besides configuration editing, this driver has a number of other useful features. I have converted the majority of the CY7C652xx libusb-based driver into Python, and reimplemented things like SPI and I2C transfers with what I hope is an easier to use and better documented API. So, you should be able to use cy_serial_bridge for controlling CY7C652xx devices from a Python application, where previously you would have had to use the Cypress DLL directly. Additionally, cy_serial_bridge provides the cy_serial_cli tool which can be used to scan for devices and do basic operations with them directly from the command line.
All in all, I really hope that people will find this driver useful and that it enables stuff to be done with the CY7C652xx devices that hasn't been done before! The package is installable through pip (pip install cy_serial_bridge) and documentation can be seen here: https://pypi.org/project/cy-serial-bridge/
Please let me know if you have any questions or issues! Also, I'd be very interested in PRs to add support for the dual channel devices -- I don't have one so I can't currently test with one.
Show LessWe built a hardware packet sniffer as an add-on for the FX2LP boards that are sold on ebay, AliExpress and similar sites.
I can answer technical questions here. Other info is on www.bugblat.com/products/ezsniff/
Show LessI am currently using the c65215 on the CyUSB3Kit-003 to access the FX3, but have some questions regarding reset control:
The JTAG interface provides vendor commands for Read/Write/Enable and Disable. Does any of these affect the state of TRST#/pin 9?
Also, I would like to wire GPIO_15 (pin 10) to the RESET# line of the FX3, to be able to control reset from the C65215. This would allow better integration with OpenOCD which somewhat requires control of both SRST and TRST for reliable startup. Currently, I have to emulate a "reset halt" by keeping the Reset button pressed and entering a halt at the prompt.
AFAICS it should be possible to control the GPIO from openocd (given the right vendor requests are added to the openjtag driver).
Show LessHi all,
I have used CY7C68013A-56LTXI (industrial version) as USB 2.0 controller.
I will check this controller chip for automotive.
If CY7C68013A-56LTXI could not be used for automotive,
I want to know which chip can.
Regards, thank you.
Kim
Hi,
I had downloaded Cypress SuiteUSB but had to uninstall it. When I tried to install it again, it throws up an error (screenshot is attached). This is an important aspect of my project so please help. Thank You.
Show LessHi,
I'm interested in evaluating the FX2LP18 USB controller in an upcoming low-power embedded design and I would like to purchase the CY3687 Developers Kit. However, according to the Cypress Website (http://www.cypress.com/documentation/development-kitsboards/cy3687-mobl-usb-fx2lp18-development-kit) this kit is out of stock and the only distributor that seems to carry this development kit (Avnet) also does not have it in stock.
Is the CY3687 Development Kit still available for purchase? If so, what is the current lead-time for this kit and where can it be purchased?
Is the MoBL-USB FX2LP18 controller still supported and recommended for new dessigns or would the FX2LP be a better choice for a low-power embedded design since the development kits for this part (CY3684) appears to be widely available from multiple distributors and directly from Cypress? Since this is a low-power design I would prefer the FX2LP18 since the core operates at 1.8 V vs. 3.3 V for the FX2LP.
As another possible alternative, since the new design will only be connecting to a USB 2.0 host, is it possible that the FX3 would consume less power than the FX2LP / FX2LP18 when connected to a USB 2.0 host?
Any feedback would be appreciated. I look forward to your response.
- Brad
Show LessHi all,
Apologies if I've selected the wrong forum; it wasn't clear to me where questions regarding CCGx USB-C devices should go. I am attempting to build a proof of concept for a simple DisplayPort pass-through using the CYPD3120 DP Dongle example firmware. So far all I have is a blinking LED and billboard info showing the vendor/product ID. I am also able to read the configuration using EZ-PD Configuration Utility.
What exactly is needed to prompt a HPD event? My understanding in reviewing the example is that this is done using events transmitted on the CC line. But I see nothing that calls eval_app_alt_hw_cmd, which appears to be the driver for the generation of the HPD events. Is there any way to prompt the HPD event/message programmatically?
I also have a DDI (an I2C slave device ready to provide an EDID on the correct address) connected to the AUX_P/AUX_N lines on the CYPD3120, but I have not been able to get the Mac to interpret the dongle as a display.
Has anyone been able to successfully prototype using the CYPD3120? Any pointers?
Thanks!
Show Less