17 silverado with prod date 09/16
D70f3525 mcu in a dash
run hours 1224 need 612
idle hours 312 need 160
17 silverado with prod date 09/16
D70f3525 mcu in a dash
run hours 1224 need 612
idle hours 312 need 160
Last edited by nickolasd; 17th October, 2018 at 08:36 PM.
good job, can you share soldering point in cluster?
sharing is the key of success
heres is connection.
with vvdiprog using mcu reflash cable
use 1kOm resistor between RTXD and VCC
green wire FLMD1 goes to pin 118 on mcu, somewhat difficult to solder that wire, pins are very small.
red wire - VCC pin 113 on mcu
yellow wire - RESET pin 114
green - FLMD1 pin 118
orange - RTXD pin 138
black - GROUND pin 31
blue FLMD0 pin 104
Last edited by nickolasd; 16th October, 2018 at 03:15 AM.
BCM solved
only dash left
Heres 2 dash Dflash files with about 30min difference between them. DFlash changes a lot. Pflash stays the same.
who is got some ideas about calculations?
I have compare first file and second file but first read seem bad reading can you share another more one to be sure
too much FFFF ??!!
sharing is the key of success
read is good, it was verified both times and also pflash came out exactly the same both times. my understanding that data moves around every time cpu shuts down and restarts, same thing you can see on a bmw ECUs like msv80, location of data will be different every time.
I know smelecom and jprog and now dp4 do the job but manually, and i don't know where's hours located in this mcu, it's a mystery at this time, but someone know how correct it? let us know if you found it mate
Last edited by mecjp; 18th October, 2018 at 10:53 PM.
sharing is the key of success
What do you think the chances are of being able to CLONE a customers inoperable cluster to a replacement cluster of the same part number using this method? Read via vvdiprog and transferring the file. It SHOULD transfer the security protocol number, vin#, hours, etc, correct? Or am I missing something?
Bookmarks