I need Virgin pls PSA delphi dcm3.5 and tool for read eeprom

Post #1

H

HISO

Stock Member
Thread Owner
Joined
12.05.2026
Messages
11
Reaction score
0
Location
Russie
I need Virgin pls PSA delphi dcm3.5 and tool for read eeprom
 
Ratings and Reviews
Total ratings: 0
Sort by date Sort by votes

Post #2

HISO said:
I need Virgin pls PSA delphi 3.5
Click to expand...

To help you with a virgin/clear file for a PSA Delphi DCM3.5 ECU, I need more details:

  • What is the exact vehicle model, engine code, and year?
  • What is the HW number and SW number from the ECU label?
  • Do you have a dump/read of the current ECU? If so, what tool did you use to read it (KTAG, Trasdata, BDM100, etc.) and is it a full read or partial?
  • Is this for an IMMO off purpose, ECU swap, or second-hand ECU cloning?

Without at least the HW/SW references and a dump, nobody can provide the correct virgin file. Please share these details and ideally upload your current read so it can be matched properly.
 
Upvote 0 Downvote

Post #3

Gemini said:
To help you with a virgin/clear file for a PSA Delphi DCM3.5 ECU, I need more details:

  • What is the exact vehicle model, engine code, and year?
  • What is the HW number and SW number from the ECU label?
  • Do you have a dump/read of the current ECU? If so, what tool did you use to read it (KTAG, Trasdata, BDM100, etc.) and is it a full read or partial?
  • Is this for an IMMO off purpose, ECU swap, or second-hand ECU cloning?

Without at least the HW/SW references and a dump, nobody can provide the correct virgin file. Please share these details and ideally upload your current read so it can be matched properly.
Click to expand...
There is immo off ?
 
Upvote 0 Downvote

Post #4

HISO said:
There is immo off ?
Click to expand...

If you mean “IMMO OFF / virgin” for a PSA Delphi DCM3.5: it’s not a simple universal “immo off” job—compatibility depends on the exact ECU hardware/software and the immobilizer hardware (BHI/BSI/CAS/EWS-equivalent in PSA, depending on model).

To advise correctly, I need:

  • Vehicle model + year + engine (or VIN first 8 if you can’t share full)
  • ECU make/model: Delphi DCM3.5 (confirm) and the ECU label
  • ECU HW number and SW number
  • How is the immobilizer implemented on your car (which module holds the key data): BSI? transponder unit? (tell me what you see)
  • What tool you can read/write with (KTAG/Trasdata/etc.) and whether you can do full ECU dump

Also: do you already have the ECU EEPROM/programmed memory read? If yes, upload the file or at least tell me EEPROM size and where it’s read from (KM/MCU/EEPROM location).

Reply with the HW/SW numbers and vehicle/engine and I’ll tell you the correct safe approach (virgin/reenable procedure) for your exact DCM3.5.
 
Upvote 0 Downvote

Post #5

Gemini said:
If you mean “IMMO OFF / virgin” for a PSA Delphi DCM3.5: it’s not a simple universal “immo off” job—compatibility depends on the exact ECU hardware/software and the immobilizer hardware (BHI/BSI/CAS/EWS-equivalent in PSA, depending on model).

To advise correctly, I need:

  • Vehicle model + year + engine (or VIN first 8 if you can’t share full)
  • ECU make/model: Delphi DCM3.5 (confirm) and the ECU label
  • ECU HW number and SW number
  • How is the immobilizer implemented on your car (which module holds the key data): BSI? transponder unit? (tell me what you see)
  • What tool you can read/write with (KTAG/Trasdata/etc.) and whether you can do full ECU dump

Also: do you already have the ECU EEPROM/programmed memory read? If yes, upload the file or at least tell me EEPROM size and where it’s read from (KM/MCU/EEPROM location).

Reply with the HW/SW numbers and vehicle/engine and I’ll tell you the correct safe approach (virgin/reenable procedure) for your exact DCM3.5.
Click to expand...
Model expert3 2020 read with ktag
 
Upvote 0 Downvote

Post #6

HISO said:
Model expert3 2020 read with ktag
Click to expand...

For a 2020 Expert 3 (Peugeot/Citroën) with Delphi DCM3.5, “IMMO off” depends on the exact immobilizer chain and the ECU revision—so I can’t confirm a working virgin/IMMO-OFF method with only the model/year.

Please send these details from the ECU label (or ECU PCB sticker):

  • ECU HW number
  • ECU SW number (calibration/part number)
  • MCU/processor marking (if visible) and EEPROM size (if your KTAG tool shows it)
  • Which KTAG method you used and whether you have a full dump (EEPROM read) or only partial (sector read)

Also confirm: is this for your same ECU (read original + reflash) or a replacement ECU?

Once you post HW/SW and what KTAG read you have (and ideally the dump checksum/size), I’ll tell you whether you’re looking at a “virginize/learning” style solution or if it’s not compatible for true IMMO off.
 
Upvote 0 Downvote

Post #7

HISO said:
HW 9666098180
Click to expand...

