Recent upgrade and can't flash anymore!

[onegonewild]

Have tried full flash and here is results I am getting after recent upgrade of V7.5:

10:21:13.943: Scanning for EFILive FlashScan V1 USB
10:21:13.954: Autodetect interface ...
10:21:14.022: Interface firmware version: 1.2.17
10:21:14.024: Connection to [FSP] interface is OK
10:21:14.059: Interface firmware model: FSP
10:21:14.077: Interface firmware model: FSP
10:21:15.298: Disconnecting ...
10:21:15.317: Disconnected
10:21:15.947: Scanning for EFILive FlashScan V1 USB
10:21:15.959: Autodetect interface ...
10:21:16.023: Interface firmware version: 1.2.17
10:21:16.026: Connection to [FSP] interface is OK
10:21:16.027: Current protocol set to: "SAE J1850 VPW"
10:21:16.029: Autodetect PCM...
10:21:17.061: PCM not detected.
10:21:17.100: Interface firmware model: FSP
10:21:17.121: Interface firmware model: FSP
10:21:17.141: Interface firmware version: 1.2.17
10:21:17.161: Interface firmware date: Jan 18, 2005
10:21:17.183: FlashScan serial number: 003480393630
10:21:17.721: Getting status...
10:21:18.274: Status: Calibration missing.
10:21:20.645: Bootloader version: LS1B_v1.7C (08DC-9623)
10:21:20.648: Preparing PCM for reflash...
10:21:22.691: Autodetect interface ...
10:21:22.765: Interface firmware version: 1.2.17
10:21:22.768: Connection to [FSP] interface is OK
10:21:22.770: Autodetect PCM...
10:21:24.806: PCM not detected.
10:21:25.827: PCM may not be secured - did not reply to seed request
10:21:25.829: Initializing PCM...
10:21:25.831: Initializing PCM, step 1 of 4
10:21:25.837: Initializing PCM, step 2 of 4
10:21:25.839: Initializing PCM, step 3 of 4
10:21:25.842: Initializing PCM, step 4 of 4
10:21:30.860: No response from PCM. Retry 1...
10:21:33.008: Autodetect interface ...
10:21:33.081: Interface firmware version: 1.2.17
10:21:33.084: Connection to [FSP] interface is OK
10:21:33.086: Autodetect PCM...
10:21:35.121: PCM not detected.
10:21:36.141: PCM may not be secured - did not reply to seed request
10:21:36.144: Initializing PCM...
10:21:36.146: Initializing PCM, step 1 of 4
10:21:36.152: Initializing PCM, step 2 of 4
10:21:36.154: Initializing PCM, step 3 of 4
10:21:36.156: Initializing PCM, step 4 of 4
10:21:41.174: No response from PCM. Retry 2...
10:21:42.566: PCM is in an unknown state.
10:21:45.005: Disconnecting ...
10:21:45.025: Disconnected
10:21:45.037: Data transfer was interrupted.
10:21:46.311: Done!

Anyone dealt with this before? issue with the upgrade or a coincidence that the pcm is bad now?

[Chevy366]

Did you open S&T (scan and tune) and make sure firmware was upgraded ?
Sometimes software and hardware (firmware) need to be upgraded in conjunction with each other .

[onegonewild]

I'm still using the old V1 FlashScan

[minytrker]

Re-install the update. I had the same thing happen, I just re-installed the update and it fixed it.

[onegonewild]

Procedure to do this without full uninstall/install??

Thanks! Glad someone has seen this

[Chuck CoW]

Yeah... I'm all hosed up too. Re-installing and switching drivers with the utility has made it function, but

it's still screwed up... My scan tool just froze in the middle of a log.... couldn't un-freeze it.

Chuck CoW

[onegonewild]

Just tried full uninstall/reinstall of software and changing drivers to V2.08.14 and still no luck. Hopefully we can get some support with this from a developer or a site admin.....

[onegonewild]

Hmmmmm. Now the pcm is dead but cant move the vehicle from the garage.

Anyone else having the same symptoms???

[joecar]

I pm'd Tech Support.

[joecar]

Just tried full uninstall/reinstall of software and changing drivers to V2.08.14 and still no luck. Hopefully we can get some support with this from a developer or a site admin.....


Hmmmmm. Now the pcm is dead but cant move the vehicle from the garage.

Anyone else having the same symptoms???What were you doing when this happened...?

Disconnect/reconnect battery.

Instead of doing the upgrade, do the manual download/install from the downloads page at www.efilive.com.

Then set the USB driver back to 2.02.04, and try again, do not do a full flash.

[onegonewild]

Was trying to flash the pcm after the new upgrade and a few changes to the current tune file.

Tried battery.......no luck
Manual download.......no luck
Flash only with no full......no luck

Driver V2.02.04 cant be found when trying to install

[onegonewild]

I have now loaded the software on a Virtual Machine running Windows XP. Same exact tests as before on the Windows 7 machine with the same results.

Any help here??

[Blacky]

Have you tried using the V8 software to read/flash the vehicle?
Sorry my mistake, I see you're using a V1 device which won't work with the V8 software.

Regards
Paul

[Blacky]

Driver V2.02.04 cant be found when trying to install

Download the V7 install from our web site and re-install it in the default location.
Don't do the "check for updates".
Use the USB Manager to downgrade the drivers to V2.02.04

Then try again.

Regards
Paul

[onegonewild]

Same issue when changing the driver on the XP side to the V2.02.04. I have downloaded the driver from the downloads page on www.efilive.com to see if that resolves but the error (File not found: C:/Program Files/EFIlive/Drivers/EFIlive/Win-2k/i386/dpinst.exe) pops up when reverting the driver to the older version.

I have only downloaded the version 7 from the main download page and have not tried checking for updates.

[Blacky]

Same issue when changing the driver on the XP side to the V2.02.04. I have downloaded the driver from the downloads page on www.efilive.com to see if that resolves but the error (File not found: C:/Program Files/EFIlive/Drivers/EFIlive/Win-2k/i386/dpinst.exe) pops up when reverting the driver to the older version.

I have only downloaded the version 7 from the main download page and have not tried checking for updates.

My mistake, sorry. The USB Manager program incorrectly tries to locate the dpinst executable in the Win-2k folder. It should be looking in the Win-XP-Vista-7 folder.
I'll post a new version of the USB Manager in a few minutes...

Regards
Paul

[onegonewild]

No rush on your part! I know you are busy with this stuff.

Truck is not my daily driver but am hoping to drive it this weekend.

Thanks for the quick responses!!

[Blacky]

I've updated the USB Manager program, you can download the updated version here, under the Utilities heading
http://www.efilive.com/index.php?option=com_content&view=article&id=48&Itemid=133

Regards
Paul

[onegonewild]

Have used the older version of the driver and still no luck flashing:

18:45:42.257: Scanning for EFILive FlashScan V1 USB
18:45:42.289: Autodetect interface ...
18:45:42.445: Interface firmware version: 40.147.64
18:45:42.445: Connection to [FSP] interface is OK
18:45:42.539: Interface firmware model: FSP
18:45:42.570: Interface firmware model: FSP
18:45:42.617: Interface firmware version: 1.2.17
18:45:42.664: Interface firmware date: Jan 18, 2005
18:45:42.711: FlashScan serial number: 003480393630
18:45:42.757: Disconnecting ...
18:45:42.804: Disconnected
18:45:44.617: Scanning for EFILive FlashScan V1 USB
18:45:44.632: Autodetect interface ...
18:45:44.851: Interface firmware version: 1.2.17
18:45:46.289: Interface firmware version: 138.234.41
18:45:46.289: Connection to [FSP] interface is OK
18:45:46.289: Current protocol set to: "SAE J1850 VPW"
18:45:46.320: Autodetect PCM...
18:45:47.382: PCM not detected.
18:45:47.461: Interface firmware model: FSP
18:45:47.492: Interface firmware model: FSP
18:45:47.539: Interface firmware version: 1.2.17
18:45:47.570: Interface firmware date: Jan 18, 2005
18:45:47.617: FlashScan serial number: 003480393630
18:45:48.179: Getting status...
18:45:48.804: Status: Calibration missing.
18:45:56.273: Bootloader version: LS1B_v1.7C (08DC-9623)
18:45:56.289: Preparing PCM for reflash...
18:45:58.367: Autodetect interface ...
18:45:58.507: Interface firmware version: 1.2.17
18:45:58.523: Connection to [FSP] interface is OK
18:45:58.523: Autodetect PCM...
18:46:00.601: PCM not detected.
18:46:01.648: PCM may not be secured - did not reply to seed request
18:46:01.648: Initializing PCM...
18:46:01.648: Initializing PCM, step 1 of 4
18:46:01.664: Initializing PCM, step 2 of 4
18:46:01.664: Initializing PCM, step 3 of 4
18:46:01.664: Initializing PCM, step 4 of 4
18:46:06.726: No response from PCM. Retry 1...
18:46:08.882: Autodetect interface ...
18:46:09.023: Interface firmware version: 1.2.17
18:46:09.023: Connection to [FSP] interface is OK
18:46:09.039: Autodetect PCM...
18:46:11.086: PCM not detected.
18:46:12.117: PCM may not be secured - did not reply to seed request
18:46:12.117: Initializing PCM...
18:46:12.117: Initializing PCM, step 1 of 4
18:46:12.117: Initializing PCM, step 2 of 4
18:46:12.117: Initializing PCM, step 3 of 4
18:46:12.132: Initializing PCM, step 4 of 4
18:46:17.179: No response from PCM. Retry 2...
18:46:24.851: PCM is in an unknown state.
18:46:27.445: Disconnecting ...
18:46:27.476: Disconnected
18:46:28.757: Data transfer was interrupted.
18:46:30.039: Done!

[Blacky]

Can you please locate the download *.blx file that matches the date/time that you attempted to flash the controller?
The *.blx files are in the folder: \My Documents\EFILive\V7.5\Bug Reports

Please send it to me at paul@efilive.com

Regards
Paul

[driver456]

I'm having problems too, On 2 pcm's!."bootloader rejected,Reason:engine speed not zero,vehicle speed not zero,a flash memeory fault has been detected.............Paul

[Blacky]

I'm having problems too, On 2 pcm's!."bootloader rejected,Reason:engine speed not zero,vehicle speed not zero,a flash memeory fault has been detected.............Paul
We're working on a problem in the V7.5.7.167 and earlier software that could cause those problems.
Don't flash anymore PCMs until update V7.5.7.168 has been released.

Regards
Paul

[joecar]

We're working on a problem in the V7.5.7.167 and earlier software that could cause those problems.
Don't flash anymore PCMs until update V7.5.7.168 has been released.

Regards
PaulPaul, is this for full flashes only, or also for cal only flashes...?

[Blacky]

Paul, is this for full flashes only, or also for cal only flashes...?
All flashes.

There are situations where the V7 editor software does not catch/update changes to the ETC tables which can cause the ECM to permanently fail with P0606.
We're working on fixing it right now, I hope a new release will be up tonight.

Regards
Paul

[driver456]

All flashes.

There are situations where the V7 editor software does not catch/update changes to the ETC tables which can cause the ECM to permanently fail with P0606.
We're working on fixing it right now, I hope a new release will be up tonight.

Regards
Paul

Cool,I'll be waiting :grin: