PCM Hammer Release 014
- Jim Blackwood
- Posts: 32
- Joined: Fri Dec 27, 2019 2:28 am
- cars: 1971 MGB/340 Buick/TKO/Jag IRS
2002 Lincoln Blackwood
1996 MCI 102DL3
Re: PCM Hammer Release 014
That does seem to be the case. I spent a lot of time on it today, reconfiguring, reloading, updating drivers, trying different computers, trying variations. All very unscientific. In the end I did not definitively prove anything, but the last steps I took before achieving success involved shutting down bluetooth and removing the OBDLink from every bluetooth devices list on every device in the area, including most notably cell phones and computers and then being very careful to enable and load the OBDL on only the computer I wanted to test. Success came first on the desktop unit... not really helpful for datalogging but a good indicator. After that I got the tuning laptop to work. Quite a success for me because I was honestly considering buying another laptop (which I do not need).
So I agree, the issue here does seem to be bluetooth interference. Although after those driver upgrades I can't swear to it as the only cause. I wish I had more to offer.
I suppose eventually Windows will be taught to make the bluetooth connection that you want and ignore the others but that may be awhile. Android seems to do it a little better at this point. But it puts me in mind of the old IRQ and address assignments we used to have to make manually back in the stone ages. As much work as it was, sometimes things seemed to be simpler back then. Odds are they were not.
Anyway, thanks again for the help, and you guys are the greatest. Onward we go.
Jim
So I agree, the issue here does seem to be bluetooth interference. Although after those driver upgrades I can't swear to it as the only cause. I wish I had more to offer.
I suppose eventually Windows will be taught to make the bluetooth connection that you want and ignore the others but that may be awhile. Android seems to do it a little better at this point. But it puts me in mind of the old IRQ and address assignments we used to have to make manually back in the stone ages. As much work as it was, sometimes things seemed to be simpler back then. Odds are they were not.
Anyway, thanks again for the help, and you guys are the greatest. Onward we go.
Jim
-
- Posts: 397
- Joined: Wed Jul 05, 2017 8:30 am
- cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E - Location: North TX, USA
Re: PCM Hammer Release 014
Hi all,Jim Blackwood wrote: But it puts me in mind of the old IRQ and address assignments we used to have to make manually back in the stone ages. As much work as it was, sometimes things seemed to be simpler back then. Odds are they were not.
Anyway, thanks again for the help, and you guys are the greatest. Onward we go.
Jim
Jim I, too remember those "good old days" before windows 95, guess it shows our age a bit eh?
Mike
-
- Posts: 2
- Joined: Sun May 10, 2020 3:44 am
- cars: 2004 GMC Yukon XL Denali
2009 Dodge Charger SXT
1998 Chevrolet Silverado
Re: PCM Hammer Release 014
I just used PCM Hammer 014 to recover my P59 1mb PCM, OS Version 12587603. LSDroid wrote a cal to it and couldn't recover it no matter how many times it tried. I did a write full flash with PCM Hammer and I was saved. Thank you very much for all of your hard work. At the end you asked to share my results here, so here it is:
Code: Select all
[12:16:46:114] PCM Hammer 014
[12:16:51:457] Thanks for using PCM Hammer.
[12:16:52:487] Voltage: 11.9V
[12:16:52:499] Elm ID: ELM327 v1.3a
[12:16:52:535] ScanTool device ID: STN1155 v4.5.2
[12:17:27:198] C:\Users\jeremy\Desktop\stockpcmread.bin
[12:17:27:203] Validating 1024k file.
[12:17:27:206] Start End Stored Needed Verdict Segment Name
[12:17:27:218] 00000 FFFFD D2E8 D2E8 Good Operating system
[12:17:27:221] 08002 162CF 24A6 24A6 Good Engine calibration
[12:17:27:224] 162D2 195FF 8045 8045 Good Engine diagnostics.
[12:17:27:229] 19602 1D8AF 28A6 28A6 Good Transmission calibration
[12:17:27:232] 1D8B2 1E1AF E3E9 E3E9 Good Transmission diagnostics
[12:17:27:236] 1E1B2 1F6BF EBD7 EBD7 Good Fuel system
[12:17:27:240] 1F6C2 1FEAF 21FF 21FF Good System
[12:17:27:245] 1FEB2 1FFDF 0A2A 0A2A Good Speedometer
[12:17:27:250] Requesting operating system ID...
[12:17:39:070] Operating system request failed, checking for a live kernel...
[12:17:45:121] Checking for recovery mode...
[12:17:45:202] PCM is in recovery mode.
[12:17:46:642] PCM Unlock not required
[12:17:46:647] Unlock succeeded.
[12:17:46:771] 4X communications disabled by configuration.
[12:17:46:783] Requesting permission to upload kernel.
[12:17:46:927] Upload permission granted.
[12:17:48:431] Kernel upload 9% complete.
[12:17:49:869] Unexpected response to STPX payload:
[12:17:52:413] Kernel upload 22% complete.
[12:17:53:967] Unexpected response to STPX payload:
[12:17:56:956] Unexpected response to STPX payload:
[12:17:58:854] Kernel upload 35% complete.
[12:18:01:058] Unexpected response to STPX payload:
[12:18:02:659] Kernel upload 48% complete.
[12:18:04:289] Kernel upload 61% complete.
[12:18:05:859] Unexpected response to STPX payload:
[12:18:06:189] Unexpected response to STPX header: STOPPED
[12:18:07:573] Kernel upload 74% complete.
[12:18:09:056] Kernel upload 87% complete.
[12:18:10:716] Kernel upload 100% complete.
[12:18:11:060] Kernel Version: 010301BB
[12:18:11:064] Kernel uploaded to PCM succesfully.
[12:18:11:278] PCM and image file are both operating system 12587603
[12:18:11:552] Flash chip: AMD AM29F800BB, 1mb
[12:18:11:643] Calculating CRCs from file...
[12:18:11:654] Requesting CRCs from PCM...
[12:18:23:510] Range File CRC PCM CRC Verdict Purpose
[12:18:27:647] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[12:18:31:940] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:18:36:366] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:18:40:761] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:18:44:864] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:18:48:950] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:18:53:050] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[12:18:56:747] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[12:19:00:169] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[12:19:03:834] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[12:19:08:055] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[12:19:11:935] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[12:19:16:499] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[12:19:20:490] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[12:19:24:446] 010000-01FFFF E476D9A5 A50F3C90 Different Calibration
[12:19:27:542] 008000-00FFFF 16B0669E 9C49015C Different Calibration
[12:19:29:461] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[12:19:31:451] 004000-005FFF 07AF2472 07AF2472 Same Parameter
[12:19:33:787] 000000-003FFF AE42598F AE42598F Same Boot
[12:19:34:042] Note that mismatched Parameter blocks are to be expected.
[12:19:34:050] Parameter data can change every time the PCM is used.
[12:19:34:235] Clearing trouble codes.
[12:19:35:483] Elapsed time 00:01:48.8302247
[12:22:50:490] C:\Users\jeremy\Desktop\stockpcmread.bin
[12:22:50:505] Validating 1024k file.
[12:22:50:515] Start End Stored Needed Verdict Segment Name
[12:22:50:526] 00000 FFFFD D2E8 D2E8 Good Operating system
[12:22:50:536] 08002 162CF 24A6 24A6 Good Engine calibration
[12:22:50:545] 162D2 195FF 8045 8045 Good Engine diagnostics.
[12:22:50:554] 19602 1D8AF 28A6 28A6 Good Transmission calibration
[12:22:50:564] 1D8B2 1E1AF E3E9 E3E9 Good Transmission diagnostics
[12:22:50:572] 1E1B2 1F6BF EBD7 EBD7 Good Fuel system
[12:22:50:581] 1F6C2 1FEAF 21FF 21FF Good System
[12:22:50:589] 1FEB2 1FFDF 0A2A 0A2A Good Speedometer
[12:22:50:598] Requesting operating system ID...
[12:23:01:986] Operating system request failed, checking for a live kernel...
[12:23:07:996] Checking for recovery mode...
[12:23:09:166] PCM is in recovery mode.
[12:23:10:478] PCM Unlock not required
[12:23:10:486] Unlock succeeded.
[12:23:10:534] 4X communications disabled by configuration.
[12:23:10:543] Requesting permission to upload kernel.
[12:23:10:586] Upload permission granted.
[12:23:11:744] Kernel upload 9% complete.
[12:23:13:339] Kernel upload 22% complete.
[12:23:14:794] Kernel upload 35% complete.
[12:23:16:173] Kernel upload 48% complete.
[12:23:17:432] Kernel upload 61% complete.
[12:23:18:617] Kernel upload 74% complete.
[12:23:20:195] Kernel upload 87% complete.
[12:23:21:475] Kernel upload 100% complete.
[12:23:21:938] Kernel Version: 010301BB
[12:23:21:944] Kernel uploaded to PCM succesfully.
[12:23:22:348] PCM and image file are both operating system 12587603
[12:23:22:609] Flash chip: AMD AM29F800BB, 1mb
[12:23:22:690] Calculating CRCs from file...
[12:23:22:703] Requesting CRCs from PCM...
[12:23:34:458] Range File CRC PCM CRC Verdict Purpose
[12:23:38:356] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[12:23:42:384] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:23:46:462] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:23:50:529] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:23:54:192] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:23:57:964] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:24:01:601] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[12:24:05:425] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[12:24:08:959] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[12:24:12:624] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[12:24:16:207] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[12:24:19:811] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[12:24:23:494] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[12:24:27:055] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[12:24:30:595] 010000-01FFFF E476D9A5 A50F3C90 Different Calibration
[12:24:33:131] 008000-00FFFF 16B0669E 9C49015C Different Calibration
[12:24:34:832] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[12:24:36:742] 004000-005FFF 07AF2472 07AF2472 Same Parameter
[12:24:38:870] 000000-003FFF AE42598F AE42598F Same Boot
[12:24:38:931] Processing range 010000-01FFFF
[12:24:38:940] Erasing.
[12:24:39:554] Writing...
[12:24:39:562] Address % Done Time Remaining
[12:24:39:665] 0x010000 0% Measuring write speed...
[12:24:41:214] 0x010400 1% Measuring write speed...
[12:24:42:827] Unexpected response to STPX payload:
[12:24:42:951] Unexpected response to STPX header: OK
[12:24:43:424] Unexpected response to STPX payload: ?
[12:24:43:796] Unexpected response to STPX header:
[12:24:45:143] 0x010800 2% Measuring write speed...
[12:24:46:693] 0x010C00 3% Measuring write speed...
[12:24:48:173] 0x011000 4% Measuring write speed...
[12:24:49:719] 0x011400 5% 03:16
[12:24:51:303] 0x011800 6% 03:05
[12:24:52:908] 0x011C00 7% 02:58
[12:24:54:269] 0x012000 8% 02:48
[12:24:55:861] 0x012400 9% 02:43
[12:24:57:898] 0x012800 10% 02:43
[12:24:59:525] 0x012C00 11% 02:39
[12:25:01:025] 0x013000 12% 02:34
[12:25:02:518] 0x013400 13% 02:30
[12:25:03:902] 0x013800 14% 02:26
[12:25:05:510] 0x013C00 15% 02:23
[12:25:06:966] 0x014000 16% 02:20
[12:25:08:745] 0x014400 17% 02:18
[12:25:10:408] 0x014800 18% 02:16
[12:25:12:092] 0x014C00 19% 02:14
[12:25:13:522] 0x015000 20% 02:11
[12:25:14:821] 0x015400 21% 02:08
[12:25:16:111] 0x015800 22% 02:05
[12:25:17:526] 0x015C00 23% 02:02
[12:25:18:988] 0x016000 25% 02:00
[12:25:20:408] 0x016400 26% 01:57
[12:25:21:807] 0x016800 27% 01:55
[12:25:23:156] 0x016C00 28% 01:53
[12:25:24:705] 0x017000 29% 01:51
[12:25:26:109] 0x017400 30% 01:49
[12:25:27:346] 0x017800 31% 01:46
[12:25:29:148] 0x017C00 32% 01:45
[12:25:30:545] Unexpected response to STPX payload:
[12:25:32:258] 0x018000 33% 01:46
[12:25:33:578] 0x018400 34% 01:44
[12:25:35:799] 0x018800 35% 01:43
[12:25:40:466] Unexpected response to STPX payload:
[12:25:43:600] 0x018C00 36% 01:52
[12:25:45:373] 0x019000 37% 01:50
[12:25:48:107] Unexpected response to STPX payload:
[12:25:49:980] 0x019400 38% 01:53
[12:25:51:260] 0x019800 39% 01:50
[12:25:52:967] 0x019C00 40% 01:48
[12:25:54:288] 0x01A000 41% 01:45
[12:25:55:916] 0x01A400 42% 01:43
[12:25:58:192] 0x01A800 43% 01:42
[12:25:59:865] 0x01AC00 44% 01:39
[12:26:01:227] 0x01B000 45% 01:37
[12:26:02:902] 0x01B400 46% 01:35
[12:26:04:176] 0x01B800 47% 01:32
[12:26:05:606] 0x01BC00 48% 01:30
[12:26:06:906] 0x01C000 50% 01:28
[12:26:08:263] 0x01C400 51% 01:25
[12:26:09:577] 0x01C800 52% 01:23
[12:26:10:929] 0x01CC00 53% 01:21
[12:26:12:289] 0x01D000 54% 01:19
[12:26:13:656] 0x01D400 55% 01:16
[12:26:14:964] 0x01D800 56% 01:14
[12:26:16:805] 0x01DC00 57% 01:13
[12:26:18:305] 0x01E000 58% 01:10
[12:26:19:792] 0x01E400 59% 01:09
[12:26:21:136] 0x01E800 60% 01:06
[12:26:22:688] 0x01EC00 61% 01:05
[12:26:24:067] 0x01F000 62% 01:03
[12:26:25:459] 0x01F400 63% 01:01
[12:26:26:827] 0x01F800 64% 00:59
[12:26:28:310] 0x01FC00 65% 00:57
[12:26:29:666] Retry count for this block: 5
[12:26:29:673] Processing range 008000-00FFFF
[12:26:29:679] Erasing.
[12:26:30:115] Writing...
[12:26:30:122] Address % Done Time Remaining
[12:26:30:163] 0x008000 66% 00:55
[12:26:31:502] 0x008400 67% 00:53
[12:26:32:903] 0x008800 68% 00:51
[12:26:34:307] 0x008C00 69% 00:49
[12:26:35:787] 0x009000 70% 00:48
[12:26:37:193] 0x009400 71% 00:46
[12:26:38:815] 0x009800 72% 00:44
[12:26:40:541] 0x009C00 73% 00:42
[12:26:42:020] 0x00A000 75% 00:41
[12:26:43:366] 0x00A400 76% 00:39
[12:26:44:860] 0x00A800 77% 00:37
[12:26:46:277] 0x00AC00 78% 00:35
[12:26:47:566] 0x00B000 79% 00:33
[12:26:48:931] 0x00B400 80% 00:32
[12:26:50:191] 0x00B800 81% 00:30
[12:26:51:528] 0x00BC00 82% 00:28
[12:26:52:939] 0x00C000 83% 00:26
[12:26:54:258] 0x00C400 84% 00:25
[12:26:55:657] 0x00C800 85% 00:23
[12:26:57:108] 0x00CC00 86% 00:21
[12:26:58:664] 0x00D000 87% 00:19
[12:27:00:081] 0x00D400 88% 00:18
[12:27:01:456] 0x00D800 89% 00:16
[12:27:03:301] 0x00DC00 90% 00:14
[12:27:05:220] 0x00E000 91% 00:13
[12:27:06:751] 0x00E400 92% 00:11
[12:27:08:082] 0x00E800 93% 00:09
[12:27:09:516] 0x00EC00 94% 00:08
[12:27:10:809] 0x00F000 95% 00:06
[12:27:12:143] 0x00F400 96% 00:04
[12:27:13:522] Unexpected response to STPX payload:
[12:27:15:140] Unexpected response to STPX payload:
[12:27:15:210] Unexpected response to STPX header: NO DATA
[12:27:16:028] Unexpected response to STPX payload: ?
[12:27:17:963] Unexpected response to STPX payload:
[12:27:18:220] Unexpected response to STPX header: STOPPED
[12:27:19:927] 0x00F800 97% 00:03
[12:27:21:785] Unexpected response to STPX payload:
[12:27:22:550] Unexpected response to STPX header: STOPPED
[12:27:24:164] 0x00FC00 98% 00:01
[12:27:25:572] Retry count for this block: 5
[12:27:25:578] Calculating CRCs from file...
[12:27:25:590] Requesting CRCs from PCM...
[12:27:25:875] Range File CRC PCM CRC Verdict Purpose
[12:27:30:213] 0F0000-0FFFFF 8D0F8F91 8D0F8F91 Same OperatingSystem
[12:27:34:071] 0E0000-0EFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:27:37:807] 0D0000-0DFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:27:41:650] 0C0000-0CFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:27:44:357] 0B0000-0BFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:27:48:158] 0A0000-0AFFFF A50F3C90 A50F3C90 Same OperatingSystem
[12:27:51:632] 090000-09FFFF 7DA5C19F 7DA5C19F Same OperatingSystem
[12:27:54:123] 080000-08FFFF CDDEAE4C CDDEAE4C Same OperatingSystem
[12:27:56:358] 070000-07FFFF D006BDC7 D006BDC7 Same OperatingSystem
[12:27:58:758] 060000-06FFFF D2B04EC0 D2B04EC0 Same OperatingSystem
[12:28:02:237] 050000-05FFFF 36511E94 36511E94 Same OperatingSystem
[12:28:05:597] 040000-04FFFF F6B0E81A F6B0E81A Same OperatingSystem
[12:28:07:761] 030000-03FFFF A97E3395 A97E3395 Same OperatingSystem
[12:28:11:670] 020000-02FFFF EE1B7BAD EE1B7BAD Same OperatingSystem
[12:28:15:367] 010000-01FFFF E476D9A5 E476D9A5 Same Calibration
[12:28:24:367] 008000-00FFFF 16B0669E 16B0669E Same Calibration
[12:28:35:035] 006000-007FFF 85B5BB36 85B5BB36 Same Parameter
[12:28:36:077] 004000-005FFF 07AF2472 07AF2472 Same Parameter
[12:28:59:326] 000000-003FFF AE42598F AE42598F Same Boot
[12:29:32:471] All relevant ranges are identical.
[12:29:32:479] Write-request messages had to be re-sent 10 times.
[12:29:32:487] We're not sure how much retrying is normal for a write operation on a 1024kb PCM.
[12:29:32:494] Please help by sharing your results in the PCM Hammer thread at pcmhacking.net.
[12:29:43:620] Clearing trouble codes.
[12:30:39:746] Elapsed time 00:07:29.2526958
[12:32:03:825] VIN query failed: Timeout
Re: PCM Hammer Release 014
Quite a few reattempts and unexpected responses there, maybe not the cleanest connection??
Your Local Aussie Reverse Engineer
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
Contact for Software/Hardware development and Reverse Engineering
Site:https://www.envyouscustoms.com
Mob:+61406 140 726
-
- Posts: 42
- Joined: Sun Jan 26, 2020 11:41 pm
- cars: 1970 Chevy El Camino with an LM7 modern GM engine.
2013 Chevrolet SS Camaro
Re: PCM Hammer Release 014
At the beginning, is 11.9 volts on the ragged edge of being too low?
Rick
Rick
Re: PCM Hammer Release 014
Good point about the voltage - 11.9 volts seems on the low side. We should probably add something to check for low voltage before reading or writing. That'll take some effort since every device is a bit different, but eventually someone is going to get burned by that. I don't know what the lower limit is, but anything under 12 should probably at least come with a warning.
That said, it did succeed... so I wonder if LS Droid was getting derailed by whatever it is that that led PCM Hammer to print those "unexpected response" messages.
It's great that it worked, but I suggest addressing the connection quality issues before doing any more flashes, just in case. Do you get roughly the same number of "unexpected response" messages if you do a test write? If so then you could try disconnecting other modules, redoing connections, routing wires away from interference, etc, until the test writes go smoothly.
That said, it did succeed... so I wonder if LS Droid was getting derailed by whatever it is that that led PCM Hammer to print those "unexpected response" messages.
It's great that it worked, but I suggest addressing the connection quality issues before doing any more flashes, just in case. Do you get roughly the same number of "unexpected response" messages if you do a test write? If so then you could try disconnecting other modules, redoing connections, routing wires away from interference, etc, until the test writes go smoothly.
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
-
- Posts: 397
- Joined: Wed Jul 05, 2017 8:30 am
- cars: 2001 Pontiac Grand AM SE
LD9 2.4l I4, 4T40E
2005 Chevrolet Venture
LA1 3400 V6, 4T65E - Location: North TX, USA
Re: PCM Hammer Release 014
Hi all,
I believe Pete has LSDroid give warning if the voltage is below 12.2v, or some such value.
Mike
I believe Pete has LSDroid give warning if the voltage is below 12.2v, or some such value.
Mike
-
- Posts: 2
- Joined: Sun May 10, 2020 3:44 am
- cars: 2004 GMC Yukon XL Denali
2009 Dodge Charger SXT
1998 Chevrolet Silverado
Re: PCM Hammer Release 014
The battery had been disconnected a dozen times. I had the battery on a maintainer, not a good charger. There is a warning about voltage in LSDroid, which came on after the umpteenth attempt. The device I was using was an OBDLink LX. The new 4.7.1 firmware didn't like to play with LSDroid, I had problems reading, so I backed it off a couple versions to 4.5.2. I'm not sure if the ELM 1.4b had anything to do with it. I'm very happy that PCM Hammer worked. I just want to give any information that I can to help. The LSDroid was a little confusing at first, but it is also a tiny screen version of complicated software. The help documents were great, maybe if I had RTFM in the beginning I would not have had such a hard time with it.
Re: PCM Hammer Release 014
A battery maintainer is probably just fine. The PCMs with Intel flash only need about 3/4 amp during writes, and the AMD versions use even less (1/4 amp? I don't remember).
Please don't PM me with technical questions - start a thread instead, and send me a link to it. That way I can answer in public, and help other people who have the same question. Thanks!
Re: PCM Hammer Release 014
Can you add the
p04 info to pcminfo.cs pretty pretty plz
case 12201465:
case 12201463:
this.KeyAlgorithm = 14;
this.Description = "P04 intel";
this.ImageBaseAddress = 0x0;
this.ImageSize = 512 * 1024;
this.KernelBaseAddress = 0x9090
break;
is this correct for adding kernel base address
p04 info to pcminfo.cs pretty pretty plz
case 12201465:
case 12201463:
this.KeyAlgorithm = 14;
this.Description = "P04 intel";
this.ImageBaseAddress = 0x0;
this.ImageSize = 512 * 1024;
this.KernelBaseAddress = 0x9090
break;
is this correct for adding kernel base address