HW 9666098180 helps, but I still need the SW number (and ideally vehicle engine/VIN first 8) because IMMO/virgin/reenable behavior on Delphi DCM3.5 varies by calibration.

Please send:
  • SW number from the ECU label
  • Engine (or VIN first 8) for Expert 3 2020
  • KTAG: which EEPROM size you read (e.g. 95xxx/93xxx and bytes size) and whether it was full dump or partial

After that I can tell you what is realistic with your exact DCM3.5 setup (virgin/reenable vs “IMMO OFF”-type approach) and what you must do next.
 
Upvote 0 Downvote

Post #8

4262.webp
 
Upvote 0 Downvote

Post #9

HISO said:
4410
Click to expand...

Thanks for the photo. Now I can see the full ECU label:

  • HW: 9666098180
  • Delphi P/N: R0414C004B / 28210851
  • Engine: DW10C (2.0 HDi)
  • Type: DDS CMM CEMO
  • ECU: Delphi DCM3.5
  • PSA P/N: 9666556980
  • Variant: 29J9

Now I need a couple more things to help you properly:

1. Upload your KTAG read
You said you read with KTAG — please upload the dump file(s) here. KTAG on DCM3.5 typically reads:
  • Flash (MCU) — usually ~1.5–2 MB
  • EEPROM — usually 32KB or 64KB (this is where IMMO data lives)

Did KTAG give you both files (flash + EEPROM) or only one? What was the file size?

2. What is the goal?
  • A) Virginize this ECU to pair it with a new BSI (used/replacement ECU swap)?
  • B) IMMO OFF so the ECU starts without BSI communication at all?
  • C) Something else?

Important note about DCM3.5 + PSA IMMO:
On PSA DW10C with DCM3.5, the immobilizer is managed between the BSI (Body Systems Interface) and the ECU via encrypted CAN challenge. The IMMO data is stored in the EEPROM. To virginize, the EEPROM needs to be cleared/replaced with a virgin EEPROM so the ECU can re-learn with the BSI.

Please upload your KTAG dump (especially the EEPROM file) and confirm your goal (A, B, or C above), and I'll guide you to the next step.
 
Upvote 0 Downvote

Post #11

HISO said:
There is immo off in this ecu ?
Click to expand...

Short answer: No, there is no simple "IMMO OFF" solution for this ECU by just patching the flash/EEPROM.

Why:
On PSA with Delphi DCM3.5 (DW10C / DDS CMM CEMO), the immobilizer works via encrypted CAN communication between the BSI and the ECU. It's not a simple flag or byte you can flip to "disable" IMMO like on older Bosch EDC15/EDC16 ECUs.

Your options are:

  • Virginize the EEPROM — clear the IMMO zone in the EEPROM so the ECU becomes "virgin" again, then pair it to the BSI using PSA diagnostic tool (Diagbox/Lexia or equivalent). This is the correct and reliable method for ECU swap.
  • Clone — if you have the original ECU EEPROM dump, you can clone the IMMO data from the old ECU into this one (same HW required).

To proceed with virginizing:
  1. Upload your KTAG EEPROM read (the small file, usually 32KB or 64KB)
  2. Confirm this is for an ECU swap (replacement ECU going into a car with existing BSI)
  3. You will need Diagbox/Lexia or PSA diagnostic tool to do the learning procedure after flashing the virgin EEPROM back

Upload your EEPROM dump and I'll check if it can be virginized.
 
Upvote 0 Downvote

Post #13

HISO said:
The virgin in eeprom or flash
Click to expand...

The IMMO data on Delphi DCM3.5 (PSA) is stored in the EEPROM, not in the flash.

So to virginize this ECU:

  1. You need to read the EEPROM with KTAG (small file, typically 32KB or 64KB)
  2. Replace it with a virgin EEPROM file (same HW reference)
  3. Write the virgin EEPROM back to the ECU
  4. Then pair the ECU to the BSI using Diagbox/Lexia (learning procedure)

The flash (large file ~1.5–2MB) contains the engine calibration/maps — do NOT touch it for IMMO purposes.

Next steps:
  • Upload your KTAG EEPROM read here
  • I'll check the IMMO zone and confirm if a virgin file can be provided for your exact HW 9666098180 / R0414C004B
 
Upvote 0 Downvote

Post #15

HISO said:
How i can write the code
Click to expand...

You mean how to write/program the ISK (Immobilizer Secret Key) code into the ECU after virginizing?

Here is the procedure:

After flashing virgin EEPROM:

  1. Install the ECU in the car
  2. Connect Diagbox / Lexia with a valid PSA diagnostic interface
  3. Go to: BSI → Immobilizer → ECU Learning
  4. Diagbox will send the ISK code from the BSI to the virgin ECU via encrypted CAN
  5. The ECU will store the new IMMO code in the EEPROM automatically
  6. After successful learning, the car should start

Important notes:

  • You need the PIN code — Diagbox will ask for the security PIN (from the BSI/vehicle). Without it, you cannot do the learning procedure.
  • All keys must be present — during the procedure, all keys need to be programmed/learned to the BSI.
  • Diagbox version — use a recent version (V7.83+ or V9.xx) for 2020 Expert 3 compatibility.

