# HG changeset patch # User Mychaela Falconia # Date 1695879584 0 # Node ID 29bff463402e90f8633a8c22f2469c0cad318776 # Parent c59011177e2e8582405755a4767fe50d6e076c75 doc/CP2102-EEPROM-format: part number byte confirmed diff -r c59011177e2e -r 29bff463402e doc/CP2102-EEPROM-format --- a/doc/CP2102-EEPROM-format Thu Sep 28 05:25:39 2023 +0000 +++ b/doc/CP2102-EEPROM-format Thu Sep 28 05:39:44 2023 +0000 @@ -14,6 +14,13 @@ fixed area allocated for it, no pointer-to-string scheme like in FTDI's EEPROMs; +* Unlike FTDI EEPROMs, CP2102 EEPROM is most certainly NOT optional - a blank + or garbage-filled EEPROM will result in a non-functional chip; + +* There is no checksum - because there is nothing for the chip to "fall back" + on when the EEPROM is bad, there is no point in checking the EEPROM content + for validity; + * The logical structure of CP2102 EEPROM is byte-oriented - no 16-bit words as elementary units. @@ -72,9 +79,9 @@ Address 0x37FF, 1 byte: - Python cp210x package notes indicate that this byte holds the part - number, presumably the one returned by the vendor-specific command that - retrieves it. This aspect remains to be tested at FreeCalypso HQ. + Part number code 0x02 for CP2102. The chip returns this EEPROM byte + when queried (via CP210x family-specific command) for its part number, + as in cp2102-read-partno. Address 0x3800, 4 bytes: