pcmhacking.net

Did you click disconnect after reading?? the kernel can stay running otherwise, makes for a lot of weird things happening.. lol..
Did the 08 have a remote start or anything aftermarket in it??

I had assumed the mode $28 message to disable normal communications would take care of the chatter. I know there was an issue with incorrectly built factory radios ignoring the $28 command, but I can't remember which series it was. I wish I had saved the log file now.

The 08 is totally stock. I did use the disconnect option in the tool. I even went into my DrewTech tool afterward and manually sent a mode $20 to resume normal communications. I got a burst of communication on the bus, but it didn't bring the ECM back online.

With that said, the 09 is also stock, except for the radio. I pulled the radio fuse on that one before I started.

I might try the 08 again this weekend. It's also 50% off at the junkyard this weekend, so I might go snag some connectors and a few other things for bench testing.

I kind of want to pull the VINs out of my bin files before I post them.

Hi.

Thanks for your testing

I can not say too much about the tooling issues as i do not have them here on bench.
As discussed, probably a driver issue.
Need to set a periodic message to keep everything alive.
If dll reports not ok it does not behave as specified in protocol specs.


As for the failed download. Yes, if disconnected in boot mode with sbl (kernel) active, it will not respond or behave normal until power off via battery or terminal.
Sorry for that.

Next release will have simple timer function. It will reset engine ecu after some seconds.
But other ECUs should always be fine...

I will check the os numbers you mentioned.
In case you have the "bad" os as dump, please post it or send me.


Updates will still have to wait some time, im busy with other stuff but will come back.
Don't like the state in which the tool is now


Stay healthy and have a good Christmas time...


Daniel

I used the PowerPCM software with a TACTRIX openport2 to read an E38 pcm it read with no problems. I then tried writing to the e38 pcm, again no problems this was done on the bench with a bench harness. Just a shame we can not write the whole tune file.
Thanks to daniel2345 for making this software available.

Attempted to read/write same bin E67 with MDI2 and now Vehicle will not start.

Any suggestions, not sure how to use recovery?



initialising Tool J2534 PassThru
Bosch - MDI...
NOT ok: init: 8

initialising Tool J2534 PassThru
Bosch - MDI...
ok.
connecting...
start diagnostic session (0x10 0x03)...ok.
disable normal communication (0x28)...ok.
security access (0x27)...
request seed...ok.
seed: 0x00002A81
key: 0x000027BB
sending key...ok.
request programming mode...ok.
sending enable programming mode...done.
downloading prog...
busy.
ok.
run prog...ok.
ready to upload flash or download calibration.
erase calib...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
busy...
ok.
done.
download calib...
download progress: 13% (0x008000)
download progress: 25% (0x010000)
download progress: 38% (0x018000)
download progress: 50% (0x020000)
download progress: 63% (0x028000)
download progress: 75% (0x030000)
download progress: 88% (0x038000)
download progress: 100% (0x040000)
done.
validating download...ok, valid.
hit disconnect or read.
upload flash...
upload progress: 4% (0x010000)
upload progress: 7% (0x020000)
upload progress: 10% (0x030000)
upload progress: 13% (0x040000)
upload progress: 16% (0x050000)
upload progress: 19% (0x060000)
upload progress: 22% (0x070000)
upload progress: 25% (0x080000)
upload progress: 29% (0x090000)
upload progress: 32% (0x0A0000)
upload progress: 35% (0x0B0000)
upload progress: 38% (0x0C0000)
upload progress: 41% (0x0D0000)
upload progress: 44% (0x0E0000)
upload progress: 47% (0x0F0000)
upload progress: 50% (0x100000)
upload progress: 54% (0x110000)
upload progress: 57% (0x120000)
upload progress: 60% (0x130000)
upload progress: 63% (0x140000)
upload progress: 66% (0x150000)
upload progress: 69% (0x160000)
upload progress: 72% (0x170000)
upload progress: 75% (0x180000)
upload progress: 79% (0x190000)
upload progress: 82% (0x1A0000)
upload progress: 85% (0x1B0000)
upload progress: 88% (0x1C0000)
upload progress: 91% (0x1D0000)
upload progress: 94% (0x1E0000)
upload progress: 97% (0x1F0000)
upload progress: 100% (0x200000)
done.
validating upload...ok, valid.
disconnecting...ok.

RonVC wrote:Attempted to read/write same bin E67 with MDI2 and now Vehicle will not start.

Let ECM sit for maybe 30 minutes, reflash original bin, engine now starts...

Looking for some help in steps to be followed to bin edit, use the utils fix sum function and re-upload to vehicle.
Went into P601 mode.... maybe not using correctly or possible flaw in the sum fix routine for E67?

Any coaching would be appreciated.

Guessing something is wrong with the bin, post it up here so we can check it and go from there.. If it turns out to be the bin I'd suggest another topic since it's not an issue wth the tool.. first suggestion is to try UniversalPatcher for a quick easy check to see what's wrong.
https://github.com/joukoy/UniversalPatcher

ironduke wrote:Guessing something is wrong with the bin, post it up here so we can check it and go from there..

Kewlio, any help would be appreciated, bin attached.
Original and then HexEdit and tool sum corrected attached. Hint look for ID: 12635735 SUM: 0x7E6A and ID: 12635733 SUM: 0x39D2

ironduke wrote:If it turns out to be the bin I'd suggest another topic since it's not an issue wth the tool..

Might be right, but P601 suggests sum's are wrong?

ironduke wrote: first suggestion is to try UniversalPatcher for a quick easy check to see what's wrong.
https://github.com/joukoy/UniversalPatcher

Ok, will take a look, thx.

RonVC wrote:

ironduke wrote:If it turns out to be the bin I'd suggest another topic since it's not an issue wth the tool..

Might be right, but P601 suggests sum's are wrong?

ironduke wrote: first suggestion is to try UniversalPatcher for a quick easy check to see what's wrong.
https://github.com/joukoy/UniversalPatcher

Ok, will take a look, thx.

This software (tool) just reads and writes the binary, it does not care what the checksums are or if they are valid or not.

Take your working bin, do your hex edit, use UniversalPatcher to correct the checksums, then use this software to write the resulting binary ...

[edit]
My appologies, I have been informed this tool does have checksum correction ...