Table of Contents
Advertisement
Touchclone™ EEPROM Reader
27
Default method data
When reading an Eeprom in circuit using the default read method you should check the data to make sure it
contains all the relevant data needed to be identified as a working module with TouchClone.
At first glance, the data read from the Eeprom would seem to look valid, but upon closer inspection you can
see that the data is copied in a 2 byte sequence. This indicates that the organisation field needs to be altered
from 8x to 16x or vice versa.
You will also notice the second half of the data is mostly FFs, indicating that there wasn't a full extraction of
data (experience of this vehicle would highlight this problem or comparison against a known successful read
on a similar vehicle/immobiliser box).
We can now assume that all the data could be retrieved from the Eeprom by changing the read method
parameters, as the Eeprom does respond with data albeit irregularly and corrupt. We will now show you how
we tune each parameter to ensure the data we get is valid.
Verify Your Data using Touchclone - Applying Hex Data
In the previous step we tried to draw our own conclusions of why the data looked incorrect and wouldn't
translate into a working immobiliser module. If you proceed to the next step using Touchclone with any hex
data you have read from an Eeprom, TouchClone will automatically use certain identifiers to try and match it
to a known vehicle immobiliser for creating a key.
As we can 'see above' the data that was read in using the default read method was not complete and so a
vehicle module was not found.
st
Touchclone™ Version 1.5 – Manufactured & Developed by 1
Call Lockouts Limited. All rights reserved 2012.
Advertisement
Table of Contents
