Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: E40 system reflash fails?

  1. #1
    New Member
    Join Date
    Mar 2010
    Posts
    9

    Default E40 system reflash fails?

    The car is a 240sx with 06 GTO swap. Manual. Ecu was from an automatic 06 GTO. 06 Corvette pedal (not that it matters) either way, the OS is different between the automatic and the manual so i figured i would just swap a stock manual complete tune with the automatic, this is what i get..

    19:38:46.165: Scanning for EFILive FlashScan V2 USB
    19:38:48.659: Scanning for EFILive FlashScan V2 HAPI
    19:38:48.849: Interface firmware version: 2.6.4
    19:38:48.929: Interface firmware model: FSV2
    19:38:48.989: Interface firmware version: 2.6.4
    19:38:49.059: Interface firmware date: Oct 22, 2008
    19:38:49.119: FlashScan serial number: 003610353337
    19:38:49.180: FlashScan license number: 003610353337
    19:38:49.260: Disconnecting ...
    19:38:49.971: CAN-VPW Bridge Deactived
    19:38:50.011: Disconnected
    19:38:50.702: Scanning for EFILive FlashScan V2 USB
    19:38:53.195: Scanning for EFILive FlashScan V2 HAPI
    19:38:53.396: Interface firmware version: 2.6.4
    19:38:53.456: CAN-VPW Bridge Actived
    19:38:53.526: Current protocol set to: "ISO 15765 CAN"
    19:38:57.662: Current protocol: "ISO 15765 CAN"
    19:38:57.742: Interface firmware model: FSV2
    19:38:57.812: Interface firmware version: 2.6.4
    19:38:57.872: Interface firmware date: Oct 22, 2008
    19:38:57.932: FlashScan serial number: 003610353337
    19:38:57.992: FlashScan license number: 003610353337
    19:38:58.132: Getting status...
    19:38:58.243: Status: OK.
    19:38:59.174: Bootloader version: E40_v1.3F (0878-D519)
    19:38:59.214: Preparing ECM for simulated reflash...
    19:38:59.294: ECM seed is: $3A65
    19:38:59.344: Unlock attempt 1 of 4
    19:38:59.504: Initializing ECM...
    19:39:00.806: Initializing ECM, step 1 of 4
    19:39:00.846: Initializing ECM, step 2 of 4
    19:39:02.148: Initializing ECM, step 3 of 4
    19:39:04.672: Initializing ECM, step 4 of 4
    19:39:05.143: Initializing bootloader...
    19:39:05.473: Initializing bootloader, step 1 of 5
    19:39:05.854: Initializing bootloader, step 2 of 5
    19:39:06.244: Initializing bootloader, step 3 of 5
    19:39:06.635: Initializing bootloader, step 4 of 5
    19:39:07.125: Initializing bootloader, step 5 of 5
    19:39:07.666: ECM ready for reflashing.
    19:39:07.806: Request GM operating system...
    19:39:07.866: GM operating system: 12596655
    19:39:08.658: Request serial number...
    19:39:08.788: Serial number: 86M052282NTJ
    19:39:10.260: AMD AM29BL802C - 1Mb
    19:39:10.771: Simulating ECM flash memory erase. (10 seconds to go...)
    19:39:12.032: Simulating ECM flash memory erase. (9 seconds to go...)
    19:39:13.294: Simulating ECM flash memory erase. (8 seconds to go...)
    19:39:14.556: Simulating ECM flash memory erase. (7 seconds to go...)
    19:39:15.818: Simulating ECM flash memory erase. (6 seconds to go...)
    19:39:17.080: Simulating ECM flash memory erase. (5 seconds to go...)
    19:39:18.341: Simulating ECM flash memory erase. (4 seconds to go...)
    19:39:19.603: Simulating ECM flash memory erase. (3 seconds to go...)
    19:39:20.865: Simulating ECM flash memory erase. (2 seconds to go...)
    19:39:22.127: Simulating ECM flash memory erase. (1 seconds to go...)
    19:39:23.168: Note: ECM flash memory has not actually been erased!
    19:39:23.469: Simulating reflash of ECM's memory...
    19:39:24.290: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:24.340: Retrying previous block...
    19:39:25.171: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:25.211: Retrying previous block...
    19:39:26.043: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:26.083: Retrying previous block...
    19:39:26.914: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:26.964: Retrying previous block...
    19:39:27.795: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:27.845: Retrying previous block...
    19:39:28.666: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:28.716: Retrying previous block...
    19:39:29.548: Error: Failed. Controller has returned to normal operation, please retry the operation.
    19:39:29.588: Retrying previous block...
    19:39:29.638: Stopping, please wait...
    19:39:29.688: Total time: 00:06
    19:39:29.728: Data compression achieved: 4.9%
    19:39:29.858: ECM is in an unknown state.
    19:39:32.011: Clear emisison related DTCs...
    19:39:32.091: Clear DTCs for all modules...
    19:39:34.264: Interface firmware version: 2.6.4
    19:39:35.636: Disconnecting ...
    19:39:36.357: CAN-VPW Bridge Deactived
    19:39:36.397: Disconnected
    19:39:36.448: Data transfer was interrupted.
    19:39:38.080: Done!


    Why is this happening? I can just reflash the .bin but not the whole OS. The whole reason i tried reflashing it was because i have 1.5v comming out for the fuel pump trigger wire so i thought maybe VATS was doing all kinds of crazy stuff.

    Any help would be great
    Thanks
    David

  2. #2
    Lifetime Member
    Join Date
    Mar 2006
    Posts
    4,936

    Default

    It is simulating a reflash, not actually performing it...

    First, that software is very old, download the latest version from here: Mar 3 RC5

    After installing both 7.5.6 and 8.1.2, follow the instructions to update you bootblock then the firmware (make sure you do the bootblock FIRST!). To do this, open EFILive Explorer, click the firmware tab, click browse. Browse into the "Boot Block" folder, then select the file "FSBootV2_06_03.efw", press okay. Back in the main EFILive Explorer windows, check the Bootblock checkbox, then press Program.

    Your V2 will sit with a blank screen and 2 orange LEDs flashing back and forth, dont freak out, this is a good sign. Now you need to press Browse again and select the "FSProgV2_06_28.efw" file, deselect the "Bootblock" checkbox and press Program. Should be good to go.

    After that, unplug and re-plug your V2 into the computer then re-open the tune file. Click the BIG red arrow and follow the instructions. Make sure you press Start at this pane, not Test.

    Report back what happens, but that should get you the latest everything and get that manual OS into the ECM. If it fails, try performing the flash with the "Alt Keys" checkbox checked.
    ~Erik~
    2013 Sonic RS Manual - 1.4L I4T E78, tuned, turbo mods, etc.
    2008 TrailBlazer SS 3SS AWD Summit White - LS2 E67/T42, bolt ons, suspension, etc.
    2002 Chevy TrailBlazer LT 4X4 Summit White - 4.2L I6 P10, lifted, wheels, etc.

  3. #3
    New Member
    Join Date
    Mar 2010
    Posts
    9

    Default

    That worked fine. Allthough i still have 1.5v to the fuel pump. Do i need the VATS Patch? if so where is it? I also have these codes:

    P0690
    P1682
    P2123
    P2138

    I have a pedal out of an 06 vette which i thought would work.. aparently it doesnt?

  4. #4
    Lifetime Member
    Join Date
    Mar 2006
    Posts
    4,936

    Default

    Does your Vette pedal have the same 0-5V and 5-0V references as the GTO OS? Im thinking no, if you want to use the Vette pedal you need to full flash an E40 Vette OS in your ECM. I know you cannot use a GTO pedal in a TBSS, you can sit there and mash the pedal all you want and it wont do anything, the ECM will ignore the input as it is different than what it expects. I would just use a Vette OS, check the pinouts but Id imagine they are the close if not identical. The throttle inputs might be reversed however.

    The first code deals with Control Module Power Relay Feedback Circuit High Voltage. The second is Ignition 1 Switch Circuit 22. The third is Accelerator Pedal Position (APP) Sensor 1 Circuit High Voltage and the fourth is Accelerator Pedal Position (APP) Sensor 1-2 Correlation.

    The first two sound like actual wiring issues, might have to trace everything back through. The last two should be taken care of if you use a Vette OS.
    ~Erik~
    2013 Sonic RS Manual - 1.4L I4T E78, tuned, turbo mods, etc.
    2008 TrailBlazer SS 3SS AWD Summit White - LS2 E67/T42, bolt ons, suspension, etc.
    2002 Chevy TrailBlazer LT 4X4 Summit White - 4.2L I6 P10, lifted, wheels, etc.

  5. #5
    New Member
    Join Date
    Mar 2010
    Posts
    9

    Default

    So i got the power codes figured out, but that left me with a APP pedal 1-2 code. So i tried to swap to an 05 corvette full flash and it is telling me that it cannot flash because my bootloader is not compatible.

    any ideas?

  6. #6
    Lifetime Member GMPX's Avatar
    Join Date
    Apr 2003
    Posts
    13,148

    Default

    Bootloader or Bootblock?
    I no longer monitor the forum, please either post your question or create a support ticket.

  7. #7
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Ls240sx,

    If your bootblock is not compatible you have do install both V7.5 and V8.1 from here:

    Quote Originally Posted by ScarabEpic22 View Post
    ...

    First, that software is very old, download the latest version from here: Mar 3 RC5

    ...
    Then, you have to flash in the bootblock 2.6.2 and firmware 2.6.28.

    See attached for more info.
    Attached Files Attached Files
    Last edited by joecar; March 29th, 2010 at 01:37 PM.

  8. #8
    New Member
    Join Date
    Mar 2010
    Posts
    9

    Default

    On my flashscan it says i am using bootblock 2.06.03 and firmware 2.06.28. In EfiLive Conrol panel and explorer it is saying the same thing. So i am guessing it is loaded correctly?

  9. #9
    Lifetime Member
    Join Date
    Mar 2006
    Posts
    4,936

    Default

    Yes, but that is not the most current stuff now Im afraid. Go to the main downloads page on www.efilive.com and download the latest software. There is a new firmware, 2.06.31 now.


    That said, have you tried the full flash again now? What error message are you getting (take a screenshot if you can)?
    Last edited by ScarabEpic22; April 10th, 2010 at 11:55 AM.
    ~Erik~
    2013 Sonic RS Manual - 1.4L I4T E78, tuned, turbo mods, etc.
    2008 TrailBlazer SS 3SS AWD Summit White - LS2 E67/T42, bolt ons, suspension, etc.
    2002 Chevy TrailBlazer LT 4X4 Summit White - 4.2L I6 P10, lifted, wheels, etc.

  10. #10
    New Member
    Join Date
    Mar 2010
    Posts
    9

    Default

    I got the update after i posted that.. here is what the error is..

    The *.tun files boot block number:12577182,
    is not compatible with the ECMS boot block number 12596655

    a full reflash on this controller is only permitted when both boot blocks are compatible

Page 1 of 3 123 LastLast

Similar Threads

  1. Current updates - V2 Fails - What Gives?
    By JR-CRUZN-C5 in forum FlashScan V2
    Replies: 21
    Last Post: May 28th, 2009, 04:29 AM
  2. Not able to reflash
    By duramaxdaddy29 in forum Duramax LB7
    Replies: 12
    Last Post: May 27th, 2008, 10:05 AM
  3. New ECM Reflash
    By Roadrunner in forum Duramax 06 LLY / 06+ LBZ & LMM
    Replies: 4
    Last Post: March 6th, 2008, 02:22 PM
  4. reflash operating system
    By 69camaro5speed in forum Custom Operating Systems
    Replies: 0
    Last Post: September 18th, 2006, 01:13 PM
  5. Logging DMA PIDs on Duramax fails
    By Blacky in forum Diesel
    Replies: 5
    Last Post: April 28th, 2006, 12:19 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •