DSG DQ250

VAG DSG DQ250 (02E) — Temic/Continental wet-clutch 6-speed dual-clutch transmission control unit (mechatronic TCU). Transverse PQ35/MQB platforms (VW/Audi/Skoda/SEAT). Generations: CXX (MK5-era), EXX/FXX (MK6-era, pre-MQB) and MQB (0D9300xxx). Tuned parameters = clutch input-torque limits, clutch/clamping + line (supply) pressure, launch, shift schedule/speed, rev + speed limiters. (DQ250 = WET-cl

Reference - updated 4 August 2026

The ECU hardware

MQB generation (0D9300xxx) = Temic/Continental mechatronic on an Infineon TriCore TC1766 — VERIFIED (TheFlashBold/DQ250-MQB-Bench-Flash): ~1.5 MB internal PFlash + PSPR scratchpad RAM + 2x16 KB internal DFlash @ 0xAFE00000 / 0xAFE10000. CORRECTION: the MQB TC1766 mechatronic ALSO carries an EXTERNAL ~8 KB SPI EEPROM (on the SSC0/SPI peripheral, application mirror ~0xC00) holding adaptation + immo/component-protection data — an external EEPROM is NOT a pre-MQB-only trait, as the original draft implied. Pre-MQB CXX/EXX/FXX generations use an earlier Temic microcontroller (commonly cited as Freescale/Motorola-class — UNVERIFIED, varies by generation) with a separate 95-series SPI EEPROM (adaptation/immo); software and layout differ by generation even on the same gearbox. Part-number families: 02E300xxx (pre-MQB, e.g. 02E300012/014/043) and 0D9300xxx (MQB).

Fuelling and load sensing

N/A — this is the TRANSMISSION controller, not the engine ECU. The DQ250 sits behind both petrol and diesel engines (commonly EA888 2.0 TSI / 2.0 TDI, up to its ~350 Nm class). Critical: the TCU tune must be co-developed WITH the engine ECU tune — input torque arrives over CAN from the ECM, and the TCU sends torque-reduction requests back to the ECM (torque-monitor lockstep). Engine-domain safety limits (knock, EGT, rail pressure, DPF) live in the ENGINE calibration, not in this file.

How this ECU is read and flashed

MQB (TC1766): (1) OBD via UDS — the normal tuning route with Kess/KTAG, Autotuner, Alientech, HP Tuners, PCMflash (VAG DSG module — VERIFY the current module number; the draft's 'Module 58' is unconfirmed), and the open-source bri3d/VW_Flash. Payload = LZSS-compressed + 256-byte rolling-offset substitution cipher (plaintext also accepted); a RAM flash-driver CRC32 challenge is run; ASW/CAL JAMCRC checksums must be corrected (tools auto-correct). (2) BENCH over CAN (TheFlashBold/DQ250-MQB-Bench-Flash; SocketCAN on a Raspberry Pi or CAN adapter, no OEM diag software) — hold the TCU in SBOOT with repeated requests on CAN ID 0x640 (responses on 0x641), then advance the internal auth phases by FORGING the RSA-1024 signature via SBOOT's relaxed PKCS#1 v1.5 verification (a Bleichenbacher-style low-exponent signature forgery; exponent e=3 is typical of such forgeries but is NOT explicitly documented). Then upload a flash-manager to PSPR RAM (0xD4000000) and erase/write/verify PFlash / CAL / ASW plus internal DFlash and the external SPI EEPROM. IMPORTANT ATTRIBUTION FIX: this RSA forge is the DQ250 (TheFlashBold) work — it is NOT bri3d's SBOOT research. it explicitly does NOT use a Bleichenbacher/RSA attack. bri3d's DSG contribution is VW_Flash (the OBD/UDS side above). (3) BOOT/service mode — for repair: read/write the internal micro + external EEPROM. Pre-MQB CXX/EXX/FXX: OBD + bench/boot; a separate 95-series external SPI EEPROM holds adaptation + immo/component-protection. IMMO/CP note: cloning or swapping a mechatronic requires copying that EEPROM (adaptation + immo/CP) to the donor; component protection is enforced on the vehicle/gateway side. Always RESET clutch adaptations after any write (EcuTek/ProECU-style DSG menu or VCDS basic settings) and relearn at correct oil temp.

Engine codes in this family

• Transmission controller — pairs with petrol/diesel engines rather than having its own engine code
• Gearbox: 02E (DQ250) WET-clutch 6-speed DSG
• TCU part families: 02E300012/014/043 (CXX/EXX/FXX pre-MQB), 0D9300xxx (MQB)
• Typical paired engines: EA888 2.0 TSI (CCTA/CBFA/CDLA/CULC etc.) and 2.0 TDI

Staging - what each stage really gives

• stage1 - Software-only TCU flash to PARTNER a Stage 1 engine tune (roughly 350 -> 420-450 Nm). Raise Max Torque (C1/C2) and Gearbox-Protection torque in LOCKSTEP with the ECM, raise line/clamp pressure + clutch target-torque correction to stop slip, quicken shifts and lift shift points, enable/raise launch RPM, raise in-gear rev limiter, remove speed limiter. The 'gain' is unlocking the engine tune (no derate) plus faster shifts and launch — not extra crank power by itself. Reset clutch adaptations after flashing.
• stage2 - Match a Stage 2 bolt-on engine tune (~450-500 Nm). More aggressive clamp/line pressure and torque-correction, higher shift firmness. Still riding the STOCK wet clutch pack, now approaching its ~520 Nm development tolerance — clutch life shortens as you near that ceiling, so pressure calibration and torque estimation must be accurate.
• stage3 - Big-turbo / injector / high-torque builds (~600-700+ Nm). Requires an UPRATED clutch pack (e.g. Dodson) and custom code to break the ~655 Nm software ceiling of the Max-Torque map. Full pressure + torque-limit rework, launch/shift re-cal for the new torque model, and a DSG cooler for hard use. The TCU calibration must track the engine's torque model EXACTLY or it will cut power / go to limp.

Safety limits

• Stock DQ250 wet-clutch input-torque rating ~350-380 Nm (factory) — the baseline a Stage 1 file lifts toward its true clamp capacity; the map lifts the LIMIT, it does not create mechanical capacity.
• ~520 Nm = development/measured tolerance ceiling of the STOCK wet clutch pack; sustained torque above this causes early clutch wear / slip. Treat as the hard limit until the clutch is upgraded.
• ~655 Nm = software number-size ceiling of the Max-Torque map; exceeding it needs custom code AND an uprated clutch pack (600-700+ Nm territory) — a bigger number in the map never adds mechanical capacity.
• Clamp/line pressure must stay within pump/solenoid/seal capability: over-pressuring risks hydraulic/solenoid/seal damage; under-clamping causes clutch slip and burn. Raise line/clamp pressure and clutch-target-torque correction TOGETHER, never in isolation.
• TCM torque limits and the torque-reduction request MUST stay coherent with the ECM torque model (torque-monitor LOCKSTEP). Any mismatch -> engine power cut, DTCs, or limp/emergency mode. Never tune the TCU without a matching, accurate engine-torque calibration.
• Clutch/gearbox-oil OVER-TEMPERATURE protection: launch slip and repeated hard launches heat the wet pack, and the mechatronic trips clutch-protection/limp on measured clutch temperature. Monitor clutch/oil temp (VCDS/logging), fit a DSG cooler for track/high-power use, and NEVER calibrate pressure only when cold — verify against oil temp.
• Over-aggressive shift overlap / switch-time / firmness raises DRIVELINE SHOCK — it accelerates wear on the clutches, dual-mass flywheel, mounts, axles/CVs and can throw shift-quality DTCs. Firm shifts up progressively, not to the limit.
• Removing the vehicle-speed limiter can exceed the tire speed rating AND the gearbox's max permissible input/output shaft and final-drive speeds — respect tire and driveline speed ratings, not just the engine rev range.
• Always RESET clutch adaptations after any write and let the box relearn the new pressure setpoints at correct oil temperature (do not trust adaptation done cold).
• Engine-domain limits (knock/detonation, exhaust-gas/EGT, fuel-rail pressure, DPF regen/soot on TDI) are NOT contained in this TCU file — they must be enforced in the paired ENGINE ECU calibration. A DQ250 flash never substitutes for, or protects against, an unsafe engine tune.

Every car using this platform (1)

Stock power and typical remap figures per car. Stage results assume a healthy engine on good fuel.

How confident is this?

HIGH / web-verified against primary sources (bri3d/VW_Flash docs/dsg.md; TheFlashBold/DQ250-MQB-Bench-Flash; TheFlashBold/tune-editor): MQB DQ250 = Infineon TriCore TC1766; block layout DRIVER(RAM)/CAL@0xA0020000(0x20000)/ASW@0xA0040000(0x130000) in a ~1.5 MB image with internal DFlash 2x16 KB @0xAFE00000/0xAFE10000, PSPR RAM @0xD4000000, PLUS an external ~8 KB SPI EEPROM; integrity = JAMCRC (inverse CRC32) in the last 4 bytes of ASW and CAL, checked by SBOOT every boot; OVER-UDS payload = LZSS + 256-byte rolling-offset substitution cipher with a RAM flash-driver CRC32 challenge (driver @0xD4000000, magic 00 00 2E A2, entry ptr @+0x4); BENCH flash holds SBOOT via CAN 0x640/0x641 and forges an RSA-1024 signature through relaxed PKCS#1 v1.5 verification; TCM<->ECM torque-monitor lockstep and the 'raise TCM limits or it caps the engine' behaviour; reference points ~350 stock / ~520 development / 655 software ceiling; and the map CATEGORIES. (b) the external SPI EEPROM exists on MQB TC1766 too, not only pre-MQB. (c) 'EcuTek ProECU DQ250' and 'PCMflash Module 58' are UNVERIFIED/possibly wrong and were demoted. MEDIUM / thinner: 'e=3' exponent for the RSA forge (only 'relaxed PKCS#1 v1.5