PSA BSI Tool - Peugeot and Citroen EEPROM Utility 1.2

PSA BSI Tool is a Windows workshop suite for supported Peugeot and Citroen body-system interface repairs. Its main program provides EEPROM and flash operations, PIN retrieval, key learning and stored-distance fields. The package also includes PSA login and dump-to-PIN helpers, FTDI interface drivers, and English and Chinese manuals. These security and configuration operations require precise BSI identification and an original read that can be restored.

Vehicle Selections Shown in the Application

• Peugeot 207.
• Peugeot 307 — 2005- in the selection label.
• Peugeot 308.
• Peugeot 407.
• Peugeot 607 — 2006-.
• Peugeot 807 — 2006-.
• Peugeot Partner — 2008-.
• Citroen C2.
• Citroen C3 — 2005-.
• Citroen C4.
• Citroen C5 — 2007+.
• Citroen C6.

These are the visible menu labels, not a guarantee for every vehicle carrying the model name or year. Supplier, hardware, EEPROM, firmware and vehicle-network variants can differ within a model. Confirm the interface and expected BSI family before using Auto Detect.

Confirmed BSI Functions

• EEPROM reading and writing.
• Flash reading and writing.
• Saving memory contents to a file and loading saved data.
• PIN retrieval where the BSI and supported procedure permit it.
• The supplied key-learning workflow.
• Reading stored distance and preparing a replacement value for an authorized repair.

Additional utilities assist with PSA login, key calculations and dump-to-PIN tasks. They do not substitute for an accurate BSI read or establish that a dump belongs to the intended vehicle.

Required Hardware

• The compatible PSA BSI interface expected by this application.
• A Windows computer with the appropriate supplied FTDI D2XX or virtual COM-port driver.
• Stable bench or vehicle power and the correct connector or pinout.
• An external EEPROM programmer when an offline memory read is part of the repair.
• A diagnostic tool for identification, fault checking and post-repair configuration.

The documented archive includes x86 and x64 FTDI components, INF/CAT files and manuals. Legacy drivers or customized interface identifiers may complicate installation on current Windows systems. Retain any hardware-specific VID/PID configuration required by the interface vendor rather than substituting drivers blindly.

Recommended BSI Backup Workflow

1. Verify ownership and privately record the VIN, model, year, BSI supplier, label and hardware/software identifiers.
2. Provide regulated power and confirm interface communication and drivers before entering a write function.
3. Read supported EEPROM and flash areas twice and compare both copies.
4. Keep untouched originals under read-only names with hashes.
5. Use copies for PIN, key or distance work, solely for a documented repair.
6. Check output length and all changed regions before programming.
7. Write with stable power, verify the result and complete any necessary diagnostic configuration.
8. Check starting, locking, lighting, wipers, indicators, windows and fault memory.

Mileage and Legal Use

Use the distance fields only for lawful module repair or replacement, with accurate records. PSA modules may synchronize mileage, allowing an incorrect value to propagate and leave a persistent discrepancy. Follow applicable disclosure and odometer requirements and document the original and final readings.

PIN retrieval and key learning affect vehicle security. Authorization is required; keep PINs, dumps and customer identifiers private.

Package Contents and Cleanup

The documented cleaned package retains the main BSI application, both language manuals, FTDI drivers, PSA login and key calculators, the complete legacy key-calculator installer and expanded PSA dump helpers. Its preparation notes describe removing redundant nested driver/calculator archives after their contents were checked, together with an empty runtime log. Functional components retain their original relative folder layout.

The application and helper executables are documented as unsigned; included FTDI drivers carry valid signatures where present. Preparation notes state that no executable was launched. ECUDB has not independently executed or certified the package, and no malware-clean claim is made.

System Requirements

Use a dedicated Windows workshop computer. Administrative rights are needed only where driver installation requires them. This legacy application may run more reliably in an isolated compatibility environment on a modern host; exact supported Windows versions are unspecified. Maintain a stable USB connection and prevent sleep or update restarts throughout memory operations.

Troubleshooting

For failed auto-detection, check model selection, BSI power, drivers, wiring and ignition state. If repeated reads differ, resolve the connection before calculation or writing. Implausible PIN or distance results call for verification of the BSI variant and file type, rather than randomly selecting other models.

Support information should include model, year, BSI supplier and part number, memory type, interface, operation, exact file length and a redacted error. Never publish the complete EEPROM, PIN, VIN or key data.