Closed charkster closed 2 years ago
Sorry, I just realized that the CH552 is running a firmware to mimic the FT2232 (with a limitation of 2.5Mbps). As this is a firmware clone of a FT2232H, I will close this issue.
I'm surprised pyftdi list this device as a FT2232. The only possible way to do so is that the CH552 is configured with the same vendor id as FTDI and the same product id as FT2232. Very, very weird. Are you sure there is no other real FT2232 device connected to your host, for example a USB-JTAG key. The Sipeed-Debug seems to be the key here: it is likely a debugger probe connected to your host on one side and to the JTAG port of the CH552 on the other side.
CH552 and FT2232 are fully unrelated, so you cannot expect any kind of compatibility no. They are fully unrelated.
What you need is a compatible debugger bridge, such as OpenOCD and GDB although I have no idea whether it supports CH552/8051 devices.
@eblot Thank you for the advise, and thanks for pyftdi!
Thanks!
I am seeing my CH552 device detected with
Ftdi.show_devices()
I get errors when I try to use the UART:
The CH552 datasheet has a list of all the register addresses, but I could not find a similar list of registers for the FT2232H (to make sure that they are the same). Here is the link to the CH552 datasheet: http://www.wch-ic.com/products/CH552.html
Should I use the "add_custom_product" method to attempt functionality? Thanks.