PCM Hammer P12 development

They go by many names, P01, P10, P12, P59, E38, VPW, '0411 etc.
User avatar
antus
Site Admin
Posts: 9017
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer fails on P12

Post by antus »

yes the earlier attempts you mentioned where the watchdog is happy and the pcm stops responding because its in a infinite loop.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
Gampy
Posts: 2332
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer fails on P12

Post by Gampy »

I have never said the Watchdog was happy, never!

I just said the logs look the same.

I have had 3 tests return to the os, the os then sent the ack ...
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
antus
Site Admin
Posts: 9017
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer fails on P12

Post by antus »

ok then I dont think your seeing the difference in the log im talking about. I'll annotate.

normal start of process:

Code: Select all

[05:42:30:181]  VPW Explorer - P12 ONLY TEST Build 824.9.1.3 darkman5001 (2/23/2022, 5:36 PM)
[05:42:30:191]  Initializing J2534 Device
[05:42:30:194]  Loaded DLL
[05:42:30:196]  Connected to the device.
[05:42:30:199]  Battery Voltage is: 13.174
[05:42:30:202]  Protocol Set
[05:42:30:202]  Device initialization complete.
[05:42:53:819]  Querying operating system of current PCM.
[05:42:53:833]  TX: 6C 10 F0 3C 0A
[05:42:53:872]  RX: 6C F0 10 7C 0A 00 C0 5B C0 41 41
[05:42:53:873]  OSID: 12606400
[05:42:53:878]  Suppressing VPW chatter.
[05:42:53:879]  TX: 6C FE F0 28 00
[05:42:53:886]  Sending 'test device present' notification.
[05:42:53:887]  TX: 8C FE F0 3F
[05:42:53:904]  RX: 6C F0 10 68 00
[05:42:53:906]  Ignoring chatter: 6C F0 10 68 00
[05:42:53:908]  Sending seed request.
[05:42:53:908]  TX: 6C 10 F0 27 01
[05:42:53:943]  RX: 6C F0 10 67 01 7A 9E
[05:42:53:944]  Parsing seed value.
[05:42:53:949]  Sending unlock request (7A9E, B05C)
[05:42:53:949]  TX: 6C 10 F0 27 02 B0 5C
[05:42:53:979]  RX: 6C F0 10 67 02 34
[05:42:53:980]  Unlock succeeded.
[05:42:53:982]  Sending 'test device present' notification.
[05:42:53:983]  TX: 8C FE F0 3F
[05:42:53:993]  Loaded M:\GM IMMO Testing\VPWExplorer\Test Kernels\watchdog.bin
[05:42:53:996]  Sending upload request for kernel size 56, loadaddress FF2000
[05:42:53:997]  Requesting permission to upload kernel.
[05:42:54:000]  TX: 6C 10 F0 34
[05:42:54:021]  RX: 6C F0 10 74 00 44
[05:42:54:022]  Found response, Success
[05:42:54:022]  Upload permission granted.
[05:42:54:025]  Going to load a 56 byte kernel to 0xFF2000
[05:42:54:026]  Sending end block payload with offset 0x0, start address 0xFF2000, length 0x38.
[05:42:54:026]  Sending 'test device present' notification.
[05:42:54:027]  TX: 8C FE F0 3F
Kernel with watchdog loop goes up and executes correctly, confirmed by there being no further RX from the pcm ~2 minutes later by the end of the log. Its alive but it can not speak :thumbup:

Code: Select all

