USB low-full-high speed peripherals Forum Discussions
text.format{('custom.tabs.no.results')}
Hello,
I am stuck at a point,
in my application , i use endpoint 2 as slave fifo mode and also use auto in for acquiring data from external peripheral
endpoint 2 is configured as BULK , quad buffered
here I make use of REVCTL = 0x03;
whereas i need another endpoint EP4 which i just need to configure as 16 bytes long , and just send communication from host to device using endpoint interrupt .
EP4 is configured as endpoint out , bulk and double buffered
Now the problem is being caused due to REVCTL register
The first two transactions are successful , as i arm the endpoint
But then re-arming of endpoint doesnt work inside the endpoint interrupt
why is that can someone help me out here ?
this is my code :
void TD_Init(void)
{
EP4CFG = 0xA2; // out endpoints do not come up armed,since the defaults are double buffered we must write dummy byte counts twice
SYNCDELAY;
FIFORESET = 0x80;
SYNCDELAY;
FIFORESET = 0x84;
SYNCDELAY;
FIFORESET = 0x00;
SYNCDELAY;
EP4BCL = 0x10; // arm EP4OUT by writing byte count w/skip.
SYNCDELAY;
EP4BCL = 0x10;
OEC = 0x01; // PC0 as output
EPIE |= bmBIT5 ; // Enable EP4 interrupt
/// For data acquisition
}
and the code in the endpoint interrupt
EZUSB_IRQ_CLEAR();
EPIRQ = bmBIT5;//Clears EP4 interrupt request
Hi Infineon Community,
I am reviewing the second SPI pinout interface, and I've noticed some discrepancies between various figures and tables regarding the pinout of SPI port 1.
Below, I have included a comparison table and images from Document Number 002-31604 Rev. **, as found on the CY7C65214D-32LTXI webpage.
I believe the correct pinout is shown in Figure 4, as it represents the actual pinout of the package. Furthermore, Figures 5, 6, and 7 are consistent with Figure 4.
Please confirm if my understanding is correct and make any necessary corrections to the document.
Regards,
Luis Flores
Show Less
Hi! 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 LessHello Team,
I apologize for the dumb question.
Long story short: I damaged one of my keyboard's multiplexed lines from a static shock. Upon disassembly I see that it has a CY7C64215-56LTXC microcontroller and was wondering if I can read its flash memory by using I2C and write it on a new one from Mouser using PSoC 4.
I see the PCB has a header which I'm presuming is the I2C (J1 in the attached picture).
Thank you so much for your help regarding this matter.
Respectfully,
Moycas.
Show LessHello,
I have a simple project using FX3 (CYUSB3014) and FX3 SDK 1.3.5.
I have Segger J-Link connected to the JTAG pins. Also, have a debug configuration that uses Segger J-Link GDB Server.
I see multiple errors, printed in the Console, like this:
827^error,msg="Dwarf Error: Cannot find DIE at 0x0 referenced from DIE at....
The debugger stops in main. After that, if I continue execution (Run), debugger does not respond anymore - does not stop at any breakpoint, does not allow to pause. I can only terminate the debug session.
If I change the project settings, and switch it to FX3 SDK 1.3.4 - everything works Ok.
It looks like there is something wrong with the pre-built libraries in SDK 1.3.5, as this is the only thing that really changes.
Any ideas how to get SDK 1.3.5 to work with the JTAG debugger?
Thank you,
D.
Show Less
Hi Experts,
We are using CY7C65213-32LTXIT (USB Interface IC USB-UART LP Bridge Controller) but USB detection is failed.
We are using Windows11PRO pc.
Can you share us the drivers ?
Thanks & Regards
Satrasala Raju
Show Less
Hello,
Please tell me about the pin handling of the CY7C65223-24LTXI.
When the flow control function is not used, should the RTS and CTS pins be OPEN?
Regards,
Show Less