GM 16216588 - Hacking

Post by **antus** » Sat May 07, 2016 9:59 am

Vl400s delco flash tool can do bin or cal. I'd expect most tools do do it this way. Certainly if your changing OS you'd want to select write bin or full program or the like. After that cal only would be fine.

Post by **Tazzi** » Sat May 07, 2016 11:08 am

quadstar87 wrote: Yea, they are slightly shifted. I guess what i'm wondering is if the complete operating system code is overwritten when you flash a calibration, however.

Antus answered that nicely

From what the commercial softwares do, looks like they have a definition file made up for each operating system for each ECU which defines the locations of each table/parameter ect for the calibration.

Flashing just the cal section would flash in technically.. but the OS would look for the tables in the locations that it has pre-defined which might not match that calibration file?

Post by **antus** » Sat May 07, 2016 6:54 pm

Not sure if this is any use to you. It can convert 128k OBD2 chev PCM bins to cal and vice versa, and calculate/verify checksum. It can also scramble/descramble bins. Note that this is NOT for the Aussie 128k ALDL bins on the Aussie pcms.

quadstar87 · Post by **quadstar87** » Sun May 08, 2016 2:02 pm

OK so my real misunderstanding was calling the flash data a calibration. Actually what we have compiled here is the entire OS and Calibration into a single file which lets us calculate the checksum.

Again the banked code had thrown me off. I'll plan to make my tool just do entire writes for now and see if we can get the latest OS to run on different trucks with different flags set correctly!

Antus, this tool is invaluable! Much better than hand slicing the files in HxD!

Post by **antus** » Sun May 08, 2016 2:24 pm

I'd recommend you dont do a write entire if the pcm has the same calibration id as what your writing. There is potential to brick the pcm between the erase and a successfull write of the os, so doing an os write when you dont need to is an unnecessary risk.

quadstar87 · Post by **quadstar87** » Mon May 09, 2016 11:49 am

antus wrote:I'd recommend you dont do a write entire if the pcm has the same calibration id as what your writing. There is potential to brick the pcm between the erase and a successfull write of the os, so doing an os write when you dont need to is an unnecessary risk.

Oh joy, good to know.

quadstar87 · Post by **quadstar87** » Tue May 10, 2016 7:10 am

First major setback today. Looks like I need to de-solder some flash chips and add sockets.

Post by **Tazzi** » Tue May 10, 2016 9:46 am

antus wrote:I'd recommend you dont do a write entire if the pcm has the same calibration id as what your writing. There is potential to brick the pcm between the erase and a successfull write of the os, so doing an os write when you dont need to is an unnecessary risk.

Are these essentially the LS1 ECUs.. but... from a truck?

Post by **antus** » Tue May 10, 2016 9:50 am

These are closer to the vx/xy pcm, but with a vpw chip in them. They look the same, with different colour connectors. HC11 processor, 128k bins. Also running diesel engines. There is also an earlier version thats still ALDL but with more or less the same software on them. Chevy express vans I think. 6.5L.

quadstar87 · Post by **quadstar87** » Tue May 10, 2016 11:24 am

What are the chances I could setup one of these with an NVRAM instead of socketing the flash? Or are those not very universal?

GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking

Re: GM 16216588 - Hacking