[05:42:54:101]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F   
[05:42:56:157]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:42:56:158]  Sending 'test device present' notification.
[05:42:56:158]  TX: 8C FE F0 3F
[05:42:58:177]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:42:58:177]  Sending 'test device present' notification.
[05:42:58:178]  TX: 8C FE F0 3F
[05:43:00:193]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:00:193]  Sending 'test device present' notification.
[05:43:00:194]  TX: 8C FE F0 3F
[05:43:02:204]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:02:204]  Sending 'test device present' notification.
[05:43:02:205]  TX: 8C FE F0 3F
[05:43:04:211]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:04:211]  Sending 'test device present' notification.
[05:43:04:212]  TX: 8C FE F0 3F
[05:43:04:218]  WritePayload: Upload request failed.
[05:43:04:398]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:06:454]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:06:455]  Sending 'test device present' notification.
[05:43:06:455]  TX: 8C FE F0 3F
[05:43:08:463]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:08:468]  Sending 'test device present' notification.
[05:43:08:471]  TX: 8C FE F0 3F
[05:43:10:484]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:10:487]  Sending 'test device present' notification.
[05:43:10:490]  TX: 8C FE F0 3F
[05:43:12:492]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:12:495]  Sending 'test device present' notification.
[05:43:12:498]  TX: 8C FE F0 3F
[05:43:14:501]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:14:504]  Sending 'test device present' notification.
[05:43:14:507]  TX: 8C FE F0 3F
[05:43:14:510]  WritePayload: Upload request failed.
[05:43:14:672]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:16:743]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:16:746]  Sending 'test device present' notification.
[05:43:16:749]  TX: 8C FE F0 3F
[05:43:18:762]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:18:765]  Sending 'test device present' notification.
[05:43:18:768]  TX: 8C FE F0 3F
[05:43:20:782]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:20:785]  Sending 'test device present' notification.
[05:43:20:788]  TX: 8C FE F0 3F
[05:43:22:790]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:22:793]  Sending 'test device present' notification.
[05:43:22:796]  TX: 8C FE F0 3F
[05:43:24:813]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:24:817]  Sending 'test device present' notification.
[05:43:24:819]  TX: 8C FE F0 3F
[05:43:24:823]  WritePayload: Upload request failed.
[05:43:24:984]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:27:041]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:27:044]  Sending 'test device present' notification.
[05:43:27:047]  TX: 8C FE F0 3F
[05:43:29:061]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:29:063]  Sending 'test device present' notification.
[05:43:29:066]  TX: 8C FE F0 3F
[05:43:31:082]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:31:085]  Sending 'test device present' notification.
[05:43:31:089]  TX: 8C FE F0 3F
[05:43:33:098]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:33:101]  Sending 'test device present' notification.
[05:43:33:104]  TX: 8C FE F0 3F
[05:43:35:118]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:35:121]  Sending 'test device present' notification.
[05:43:35:124]  TX: 8C FE F0 3F
[05:43:35:127]  WritePayload: Upload request failed.
[05:43:35:304]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:37:371]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:37:374]  Sending 'test device present' notification.
[05:43:37:377]  TX: 8C FE F0 3F
[05:43:39:388]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:39:391]  Sending 'test device present' notification.
[05:43:39:394]  TX: 8C FE F0 3F
[05:43:41:404]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:41:407]  Sending 'test device present' notification.
[05:43:41:410]  TX: 8C FE F0 3F
[05:43:43:423]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:43:426]  Sending 'test device present' notification.
[05:43:43:429]  TX: 8C FE F0 3F
[05:43:45:443]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:45:446]  Sending 'test device present' notification.
[05:43:45:449]  TX: 8C FE F0 3F
[05:43:45:451]  WritePayload: Upload request failed.
[05:43:45:630]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:47:699]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:47:702]  Sending 'test device present' notification.
[05:43:47:705]  TX: 8C FE F0 3F
[05:43:49:707]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:49:710]  Sending 'test device present' notification.
[05:43:49:712]  TX: 8C FE F0 3F
[05:43:51:727]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:51:730]  Sending 'test device present' notification.
[05:43:51:733]  TX: 8C FE F0 3F
[05:43:53:742]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:53:746]  Sending 'test device present' notification.
[05:43:53:748]  TX: 8C FE F0 3F
[05:43:55:751]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:55:754]  Sending 'test device present' notification.
[05:43:55:757]  TX: 8C FE F0 3F
[05:43:55:760]  WritePayload: Upload request failed.
[05:43:55:922]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:43:57:991]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:43:57:994]  Sending 'test device present' notification.
[05:43:57:997]  TX: 8C FE F0 3F
[05:44:00:012]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:00:016]  Sending 'test device present' notification.
[05:44:00:020]  TX: 8C FE F0 3F
[05:44:02:022]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:02:025]  Sending 'test device present' notification.
[05:44:02:028]  TX: 8C FE F0 3F
[05:44:04:042]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:04:045]  Sending 'test device present' notification.
[05:44:04:048]  TX: 8C FE F0 3F
[05:44:06:049]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:06:052]  Sending 'test device present' notification.
[05:44:06:055]  TX: 8C FE F0 3F
[05:44:06:058]  WritePayload: Upload request failed.
[05:44:06:235]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:44:08:304]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:08:307]  Sending 'test device present' notification.
[05:44:08:311]  TX: 8C FE F0 3F
[05:44:10:324]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:10:327]  Sending 'test device present' notification.
[05:44:10:330]  TX: 8C FE F0 3F
[05:44:12:336]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:12:339]  Sending 'test device present' notification.
[05:44:12:342]  TX: 8C FE F0 3F
[05:44:14:355]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:14:358]  Sending 'test device present' notification.
[05:44:14:361]  TX: 8C FE F0 3F
[05:44:16:370]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:16:373]  Sending 'test device present' notification.
[05:44:16:376]  TX: 8C FE F0 3F
[05:44:16:379]  WritePayload: Upload request failed.
[05:44:16:556]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:44:18:613]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:18:616]  Sending 'test device present' notification.
[05:44:18:619]  TX: 8C FE F0 3F
[05:44:20:620]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:20:623]  Sending 'test device present' notification.
[05:44:20:626]  TX: 8C FE F0 3F
[05:44:22:634]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:22:637]  Sending 'test device present' notification.
[05:44:22:641]  TX: 8C FE F0 3F
[05:44:24:652]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:24:655]  Sending 'test device present' notification.
[05:44:24:658]  TX: 8C FE F0 3F
[05:44:26:660]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:26:663]  Sending 'test device present' notification.
[05:44:26:666]  TX: 8C FE F0 3F
[05:44:26:669]  WritePayload: Upload request failed.
[05:44:26:832]  TX: 6D 10 F0 36 80 00 38 FF 20 00 61 00 00 14 61 00 00 06 4E FA FF F6 4E 71 4E 71 4E 71 4E 71 4E 75 13 FC 00 55 00 FF FA 55 13 FC 00 AA 00 FF FA 55 08 B9 00 07 00 FF FA 21 08 F9 00 07 00 FF FA 21 4E 75 18 2F
[05:44:28:900]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:28:903]  Sending 'test device present' notification.
[05:44:28:906]  TX: 8C FE F0 3F
[05:44:30:920]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:30:923]  Sending 'test device present' notification.
[05:44:30:926]  TX: 8C FE F0 3F
[05:44:32:929]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:32:933]  Sending 'test device present' notification.
[05:44:32:935]  TX: 8C FE F0 3F
[05:44:34:951]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:34:955]  Sending 'test device present' notification.
[05:44:34:958]  TX: 8C FE F0 3F
[05:44:36:959]  ReadMsgs OBDError: ERR_BUFFER_EMPTY
[05:44:36:962]  Sending 'test device present' notification.
[05:44:36:965]  TX: 8C FE F0 3F
[05:44:36:968]  WritePayload: Upload request failed.
[05:44:37:082]  WritePayload: Giving up.
[05:44:37:085]  Could not upload kernel to PCM, remainder payload not accepted.
[05:44:37:088]  Failed to upload kernel to PCM


Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
antus
Site Admin
Posts: 9017
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer fails on P12

