-
Disconnect FlashScan.
When EFILive_Explorer is running, double click on the EFIlive_Hapi (EFILive Control Panel) in the task bar's system tray.
Select the Connections->Settings page. Make sure FlashScan is selected and AutoCal is not.
Select the Trace->settings page and check the Enable diagnostic tracing check box. Click [Apply].
Go back to the trace page.
Click [Clear].
Connect FlashScan.
Click [Refresh (F5)] on the Firmware tab page of EFILive_Explorer.
Go back to the Trace page in EFILive_Hapi and click on Save. Save the trace file and post it in this thread as an attachment (or just email it to me).
Note: Saving the trace file saves more data than is displayed on the screen.
Regards
Paul
-
Going back to basics, make sure that Windows can see your FlashScan device.
With FlashScan connected, right click on My Computer, select Properties.
Goto Hardware->Device Manager->Universal Serial Bus Controllers. Locate EFILive FlashScan V2, right click on it and select Properties. Make sure it says "This device is working properly" in the device status.
Regards
Paul
-
1 Attachment(s)
This is the data that should be captured by the EFILive_Hapi trace when FlashScan is in deadpoll.
Regards
Paul
-
1 Attachment(s)
-
Paul,
I sent a trace file to support earlier tonight.
In Device Manager EFILive FlashScan V2 is working properly.
-
1 Attachment(s)
Here's a new trace per your email.
-
Unfortunately, as indicated in the trace file both of those FlashScan's are unresponsive. They will need to be returned to EFILive to be reprogrammed/recovered.
I do not know yet, why that happened. If you can offer any further info on the process that you followed prior to the FlashScan unit becoming unresponsive it may help me track down the cause and hopefully prevent it from happening to others.
Particularly, what firmware version was in the FlashScan unit prior to the failed boot block update attempt?
I just presumed it was 2.05.15(0326), but did either of you have an earlier firmware version in FlashScan?
Regards
Paul
-
I was on 2.05.15(0326) and started at step 5 of the Beta Release document and got to item 6 when the error message popped up.
Where do I have to send the V2 to be reprogrammed/recovered?
-
ok i have been using the march 4th update since it was released, then this morning updated to the march 26th update which went threw with no problems, did a quick log just to make sure all was well which it was so i then went to update to the new 0407 bootblock which is where the problem happened.
After i return from melbourne i will send you my V2 for repair and also for you to repair the usb inlet power problems that we discussed via email a few weeks ago.
-
ok, for now it looks like i have been able to borrow a spare V1 from Oztrack to be able to log with while down there, so a huge thanks to Blacky for helping me fix this problem and also a huge thanks to Oztrack for letting me borrow 1 of his units.
As soon as we return from Melbourne i will have it sent to you blacky for repair.
