PDA

View Full Version : Cannot connect to lb7 ecm but can tcm



blewgrassmotorsports
February 11th, 2011, 04:04 AM
I have tried on several ocasions to try and read the computer on an 03 lb7 i get the same response everytime. i have had no trouble on my 03 or the other trucks i have programmed. i have tried alt keys and making sure everything else on the truck is unpugged. like i said it reads the tcm fine. this is what it says to me.

08:31:24.312: Scanning for EFILive FlashScan V2 USB
08:31:24.328: Autodetect interface ...
08:31:26.156: Interface not detected
08:31:26.828: Scanning for EFILive FlashScan V2 HAPI
08:31:26.843: Autodetect interface ...
08:31:27.031: Interface firmware version: 2.6.12
08:31:27.031: Connection to [FSV2] interface is OK
08:31:27.062: Interface firmware model: FSV2
08:31:27.078: Interface firmware version: 2.6.12
08:31:27.109: Interface firmware date: Jun 07, 2009
08:31:27.125: FlashScan serial number: 003798697541
08:31:27.140: FlashScan license number: 003798697541
08:31:27.171: Disconnecting ...
08:31:27.562: CAN-VPW Bridge Deactivated
08:31:27.562: Disconnected
08:31:28.250: Scanning for EFILive FlashScan V2 USB
08:31:28.265: Autodetect interface ...
08:31:30.093: Interface not detected
08:31:30.765: Scanning for EFILive FlashScan V2 HAPI
08:31:30.781: Autodetect interface ...
08:31:30.968: Interface firmware version: 2.6.12
08:31:30.968: Connection to [FSV2] interface is OK
08:31:30.984: CAN-VPW Bridge Activated
08:31:31.015: Current protocol set to: "SAE J1850 VPW"
08:31:31.015: Autodetect PCM...
08:31:31.046: Connection to PCM is OK
08:31:31.062: Autodetect TCM...
08:31:31.093: Connection to TCM is OK
08:31:31.109: Current protocol: "SAE J1850 VPW"
08:31:31.140: Interface firmware model: FSV2
08:31:31.171: Interface firmware version: 2.6.12
08:31:31.187: Interface firmware date: Jun 07, 2009
08:31:31.203: FlashScan serial number: 003798697541
08:31:31.218: FlashScan license number: 003798697541
08:31:31.343: Getting status...
08:31:31.406: Status: OK.
08:31:32.218: Bootloader version: DLB7_v1.3R (0496-61DA)
08:31:32.218: Preparing ECM for reading flash...
08:31:32.250: ECM seed is: $EFFD
08:31:32.250: Unlock attempt 1 of 1
08:31:32.656: Disconnecting ...
08:31:33.046: CAN-VPW Bridge Deactivated
08:31:33.046: Disconnected
08:31:53.625: Done!
08:32:21.609: Scanning for EFILive FlashScan V2 USB
08:32:21.625: Autodetect interface ...
08:32:23.453: Interface not detected
08:32:24.125: Scanning for EFILive FlashScan V2 HAPI
08:32:24.140: Autodetect interface ...
08:32:24.312: Interface firmware version: 2.6.12
08:32:24.328: Connection to [FSV2] interface is OK
08:32:24.359: Interface firmware model: FSV2
08:32:24.375: Interface firmware version: 2.6.12
08:32:24.390: Interface firmware date: Jun 07, 2009
08:32:24.406: FlashScan serial number: 003798697541
08:32:24.437: FlashScan license number: 003798697541
08:32:24.453: Disconnecting ...
08:32:24.843: CAN-VPW Bridge Deactivated
08:32:24.859: Disconnected
08:32:25.531: Scanning for EFILive FlashScan V2 USB
08:32:25.546: Autodetect interface ...
08:32:27.375: Interface not detected
08:32:28.046: Scanning for EFILive FlashScan V2 HAPI
08:32:28.062: Autodetect interface ...
08:32:28.250: Interface firmware version: 2.6.12
08:32:28.250: Connection to [FSV2] interface is OK
08:32:28.265: CAN-VPW Bridge Activated
08:32:28.281: Current protocol set to: "SAE J1850 VPW"
08:32:28.296: Autodetect PCM...
08:32:28.328: Connection to PCM is OK
08:32:28.328: Autodetect TCM...
08:32:28.375: Connection to TCM is OK
08:32:28.406: Current protocol: "SAE J1850 VPW"
08:32:28.437: Interface firmware model: FSV2
08:32:28.453: Interface firmware version: 2.6.12
08:32:28.468: Interface firmware date: Jun 07, 2009
08:32:28.484: FlashScan serial number: 003798697541
08:32:28.500: FlashScan license number: 003798697541
08:32:28.609: Getting status...
08:32:28.656: Status: OK.
08:32:29.500: Bootloader version: DLB7_v1.3R (0496-61DA)
08:32:29.500: Preparing ECM for reading flash...
08:32:29.531: ECM seed is: $EFFD
08:32:29.531: Unlock attempt 1 of 4
08:32:29.937: Unlock attempt 2 of 4
08:32:30.343: Not ready, waiting 1 second for retry...
08:32:31.609: Not ready, waiting 1 second for retry...
08:32:32.859: Not ready, waiting 1 second for retry...
08:32:34.140: Not ready, waiting 1 second for retry...
08:32:35.421: Not ready, waiting 1 second for retry...
08:32:36.687: Not ready, waiting 1 second for retry...
08:32:37.968: Not ready, waiting 1 second for retry...
08:32:39.250: Not ready, waiting 1 second for retry...
08:32:40.515: Not ready, waiting 1 second for retry...
08:32:41.796: Unlock attempt 3 of 4
08:32:42.203: Unlock attempt 4 of 4
08:32:42.625: Not ready, waiting 1 second for retry...
08:32:43.890: Not ready, waiting 1 second for retry...
08:32:45.156: Not ready, waiting 1 second for retry...
08:32:46.437: Not ready, waiting 1 second for retry...
08:32:47.703: Not ready, waiting 1 second for retry...
08:32:48.984: Not ready, waiting 1 second for retry...
08:32:50.265: Not ready, waiting 1 second for retry...
08:32:51.531: Not ready, waiting 1 second for retry...
08:32:52.812: Not ready, waiting 1 second for retry...
08:32:54.093: Initializing ECM...
08:32:54.906: Initializing ECM, step 1 of 4
08:32:54.906: Initializing ECM, step 2 of 4
08:32:55.750: Initializing ECM, step 3 of 4
08:32:55.750: Initializing ECM, step 4 of 4
08:32:56.046: ECM lock has been re-armed, attempting to unlock ECM again...

08:32:56.078: ECM seed is: $EFFD
08:32:56.078: Unlock attempt 1 of 4
08:32:56.500: Unlock attempt 2 of 4
08:32:56.921: Not ready, waiting 1 second for retry...
08:32:58.187: Not ready, waiting 1 second for retry...
08:32:59.468: Not ready, waiting 1 second for retry...
08:33:00.750: Not ready, waiting 1 second for retry...
08:33:02.031: Not ready, waiting 1 second for retry...
08:33:03.296: Not ready, waiting 1 second for retry...
08:33:04.578: Not ready, waiting 1 second for retry...
08:33:05.859: Not ready, waiting 1 second for retry...
08:33:07.125: Not ready, waiting 1 second for retry...
08:33:08.437: Unlock attempt 3 of 4
08:33:08.859: Unlock attempt 4 of 4
08:33:09.281: Not ready, waiting 1 second for retry...
08:33:10.562: Not ready, waiting 1 second for retry...
08:33:11.812: Not ready, waiting 1 second for retry...
08:33:13.078: Not ready, waiting 1 second for retry...
08:33:14.328: Not ready, waiting 1 second for retry...
08:33:15.609: Not ready, waiting 1 second for retry...
08:33:16.859: Not ready, waiting 1 second for retry...
08:33:18.140: Not ready, waiting 1 second for retry...
08:33:19.421: Not ready, waiting 1 second for retry...
08:33:20.687: Initializing ECM...
08:33:21.500: Initializing ECM, step 1 of 4
08:33:21.500: Initializing ECM, step 2 of 4
08:33:22.328: Initializing ECM, step 3 of 4
08:33:22.328: Initializing ECM, step 4 of 4
08:33:22.625: ECM lock has been re-armed, attempting to unlock ECM again...

