T2 won`t help much. Here is what we have as data.
Now it needs to be cleared what is on the eprom.
I suspect eeprom is stored in the processor, which seem as some variant of 68hc11.
The main bin can be stored to the eprom or inside the processor too.
Noticed some options configuration. Here we might have it at the eprom also.
Someone posted dumps of ccm and I even managed to make a disasembly of them, but couldn`t figure anything specific.
You can read the ccm with flashhack and post the dump too.
Step too. Unsolder the eprom and try to det a dump of it, also put a socket, in case a deeper hackjob will be needed.
We also need to figure what went wrong with the ccm and figure if that consuption is the result of the ccm or something else keeps it alive.
Newer modules have something called go to sleep after predefined time elapsed. Also it sends messages to other modules to wake and sleep them. Something similar might be used here and something might be preventing the ccm to go to low power mode.
Tom H have deeper insight about the vats exchange info between pcm and ccm. It is some password related cycling of some data that is still unclear in the dissasembly.
There was some post somewhere in the corvette forums about repairing ccms, and updating the vins, but was paid top secret stuff. Someone might dig up the threads.
Also adding some datalogging to eehack of that module will not be hard at all, since the stream data is available already. Not so sure about handling dtcs.
Reply With Quote
Bookmarks