Is this PCM dead

[Sudsy]

G'day all, have been trying to load a complete file on to this pcm but for some reason i can't read it or write to it. Have used the lock bypass method with the earthing of the pin which i've now done succesfully on a couple of other tuner locked pcms that worked fine. This is what comes up after trying

[11:08:49:113] C:\Users\HP\Desktop\Car stuff\Ls1\LS files\Stock tune VT manual reflashed.bin
[11:08:49:148] Validating 512k file.
[11:08:49:157] Start End Stored Needed Verdict Segment Name
[11:08:49:167] 00000 7FFFD 7F53 7F53 Good Operating system
[11:08:49:182] 08002 13FFF 54B9 54B9 Good Engine calibration
[11:08:49:191] 14002 16DFF 37C8 37C8 Good Engine diagnostics.
[11:08:49:201] 16E02 1BDFF 017C 017C Good Transmission calibration
[11:08:49:217] 1BE02 1C7FF FF8B FF8B Good Transmission diagnostics
[11:08:49:234] 1C802 1E51F B566 B566 Good Fuel system
[11:08:49:250] 1E522 1EE9F 37BC 37BC Good System
[11:08:49:268] 1EEA2 1EF9F 2F23 2F23 Good Speedometer
[11:08:49:285] Requesting operating system ID...
[11:09:09:364] Operating system request failed, checking for a live kernel...
[11:09:19:956] Checking for recovery mode...
[11:09:40:024] PCM is not responding to OSID, kernel version, or recovery mode checks.
[11:09:40:035] Unlock may not work, but we'll try...
[11:09:44:177] Unlock was not successful.

Any ideas what could be the problem or is it a brick?

Thanks Bob

[antus]

Got the debug output? Its either a brick, or you have a wiring problem - power, ignition or data pins. If you are not seeing anything come back from it and its not an electrical problem its a brick.

[Sudsy]

Got the debug output? Its either a brick, or you have a wiring problem - power, ignition or data pins. If you are not seeing anything come back from it and its not an electrical problem its a brick.

All the wiring is good as i have no problem with other ecu's. I guess its a brick. How do i get debug output if it doesn't read anything?

[antus]

In pcmhammer there is another tab. Your output is from the default user tab. Debug will show more detail, and sometimes shows something unexpected that gives a clue whats going on. Yours will probably show nothing at all coming back but if you see hints of a recovery mode or something you might have something you can work with. If it is a brick from a bad flash (not physical damage), you might still be able to recover it with BDM. There are other threads about that and you need to be handy with a soldering iron and need a usbjtag-nt.

[Sudsy]

In pcmhammer there is another tab. Your output is from the default user tab. Debug will show more detail, and sometimes shows something unexpected that gives a clue whats going on. Yours will probably show nothing at all coming back but if you see hints of a recovery mode or something you might have something you can work with. If it is a brick from a bad flash (not physical damage), you might still be able to recover it with BDM. There are other threads about that and you need to be handy with a soldering iron and need a usbjtag-nt.

Fairly handy with a soldering irn but will have to do more studying on the usbitg. Thanks for your replies

[Sudsy]

This was what i found in the debug logger.

[09:47:00:364] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:00:365] Receive timed out. Attempt #5, Timeout #5.
[09:47:00:365] TX: 6C 10 F0 3C 0A
[09:47:02:375] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:02:375] Sending 'test device present' notification.
[09:47:02:376] TX: 8C FE F0 3F
[09:47:04:381] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:04:382] Sending 'test device present' notification.
[09:47:04:382] TX: 8C FE F0 3F
[09:47:06:387] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:06:388] Sending 'test device present' notification.
[09:47:06:389] TX: 8C FE F0 3F
[09:47:08:394] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:08:395] Sending 'test device present' notification.
[09:47:08:395] TX: 8C FE F0 3F
[09:47:10:400] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:10:400] Receive timed out. Attempt #5, Timeout #5.
[09:47:10:400] Operating system query failed: Error
[09:47:10:404] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[09:47:10:406] Sending 'test device present' notification.
[09:47:10:407] TX: 8C FE F0 3F
[09:47:27:070] Sending 'test device present' notification.
[09:47:27:070] TX: 8C FE F0 3F
[09:47:27:079] Using OsID: 0
[09:47:27:084] Suppressing VPW chatter.
[09:47:27:084] TX: 6C FE F0 28 00
[09:47:27:091] Sending 'test device present' notification.
[09:47:27:091] TX: 8C FE F0 3F
[09:47:29:097] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:29:214] Sending seed request.
[09:47:29:216] TX: 6C 10 F0 27 01
[09:47:31:222] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:47:31:227] No response to seed request.
[09:47:31:230] Unlock was not successful.

[antus]

Yep only receive timed out messages, and transmits. nothing to indicate any kind of activity from the pcm being in any state of alive.

This is where you get the usbjtagnt https://www.usbjtag.com/ (though these PCMs use an earlier standard, known as BDM which the usbjtagnt product does include support for)
There is a thread about BDM here: viewtopic.php?t=6215 with lots of info scattered through the thread. There is probably also information on the official site above, and youtube that might be more to the point.
That is assuming the contents of the flash chip are erased, and there is no hardware problem with the PCM.

[NSFW]

I put some info about using that flash tool here:
https://github.com/LegacyNsfw/PcmHacks/wiki/BDM

It's not very user-friendly, and I've only used it about three times since we started the PCM Hammer project, so each time I used it, I had to figure it out all over again. The third time, I took notes.

[Sudsy]

Luckily this is just a spare i picked up. Will take this old fart a while to work out how to do all that so for now it can sit on the shelf while i do some studying lol. Thank you all for your replies