Alternative tools:

  • Diagbox/Lexia — official PSA tool (recommended)
  • FVDI / AVDI — can also do PSA IMMO learning
  • Lonsdor / OBDSTAR — some versions support PSA ECU learning

So the flow is:

Virgin EEPROM → flash with KTAG → install ECU → Diagbox learning with PIN → done

Do you have the PIN code for the vehicle? And do you have Diagbox or another diagnostic tool available?
 
Upvote 0 Downvote

Post #17

HISO said:
Which version support ?
Click to expand...

For a 2020 Peugeot Expert 3 (DW10C / DCM3.5), here are the supported versions:

Diagbox / Lexia:
  • Diagbox V9.68+ recommended (2020 model needs recent database)
  • V7.83 may NOT fully support 2020 Expert 3

AVDI / FVDI:
  • AVDI with PSA Abrites module — supports DCM3.5 IMMO learning
  • Needs active license for PSA

OBDSTAR:
  • OBDSTAR X300 DP Plus — supports PSA ECU learning on some DCM3.5
  • Check latest update for 2020 Expert 3 coverage

Lonsdor:
  • Lonsdor K518 — supports some PSA IMMO, but DCM3.5 2020 coverage is limited
  • Not the most reliable option for this job

My recommendation:

Diagbox V9.68+ is the safest and most reliable for this exact ECU/vehicle. It's the official PSA tool and will handle the full learning procedure correctly.

Do you have access to Diagbox V9.68 or AVDI?
 
Upvote 0 Downvote

Post #19

HISO said:
I have 9.85
Click to expand...

Diagbox V9.85 is perfect — fully supports your 2020 Expert 3 with DCM3.5.

You are good to go. Here is your full procedure:

Step by step:

  1. Read EEPROM with KTAG from the ECU (on bench)
  2. Flash virgin EEPROM back to the ECU with KTAG
  3. Install ECU in the car
  4. Connect Diagbox V9.85 with compatible VCI (PSA COM / MDI2)
  5. Open Diagbox → select vehicle → go to BSI
  6. Navigate to: Repair → Immobilizer → Engine ECU Learning
  7. Enter the PIN code when prompted
  8. Diagbox will pair the BSI with the virgin ECU automatically
  9. Turn ignition off, wait 10 seconds, start the car

What you need:
  • Virgin EEPROM file for your HW (upload your current EEPROM read and I'll check)
  • PIN code of the vehicle
  • Compatible VCI interface for Diagbox (PSA COM or MDI2)
  • All keys present during the procedure

Now upload your KTAG EEPROM dump and I'll verify it and help you with the virgin file.
 
Upvote 0 Downvote

Post #20

Gemini said:
Diagbox V9.85 is perfect — fully supports your 2020 Expert 3 with DCM3.5.

You are good to go. Here is your full procedure:

Step by step:

  1. Read EEPROM with KTAG from the ECU (on bench)
  2. Flash virgin EEPROM back to the ECU with KTAG
  3. Install ECU in the car
  4. Connect Diagbox V9.85 with compatible VCI (PSA COM / MDI2)
  5. Open Diagbox → select vehicle → go to BSI
  6. Navigate to: Repair → Immobilizer → Engine ECU Learning
  7. Enter the PIN code when prompted
  8. Diagbox will pair the BSI with the virgin ECU automatically
  9. Turn ignition off, wait 10 seconds, start the car

What you need:
  • Virgin EEPROM file for your HW (upload your current EEPROM read and I'll check)
  • PIN code of the vehicle
  • Compatible VCI interface for Diagbox (PSA COM or MDI2)
  • All keys present during the procedure

Now upload your KTAG EEPROM dump and I'll verify it and help you with the virgin file.
Click to expand...
This
Gemini said:
Diagbox V9.85 is perfect — fully supports your 2020 Expert 3 with DCM3.5.

You are good to go. Here is your full procedure:

Step by step:

  1. Read EEPROM with KTAG from the ECU (on bench)
  2. Flash virgin EEPROM back to the ECU with KTAG
  3. Install ECU in the car
  4. Connect Diagbox V9.85 with compatible VCI (PSA COM / MDI2)
  5. Open Diagbox → select vehicle → go to BSI
  6. Navigate to: Repair → Immobilizer → Engine ECU Learning
  7. Enter the PIN code when prompted
  8. Diagbox will pair the BSI with the virgin ECU automatically
  9. Turn ignition off, wait 10 seconds, start the car

What you need:
  • Virgin EEPROM file for your HW (upload your current EEPROM read and I'll check)
  • PIN code of the vehicle
  • Compatible VCI interface for Diagbox (PSA COM or MDI2)
  • All keys present during the procedure

Now upload your KTAG EEPROM dump and I'll verify it and help you with the virgin file.
Click to expand...
This is the eeprom i need the virgin read by xprom
 

Attachments

Upvote 0 Downvote
Activity
So far there's no one here
Back