Post by antus »

in the bin direct read from the flash chip I think this is talking to the DLC.

FFFF6CC0 is equivalent to FF6CC0 and in the other PCMs the DLC is in the vicinity of FF6xxx

We also have a loop and were comparing a register to $40 near the end which is consistent with looking for a completion code at the end of the packet. I also see a reference to 3F which sounds like a VPW error code.

I found this by looking for bytes 00 40 then looking closer to find one thats used in a compare opcode, then looked at the function around it.

Code: Select all

ROM:000D5948 ; =============== S U B R O U T I N E =======================================
ROM:000D5948
ROM:000D5948
ROM:000D5948 sub_D5948:                              ; CODE XREF: sub_8900:loc_8A10↑p
ROM:000D5948                 movem.l d4-d7/a4-a5,-(sp)
ROM:000D594C                 moveq   #0,d4
ROM:000D594E                 movea.l #$FFFF6CC0,a1
ROM:000D5954                 movea.l #$FFFF6BA0,a4
ROM:000D595A
ROM:000D595A loc_D595A:                              ; CODE XREF: sub_D5948+92↓j
ROM:000D595A                 moveq   #0,d7
ROM:000D595C                 moveq   #3,d5
ROM:000D595E                 moveq   #2,d6
ROM:000D5960                 movea.l #$FFFF6BE0,a5
ROM:000D5966                 move.l  d4,d0
ROM:000D5968                 move.l  d0,d1
ROM:000D596A                 add.l   d0,d0
ROM:000D596C                 add.l   d0,d1
ROM:000D596E                 adda.l  d1,a5
ROM:000D5970
ROM:000D5970 loc_D5970:                              ; CODE XREF: sub_D5948+3C↓j
ROM:000D5970                 move.b  d6,(a5,d7.l)
ROM:000D5974                 move.l  d7,d0
ROM:000D5976                 addq.b  #1,d0
ROM:000D5978                 moveq   #0,d7
ROM:000D597A                 move.b  d0,d7
ROM:000D597C                 move.l  d7,d0
ROM:000D597E                 sub.l   d5,d0
ROM:000D5980                 moveq   #3,d1
ROM:000D5982                 and.l   d0,d1
ROM:000D5984                 bne.s   loc_D5970
ROM:000D5986                 cmp.b   d5,d7
ROM:000D5988                 bcc.s   loc_D59C4
ROM:000D598A
ROM:000D598A loc_D598A:                              ; CODE XREF: sub_D5948+7A↓j
ROM:000D598A                 move.b  d6,(a5,d7.l)
ROM:000D598E                 movea.l a5,a0
ROM:000D5990                 move.l  d7,d0
ROM:000D5992                 addq.b  #1,d0
ROM:000D5994                 moveq   #0,d1
ROM:000D5996                 move.b  d0,d1
ROM:000D5998                 adda.l  d1,a0
ROM:000D599A                 move.b  d6,(a0)
ROM:000D599C                 movea.l a5,a0
ROM:000D599E                 move.l  d7,d0
ROM:000D59A0                 addq.b  #2,d0
ROM:000D59A2                 moveq   #0,d1
ROM:000D59A4                 move.b  d0,d1
ROM:000D59A6                 adda.l  d1,a0
ROM:000D59A8                 move.b  d6,(a0)
ROM:000D59AA                 movea.l a5,a0
ROM:000D59AC                 move.l  d7,d0
ROM:000D59AE                 addq.b  #3,d0
ROM:000D59B0                 moveq   #0,d1
ROM:000D59B2                 move.b  d0,d1
ROM:000D59B4                 adda.l  d1,a0
ROM:000D59B6                 move.b  d6,(a0)
ROM:000D59B8                 move.l  d7,d0
ROM:000D59BA                 addq.b  #4,d0
ROM:000D59BC                 moveq   #0,d7
ROM:000D59BE                 move.b  d0,d7
ROM:000D59C0                 cmp.b   d5,d7
ROM:000D59C2                 bcs.s   loc_D598A
ROM:000D59C4
ROM:000D59C4 loc_D59C4:                              ; CODE XREF: sub_D5948+40↑j
ROM:000D59C4                 andi.b  #$3F,(a4,d4.l) ; '?'
ROM:000D59CA                 clr.b   (a1,d4.l)
ROM:000D59CE                 move.l  d4,d0
ROM:000D59D0                 addq.b  #1,d0
ROM:000D59D2                 moveq   #0,d4
ROM:000D59D4                 move.b  d0,d4
ROM:000D59D6                 cmp.w   #$40,d4 ; '@'
ROM:000D59DA                 blt.w   loc_D595A
ROM:000D59DE                 move.l  (sp)+,d4
ROM:000D59E0                 move.l  (sp)+,d5
ROM:000D59E2                 move.l  (sp)+,d6
ROM:000D59E4                 move.l  (sp)+,d7
ROM:000D59E6                 movea.l (sp)+,a4
ROM:000D59E8                 movea.l (sp)+,a5
ROM:000D59EA                 rts
ROM:000D59EA ; End of function sub_D5948
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
Gampy
Posts: 2332
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer fails on P12