08:33:22.781: Initializing bootloader...
08:33:22.968: Error: Failed. Controller has returned to normal operation, please retry the operation.
08:33:23.218: Initializing bootloader, step 1 of 3
08:33:23.218: Error
08:33:23.218: Disconnecting ...
08:33:23.937: CAN-VPW Bridge Deactivated
08:33:23.937: Disconnected
08:34:30.734: Done!


this also pops up : bootloader Rejected Reason- controller has returned to normal operation please retry the operation

Tordne
February 11th, 2011, 07:35 AM
The first thing I can see is that your firmware and likely software are out of date and unsupported. Please update to the latest versions as described in these knowledgebase articles:
- Software
(http://support.efilive.com/kb_article.php?ref=5404-IJZV-0820)- Firmware (http://support.efilive.com/kb_article.php?ref=7243-SFGL-2949)

Also ensure you are pulig the Radio and Info fuses as these are know to cause problems (interfere on the bus). If you still have issues after the updates please see this knowledgebase article (http://support.efilive.com/kb_article.php?ref=8254-QOGC-9586) and supply the ONE relevant file.

Cheers,

blewgrassmotorsports
February 11th, 2011, 07:57 AM
Andrew i have tried to unplug the fuses and i use alt keys and take high speed off. it wont even read the vin on the ecm the truck was bought without a key and was brought to the dealer and had a new key flashed could this be part of the problem?

blewgrassmotorsports
February 11th, 2011, 07:58 AM
it does read the tcm fine though

Tordne
February 11th, 2011, 08:33 AM
You need to ensure you have updated software and firmware for a couple of reasons before we can investigate further:
1) There is a codependency between software and firmware so it is not unexpected that issues might arise if they are mismatched. The process for updating is listed in my previous post.
2) There is no point us looking for an issue that is being notified to us where the customer is using already obsolete software/firmware. Our code base is constantly evolving so we will only investigate/trace issues on current and supported software/firmware versions.

If after you've updated and you still have issues please see the other link in t he previous posts which describes the debug that we'll need you to send to us for analysis.

Unless the ECM was locked I would expect you to be able to read it, I don't think the key thing is significant in this case.

Cheers,

blewgrassmotorsports
February 11th, 2011, 02:12 PM
hate to be a pain but there has to be something wrong with the process outlined above to update firmware Follow these steps to upgrade the Bootblock and Firmware on your FlashScan V2 or AutoCal device.

Connect your FlashScan V2 or AutoCal device to your PC.
Open the EFILive Scan And Tune application.
Select the F6: Device Settings option in the left-hand pane.
In the bottom right corner of the FlashScan and AutoCal Device Settings screen click on the image that represents the FlashScan V2 or AutoCal device you have.
The EFILive Control Panel application should appear in your system taskbar. The icons appearance will resemble a FlashScan V2 device.
Click on the EFILive Control Panel icon in the taskbasr to open the aplication.
Select the F6: Firmware option in the left-hand pane.
If an updated Bootblock and/or Firmware is available Upgrade buttons will be visable for the available update(s). Note: Always update the Bootblock version first.

blewgrassmotorsports
February 11th, 2011, 02:25 PM
ok after all day trying i believe i have the correct firmware/ bootblocker 2.07.01 bootblocker 2.07.04 firmware ?

Tordne
February 11th, 2011, 03:04 PM
Correct. Those are the latest versions.