Having just discovered this post "CY7C65211 cyusbserial.dll library function CyI2cRead() length bug, errata?", I wonder where the errata are hidden for the CY7C6521x devices.
Despite most of the discussions having taken place behind the scenes I think it's clear that some CY7C6521x have firmware issues. Please correct me if I'm wrong.
Is it possible to get a comprehensive, up-to-date list of known firmware errors?
A.k.a.: Where are the errata?
I can tell you that right now I'm inclined to ditch the CY7C6521x chips.
Solved! Go to Solution.
We are currently in the process of updating the Errata in the datasheets as mentioned in the referred thread. We will update the timeline after discussing internally since the compiled list will include known issues for all the three parts.
Why don't you just publish it?
I'm not using these chips until I see the errata.
We are working on it publishing it and as per discussions, it will be on the web by mid April.
I also would like to see a link and more information about these devices. I've gone through quite a bit of frustration until deciding to replace the design by a known working USB bridge, you can guess the vendor.
I don't think it would hurt disclosing a bit more information. If the solution would be easier programmable (as obviously ARM based), it could be an interesting alternative to existing solutions...if it wasn't so easy to brick (with the original Cypress firmware update tool).
Followup: After bricking the CY7C65125 on a few development prototypes, I decided to give it another go on a VIP IO Board from Lattice Semiconductor which has the same chip on it, and managed to brick the firmware again as well with the programming tool (CyUSBSerialCommandUtility for Linux, see https://community.cypress.com/thread/13489), this time paying special attention (last time I accidentally must have used the wrong binary, but the tool just went through with it).
I was told by tech support to use recovery via SWD programming.
However I'm somewhat not inclined to obtain another programmer (MiniProg3, suggested by support) for resurrecting these units, so I was wondering if there's an easy way of uploading the firmware using OpenOCD - as this is the known working reference we program the boards with.
Unfortunately I closed my support case too early, therefore my question here: Is it possible to flash the CY7C65125 using OpenOCD?
OpenOCD is used as a JTAG debugger in the USB-Serial since the part supports JTAG master interface and cannot be programmed using the JTAG interface. Hence SWD programming could be used if you are not able to see any device enumeration after bricking the firmware.