Post by Gampy »

Just like my first micro-kernel test ...
FF2000-VPWExplorer_debugLog_20220221@175558.txt
(46.28 KiB) Downloaded 238 times
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
antus
Site Admin
Posts: 9017
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer fails on P12

Post by antus »

yep that looks like it executed and the watchdog is happy
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
Gampy
Posts: 2332
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer fails on P12

Post by Gampy »

That would be impressive, considering it was all stock P01/P59,

Code: Select all

    #define DLC_CONFIGURATION          (*(unsigned char *)0x00FFF600)
    #define DLC_INTERRUPTCONFIGURATION (*(unsigned char *)0x00FFF606)
    #define DLC_TRANSMIT_COMMAND       (*(unsigned char *)0x00FFF60C)
    #define DLC_TRANSMIT_FIFO          (*(unsigned char *)0x00FFF60D)
    #define DLC_STATUS                 (*(unsigned char *)0x00FFF60E)
    #define DLC_RECEIVE_FIFO           (*(unsigned char *)0x00FFF60F)
    #define WATCHDOG1                  (*(unsigned char *)0x00FFFA27)
    #define WATCHDOG2                  (*(unsigned char *)0x00FFD006)
:o :shock:

The success I've had is simple, and this is one of them,
[09:13:25:618] VPW Explorer - P12 ONLY TEST Build 824.9.1.3 darkman5001 (2/23/2022, 5:36 PM)
[09:13:25:638] Initializing J2534 Device
[09:13:25:644] Loaded DLL
[09:13:25:653] Connected to the device.
[09:13:25:663] Battery Voltage is: 13.174
[09:13:25:672] Protocol Set
[09:13:25:675] Device initialization complete.
[09:15:41:576] Querying operating system of current PCM.
[09:15:41:637] TX: 6C 10 F0 3C 0A
[09:15:41:699] RX: 6C F0 10 7C 0A 00 C0 5B C0 41 41
[09:15:41:701] OSID: 12606400
[09:15:41:721] Suppressing VPW chatter.
[09:15:41:723] TX: 6C FE F0 28 00
[09:15:41:730] Sending 'test device present' notification.
[09:15:41:733] TX: 8C FE F0 3F
[09:15:41:754] RX: 6C F0 10 68 00
[09:15:41:757] Ignoring chatter: 6C F0 10 68 00
[09:15:41:759] Sending seed request.
[09:15:41:761] TX: 6C 10 F0 27 01
[09:15:41:793] RX: 6C F0 10 67 01 7A 9E
[09:15:41:794] Parsing seed value.
[09:15:41:798] Sending unlock request (7A9E, B05C)
[09:15:41:800] TX: 6C 10 F0 27 02 B0 5C
[09:15:41:830] RX: 6C F0 10 67 02 34
[09:15:41:832] Unlock succeeded.
[09:15:41:837] Sending 'test device present' notification.
[09:15:41:838] TX: 8C FE F0 3F
[09:15:41:862] Loaded M:\GM IMMO Testing\VPWExplorer\Test Kernels\simple-routine-P12-FF2000.bin
[09:15:41:872] Sending upload request for kernel size 4, loadaddress FF2000
[09:15:41:874] Requesting permission to upload kernel.
[09:15:41:882] TX: 6C 10 F0 34
[09:15:41:909] RX: 6C F0 10 74 00 44
[09:15:41:910] Found response, Success
[09:15:41:912] Upload permission granted.
[09:15:41:917] Going to load a 4 byte kernel to 0xFF2000
[09:15:41:919] Sending end block payload with offset 0x0, start address 0xFF2000, length 0x4.
[09:15:41:920] Sending 'test device present' notification.
[09:15:41:923] TX: 8C FE F0 3F
[09:15:41:984] TX: 6D 10 F0 36 80 00 04 FF 20 00 4E 75 00 00 02 66
[09:15:42:021] RX: 6C F0 10 76 00 73
[09:15:42:022] Found response, Success
[09:15:42:025] Kernel upload 100% complete.
[09:15:42:032] Kernel uploaded to PCM succesfully...
[09:15:42:036] Sending 'test device present' notification.
[09:15:42:038] TX: 8C FE F0 3F
It executed my code, returned to the os, the os sent the ack.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
Gampy
Posts: 2332
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer fails on P12

Post by Gampy »

O-yea, I also asked darkman5001 if he had to reboot his PCM after your bin, he says no!

If I'm not mistaken your code is an indefinite loop ... That would require a reboot to get the PCM responsive again, correct ??
That is if your code was running and the dog was happy ...
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
User avatar
antus
Site Admin
Posts: 9017
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: PCM Hammer fails on P12

Post by antus »

I dont know what to make of it. Im still looking for DLC registers.

The detail about not needing to reboot paints a different picture, as does having what is clearly the wrong watchdog in your test. But I dont know why it would go silent without a working watchdog loop.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
User avatar
Gampy
Posts: 2332
Joined: Sat Dec 15, 2018 7:38 am

Re: PCM Hammer fails on P12

Post by Gampy »

I'm looking at the current direction as if it were a C void routine ...

The os receives the upload, executes the upload, the upload does it's thing then exits returning control to the os, the os then sends the ack.

I think kur4o said something like, it's a different beast, took me long enough to realize what he was saying, that's when I said I'm going in a different direction ... The direction of an empty C routine, I got the ack.
Intelligence is in the details!

It is easier not to learn bad habits, then it is to break them!

If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
Post Reply