IPC Hammer

[darkman5001]

I would really like to see support for the Trailblazer/Envoy clusters.

[Phoenix]

I would really like to see support for the Trailblazer/Envoy clusters.

Me too!

I've go a 2006 TBSS and would love to know if there is anything I can do as far as reading the stock file to help out.

[roughneck427]

I would absolutely love to be able to disable the "Service TPMS system" message on the cluster of my 2004 Suburban. I made the mistake of "Enabling" TPMS using my Snap-On scanner, and now I can not turn the damn thing off. SMFH

TPMS is controlled in the passenger door module on your truck. I found the commands to turn it on and off on a bench module. If you have the tools to send raw class 2 commands, I can tell you how I did it. Otherwise maybe I can just send you my bench module or something. Send me a PM if you're interested in either option.

Block# - Byte# R/W Description Units
$82-(2) R TPM Enabled Status $00 = No TPM
$01 = TPM equipped

[kur4o]

Anyone know how to recover IPC bricked during flashing.

One is hardbricked, no data being send, the other only dumps a2 status and don`t take any commands.

[NSFW]

I've had my instrument cluster freeze in my Corvette a few times, but it has always returned to normal after a few driving cycles so I haven't investigated it.

Sending the "clear codes" command does nothing, but that's the only thing I really know.

It happened last weekend and went away after a few key-on / key-off cycles. I have a hunch that pulling the fuse might reset it, but I haven't tried that.

It might be interesting to look at the "resume normal communications" messages that PCM Hammer sends after a flash completes. Maybe one of those messages is just getting missed, and should be sent five times just to make sure it gets through.

[kur4o]

I've had my instrument cluster freeze in my Corvette a few times, but it has always returned to normal after a few driving cycles so I haven't investigated it.

Sending the "clear codes" command does nothing, but that's the only thing I really know.

It happened last weekend and went away after a few key-on / key-off cycles. I have a hunch that pulling the fuse might reset it, but I haven't tried that.

It might be interesting to look at the "resume normal communications" messages that PCM Hammer sends after a flash completes. Maybe one of those messages is just getting missed, and should be sent five times just to make sure it gets through.

That issue happens during pcm flashing or reading. It freezes some modules to the point it needs battery power removed to revive them.
I actually at some point investigate the problem and got a solution how to resolve it, just need to remember what it was. Some commands missing at end of flash.[I just remembered the flash routine exit is not correct, it needs to crash pcm[2700-stop opcode] so it sends some data on bus and wake the other modules, the way it is now is to just to return back or something].


The problem I got is IPC bricked during reflashing the IPC[lost of communication], it will be nice if there is a way for easy recovering.

[NSFW]

For P01 and P59, we hang the PCM with "for (;;)" and just wait for the watchdog to reboot it. For P12 it executes a "reset" opcode.

I wonder if the IPC staying frozen due to something else happening on the bus at the same time that the PCM is sending "wake up" messages.

[kur4o]

That is the issue
"for (;;)"

If you want to test for a cure change exiting from code to this

move.l (sp),d0 [opcode 20 17]
stop #$2700 [opcode 4E 72 27 00]

I have seen other modules freezing even on reading, which is very annoying.

[zack4200]

Anyone know how to recover IPC bricked during flashing.

One is hardbricked, no data being send, the other only dumps a2 status and don`t take any commands.

Should be able to do it with minimon. I know FixedUntilBroken has covered it in some of his videos on YouTube but I don't remember which ones.

[NSFW]

That is the issue
"for (;;)"

If you want to test for a cure change exiting from code to this

move.l (sp),d0 [opcode 20 17]
stop #$2700 [opcode 4E 72 27 00]

I have seen other modules freezing even on reading, which is very annoying.

Keep in mind that it doesn't really stop at the "for (;;)" statement.
It only stays in that loop for a fraction of a second before the watchdog forces a reboot.

Is there reason to expect it to send different messages after a watchdog reboot versus after a "stop 2700" reboot?