Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
"Software drivers, Design documents for DVK (Schematics, Gerbers, and BOM), Configuration Utility, DVK User Guide, DVK Quick Start Guide, terminal application Tera Term, Application examples, and .NET framework files."
Of course what I found that this actually meant is that it includes the .NET Framework installer, not actual .NET libraries. They appear to be unmanaged C++ libraries, which seems a little funny, as it appears the cypress provided config utility is in written in .NET.
The idea was to build a bootloader host application in .NET as I have done with USB HID and UART bootload interfaces in the past. There are examples from Cypress, written in .NET that I was able to follow to get them going. The problem is for this USB-Serial API, there are no such examples.
Now, I'm a firmware guy and PC application development isn't my strong suit, so I have no idea how to get this API going in a .NET application. Getting the bootload host API going in .NET was as simple as following the instructions in chapter 5 of this guide: http://www.cypress.com/file/45376/download
The problem is, now I'm at the step where I have to talk to the USB-Serial bridge in order to write the OpenConnection/CloseConnection/ReadData/WriteData functions. The USB-Serial API is much larger, more complex, and there isn't a guide like the above link.
Does anyone maybe have some insight they could share into how I can get this working? It would be greatly appreciated.
Would I maybe be better off just writing a C++ console application so I can just call all this stuff native rather than having to worry about managed vs. unmanaged?