FTDI Chip Saga V2.0 - this time it could be worse..!
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
i think he would be sending constant consistent data, then checking it on the scope, the clone just floods the packet im guessing, the genuine may have a pause window or some kind of internal checking or it could also be because of the changes made to the driver.
- antus
- Site Admin
- Posts: 8237
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
From reading the thread its a demonstration of a known bug in genuine ftdi which they have not fixed. The output should be a 38khz square wave but only the clone works.
Those cloners could make a killing if they invested in writing their own driver, purchasing usb ids, get it tested and put in to windows as a WHCL driver, submitted patches to linux and bsd so the open source ftdi drivers recognise their usb id (bsd so it ends up in mac). Finally replace the ftdi branding on the chip with their own and sell it as ftdi pinout compatible. Considering the effort and cost of developing their own silicon (last clone batch was software emulation of ftdi protocol on a generic mcu not a copy of the silicon) i dont see why they dont finish the job. Maybe cloneing is all they know.
Those cloners could make a killing if they invested in writing their own driver, purchasing usb ids, get it tested and put in to windows as a WHCL driver, submitted patches to linux and bsd so the open source ftdi drivers recognise their usb id (bsd so it ends up in mac). Finally replace the ftdi branding on the chip with their own and sell it as ftdi pinout compatible. Considering the effort and cost of developing their own silicon (last clone batch was software emulation of ftdi protocol on a generic mcu not a copy of the silicon) i dont see why they dont finish the job. Maybe cloneing is all they know.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
What the hell did antus just say?.....
Just when i thought i had my head around most tech acronyms, you go and do that....
Just when i thought i had my head around most tech acronyms, you go and do that....
According to chemistry, alcohol is a solution...
- antus
- Site Admin
- Posts: 8237
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
lol
usb id=identification numbers for usb devices. Registered for $ at http://www.usb.org/developers/vendor/
WHCL driver=windows hardware compatability labs - pay for and pass this test to get your drivers in to windows so your devices plug n play without manual driver install. (ftdi has paid for this, cloners use ftdis investment)
linux=the most common open source unix, especially since its in all your android phones and tablets.
mac=apple mac, another unix computer system. Underlying operating system is called darwin but its a variation on BSD. Not sure of exact process to get driver support in to mac but bsd is a good start.
Bsd=http://en.m.wikipedia.org/wiki/Berkeley ... stribution used by apple, sony (ps4) and others because of favourable licensing. Essentually take it, use it, make money with it, dont have to give any of your software developments or pay any money to use it at all.
ftdi pinout compatible=developers can not modify their hardware design at all and build with alternate chip and it should work just fine.
mcu=micro controller unit. Same as a cpu.
usb id=identification numbers for usb devices. Registered for $ at http://www.usb.org/developers/vendor/
WHCL driver=windows hardware compatability labs - pay for and pass this test to get your drivers in to windows so your devices plug n play without manual driver install. (ftdi has paid for this, cloners use ftdis investment)
linux=the most common open source unix, especially since its in all your android phones and tablets.
mac=apple mac, another unix computer system. Underlying operating system is called darwin but its a variation on BSD. Not sure of exact process to get driver support in to mac but bsd is a good start.
Bsd=http://en.m.wikipedia.org/wiki/Berkeley ... stribution used by apple, sony (ps4) and others because of favourable licensing. Essentually take it, use it, make money with it, dont have to give any of your software developments or pay any money to use it at all.
ftdi pinout compatible=developers can not modify their hardware design at all and build with alternate chip and it should work just fine.
mcu=micro controller unit. Same as a cpu.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
he's saying they are so close to having a better product, they could easily do a proper job finishing it and kill off FTDI's part market and theyve even fixed a bug in exising FTDI chips.
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
Thanks for explaining that guys, us meare mortals need it spelled out sometimes
According to chemistry, alcohol is a solution...
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
Hmmm ...
Looks perhaps that someone isn't telling the whole truth about the FT232R bitbang bug. According to section 3.1.2 of the following tech. note, this bug was only present in the Rev. A silicon (fixed long ago at Rev. B, current Rev. is C) and even had a documented work-around :
http://www.ftdichip.com/Support/Documen ... 20Note.pdf
Joe.
Looks perhaps that someone isn't telling the whole truth about the FT232R bitbang bug. According to section 3.1.2 of the following tech. note, this bug was only present in the Rev. A silicon (fixed long ago at Rev. B, current Rev. is C) and even had a documented work-around :
http://www.ftdichip.com/Support/Documen ... 20Note.pdf
Joe.
- antus
- Site Admin
- Posts: 8237
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
Thanks for posting that. Always good to keep it real!
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
- hoopstar
- Posts: 46
- Joined: Thu Mar 21, 2013 7:29 pm
- cars: 350 Chev HR Holden (carby)
VK Calais with (soon) VR EFI 304 - Location: Adelaide
Re: FTDI Chip Saga V2.0 - this time it could be worse..!
An interesting interview with FTDI's CEO about the counterfeiting..
https://blog.adafruit.com/2016/02/08/ex ... -adafruit/However, you should realise that we are dealing with a professional criminal gang here who counterfeit a lot more than just one or two chips