Bosch EDC17C64 Guide: VW Golf 7, Audi A6, Octavia, Caddy and Crafter EA288 TDI ECU Files
The Octavia on the ramp hesitates under load, the customer admits a previous tuner has been at it, and the ECU now on your bench carries a Bosch label with hardware number 0281018510 and VAG part number 04L906021N. The read you just took is somebody else’s map with the checksums patched over, so before you touch a single calibration value you want the stock software for that exact version, to compare against, to put back or to build on. That is the most common EDC17C64 job we see, and 0281018510 is the hardware number behind it: 17 listings in our catalogue, more than any other in this family.
This guide is built on what is actually published in the shop today: 360 EDC17C64 files, the vast majority tagged as read with KESS V2, with Flex and New Trasdata reads behind them, across VW, Audi, Skoda and SEAT. Below: how to identify the unit, which cars and engine codes turn up, how to read and write it without leaving a brick on the bench, and what to check when a car arrives in limp mode after someone else’s flash.
Recognising an EDC17C64 on the car and on the bench
EDC17C64 is the Bosch diesel engine ECU VAG fitted to many EA288 TDI applications, the engine generation that followed the EA189. You will find it on MQB cars such as the Golf 7, Octavia 3, Leon 3 and A3 8V, on longitudinal Audi models such as the A6, A5 and Q5, and on commercial vehicles including the Caddy and, in our listings, the Crafter. Where it sits in the car depends on the platform, so don’t identify it by position. Go by the label and by what the diagnostic tool reports.
The processor on the common versions is an Infineon TriCore TC1797. That matters for tool selection and for boot mode, which we come back to further down. As on most TriCore EDC17 units, the immobiliser and adaptation data sit in the processor’s internal data flash on the versions we handle, not in a separate 95xxx EEPROM, so a complete backup means reading both the program flash and that data area.
The numbers on the label
A typical EDC17C64 label gives you three things you need when you look for a file, and a fourth number comes from the ECU itself. If you’re unsure which line is which on a scuffed or partly peeled sticker, our walk-through on reading ECU label numbers covers the layout in detail.
- Bosch hardware number: ten digits starting 0281. In our catalogue the most frequent are 0281018510, 0281030170, 0281030374, 0281031413, 0281019175, 0281031786 and 0281033072. Others such as 0281018526, 0281019641, 0281019934, 0281030376, 0281030412 and 0281031411 appear in individual listings.
- VAG part number: on most cars this is 04L906021 followed by one or two letters (04L906021M, 04L906021N, 04L906021AP, 04L906021FQ and so on). Several Caddy and Jetta listings use 04L906016 instead (04L906016GK, 04L906016PM, 04L906016B). The Crafter files carry 03L906021A, 03L906021B or 03L906021C, and two VW listings use 04F906021A.
- Bosch software number: either the older ten-digit 1037 format (1037538356, 1037543824) or the newer 10SW format (10SW007940, 10SW047342). Some listings carry two of these because the tool reported more than one software ID.
- VAG software version: the four-digit number that follows the part number in our titles, as in 04L906021N 6547 or 04L906021M 5517. It is what the ECU reports on diagnosis. It is not always printed on the label, so read it with VCDS or ODIS, or from the identification screen of your flashing tool.
Why the hardware number alone is not enough
One hardware number carries many calibrations. Just in the listings under 0281018510 we have 04L906021M 5517, 04L906021M 6545, 04L906021M 7635, 04L906021N 5518, 04L906021N 6547, 04L906021N 7636, 04L906021N 8138 and 04L906021N 9213. The software versions that repeat most often in the catalogue are 04L906021M 5517, 04L906021N 5518, 04L906021N 6547 and 04L906021N 7636, with three listings each. Write the wrong one of those into a car and at best you get fault codes, at worst a car that won’t start or a CAN mismatch with other modules.
The reverse is also true, and it’s useful. The same software is often shared across the group. 04L906021N 6547 with Bosch number 1037538356 appears in our catalogue as a Skoda file, an Audi A3 file and a SEAT Leon file. 04L906021N 5518 with 1037533832 shows up on a Golf, a Rapid and an Octavia. The brand on the listing tells you which car the read came from, not that the file only suits that badge. Match the part number, the software version and the Bosch software number, and the brand becomes secondary.
Vehicles and engines in our EDC17C64 catalogue
The table groups the 360 published EDC17C64 files by brand. VW and Volkswagen are the same make tagged two ways in the shop, so they are merged here (276 plus 8). Model names come from the product tags and titles, and engine codes are the ones attached to listings for that brand. A good share of the files are tagged by part number only, without a specific model, which is why the model counts further down don’t add up to the brand totals.
| Brand | Models in our listings | Engine codes seen on these listings | Files in our catalogue |
|---|---|---|---|
| VW | Golf (incl. Golf 7), Caddy, Crafter, Jetta | CUNA, CSLB, CSNA, CUUA, CVCA, CSCA | 284 |
| Audi | A6, A3, Q5, A5 | CNHA, CRKA | 52 |
| Skoda | Octavia, Rapid | CLHB, CXMA | 16 |
| SEAT | Leon | CLHB | 8 |
By model, the A6 leads with 42 files in our catalogue, then the Golf with 28, the Crafter with 13, the Octavia with 12, the Caddy and Leon with 8 each, the A3 with 5, the Q5 and Rapid with 3 each, the A5 with 2 and a single Jetta. The A6 figure surprises some people who think of EDC17C64 as a Golf ECU, but the longitudinal 2.0 TDI in the A6 is well represented, with several hardware numbers (0281030374, 0281031413, 0281031411, 0281033072) among the A6 listings.
Engine codes
Engine codes are the quickest cross-check when the label is missing and the car is still in the workshop. The most common codes on our EDC17C64 listings are CNHA (36 files), CUUB (29), CUUA (22), CLHB (18), CSUA (18), CVCA (18), CKFB (17), CUWA (17), DELA (13), CRKA (12) and CUNA (12). Behind those come CUVB (8), CRMB, CXMA, DEKA and DEJA (7 each), CRUA, CSLB, CSNA and CUUF (6 each), CRVA and CUPA (5 each), and CRVC, CUVE and DFSB (4 each).
Treat the engine code as supporting evidence, not as the key, because one engine code runs across several part numbers and software versions over the production years. In the listings we have, CLHB appears on Octavia, Leon and Rapid files, and CNHA on A6, A5 and Q5 files. The ECU numbers decide which file you need; the engine code confirms you are looking at the right car.
The Crafter and 04F exceptions
Two groups in the data don’t fit the neat 04L picture. The Crafter files use 03L906021 part numbers with engine codes CSLB and CSNA, and two VW listings use 04F906021A with engine code CSCA. They are still EDC17C64 according to the ECU identification, but if a customer tells you “it’s an EA288, same as the Golf”, check the label before you pull a file. Family name and engine generation do not always line up the way people expect.
Example EDC17C64 files from our catalogue
These are real listings picked to show the spread of vehicles, hardware numbers and file types. Where the hardware number is not in the product title we say so rather than guess it. The software column gives the VAG part number and software version first, then the Bosch software number where the listing has one.
A few things stand out once you look at the rows side by side. The Golf 7 04L906021M 5517 calibration exists in the catalogue both as a tuned file and as a stock dump, which is the pairing you want if you need to see exactly what was changed. The Caddy 0281030170 hardware turns up with several software versions (04L906016GK 1667, 04L906016GJ 1666, 04L906016MR 4099 and more), so a Caddy owner’s “same ECU as my mate’s van” is rarely the same file. And the two Rapid rows show the same 04L906021EG part number with different software versions and different Bosch numbers, which is exactly why the four-digit version matters.
Which EDC17C64 file does the job need?
For this family the catalogue is almost entirely stock software. Of the 360 files, 355 are listed under Original File, 4 under Chip Tuning and 1 under FRF / SGO. That split reflects what workshops actually ask for on EA288 cars: a clean base to recover from, compare with or tune from.
Original files
An original file is a full read of an ECU running factory software, the kind of dump you’d take from a car that has never been touched. You need one when a previous tune has to come off before a dealer visit or a sale, when a flash failed and the ECU needs its program back, when you’ve bought a used ECU and want to put the correct calibration for the customer’s car into it, or when you’re building your own map and want a known-good starting point. It is also the reference when you suspect a car has been tuned and the owner says it hasn’t.
An original file won’t fix a sticking EGR valve, a cracked injector or a turbo with play in the shaft. If the car had a mechanical fault before someone tuned it, putting stock software back leaves you with the same fault and a cleaner ECU.
FRF / SGO containers
FRF and SGO are VAG flash container formats, the files a dealer tool writes over the diagnostic port. The single FRF / SGO listing for this family is for a SEAT Leon on 04L906021N 6547. A container like this is handy when you want to return an ECU to a factory calibration through the normal VAG update route with ODIS or a compatible tool, rather than by writing a raw dump. It is a different kind of file from a tool read, so check that your equipment actually handles the container before you buy.
Tuned files
The four chip tuning files are modified versions of specific software, including the Golf 7 and Leon files in the table above. A tuned file only belongs in an ECU running exactly the same software version it was built from. If your read shows 04L906021N 8138 and the tuned file is for 04L906021N 7636, it is not a match, however similar the car.
One Caddy file is labelled SCR DPF TUNED, meaning the AdBlue system and the particulate filter functions have been altered as well as the performance map. Removing or disabling SCR, DPF or EGR on a road vehicle is illegal in the EU, the UK and many other countries, and it will fail an emissions inspection. Files like that are for vehicles used off road, in motorsport or exported to markets where that use is permitted. The customer’s paperwork and intended use are your responsibility, not the file’s.
Immo off, virgin, DPF and EGR solutions
The shop sells immo off, virgin, DPF and EGR solutions for many other families, but at the time of writing none are published for EDC17C64. If you need one, send a full read and we’ll tell you what’s possible for that software. An immo off file should only go into an ECU on a vehicle the customer owns, for a legitimate reason such as a failed immobiliser component or an ECU replacement where pairing isn’t practical. On MQB cars the immobiliser is part of a wider system with component protection, so on many versions a proper adaptation through the dealer route is the better answer.
Reading and writing EDC17C64: OBD, bench and boot
The tool tags on our EDC17C64 listings give a fair picture of how these ECUs are read in the field. KESS V2 appears on 315 listings, Flex on 27 and New Trasdata on 13. KTAG, HexProg, Multi Prog and X17 MagPro each appear on a single listing. KESS V2 is first and foremost an OBD tool, while Flex and New Trasdata are generally used on the bench, and on our listings those two tags turn up on Audi A6, A5 and A3 reads, on Caddy, Crafter and Golf 7 reads, and on several Octavia, Leon and Rapid files. For a general comparison of the three access methods on this generation of Bosch ECU, see our guide to OBD, bench and boot mode on EDC17 and MED17.
OBD
On earlier EDC17C64 software, OBD reading and writing works with the common tools, and that’s why KESS V2 dominates our data. It’s fast and the ECU stays in the car. The limits are real, though. OBD on its own may not give you a complete backup that includes the data flash, and later software versions carry tuning protection that blocks or restricts writes through the diagnostic port. Our page on TPROT tuning protection explains what that means on EDC17 units and how tools deal with it. If your tool reports the ECU as protected, don’t keep retrying over OBD. Take it to the bench.
Bench
Bench mode means the ECU is out of the car and powered through its own connector, with the tool talking to the processor directly rather than through the normal diagnostic session. On EDC17C64 this is the usual route with Flex, New Trasdata and KTAG, and it’s the one to use when OBD is locked or when you need a full backup including the data area before a job. A write that goes wrong is also easier to recover on the bench than halfway through an OBD session.
Boot
Boot mode on the TC1797 means opening the case and connecting to the board so the processor starts in its bootstrap loader. It is the fallback when bench access doesn’t work on a particular software version, or when the ECU no longer responds at all after a failed flash. It’s more invasive, since the case has to be opened and resealed properly afterwards. Follow your tool’s connection diagram for the exact hardware number in front of you, because pinouts and required pads can differ between versions.
Before you write anything
- Power the ECU or the car from a stable supply. A good bench supply or a proper battery maintainer that holds voltage steady, not a tired battery or a trickle charger. A dip during a write is the classic way to lose an EDC17.
- Take a full backup of the program flash and the data flash (the area holding immobiliser and adaptation data) and save it with the car’s VIN and the full ECU identification. Keep a second copy off the workshop PC.
- Read the ECU identification and write down the part number, software version and Bosch software number before comparing against any file you intend to write.
- Make sure checksums are correct. Most tools correct them automatically on write, but if you’ve edited a file in a separate editor, confirm the checksum correction was applied before it goes anywhere near the ECU.
- Don’t open doors, switch on lights or let anyone start cranking the car during an OBD write. On the bench, don’t let the harness move.
Bench notes and typical EDC17C64 problems
ECU dead after a failed OBD flash
The most frequent rescue job on this family: an OBD write stopped partway, usually after a voltage dip, a lost laptop connection or a tool that didn’t handle the protected software properly. The ECU no longer talks over OBD and the car won’t start. In most cases the processor is fine and only the program area is incomplete. Bench or boot access, a correct original file for the exact software version, and the backup you took before the write (you did take one) usually bring it back. Our article on recovering a bricked ECU after a failed flash walks through the order of attempts. If you don’t have a backup, the data flash is what you’ll miss most, because that’s where the immobiliser information sits.
Swapped or second-hand ECUs
A used EDC17C64 from a breaker, even with an identical part number, won’t start the customer’s car on its own. The immobiliser data doesn’t match. The practical route is to clone: read the customer’s original ECU in full (flash and data flash) and write both into the replacement, so it is effectively the same unit. That only works if the customer’s original ECU can still be read. If it’s physically damaged, the choices are an online adaptation through the dealer route or, where the vehicle owner accepts it and it’s lawful, an immobiliser solution. Also check the replacement’s hardware number. A unit with a different hardware number may accept a clone of the data but not always the program, so compare before you write.
Limp mode after a tune
When a car comes in with a tune from elsewhere and a warning light, start by reading the fault memory with VCDS or ODIS before you touch the ECU. Boost deviation, rail pressure deviation and exhaust temperature faults are common on tuned EA288 engines, and the cause is often mechanical: a boost leak, a weak injector, a sticking EGR valve or a blocked DPF that the extra fuelling has pushed over the edge. Then read the ECU and compare it with the stock file for the same software version. If the tune is simply too aggressive for the hardware, putting the original back and fixing the fault is usually quicker than rebuilding someone else’s map.
Wrong file for the car
Symptoms after writing a file that doesn’t match: starting problems, communication faults with other modules, gearbox or ABS complaints, or a car that runs but logs dozens of faults. On EDC17C64 this almost always comes from matching on the hardware number only. Remember that 0281018510 alone carries at least eight different software versions in our listings. Go back to the identification you recorded, find the file with the same part number and software version, and write that.
Checksum and verification errors
If the tool reports a checksum error on write, stop. The file was modified without correction or corrupted in transfer. Re-download it or re-apply the checksum in your tool. Reads from different tools can differ in size and layout (full flash, calibration area only, or a tool-specific container), so check your tool’s import options before deciding a size mismatch means a bad file.
Questions workshops ask about EDC17C64
Can I read and write an EDC17C64 over OBD?
On many versions, yes, and 315 of our 360 listings are tagged as KESS V2 reads. Later software with tuning protection may block OBD writes or only allow a partial read. When the tool reports protection, go to the bench rather than forcing it.
Will a Skoda file work in a Golf with the same numbers?
If the part number, software version and Bosch software number all match, the software is the same, whatever the badge on the listing. Our catalogue has 04L906021N 6547 with 1037538356 listed as Skoda, Audi A3 and SEAT Leon files. The immobiliser and coding data are specific to each car, though, which is why you keep the car’s own data flash rather than borrowing another car’s.
What’s the difference between a 1037 number and a 10SW number?
Both are Bosch software numbers, just in two formats: 1037 followed by six digits on older calibrations, and 10SW followed by six digits on newer ones. In our EDC17C64 listings you see both, sometimes two on the same listing. Match whichever your tool reports.
Is the Crafter unit the same as the Golf unit?
It’s the same ECU family, but the Crafter files in our catalogue use 03L906021 part numbers with engine codes CSLB and CSNA, not the 04L906021 numbers seen on the Golf and Octavia. The files are not interchangeable. Always match on part number and software version.
Is there an immo off or virgin file for EDC17C64?
None are published in our catalogue for this family right now. Send a full read of the ECU (flash and data flash) with the identification details and we’ll check what can be done for that software. Immobiliser work is only for vehicles the customer owns.
The car has AdBlue. Can I use an SCR off file?
Not on a car that goes on public roads in the EU or UK. Disabling SCR is an emissions offence in most countries and the car will fail an inspection. For off-road, motorsport or export use there is one SCR DPF tuned Caddy file in the catalogue, and anything else would have to be requested with a read.
What exactly should I back up before a job?
The full program flash, the data flash and a note of the ECU identification (part number, software version, Bosch software number, VIN). Save it with the job card. If anything goes wrong, that backup is what gets the car home the same day.
When the file you need isn’t listed
The EDC17C64 family page shows every published file for this ECU, and it’s worth searching there by software version first, then by hardware number. If nothing matches, use the file request form and give us the Bosch hardware number (0281…), the VAG part number with its four-digit software version, the Bosch software number (1037… or 10SW…), the vehicle and model year, the engine code, and the tool you’ll be writing with. If you already have a read, attach it, even a partial one, because the identification block inside it answers most of our questions before we have to ask them. For a tuned car where you need the stock software back, say so, since that changes which version we look for.
More ECU guides
Bosch EDC17CP44 guide for Audi A4, A6, A7, A8, Q7, VW Touareg and Porsche 3.0 TDI
A Q7 turns up with a replacement ECU from a breaker. The label on the case reads 0281016832, the VAG number is 4L1910401H, and the owner…
Bosch MD1CS003 Original File: Peugeot, Citroen, Opel, Fiat and Toyota 1.5 / 1.6 BlueHDi ECU Recovery
The Bosch MD1CS003 is the engine controller of the PSA 1.5 BlueHDi (DV5) and 1.6 BlueHDi (DV6FD) engines fitted since 2017 to the Peugeot 208, 308,…
SID305 Virgin File: Resetting the Immobilizer Pairing on Renault, Dacia and Nissan 1.5 dCi
The Continental SID305 controls the 1.5 dCi K9K engine in the Renault Clio III/IV, Megane III, Kangoo, Dacia Logan, Sandero and Duster, and in Nissan Qashqai,…