COS3 bootblock error 12212156

[bigblock69]

A little background, its a 98 camaro with a 0411 swap. I just finished the swap and did a full flash with a 12212156 with the fuel segment swap. Started the car up and did the CASE relearn and checked for codes, everything looked good so proceeded to do a full flash of the 02020003 and i keep getting a bootblock error. I also tried COS5 and got the same error, but after the error a can go back and do a full flash of the 12212156 file and it works fine.
I also updated 7, 8, flash scan bootblock and firmware.

[joecar]

After doing full flash of 02020003 did you do cal flash from the 12212156 file...?

( the full flash you did of 02020003 writes an un-populated file into the PCM, i.e. all the tables/parameters are empty )


The steps are as follows:
- full flash 02020003,
- cal flash from 12212156,
- read COS file back from PCM,
- edit COS file to correct B3647 and OOR cells and save COS file,
- cal flash saved COS file.

[bigblock69]

After I flashed the 02020003 it would pop up with flash failed. Or is that normal untill I do a cal flash.

[joecar]

No, "flash failed" is an error...

can you post the log text that appears during flashing.

[bigblock69]

19:37:37.531: Scanning for EFILive FlashScan V2 USB
19:37:37.546: Autodetect interface ...
19:37:39.781: Interface not detected
19:37:40.734: Scanning for EFILive FlashScan V2 HAPI
19:37:40.750: Autodetect interface ...
19:37:41.031: Interface firmware version: 2.7.45
19:37:41.031: Connection to [FSV2] interface is OK
19:37:41.250: USB driver version: 2.8.40
19:37:41.250: USB library version: 3.2.7
19:37:41.281: Interface firmware model: FSV2
19:37:41.296: Interface firmware model: FSV2
19:37:41.312: Interface firmware version: 2.7.45
19:37:41.343: Interface firmware date: Jun 08, 2013
19:37:41.359: FlashScan serial number: 003816159156
19:37:41.390: FlashScan license number: 003816159156
19:37:41.421: Disconnecting ...
19:37:41.828: CAN-VPW Bridge Deactivated
19:37:41.828: Disconnected
19:37:42.750: Scanning for EFILive FlashScan V2 USB
19:37:42.765: Autodetect interface ...
19:37:44.937: Interface not detected
19:37:45.890: Scanning for EFILive FlashScan V2 HAPI
19:37:45.906: Autodetect interface ...
19:37:46.187: Interface firmware version: 2.7.45
19:37:46.187: Connection to [FSV2] interface is OK
19:37:46.203: CAN-VPW Bridge Activated
19:37:46.281: Current protocol set to: "SAE J1850 VPW"
19:37:46.281: Autodetect PCM...
19:37:46.343: Connection to PCM is OK
19:37:46.359: Current protocol: "SAE J1850 VPW"
19:37:46.578: USB driver version: 2.8.40
19:37:46.593: USB library version: 3.2.7
19:37:46.609: Interface firmware model: FSV2
19:37:46.625: Interface firmware model: FSV2
19:37:46.656: Interface firmware version: 2.7.45
19:37:46.671: Interface firmware date: Jun 08, 2013
19:37:46.703: FlashScan serial number: 003816159156
19:37:46.718: FlashScan license number: 003816159156
19:37:47.031: Getting status...
19:37:47.062: Status: OK.
19:37:47.906: Bootloader version: PCM32v1.9F (080A-5B97)
19:37:47.906: Preparing PCM for reflash...
19:37:47.953: PCM seed is: $7C32
19:37:47.953: Unlock attempt 1 of 1
19:37:48.093: Initializing PCM...
19:37:48.859: Initializing PCM, step 1 of 4
19:37:48.859: Initializing PCM, step 2 of 4
19:37:49.625: Initializing PCM, step 3 of 4
19:37:51.156: Initializing PCM, step 4 of 4
19:37:51.593: Initializing bootloader...
19:37:51.875: Initializing bootloader, step 1 of 5
19:37:52.281: Initializing bootloader, step 2 of 5
19:37:52.671: Initializing bootloader, step 3 of 5
19:37:53.062: Initializing bootloader, step 4 of 5
19:37:53.453: Initializing bootloader, step 5 of 5
19:37:53.953: PCM ready for reflashing.
19:37:53.953: Request VIN...
19:37:54.015: VIN: 00000000000000000
19:37:54.750: Request serial number...
19:37:54.828: Serial number: 2EB3AEGW2171
19:37:55.796: Request hardware number...
19:37:55.812: Hardware: 9386530
19:37:56.312: Request GM CASE[1]...
19:37:56.328: GM CASE[1]: -2145681428
19:37:56.453: Request GM CASE[2]...
19:37:56.468: GM CASE[2]: -2147385347
19:37:57.375: Intel AB28F400B - 512KB
19:37:58.203: Erasing PCM flash memory... (please wait up to 120 seconds)
19:37:58.218: Waiting 1 of a possible 120...
19:37:59.218: Waiting 2 of a possible 120...
19:38:00.328: Waiting 3 of a possible 120...
19:38:00.703: PCM flash memory erased OK
19:38:00.937: Reflashing PCM's memory...
19:41:07.515: Total time: 03:06
19:41:07.515: Data compression achieved: 3.2%
19:41:07.953: Unknown reply from boot loader: $FE.
19:41:07.968: PCM is in an unknown state.
19:41:10.078: Clear emisison related DTCs...
19:41:11.125: Autodetect interface ...
19:41:11.390: Interface firmware version: 2.7.45
19:41:11.390: Connection to [FSV2] interface is OK
19:41:11.406: Autodetect PCM...
19:41:11.437: Connection to PCM is OK
19:41:11.968: Clear DTCs for all modules...
19:41:13.015: Autodetect interface ...
19:41:13.281: Interface firmware version: 2.7.45
19:41:13.281: Connection to [FSV2] interface is OK
19:41:13.296: Autodetect PCM...
19:41:13.328: Connection to PCM is OK
19:41:14.140: Disconnecting ...
19:41:15.078: CAN-VPW Bridge Deactivated
19:41:15.078: Disconnected
19:41:15.562: Reflash failed.
19:41:18.625: Done!

