Infineon Tricore BSL (Module 53)
Infineon Tricore BSL (Module 53)
Infineon Tricore BSL (Module 53)
Possible password reading for SIM2K-24x, Ford EMS22XX, Ford SID20X, Bosch, Bosch GPT, etc.
Bosch
VAG MED17.1 TC1796
VAG MED17.1.1 TC1796
VAG MED17.1.6 TC1797
Ford MED17.2 TC1767 TPROT7
Ford MED17.2 TC1767 GPT
BMW MEVD17.2.4 TC1797 GPT
BMW MEVD17.2.9 TC1797 GPT
PSA MED17.4.2 TC1767
VAG MED17.5 TC1766
VAG MED17.5.5 TC1766
VAG MED17.5.5 TC1766 GPT (The password is to be read via Ford/Opel/Volvo)
VAG MED17.5.5 TC1767 GPT
VAG MED17.5.21 TC1782 GPT
VAG ME17.5.24 TC1724 GPT
VAG ME17.5.26 TC1724 GPT
MB MED17.7.1 TC1797 TPROT7
MB MED17.7.2 TC1797 GPT
China ME17.8.8 TC1728
K/H MEDG17.9.8 TC1767
VAZ ME17.9.7 TC1762
K/H ME17.9.11 TC1762
K/H ME17.9.12 TC1762
K/H ME17.9.13 TC1762
UAZ ME17.9.71 TC1724
Siemens/Continental
K/H SIM2K-241 TC1767
Ford SID208/SID209 TC1797
Ford EMS2204/EMS2211 TC1738
Delphi
GM MT-60 TC1766
China MT-80 TC1762
GM MT-80 TC1762
K/H MT-86 TC1766
MB CRD 3.10 TC1797 (a 120Ω resistor is required for CAN bus)
Operation speed will be a welcome surprise. The file format is usual (BIN).
Any J2534 adapter can be used. There is a possibility to automatically control the power via L-line (ground
with the power on), like in Multiflasher and ChipLoader. Besides, in the BSL mode there is +5V voltage in the
12th adapter contact which can be used for boot pins switching.
Terminology (the developer doesn’t claim to be absolutely precise, but adapts the terms for better understanding).
1) BSL - bootstrap loader – a special CPU mode when it loads its software not from the internal or external
memory, but through some external interface, e.g. CAN bus or a serial port.
2) TPROT - tuning protection – a general term for Bosch technology for protecting the ECU software from
outside modification including both ECU software protection ("RSA signature"), and hardware one (CPU
internal memory access password).
3) GPT – a special Bosch ECU mode used for reading passwords of some ECUs.
General Operating Procedure
2) Define the ECU pinout using the appropriate schematics, and if there is no schematic, it is possible for
Bosch ECUs to define the connection points using the programming board (ECU opening is required);
3) Using a multimeter check if there is a terminator (a 120Ω resistor) on the CAN bus; if necessary ‘connect’
the resistor from outside. If you have a special adapter for working in the BSL mode, this resistor is likely to be
inside it already and there is no need to connect it. Please note that the resistor can be connected always,
from the developer’s experience, it will be helpful as CAN bus normal resistance in the vehicle is 60Ω (two
terminating resistors in the ECU on the CAN bus ‘edges’, i.e. connected in parallel).
5) Open the ECU, put the CPU in the BSL mode using either the appropriate manual or taking into
consideration the following data depending on the CPU:
H is the CPU pin connection to +3.3V via a 470Ω-2kΩ resistor, L is the connection via a similar resistor to the
ECU ground. CPU contacts must not be connected without resistors!
Depending on the operation mode (reading-flashing), you will see the following window:
1) ECU – choose the ECU type which you are going to work with (the list is filled according to the chosen
CPU), the choice determines checksum verification and correction as well as the unlocking function while
writing via OBD;
2) Password – choose a password to be used: a) "Auto" for ECUs without passwords or Bosch ECUs with
TPROT version earlier than 8, b) ‘Browse…’ allows to choose a previously saved file with a password, c) the
latest used file.
3) Automatic power control (L-line switch) – the loading program controls the ECU power via L-line (pin 15).
4) Use write optimizations – writing speedup, in this case those data areas that have not been changed are not
reflashed; you should disable it when some problems appear during the writing process.
5) Disable digital signature check (unlock ECU) – works for the following ECUs: SID, EMS, 17.9.71 and VAG
(and their ‘relatives’).
6) Write only SW areas, skip service areas - for SID, EMS, SIM2K, ME17.9.71 ECUs, the writing result will be
the same as the original protocol writing, i.e. all service areas containing the ECU unique data will be skipped,
and for MED17/EDC17 ECUs Bosch service areas will be skipped even if they do not belong to the OTP
areas.
Important (for ECUs with external FLASH memory): FULL (MICRO+EXT) reading is required for correct
checksum verification and correction. It is impossible to ‘check’ them separately.
Connection instructions
Unfortunately, the developer is unable to make the instructions for all the ECUs, he simply does not have all of
them. The module covers not just one ECU, but hundreds. Some unique ECUs are already described in other
topics. You can find some general information above. Please remember that the module is for professional
use only.