Вот мануал, подробнее нет:
- Install PSAInterfaceChecker available here:
http://dl.free.fr/nnYkeorAY
- Place vci_updater.com file of the zip archive in the folder
C:/APPLIC/LEXIA/MajAppCom/APPLIsoftware of your hard drive. Warning this
step is very important because if the file is placed elsewhere
PSAInterfaceChecker may refuses to proceed to the download !
- If you have Diagbox, pp2000 or Lexia opened, close them
- Connect the interface on USB
- Run PSAInterfaceChecker (shortcut on the desktop normally), and then
click "Activate"
- Make sure there is good communication with the interface by reading
the actual version and reference
- Select the customized firmware vci_updater.com which is in
C:/APPLIC/LEXIA/MajAppCom/APPLIsoftware of your hard drive
- Start downloading
- Carefully watch the green LED of the interface: after twenty seconds,
the download completes (PSAInterfaceChecker will show "KO" but it's
not important), the LED turns off, indicating that the firmware starts
its work, then after 5 to 20 seconds it flashes to indicate that the
work is finished. Be careful there is no power off during the 5 to 20
seconds phase where the LED is off (notebook connected on mains, do
not disconnect the USB during this phase)
- Disconnect the interface from USB when the green LED flashes
- Reconnect the interface on USB. Now it must be recognized as Evolution
and windows will ask you for the driver. Select "not this time" for
Windows update connection, then select "Install the software
automatically". If your diagbox installation is good Windows will find
and install the driver automatically
Now two possibilities:
- With PSAInterfaceChecker you reflash an official firmware
- You run diagbox and it will automatically updates the interface with
4.3.0 firmware (don't forget to activate the automatic update if you
disabled it)
Note : At the end of the vci_updater.com firmware download if the green
LED stay ON (don't turn OFF and don't blink), it's because you have an
incompatible interface, which cannot work with the Evolution bootloader.
In this case your interface is not upgraded, and you must download an
older firmware (4.2.2 or 4.2.4DB)
What are the risks for my interface ?
-------------------------------------
The risk to brick your interface (require reprogramming the MCU
by the internal 12-pin connector) is low, but zero risk does not exist.
- If the interface is already recognized as Evolution, there is
absolutely no risk to brick your interface because the firmware will
not erase nor update the bootloader area in the MCU.
- If your interface is not recognized as Evolution, vci_updater.com will
update the bootloader area, in 2 steps : erasing the last sector of the
MCU flash, and programming the new bootloader. These two phases are
critical, it's important to not have a power failure or USB
disconnect during these two step, otherwise the interface will
not boot correctly and will not be recognized by the computer.
Fortunately these two consecutive steps takes about 2 seconds only.
But be careful to not have power failure during the phase where the
LED is OFF (5 to 20 seconds depending on the interface).
When the LED flashes the procedure is complete, you can disconnect.
- If the firmware detects that your interface is not compatible with
the Evolution bootloader, it will not proceed the upgrade to avoid
bricking your interface. In this case the green LED does not turn
off at the end of download. You can then disconnect / reconnect
your interface, and download a 4.2.2 or 4.2.4 firmware.
History versions of vci_updater.com :
-------------------------------------
V1.0.0 (30/03/2013)
- First working version
- Update bootloader to switch the interface to Evolution
- Clear the sector 5 of MCU flash, to erase all traces of
the old bootloader
- Erase external SPI EEPROM, and reprogram a random serial
number with recognition Peugeot (ACTIA/963830 C/42-07/nnnnnn)
V1.0.1 (31/03/2013)
- On some interfaces SPI EEPROM is not a Winbond but a Spansion,
which only supports the delete command 0xC7 against 0xC7 or
0x60 for Winbond -> Using the command 0xC7 instead of 0x60
to be compatible on the two models.
V1.0.2 (31/03/2013)
- The serial number is no longer generated randomly by the
firmware but during the firmware customization. So if you
share your custom firmware on Internet and it becomes public,
the serial number will be quickly blacklisted and your
interface will work not anymore with future diagbox versions
V1.0.3 (13/04/2013)
- Before the upgrade, check if the SPI EEPROM is readable to
determine if the interface is compatible or if it's an
incompatible interface with simplified hardware. No upgrade
occurs in this case to not brick the interface