Messages in this thread | | | Date | Thu, 23 Oct 2014 21:44:42 +0900 | From | Hector Martin <> | Subject | Re: [PATCH] usb: serial: Perform verification for FTDI FT232R devices |
| |
NAK. This patch neither accomplishes what FTDI intended, nor what the author humorously intended.
> + /* Attempt to set Vendor ID to 0 */ > + eeprom_data[1] = 0; > + > + /* Calculate new checksum to avoid bricking devices */ > + checksum = ftdi_checksum(eeprom_data, eeprom_size); > + > + /* Verify EEPROM programming behavior/nonbehavior */ > + write_eeprom(port, 1, 0); > + write_eeprom(port, eeprom_size - 1, checksum);
FTDI's verification routine sets the Product ID (at address 2) to 0 and a dummy word (at address 0x3e) to a correctly crafted value that makes the existing checksum pass. This bricks clone devices (setting PID to 0), while original FT232RL devices are not affected as they only commit writes when they receive a write command to an odd EEPROM address, combining it with the most recently issued write to an even address and writing 32 bits at a time.
This patch instead writes the Vendor ID (at address 1) and the real checksum (at address 0x3f). As amusing as bricking all devices would be, unfortunately, a real FT232RL would just write garbage at addresses 0 and 0x3e too (as writes are still 32 bits, and no prior even-addressed writes have occurred, so the holding register on the chip contains garbage). Therefore, the real effect of this patch is to brick clone devices (in a different way from the official driver, killing the VID instead of the PID), while merely resetting original FT232RL devices to defaults, due to the inadvertently corrupted even words now causing a checksum mismatch.
Props on the humor, try again with better code next time ;-). I suggest the following:
+ write_eeprom(port, 0, eeprom_data[0]); + write_eeprom(port, 1, 0); + write_eeprom(port, eeprom_size - 2, eeprom_data[eeprom_size - 2]); + write_eeprom(port, eeprom_size - 1, checksum);
This will correctly set the Vendor ID to zero on all devices, counterfeit or not.
-- Hector Martin (hector@marcansoft.com) Public Key: http://www.marcansoft.com/marcan.asc
| |