[joecar]

I notified Tech Support.

[bigblock69]

Ok thank you for taking time to help greatly appreciated.

[joecar]

Also, can you post the COS file that you were flashing.

[Blacky]

A little background, its a 98 camaro with a 0411 swap. I just finished the swap and did a full flash with a 12212156 with the fuel segment swap. Started the car up and did the CASE relearn and checked for codes, everything looked good so proceeded to do a full flash of the 02020003 and i keep getting a bootblock error. I also tried COS5 and got the same error, but after the error a can go back and do a full flash of the 12212156 file and it works fine.
I also updated 7, 8, flash scan bootblock and firmware.

After flashing a custom OS the PCM will be left in an "error state" (i.e. what we call dead-poll). That is because a custom OS file does not contain any calibrations and the PCM cannot operate correctly without any calibrations. After the initial custom OS full-flash, you need to perform a cal-flash from a file that contains a valid calibration. I.e. follow the steps Joe posted earlier.

I'm not sure why the error is being displayed to the end user, but it is expected and normal for that to occur "behind the scenes".

Regards
Paul

[joecar]

. . .
19:41:07.953: Unknown reply from boot loader: $FE.
19:41:07.968: PCM is in an unknown state.
. . .
Ok, understood, these are expected/ok then.

[Blacky]

Ok, understood, these are expected/ok then.

Not really "expected/ok".

The $FE reply code is an internal code from the boot loader (running in the PCM) to the EFILive software telling the software that the check sum in the PCM is incorrect. When loading a COS operating system the check sum is deliberately left incorrect to prevent any attempt to operate the vehicle until a valid calibration is flashed. So yes, it is expected but no it should not be displayed to the user as an error. It should be handled silently by the software and a message such as "You should now program the calibrations" should be displayed to the user instead.

I'm, working on fixing it for the next update.

Regards
Paul

[joecar]

Not really "expected/ok".

The $FE reply code is an internal code from the boot loader (running in the PCM) to the EFILive software telling the software that the check sum in the PCM is incorrect. When loading a COS operating system the check sum is deliberately left incorrect to prevent any attempt to operate the vehicle until a valid calibration is flashed. So yes, it is expected but no it should not be displayed to the user as an error. It should be handled silently by the software and a message such as "You should now program the calibrations" should be displayed to the user instead.

I'm, working on fixing it for the next update.

Regards
PaulPaul, thanks for the clarification.

[Hambone]

So does that mean the COS actually flashed in ok? I've gotten that same error, but it HAS to be something new, or else everyone trying to flash a COS would get it, right? I tried and tried, got it every time. Went back to my original OS, then started a thread looking for help. You're saying a cal flash should work after this, even though it indicates a failure?

[joecar]

So does that mean the COS actually flashed in ok? I've gotten that same error, but it HAS to be something new, or else everyone trying to flash a COS would get it, right? I tried and tried, got it every time. Went back to my original OS, then started a thread looking for help. You're saying a cal flash should work after this, even though it indicates a failure?Are you flashing into a 512KB PCM (part number '0411)...?

[Hambone]

It definitely is a 512k PCM, not certain if its a 411 or not. Its an LS1B from a 2000 Sierra. I did make sure EFI has permissions in the V7.5 folder too. I keep seeing that as a solution for similar problems.

[Blacky]

So does that mean the COS actually flashed in ok?
Yes

I've gotten that same error, but it HAS to be something new, or else everyone trying to flash a COS would get it, right?
Yes it was accidentally introduced when we tightened up error detection in some other areas. We get the same "error message" here on our test systems.

You're saying a cal flash should work after this, even though it indicates a failure?
Yes.

It is fixed in the next update (V7.5.7 build 248).

Regards
Paul

[Hambone]

Well, either running as an Administrator, or changing permissions did the trick. I still got the error message, but it didn't say the flash failed this time. I put a cal on top of that, and it loaded. Read the PCM after that, and it showed the Custom tables, so I am gonna say it worked! Next step is now the hard part. I didn't see in the guides that it was critical to A: run as an admin, and B: be sure to specifically grant permissions to that one folder.

[joecar]

Yes

Yes it was accidentally introduced when we tightened up error detection in some other areas. We get the same "error message" here on our test systems.

Yes.

It is fixed in the next update (V7.5.7 build 248).

Regards
PaulThanks Paul.

[Blacky]

I didn't see in the guides that it was critical to A: run as an admin, and B: be sure to specifically grant permissions to that one folder.

The "Admin" issue is caused by the "User Access Control" (UAC) security changes Microsoft made to Windows 7. Previously (in Windows XP and earlier) applications could create/write files in the "Program Files" folder without requiring elevated priviliges. But with Win7 and later operating systems, only Admin privileged accounts can write to the "Program Files" folder.

Older versions of EFILive V7 still have legacy code that, during an LS1 full flash, tries to save the controller's seed/key information in a file called PCMLocks.ini in the "Program Files" folder. Later version of EFILive V7 store that file in "My Documents".
The seed/key is saved in that file in case something goes wrong with the full-flash and the controller gets accidentally locked with a seed/key other than what was commanded. We can always recover the seed/key from the file in such cases.

Regards
Paul