PDA

View Full Version : Digiprog 3 V4.94: Problem with writing to ATMEL EEPROM



2008TBSS
29th December, 2015, 07:38 PM
I have a 2008 Chevy Trailblazer SS that I hooked up the correct plug (Plug 1) properly to the chip (ATMEL 8 pin EEPROM) on a spare odometer board for this SUV and plugged the other end of the cable into the port on the Digiprog3. Next, I powered up the Digiprog3 and from Main Menu I selected CAR/TRUCK ? CHEVROLET and scrolled down and selected TRAILBLAZER. I then selected the check button to read the chip data. In KM, the old odometer reading displayed to 195030 which translates to 121186 miles which is correct. By way of comparison, if I don?t have the plug 1 connected it showed some bogus number like 1270000. When I entered the new odometer reading in Kilometers and selected the check button, a message appears to check the odometer reading which shows the old/original number of 195030 Kilometers not the new odometer reading. I then unplugged everything and went through the steps to read and program the correct odometer board chip multiple times but it never stored the new odometer reading to the odometer board chip. I even tried another plug 01 cable and it still did not work. I followed the directions on the web page and video below:
https://www.youtube.com/watch?v=61MznrvTdRw&feature=youtu.be
http://gmtnation.com/forums/threads/trailblazer-mileage-correction-with-digiprog-3-odometer-programmer.13579/
Please let me know if I?m possibly missing something that would prevent this EEPROM chip from saving the new odometer reading.

tavicu21
29th December, 2015, 08:18 PM
not red correct in circuit.desolder and work 100%

clusters
29th December, 2015, 08:33 PM
Ignore this post, bad info. :banghead:

2008TBSS
30th December, 2015, 12:17 AM
Hello,
Thank you for getting back to me. I hooked up Plug 01/2 to the ATMEL 8 pin EEPROM the same as it is in the YouTube video I posted in my first message. Then at the Main Menu I selected EEPROM – EEPROM – READ – 95.. – S95080. After reading, all 7Ds are displayed. By way of comparison, when I select Main Menu – EEPROM – EEPROM – READ – 95.. – S95020, the data is displayed on the first two rows:
0000| 12 7D FF FF FF D5 FF FF FF FF FF FF 12 7D FF FF
0010| FF D5 FF FF FF FF FF FF 12 7D FF FF FF D5 FF FF

Also, in your message, I see that you stated that it’s a 95080 and a different algorithm in a different location. Does this mean I’m possibly using the wrong chip? It's a bit lousy that the manual really doesn't provide enough guidance for performing this procedure. In addition, as for posting the file, I tried to use the DiaProg3 Setup program that came on the disk that I got with the programmer but it doesn’t see the device. Any advice would be greatly appreciated.

2008TBSS
30th December, 2015, 12:20 AM
Hello,

Thank you for getting back to me. I'm not sure what you mean by "not red correct in circuit." Maybe you mean that the 01/2 CLIP is upside down on the ATMEL 8 pin EEPROM. Please advise...

raf0468
30th December, 2015, 12:41 AM
he means that some eeprom don't read or write properly in circuit whilst soldered on board..
he wants you to desolder eeprom off the circuit board and read..

2008TBSS
30th December, 2015, 01:22 AM
For this 2008 Trailblazer SS, can the odometer be reprogrammed using the 01/2 plug with the EEPROM soldered on the printed circuit board or via some other method, possibly another programmer such as the GM TECH II? Don't want to full with unsoldering this chip if I don't have to being I'm concerned that I would damage the chip or printed circuit traces.

clusters
30th December, 2015, 01:27 AM
Hello,
Thank you for getting back to me. I hooked up Plug 01/2 to the ATMEL 8 pin EEPROM the same as it is in the YouTube video I posted in my first message. Then at the Main Menu I selected EEPROM – EEPROM – READ – 95.. – S95080. After reading, all 7Ds are displayed. By way of comparison, when I select Main Menu – EEPROM – EEPROM – READ – 95.. – S95020, the data is displayed on the first two rows:
0000| 12 7D FF FF FF D5 FF FF FF FF FF FF 12 7D FF FF
0010| FF D5 FF FF FF FF FF FF 12 7D FF FF FF D5 FF FF

Also, in your message, I see that you stated that it’s a 95080 and a different algorithm in a different location. Does this mean I’m possibly using the wrong chip? It's a bit lousy that the manual really doesn't provide enough guidance for performing this procedure. In addition, as for posting the file, I tried to use the DiaProg3 Setup program that came on the disk that I got with the programmer but it doesn’t see the device. Any advice would be greatly appreciated.
OK, that's a standard S95P02 chip algorithm and I must have been mistaken. **Make sure you write it as S95P02**
But the 12 7D D5 should be 121186.1 Km To calculate a new mileage, enter the mileage into hex calculator X 10 (as decimal) then convert to hex.

Possible the Digi wrote the wrong address for the third byte, try this string and see what it gives you.

0000: 12 7D FF FF FF FF FF FF FF FF FF D4 12 7D FF FF
0010: FF FF FF FF FF FF FF D4 12 7D FF FF FF FF FF FF
0020: FF FF FF D4

clusters
30th December, 2015, 01:28 AM
For this 2008 Trailblazer SS, can the odometer be reprogrammed using the 01/2 plug with the EEPROM soldered on the printed circuit board or via some other method, possibly another programmer such as the GM TECH II? Don't want to full with unsoldering this chip if I don't have to being I'm concerned that I would damage the chip or printed circuit traces.
Done plenty of earlier Trailblazers in circuit with Digi with no problems. No, a Tech2 will not work for this.

clusters
30th December, 2015, 01:38 AM
One more thing, are you powering this on the bench afterwards to check the mileage or in the truck? They might have gone to two locations in the 2007 up.

Try powering it on the bench to see if it is good using the pinout below.

2008TBSS
30th December, 2015, 01:53 AM
Glad to hear that I don't have to unsolder the EEPROM to program this unit. The used cluster I'm practicing on has 121186 miles on it. When using the Digiprog3, do I need to enter the new odometer reading as KM or miles being the Digiprog3 shows KM when it powers on and I don't see anyway to change it on the programmer? In reading on the Internet, I found that if I put in the correct reading in kilometers, the amount will convert to US miles when I press the button to switch to miles. Is this correct?

Thanks!

clusters
30th December, 2015, 02:07 AM
Yes, if the Digi is displaying old mileage as KM, then convert your new mileage to Km before you enter it.

If it's not writing properly, maybe between reading and writing the clip is coming loose. :dontknow:

Clean the eeprom really well with alcohol and a stiff brush before clipping onto it.

All I know is that Digi does these easily in circuit.

2008TBSS
30th December, 2015, 02:16 AM
My preference is to bench test this unit before installing it so the pinout will be very handy. Also, I'm not clear what you mean by "gone to two locations in the 2007 up." Please let me know what you are advising for me to check. Thanks!

clusters
30th December, 2015, 02:17 AM
You can ignore that comment, I thought you changed it and put it back in the truck to test it.

2008TBSS
30th December, 2015, 02:36 AM
I took your advise and cleaned the EEPROM leads then used the Digiprog3 to read the chip. Again it displayed:
0000| 12 7D FF FF FF D5 FF FF FF FF FF FF 12 7D FF FF
0010| FF D5 FF FF FF FF FF FF 12 7D FF FF FF D5 FF FF
0020| FF FF FF FF 12 17 73 54 40 02 76 96 0F 00 00 0F

As you noted, 127DD5 converts to 121186. This unit was sold to me with 121186 miles on it so maybe I should convert the new odometer reading from miles to hex, enter it and then bench test it to see if it displays miles instead of KM.

2008TBSS
30th December, 2015, 03:01 AM
I used the Digiprog3 to read the EEPROM. Without changing any hex values, if I select EEPROM - WRITE - (Message WRITE OLD DATA WILL BE DESTROYED) press the check button, write bar goes across and no messages are displayed. When I changed the hex values and then attempted to write to the chip the message "ERROR CANCEL" pops up. I even entered the same hex value that you had
0000: 12 7D FF FF FF FF FF FF FF FF FF D4 12 7D FF FF
0010: FF FF FF FF FF FF FF D4 12 7D FF FF FF FF FF FF
0020: FF FF FF D4
and got the same message.

Also, not sure if I asked, but going the route MAIN MENU CAR/TRUCK, CHEVROLET - TRAILBLAZER - Press Check button - KM (NEW) Entered new KM then pressed the check button doesn't work. Should this method work or can you only change the mileage by changing the hex values within the EEPROM section for the 2008 TBSS? I assume only changing the hex value works otherwise you would have advised that I go this route. :-)

clusters
30th December, 2015, 03:23 AM
Either way works to change those.

You may not be getting a good connection on the eeprom, the chinese clips that come with those are garbage. If this is the first time you've used it, you should double check the wiring on the clip, cable pinouts in attachment.

The 110V transformers are also garbage, try using the lighter plug adapter to power the Digi.

You should set the eeprom type to S95P02 for those.

2008TBSS
30th December, 2015, 03:33 AM
What's funny is the new 01 plug that came with the new Digiprog3 unit did not work being when it read the chip, it showed all FFs. I actually purchased a new 01 plug on Amazon and this plug appears to read the EEPROM but won't write to it when any hex value is changed. I think I will give up for this evening and try again tomorrow. Thanks! :-)

2008TBSS
30th December, 2015, 10:43 PM
Hello, Today I selected the correct EEPROM type S95P02 and after selecting EEPROM - READ, the hex data was displayed (appears the same as yesterday and the hex converts to the original odometer reading. After reading the chip, I selected EEPROM - WRITE without changing any of the hex values, I then get the message (WRITE OLD DATA WILL BE DESTROYED). Then if I select the checkbox, the WRITE bar goes across and no other messages are displayed. In restarting the unit and reading the data again, if I change the hex values for the new odometer reading in rows 0000 thru 0020 and select EEPROM - WRITE, the ERROR CANCEL message pops up. Wondering if possibly writing the new hex values right after reading it may not be the proper way to do it or maybe I'm entering the hex values wrong (seems pretty straight forward). Also, I went back to the MAIN MENU - CAR/TRUCK - CHEVROLET - TRAILBLAZER - selected the Checkbox with plug 01/2 connected. Old KM reading shows 195030 which translates to 121k miles which is correct. I entered the new mileage in KMs and selected the Check button. On the right, it shows WRITE with the new reading, but in the center of the screen it shows CHECK WRITTEN VALUE - 195030 KM. Seems to me that this should show the new miles in KMs that I just entered. When I go back through and read the EEPROM data, it still shows the same hex values. In addition, I went out to my vehicle and uses the car charger and received the same results. Any additional ideas will be greatly appreciated. :-)

clusters
30th December, 2015, 11:14 PM
Check the wiring on your cable with a meter using the pinouts I posted before, and possibly replace the DB 25 connector on the end, your unit is not writing to the chip for some reason. If this is the first dash you've tried with Digi, it may be a bad clone.

I wish you had mentioned the write error in the first place, could have saved a lot of time.

Nothing to do with what hex values you enter, it should write whatever you put in it.

sterling
31st December, 2015, 02:55 AM
victor

Sent from my Hudl HT7S3 using Tapatalk

2008TBSS
31st December, 2015, 03:40 AM
If I successfully read the EEPROM then without changing any hex values select EEPROM – WRITE and the WRITE bar goes across without any error message, did the programmer successfully overwrite the existing data with the same data? By way of comparison, when I read the data again and unhook the plug 1/02 cable before writing to the chip, the ERROR CANCEL message pops up after I attempt to write to it which I assume is normal. So it seems strange that when I change the hex values and try to write to the EEPROM, the ERROR CANCEL message pops up being rewriting the existing values seems to work.

Also, this is my 2nd new Digiprog3 that I got off of eBay within the last month. With the first system, the touchscreen did not work well and the 1/02 plug was broken (wires broken on clip). I purchased a new 1/02 off of Amazon and got the same results with both Digiprog3s. In addition, the 2nd Digiprog3’s plug 1/02 was defective out of the box so I will check the pinout of the two plugs tomorrow.

2008TBSS
31st December, 2015, 03:43 AM
Duplicate message

clusters
31st December, 2015, 06:45 AM
If I successfully read the EEPROM then without changing any hex values select EEPROM ? WRITE and the WRITE bar goes across without any error message, did the programmer successfully overwrite the existing data with the same data?




No it did not overwrite the data, verify is part of the write process using the eeprom menu. It writes the data, re-reads the eeprom, and compares the read data to the buffer in the Digi. Writing the same data to the eeprom gives no error because when it verifies it, the data in the eeprom matches the data in the buffer.

Error with no eeprom connected is because the verify re-read will be all FF and doesn't match the data in the buffer. Error after changing the file is because it didn't write and the unmodified data in the eeprom doesn't match the modified data in the buffer.

You either have a bad cable, clip, connection, or the units are doorstops. :)

