Hello,
SafeGuard-IT is a very old application that’s no longer supported by R&D.
It was developed many years ago in 2007.
Note ChipID and SafeGuard are two different things.
SafeGuard-IT uses the Chip ID which can be found here:
http://www.ftdichip.com/Support/SoftwareExamples/FTDIChip-ID.htmThis Chip ID DLL is used with the
D2XX Drivers.
It’s better to develop your own code using FTDIChip-ID.
There is another option to avoid using the Chip ID DLL which means even less dependency on our DLLs:
The FTChipID cannot be read from the FTD2XXX library directly as standard.
There is an NDA option available where we can provide the memory location of the raw FTChipID in EEPROM.
However, note that the FTDIChip-ID.dll does some additional manipulation of this EEPROM data, so the dll vs direct EEPROM read might not match.
If you would like this information under NDA, please
Contact Us.
As for your error "Insufficient space in EEPROM user data area" there is a limited amount of memory available in the EEPROM (1024 bits).
The size of the user area depends on the length of the Manufacturer, ManufacturerId, Description and SerialNumber strings programmed into the internal EEPROM. More memory space is freed up if the lengths of the information strings are shortened. The Maximum length of the Manufacturer, ManufacturerId, Description and SerialNumber strings is 48 words (1 word = 2 bytes). If all the 48 words are used, then no user area space is available.
To reduce the memory already taken up and to free up more space available to User Area, you could reduce the serial number and description strings using
FT_PROG.
Also see AN_121
Accessing The EEPROM User Area Of FTDI Devices for more information.
Maybe there are other community users who can help you further.
Best Regards,
FTDI Community
