Make sure you're only flashing the same OS into the ECM, if you try and switch OS' using commercial tools, you will brick the ECM. Only use the full programming operation if you absolutely need to (some VATS, Custom OS', or explicitly stated that it's required), otherwise only do calibration writes and you won't have a problem.xadonxander wrote:I just found this site. I will be a regular here now. I am working on a 2009 corvette with the e38 pcm. I normally work on BMW, Ferrari, and Lamborghini where I have done extensive work with their ECU's. I have ktag, kess, carprog, several various VCI's. I am willing to help out. HPTuners has bricked 2 PCM's so far.
Are you able to revive them by flashing a compatible OS via TDS? If you can communicate on a bench harness, that'll be your best bet.
There are 2 CPUs in E38/E67s, main and slave. Only GM's software so far writes the slave CPU, which contains the DBW/ETC OS+calibration. If there's a mismatch between that OS+cal and the main OS, you'll have a dead pedal, loss of comms errors, or other odd behavior. That's if you're switching between the same year OS' but changing vehicle platforms. If you go between OS years, such as 07 -> 09, there are different corresponding ECM hardware service numbers. Tazzi mentions why that's important earlier in this thread (check out his post here: viewtopic.php?f=38&t=6416&start=360#p100054) as the parameter block, which contains the VIN, ECM serial, and so forth, changes. I had this issue in 2011 when I flashed an 07 (main) OS into an 08 ECM using a commercial tool. When reading the VIN, it was in a scrambled/non-standard format. Flashing back to the correct OS/hardware pair resolved it.