2008TBSS
3rd January, 2016, 03:57 AM
Hello, Using your attached diagram, I checked the pin outs of the 01/2 cable I have been using and it matches your diagram. Also, today, I received another 01/2 cable from Amazon and received the same results. Using EEPROM S95P02 I can read and save but to the Digiprog3 but when I change the hex values, save it, then attempt to write to the EEPROM, I receive the ERROR CANCEL message. Possibly from all of this tinkering around with this EEPROM chip, could I have possibly damaged its ability to write to it? If so, should I still be able to read it? Would you advise possibly getting another GM instrument cluster and attempt to write it in order to validate whether the problem is with the programmer or cluster? Or how about powering this cluster up by applying 12vdc and ground to the proper terminals to see if the LCD display comes to ready and shows the existing odometer reading? If it powers up properly, would that indicate that the EEPROM is most likely ok? Thankfully, the company I purchased it through offers a money back guarantee so worse case I can get my money back if I got another defective Digiprog3.

XmoDDeR
3rd January, 2016, 02:44 PM
no one would get that many bad ones , first of all the clips they send the with are crap buy and original clip wire up and have a go at it . after it works if you want to keep dropping money like that bu a major tool , or simply buy an UPA its great and cheap choice.

2008TBSS
4th January, 2016, 12:44 AM
Hello, Thank you for providing me with your excellent feedback once again. In regards to a UPA, could you please provide me more info on what that is and where I can buy one? As for this POS, I'll send it back after I get a UPA. Thanks!

2008TBSS
5th January, 2016, 04:11 AM
Hello, The EEPROM ATMEL identification number on the 08 Chevy odometer board I'm working on is 742 25020AN SE27. Just to clarify, should I be able to program this with using ST 01 clip on plug or possibly does this chip need to be unsoldered and programmed? In your earlier reply, I recall you mentioning that I should be able to program the EEPROM will it soldered on the board but in providing you with the chip's part number, I just wanted to double check.

Also, can you tell me where I can purchase a genuine ST 01 cable for the Digiprog3? In performing a search on the Internet, it appears that the ones I found are reproductions for the clone. I've purchased two of the reproduction ST 01 cables off of Amazon (link below) and while I can read the EEPROM chip with these cables, I can't write to it even though the pinouts look correct. Thanks!

http://www.amazon.com/gp/product/B00X79Z1GE?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

clusters
5th January, 2016, 02:29 PM
Before you buy anything more, fire up your soldering iron and make a proper Cable 47, if you're going to be using this unit much you'll need one. Then solder wires directly to the legs of the chip, making sure you have the pinout correct using the pic below.

If it still won't write, unsolder the chip and try it. Still won't write, your units are crap.

2008TBSS
6th January, 2016, 12:42 AM
Hello, I looked in my Digiprog3 master kit and found cable 47. I will attempt to solder the wires to the EEPROM legs as you noted in the attachment and will let you if it works. Also, is it possible to purchase ATMEL EEPROM chips for this cluster in case I fry this one or just want to try it with the programmer? The number on the chip is 742 25020AN SE27.

ralphie25
10th September, 2016, 01:30 AM
Hello, I looked in my Digiprog3 master kit and found cable 47. I will attempt to solder the wires to the EEPROM legs as you noted in the attachment and will let you if it works. Also, is it possible to purchase ATMEL EEPROM chips for this cluster in case I fry this one or just want to try it with the programmer? The number on the chip is 742 25020AN SE27.

Hi, Im sorry for asking. Where you able to get it working? I am going through the same issues. I have built a new cable with new clips and not able to write back to the eeprom.

clusters
10th September, 2016, 02:13 AM
Unlikely he is going to answer, he hasn't been here since then I don't believe. Try unsoldering the eeprom to program it AFTER you save a copy of the original file. I haven't done a 2008 yet, so I'm not sure what is going on, maybe some sort of write protection? :dontknow:

You should be able to use an eeprom from any 2000-2006 full size truck cluster if you want to replace it, they program with no problems with Digiprog as S95P02 or using the Trailblazer option.