PowerPCM_Flasher: my tool for E38 and E67

[ocerrr]

Does sps programming tool offers a way to enter custom seed key? Or use gm engineer tool? I tried enter ffff section not worked, but I could miss 0x ,I will try again. The brutle force seed key tool says 3f80 is right key. Or should I use Hptuners to wright entire? Do you know any tool offers seed key input?

[ironduke]

ok, I'm definitely not the most knowledgeable to answer all your questions but..
sps programming does NOT allow you to specify the key used to unlock.

the gm engineer tool that is not allowed here does indeed let you override the key.

As far as this PowerPCM I don't think I've ever tried entering my own key so not sure if it works or if the 0x in front of the key is needed? I think because it shows up in the box I would try entering the 0x in front of 3f80

It sounds like you definitely have a mismatched OS versus eeprom. The only ways I know to fix it is to clone the flash of a known good bin to the ecm or eeprom segment matching the OS or go backwards and write back the correct OS for that eeprom layout..

hpt can do things but I don't use it so I've got no advise there.

[ocerrr]

I will keep this update when I tried something

[ScottyhsvR98]

If you need a good flash from an E38 Ive got mine its an 2007 HSV R8
OS 12612381
Cal 12612380
OS ID AA
BCC YPRZ

[antus]

Yeah, but the reason I mention it is because J2534 (2002) says in table 7.2.1.4 "Raw CAN (flow control not handled by interface)", so if ISO15765-2 CAN includes the description of the transmit OK packet at the end of any sequence - 1 or more packets required to send the payload and then even though we are just doing one packet at a time in raw that could explain the difference and would mean that it is not required for raw which looks like where this is going.

[clyde]

tpepmeie, No. I gave up on the OBDXPro GT and got it working with a MDI1 clone.

clyde, I am also getting the exact same errors on both programs with an E38. Did you ever resolve the issue? I'm using OBDXPro GT also. My device works flawlessly with SPS. I was hoping to use this tool to pull a binary from my ECM after a clean SPS re-place and reprogram.

I am in the USA, this e38 is from a Canadian 2008 Chevrolet Silverado 1500, the other e38 is from a USA 2008 Chevrolet Express 2500. Both have the same (similar) error and both I got off eBay and they should be junkyard pulls. I tried to use the ECU brute force unlocker, but I get the mscorlib error on both computers too.

ECU brute force unlocker-tested with E38,E78, and E92 ecu and gm MDI
Should work with any GM ecu with a 2 byte seed/key and a 10 second timeout between keys
This could take up to 7 days so make sure you have a stable power supply.
using dll from https://github.com/BrianHumlicek/J2534-Sharp
1 - Unlock Ecu
2 - Change starting key from decimal:0 / Hex:0000
3 - Connect to MDI and check connection by reading Vin
4 - Change Send timout from 600 milliseconds
5 - Change Read timout from 600 milliseconds
6 - Enable debug- more feedback
7 - Close Program
8 - Read vin - check connection and ecu
8
1 - OBDX Pro VX

Input Device Number:1
SendCommand Error source: mscorlib
SendCommand Error source: mscorlib
SendCommand Error source: mscorlib
SendCommand Error source: mscorlib
SendCommand Error source: mscorlib
SendCommand Error source: mscorlib
Press any key to exit.

This is the only J2534 device I have (OBDX Pro VX). Since the driver just got released, I'm not sure where the issue might be.

[ironduke]

Hey guys, since the issue seems to be with CAN raw communication and the protocols used here is a VERY quick ISO15765 version.
Should work the exact same and maybe work with more J2534 devices..
Download, unzip and run the exe.. I compiled the J2534 dll into the exe to make it a little easier.. Program is t he same, just compressed/saved differently for whichever you prefer

Please give me some feed back for those having difficulty with the original version.

ECU_brute_force.ISO15765_V0.0.2.7z

(40.88 KiB) Downloaded 39 times

ECU_brute_force.ISO15765_V0.0.2.zip

(41.13 KiB) Downloaded 41 times

[tpepmeie]

Ironduke, thanks sir. It works now... I was able to connect to both E38 and E92. At least read the VIN. haven't tried to unlock yet.

Is there any hope for PowerPCM_Flasher to ever be able to work with the OBDXPro GT? Maybe I would have been better off with a clone MDI for that one.
Best,
Todd

[ironduke]

Ironduke, thanks sir. It works now... I was able to connect to both E38 and E92. At least read the VIN. haven't tried to unlock yet.

Is there any hope for PowerPCM_Flasher to ever be able to work with the OBDXPro GT? Maybe I would have been better off with a clone MDI for that one.
Best,
Todd

Powerpcm will likely not be updated again. The creator was here and graciously gave is this program but really hasn't been seen since, I did just send him an message asking if he would let me release a program using his kernel but since hasn't been here in awhile I have no idea when or if he'll respond. His kernel even if used in another program will only ever read and write the E38 ecm and will only write the calibration segments of the e38, it will not write the OS segment or the eeprom segment containing the vin,serial number, and seed or key.
As far as working with the OBDX Pro GT I don't have one so I cannot say why it's not working. J2534 is kinda a picky beast and it seems gm doesn't always follow the rules and tends to bend them a bit sometimes.. Makes other tools finicky.. Tazzi might make some changes to help it work, but I'm guessing it would be something of a bandaid to make his tool not follow the actual standard.

[geep]

ironduke you may be able to get ahold of him on here http://nefariousmotorsports.com/forum/i ... 58.0title=