3 ms·
If I recall correctly, FTDI took some well deserved heat, but quickly discontinued this practice.
by analog31 6y ago
If I recall correctly, FTDI took some well deserved heat, but quickly discontinued this practice.
- voltagex_ 6y agoBoth FTDI and Prolific have done this kind of thing. I switched to the CH340 a while back without any issues.
- omgtehlion 6y agohow about cp2102? I prefer it to ch340, for no reason though ))
- pantalaimon 6y agoI found both cp2102 and ch340 seem to use less power too than ft232r. At least there are some boards I can power with the 3.3V output of the cp2102 and ch340 dongles, but which will brown-out with the old ft232r ones.
- janekm 6y agoIt's my go-to part for this purpose also (and I don't believe I've encountered any clones so far, knock on wood). Another part I've used in a high-volume application is the Holtek HT42B534 which is great because it's CDC class and hence doesn't need a driver for Win/Mac/Linux. It's EOL sadly. There's HT42B564 which is a HID-class replacement. The other alternative is using a cheap micro with USB interface.
- analog31 6y agoAha, I didn't know about the CP2102. Looks like I'll have to give one a whirl, and there's even a breakout board at Adafruit. I've used relatively few VCP adapters since I've been using microcontrollers with built-in VCP. I was nervous about the CH340 because the Windows drivers seemed to come from some weird place in China, but maybe US sourced drivers aren't any more of a comfort in these times.
- voltagex_ 6y agoIf someone wants to quote me for a full reverse engineering of those drivers then I'd be interested in (crowd)funding it. But in terms of risks to worry about, it's pretty low down on the list IMO.
- makomk 6y agoIf I remember rightly, what Prolific did was worse in some ways because it rendered genuine but older-revision chips that they'd actually made non-functional with current drivers. (Also, some of the CH340 clones are genuinely really badly done and can't understand register writes that differ even slightly from what a particular version of the official driver sent.)
- marcan_42 6y agoThe really sad thing is that the FTDI clones worked better than the original ones. The original FT232R chips have a clocking bug that makes bitbang mode unusable for many applications, with no workaround (their errata sheet suggests a bullshit workaround of setting the clock speed to max, that is unusable in practice because USB can't keep up). It's supposedly fixed in a revision that I've never seen, and I believe they never manufactured it. The clones... work perfectly fine: https://twitter.com/marcan42/status/695292366639378433 https://twitter.com/marcan42/status/695292366639378433 In fact, I reverse engineered FTDI's bricker, and it works by exploiting the fact that their own chips violate their own interface design by requiring EEPROM words to be written back to back - even word writes alone are staged and ignored without an odd word write. The clones honor the writes independently, like FTDI's other chips. Their bricker code only writes even EEPROM words and preimage attacks their own checksum algorithm (since the real checksum is at an odd word they can't touch) to make it work, so it has no effect on the real chips (which get sent the same commands). It's hilarious. Don't buy FTDI. They're just bad.
- feteru 6y agoWait so the bricker wouldn't even work on the clones? Or it only works on the clone because they don't have the FTDI checksum algorithm bug?
- kd5bjo 6y agoIf I’m reading marcan_42’s comment correctly, the FTDI chip defers any EEPROM write request to an even address until it receives the next write request to the subsequent, odd, location. If the next write is somewhere else, it discards the original data. The 3rd-party chips, on the other hand, perform each write immedately per the official documentation. The malicious driver uses this difference to overwrite the firmware of the 3rd-party chips with carefully-crafted nonsense that has the same checksum as the legitimate firmware.
- drothlis 6y agoWe too found that the FT232R is unusable in bitbang mode. After much to-and-froing, FTDI support eventually acknowledged that even their later hardware revision "C" is still buggy, despite what the errata sheet implied. We switched to the FT230X, which works great. Our detailed investigation: https://stb-tester.com/blog/2016/05/26/ir-post-mortem https://stb-tester.com/blog/2016/05/26/ir-post-mortem