edc17c49 dpf off please

I'm going to pass on the DPF delete — emissions-defeat calibrations aren't something I'll produce, and on a Doblo that's still a road car it's an MOT/roadworthiness fail plus a real health issue for whoever's behind it. Not a judgement on you, just where I draw the line.

That said, there is something worth flagging about the upload itself:

The read looks half-empty
Everything from 0x200000 to the end of the file is 00. The populated region stops right after the block at 0x1FFF40-0x1FFFFF (that tail is a SHA constant table, so it's a legitimate end-of-data boundary, not garbage). On a TC1797-based EDC17C49 you'd normally expect content across the full 4 MB in a proper full read. So either:

• the tool only pulled the first bank and padded the rest, or
• it's an MPC container where the upper half is intentionally blank.

Either way I would not write that back as-is until you've confirmed it against a second read. Fact from the file: identifiers are 1037542422, P687_F16C_v1, Bosch 0281030837, Fiat 55263144, bootloader SB_V10.00.00/1797, TPROT_V12.00.00/1767. Inference: the zero region is a read artefact, not a valid empty flash.

What I'd actually help with
If the DPF is causing you grief, the fix is usually diagnosable rather than deletable. Post:

• Full DTC list (stored + pending), with freeze frame
• Soot load calculated vs measured, and ash load in grams
• Distance/time since last successful regen, and regen abort counters
• Differential pressure sensor reading at idle (should be near 0 mbar) and at ~3000 rpm
• Oil dilution / oil change counter status

Nine times out of ten on these 1.3/1.6 MJet Doblos it's a blocked or split pressure sensor pipe, a knackered sensor, or short-trip use never letting a regen complete — all cheap to sort. Ash load over roughly 100-120 g is the point where the filter genuinely needs cleaning or replacing.

What's the year, engine (1.3 or 1.6 MJet) and what symptoms are you chasing? If you tell me what it's doing I'll help you work it out properly.

is not full file .. somthing wrong

Agreed — that matches what the dump shows. Data ends cleanly at 0x1FFFFF and everything from 0x200000 to 0x3FFFFF is 00, so you effectively have a 2 MB read padded out to 4 MB. TC1797 has 4 MB internal flash, so the second bank is simply missing.

Most likely causes

• OBD read that only pulled the first bank (common when the tool's protocol entry is wrong for the C49 variant)
• Read aborted partway and the tool wrote the remainder as padding instead of erroring out
• Wrong read mode selected — e.g. "program/calibration only" instead of full flash

Next step
Do a fresh read and verify it before doing anything else. Two quick sanity checks on the new file:

• The region around 0x200000 should contain real code/data, not zeros
• Compare the first 2 MB of the new read byte-for-byte against this file — they should be identical if the original bank read was at least clean

If you can, take it on bench/BSL rather than OBD for a full 4 MB — much more reliable on this ECU.

For anyone to help further, post:

• Tool and version used for the read
• Read type (OBD / bench / boot) and the exact profile you selected
• Vehicle details — Doblo year, engine code, gearbox
• Whether the tool reported any error or "read finished with warnings"

Identifiers already visible in what you uploaded: 1037542422, P687_F16C_v1, Bosch 0281030837, Fiat 55263144, boot SB_V10.00.00/1797. Those look consistent, so the ECU ID side is fine — it's purely the read that's short.

One thing I won't do is the DPF delete itself, as I said above. But sorting out the read is worth doing regardless, since a partial file is useless for any work and dangerous to write back.