USB low-full-high speed peripherals Forum Discussions

Would you help to confirm CYUSB3 driver support Long-Term Servicing Channel (LTSC) or not?

https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/LTSC-What-is-it-and-when-should-it-be-used/ba-p/293181​

Thanks,

Mitchell

hi   CYPRESS:

    When i use  cypress  CY8C68013A to do myself tool, when i install the kit, it show Cypress FX2LP No EEPROM Device? in my sch , the iic connct to the at24c02 and sch has been attached ,  when i use USB Console it show the erro, so if the at24co2 has issue or other issue ?

We use openocd "adaper_khz" to set cy7c65215's jtag clock speed. But the command takes no effect, though openocd doesn't report errors. Measuring the jtag clock with oscilloscope, it is always 450khz. Can we change it?

Thanks.

Hello,

I think that　Windows 10 Driver for CY7C65213 (USB-UART LP Bridge Controlle) can be downloaded as follows.

http://www.cypress.com/documentation/software-and-drivers/ez-usb-fx3-software-development-kit

Is this EZ-USB FX3 SDK 1.3.4 for Windows driver available on ’Windows 10 Enterprise 2019 LTSC ' ?

Or need a new driver ? 

Please  provide a driver for Windows 10 Enterprise 2019 LTSC  if it exists?

Best regards,

Haruhiko Shimoda

When FX2 device with FX3 SDK , .hex file is generated but iic file is not generated.

I can write program to RAM but can't write to EEPROM because there is no iic file.

Files built with keil can be converted to iic files with HEX2.bix.

I get an error when I try to convert data built with EZ USB Suite.

PS C:\Tools\Cypress> .\Hex2bix.exe -I TestProject.hex Intel Hex file to EZ-USB Binary file conversion utility Copyright (c) 1997-2005, Cypress Semiconductor Inc.

Error: Input image too big for output file size.  Addr = 0xe000, len = 0x20.

PS C:\Tools\Cypress>

Size of two files is almost equal.

Please tell me how to generate iic file with FX3 SDK.

I used this URL as a reference

http://e-tipsmemo.hatenablog.com/entry/2018/01/03/000000

hi  Cypress:

     在使用CY8C68013A的问题，上位机需要发送512Byte 或者其整数倍的数据才能接受到； 如果发小于512Byte 的数据

则无法接受到， USB的相关协议中应该是需要发送相关操作指令才可以实现非512byte 接受， 客户需要知道怎么进行操作？ 是否有相关的

建议； TKS;

Hi

I am interested in using the EZ USB chips for a new design and would like some help choosing the best part that has software example to prove concept. These are the requirements:

- USB 2.0 device (USB 3.0 not available for this application) on Windows platforms

- Supporting OV5640 (or equally similar image sensor) running in 8 bit parallel mode output is YUV and MJPEG

- Video capture using UVC drivers (ie. looks like a webcam to PC requiring no drivers to be written)

- Capture of images of at least 1M pixels (at least 1280x1024 SXGA resolution at 15 fps min). For this, compression is required (if I am not mistaken) and the OV5640 supports MJPEG.

- Application is cost sensitive so I would ideally like to go with the EZUSB 2 devices as opposed to the newer EZ USB 3 devices (unless the EZUSB 2 devices are to be obsoleted in the next 5 years)

- There is a space constraint where the PCB width should not exceed 8mm so the 56 pin BGA EZ USB 2 devices are very attractive

Can you please recommended a suitable part that has a reference design that I can use/adapt to achieve a proof of concept.

Thanks in advance

Probably answering the question myself, the TRM states that the aadj=1 will check only 1024byte commited buffers but I was wondering if it should work also on 512byte packets /fifo buffers for IN(2) endpoints. It doesn't seem to work with me so I was wondering if it is suposed to or if by design it doesn't, then, is there any sample on how to do the pid sequencing in the firmware? I need the quad buffering and (512*3)*8

Thank you in advance.