PDA

View Full Version : Bootloader Rejected error during reading calibration data



Godwin1245
January 11th, 2009, 10:40 AM
FlashScan V2 - 2.5.6
EFILive Tune 7.5.x

LS1 1998, PCM 16239740, OPSYS 19980100
This is in a 33 Ford, with an Street and Perfomance Wire harness so I don't have all the bells and whistles of the 98 TA the engine came out of.

I'm trying to figure out why the car won't fire after it was taken apart to be painted. It ran fine before it was torn down. While it was being painted, I had the PCM shipped to Street and Performance to have some misc sensors removed and stuff and suspect the PCM now has issues, hence my buying the EFILive setup to help me figure out the problem.

The problem I'm having, beside the car not firing :ranting:, was when I tried to use the read calibration data of EFILive Tune. I'm assuming the 98 PCM can be read this way, and that may by first mistake. I have read the other posts on Bootloader issues and have tried turning off high speed and used Alt keys as well. The controller is set to Gen III LS1 97-98. Check Status does go Green when the process starts. All attempts end with the same error of:

Bootloader rejected.

Reason:
Unhandled mode $34 response
[$6C,$F0,$10,$74,$00,$99]


It happens during step 4 of Initializing PCM. Here is the what the on screen session says:

17:01:27.689: Scanning for EFILive FlashScan V2 USB
17:01:30.267: Scanning for EFILive FlashScan V2 HAPI
17:01:30.423: Interface firmware version: 2.6.5
17:01:30.501: Interface firmware model: FSV2
17:01:30.532: Interface firmware version: 2.6.5
17:01:30.564: Interface firmware date: Oct 28, 2008
17:01:30.611: FlashScan serial number: <deleted>
17:01:30.657: FlashScan license number: <deleted>
17:01:30.704: Disconnecting ...
17:01:31.111: CAN-VPW Bridge Deactived
17:01:31.126: Disconnected
17:01:31.798: Scanning for EFILive FlashScan V2 USB
17:01:34.392: Scanning for EFILive FlashScan V2 HAPI
17:01:34.642: Interface firmware version: 2.6.5
17:01:34.673: CAN-VPW Bridge Actived
17:01:34.736: Current protocol set to: "SAE J1850 VPW"
17:01:35.923: Current protocol: "SAE J1850 VPW"
17:01:36.001: Interface firmware model: FSV2
17:01:36.048: Interface firmware version: 2.6.5
17:01:36.079: Interface firmware date: Oct 28, 2008
17:01:36.126: FlashScan serial number: <deleted>
17:01:36.173: FlashScan license number: <deleted>
17:01:36.376: Getting status...
17:01:36.439: Status: OK.
17:01:37.626: Bootloader version: 98LS1v1.2R (04BC-8A97)
17:01:37.626: Preparing PCM for reading flash...
17:01:37.689: PCM seed is: $4220
17:01:37.689: Unlock attempt 1 of 4
17:01:37.845: Initializing PCM...
17:01:38.657: Initializing PCM, step 1 of 4
17:01:38.657: Initializing PCM, step 2 of 4
17:01:39.501: Initializing PCM, step 3 of 4
17:01:39.501: Initializing PCM, step 4 of 4
17:01:39.829: Disconnecting ...
17:01:40.517: CAN-VPW Bridge Deactived
17:01:40.532: Disconnected
17:01:45.082: Done!

Any ideas on how to get past the error?

ChipsByAl
January 11th, 2009, 12:34 PM
Have you been able to connect and scan yet?
Al

GMPX
January 11th, 2009, 12:40 PM
I think the error response you are seeing is due to the PCM having a flash memory error. Try checking DTC's in the scantool to confirm, if there is a memory fault it will show up in the DTC list.

Cheers,
Ross

wait4me
January 11th, 2009, 02:35 PM
Are you sure They didnt lock the ecm?

Did they say they where able to make changes to the computer?

If they locked it, You just need to know the key.

Also, make sure they delete the columnlock in the vats section it will cause a no fueling.

GMPX
January 11th, 2009, 04:15 PM
I checked up for you, Error $99 is a corrupted controller, sorry to say but generally they are junk once this happens. Just double check the DTC's (look for P0601), if it is set you better let the company that programmed the PCM know.
When that DTC is set the engine will not run and the PCM cannot be read or programmed.

Cheers,
Ross

Godwin1245
January 12th, 2009, 10:49 AM
Thanks all for the quick replies. I have been able to scan the PCM and it's not locked. GMPX's reply has it. I have two codes in the PCM. P1336 and the P0601 GMPX mentioned. That would explain it, a fried PCM. I guess I have some complaining to do.

If there is a bright side to this, I've had enough of this 98 PCM. Time to convert to the 411.

As others have said on the forum, you are the best. Thanks to everyone for your help.

Mark

GMPX
January 12th, 2009, 12:28 PM
I put in a lot of hours trying to find a way to reset that DTC once set, I don't think it can be done. There is lots of those dead 98 ECM's out there, which also means a new one demands a premium price.
We worked pretty hard here to make sure EFILive didn't cause that DTC to get set on a reflash, I hope Street and Performance aren't using our software.

Cheers,
Ross

Godwin1245
January 25th, 2009, 07:14 AM
:cheers: This is just a follow up for future searches. I got the 98 PCM back from Street and Performance. They said the fuel management section of the flash did not take for some reason. They re-flashed it and sent it back. I just turned the key and now hear the sweet rumble again. All is fine now.

I have checked the PCM and there are no DTCs and I have also been able to take a snap shot of the OS. I hope that's the last P0601 I ever see. Thanks to all for your help.

Mark

GMPX
January 26th, 2009, 12:25 PM
Mark, good to hear it's running again, you (they) got lucky, usually once that DTC is set the ECM becomes a door stop.

Cheers,
Ross