USB low-full-high speed peripherals Forum Discussions
Hello,
We confirmed inquiries on this matter in September 2017.
https://community.cypress.com/message/142234#142234
Please tell us about current development situation and future schedule.
Best Regards,
Show LessWe started iris design using Cypress controller, we need hardware and firmware support.The schematic has been attached in community forum,please alot one Engineer for schematic review
Show LessHello,
Could you please tell me whether CY7C65213 driver supports Windows 10.
In the data sheet, Window 10 is supported. However, when I check the driver at the following site, it seems that it does not correspond yet.
http://www.cypress.com/documentation/other-resources/usb-serial-drivers
Best Regards,
Show LessI'd like to report to folks that I have successfully migrated a design that was based on SuiteUSB to the Microsoft USB stack and WinUSBNet. I will never use cypress software again if I can help it. If you move to the MS USB stack, you get a simple driver install, a USB stack that will grow with OS releases, and WinUSBNet that was developed by people that understand and love c#. SuiteUSB was not IMO.
Before the investigation, I started having problems with weird exceptions, x32/x64/any, countless updates to SuiteUSB, CyUsb, etc. It seems every release from MSFT required EVERYTHING from Cypress to be touched.
If you are starting a new project, look very, very closely at using WinUSB. I've also built some first prototypes that are running LibUSB, which is a platform independent USB library. That library uses WinUSB on the lower edge when running on Windows. And it is working under Mono. I have another project using FTD600 USB part, and I see a path to have a common library for FTDI and Cypress parts, that runs on Windows and under Mono. The holy grail would be to get running under dotnet core, because then the mono dependency goes away. But currently there's a hitch in LibUSB that seems to require Winforms. But someone will iron that out.
In short, if you are thinking about directions for a new product, the days of custom vendor software should be coming to a close. I hope. It cannot come soon enough. This update to Win10 version 1803 was very painful from a cypress USB perspective.
Show LessI have to read data from Barcode Scanner (USB type) to PIC Microcontroller. MAX3421E used as a Host. I can enable to communicate with the Barcode Scanner and Enumerated successfully. But after that, I could not able to receive data from the barcode scanner when reading the barcode label. The barcode sends good-read beep when reading barcode label. In the MAX3421E datasheet, it says it will wake the MCU when it receives data from USB Peripheral thru' RWUIRQ (Remote Wake Up) interrupt. But interrupt not fired when reading barcode label. All interrupts work fine except RWUIRQ (i.e RSMREQIRQ).
Barcode Scanner works fine with PC. But we have to open notepad or similar text editor in order to receive the Barcode Value.
What could be the problem?
I have used USB HOST SHIELD FOR ARDUINO MODULE. Because it has MAX3421E on the board.
PIC MCU VCC = +5V
MAX3421E VCC = +3.3V
BARCODE SCANNER = +5V (100mA, BUS Powered), Powered from Seperate +5V Adapter.
Your help would be highly appreciated.
thank you.
Show LessMy driver works fine in Windows XP, but fails in Win7. Window shows "This device cannot start.(code 10)".
I use CY7C68013-128AC. My computer has 2 system XP and Win7 ( 32-bit ).
Driver outputs the below result. After the driver sends SET CONFIGURATION, return from IoCallDriver
USBD is wrong (c0000001).
............
Entire Configuration Descriptor is at 86127e28, bytes txferred: 25
enter XUsb_SelectInterfaces
0000 78 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0010 28 7E 12 86 00 00 00 00 60 00 00 00 00 00 00 00
0020 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00
0030 00 00 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0040 00 00 00 00 00 00 00 00 FF FF FF FF 00 00 00 00
0050 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0070 FF FF FF FF 00 00 00 00
enter CallUSBD
Calling USB Driver Stack
XUsb_IoIncrement::3
return from IoCallDriver USBD: 0xc0000001
URB status = c0004000, status = 0, irp status = c0000001
XUsb_IoDecrement::2
exit CallUSBD (c0000001)
0000 78 00 00 00 00 40 00 C0 A8 70 D3 84 00 00 00 00
0010 28 7E 12 86 00 00 00 00 10 00 00 00 00 00 00 00
0020 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00
0030 00 00 00 00 FF FF FF FF 00 00 00 00 00 00 00 00
0040 00 00 00 00 00 00 00 00 FF FF FF FF 00 00 00 00
0050 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF
0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0070 FF FF FF FF 00 00 00 00
exit XUsb_SelectInterfaces (c0000001)
exit XUsb_ConfigureDevice (c0000001)
Firmware is very simple.
{ ...............;
case usb_SET_CONFIGURATION:
Configuration = Xbyte[aSETUPDAT+2];
break;
EP0CS |= bm7
}
I would really appreciate some hints about this issue. Thanks!
Steven
Show LessI went through the driver resell process for cyusb3 for win10, and it appears to be installing and working. Excellent, thank you. However, the modified driver package that I submitted only included our company's USB devices (VID/PIDs). I would like to also add a default Cypress VID/PID to our INF so that we can easily program new/blank boards we receive. From the CyUSB.pdf this seems perfectly fine ? I wanted to check before submitting another modified package on the microsoft hw dashboard.
Specific questions:
1. Are third parties allowed to add Cypress VID/PIDs to their driver package for resell ?
2. If I can add Cypress VID/PIDs (or if I need to add our own new VID/PID), do I need to submit this new INF to cypress or can I just upload another modified driver package to the dashboard (same as initial one)?
2.a. If I need to submit an INF to cypress first, how would I go about doing that now that technical cases are gone ?
Thanks,
Erik
Show LessHi,
I have an Bulk IN endpoint with Auto-IN enabled that is constantly filled with data from the external master.
After a pause in data transfer I might want to discard the presumably old content of the endpoint buffers before I continue with the new transfer.
What do I have to write in which registers to declare the input buffers empty so that they can accept new data from the external master?
I assume this is an easy and silly question, but I have worked overnight on my previous problem and my brains feel like two soaked loafs of old bread.
Many thanks for any help!
Show LessHello,
Maximum 18 mA is specified as the total power consumption of Vcc and Vccio in the data sheet of CY8C65213.
I want to know the power consumption Vcc and Vccio separately.
Please teach me the power consumption each power-pin.
Thanks,
Shimamura
Show LessHi,
I tried to activate GPIO pins on PortA but to no avail.
My minimalistic firmware is this:
IFCONFIG = 0x03;
SYNCDELAY;
REVCTL = 0x03;
SYNCDELAY;
EP6CFG = 0xE0;
SYNCDELAY;
FIFORESET = 0x80;
SYNCDELAY;
FIFORESET = 0x86;
SYNCDELAY;
FIFORESET = 0x00;
SYNCDELAY;
EP6FIFOCFG = 0x0C;
SYNCDELAY;
PINFLAGSAB = 0x00;
SYNCDELAY;
while (1) {}
Now I want to activate PA1 and PA3 as GPIO outputs and inserted this before the while (1) {}:
OEA=0x0A;
SYNCDELAY;
CLR IOA.1
SYNCDELAY;
CLR IOA.3
SYNCDELAY;
I know, syncdelay is not really required here, but it should not do any harm.
The PA1 and PA3 pins are pulled to VCC by 22kOhm resistors and they stay high despite the GPIO pins being enabled as outputs (0x0A to OEA at SFR 0xB2) and cleared by the CLR commands.
Even if I write 0x00 to 0xB0, which should also set the output pins low, they stay at 3.3V.
What am I doing wrong?
Show Less