Repeatable Bin Verification Failure after Upload to AutoProm

[toliphint]

Have searched and can’t find others experiencing exactly this.
TProRT v5 (Rel .8144) is open and emulation hardware is initialized. Then if open a known good Bin and upload it to the AutoProm, upload is successful, but it fails verification. If reinitialize the emulation hardware and retry, upload is again OK but verify again fails. Ditto if continue to repeat above process.
But if exit TP and reopen it with same Bin opened by TPro at initial loading, verification is OK. Have not touched any cables or anything. Win 7 with USB 2.0. Thanks for any ideas I can chase?

[Mangus]

What does this part mean, exactly:

But if exit TP and reopen it with same Bin opened by TPro at initial loading, verification is OK.

Is it succeeding with a bin different from the one where verification was previously failing?

I've seen this with the AutoProm recently, and it turned out to be a bad NVRAM module in the AutoProm. In that case, however, all verification attempts failed.

[toliphint]

What does this part mean, exactly:

But if exit TP and reopen it with same Bin opened by TPro at initial loading, verification is OK.

Is it succeeding with a bin different from the one where verification was previously failing?

I've seen this with the AutoProm recently, and it turned out to be a bad NVRAM module in the AutoProm. In that case, however, all verification attempts failed.

Sorry I wasn't clear. What I meant was that rather than opening a bin after TPro loads, I use the bin that TPro opened and it uploads OK and verifies OK. But if open TPro and the open another bin, it uploads OK, but repeatedly does not verify. Will only verify if close TPro and reopen it, changing nothing. The only thing that is different is that TRPro opened the bn, because it was the last one open at TrPro exit, rather than me opening it.
Hope that is clearer.

[Mangus]

So, when you launch TunerPro, bin A is loaded, and successfully verifies. When you manually load bin B, verification fails. I presume manually loading bin A results in a successful verify? And that opening bin B, closing TunerPro, and re-opening TunerPro such that bin B is reloaded automatically, still fails to verify?

Bin A and B are both intended for the same XDF, and are identical in file size?

If so, this sounds like an NVRAM failure.

[toliphint]

So, when you launch TunerPro, bin A is loaded, and successfully verifies. When you manually load bin B, verification fails. I presume manually loading bin A results in a successful verify? And that opening bin B, closing TunerPro, and re-opening TunerPro such that bin B is reloaded automatically, still fails to verify?

Bin A and B are both intended for the same XDF, and are identical in file size?

If so, this sounds like an NVRAM failure.

Using your nomenclature:
- Open TP and Bin A is opened by TP
- Bin A will upload OK and verify OK

But with same XDF and ADX and Bin A & B both being $8D
- Open TP and Bin A is opened by TP
- Open Bin B
- Bin B will upload OK but will not verify

Can swap Bin A and B in the above scheme and the same thing happens, so it is not the Bin. And there are no other variables in the equation other than when and how the Bin is opened.

Hope this makes sense.

And when you say it’s NVRAM – does that mean the AutoProm is toast? If so, don’t understand why it works one way and not the other because the AutoProm does not know which bin has been opened. All it knows is that a Bin is being uploaded and verified. Right?

[Mangus]

If swapping A & B in your steps above yields the same results (namely that the bin auto-opened by TunerPro verifies successfully, regardless of what bin it is), then it sounds like a bug.

Can you please email me the XDF and bins A and B in this discussion?

Thanks.

-Mark

[toliphint]

If swapping A & B in your steps above yields the same results (namely that the bin auto-opened by TunerPro verifies successfully, regardless of what bin it is), then it sounds like a bug.

Can you please email me the XDF and bins A and B in this discussion?

Thanks.

-Mark

Mark --
It might not be a software bug, but there is definitely some strange behavior. Went out today to do some testing and provide the files you requested. Ran through more tests to absolutely ensure that the problem reported could again be duplicated without fail. But it could not despite doing it for the past 3-4 days. WTH!
So, fiddled around with the USB connection at the computer and could move it around slightly (not a real tight fit and was the same with several cables). Various cable positioning would cause random upload and verify failures. Was the same for both USB ports. But the interesting thing is that when a Bin uploaded to the AutoProm OK, at times it would not verify – and this was without touching anything but the mouse to click the upload and verify icons. The cable was not moved!
This seems really strange. How can the USB cable be positioned so as to allow a successful upload, but then not allow a verify? Makes no sense. Any ideas? Thanks.

[Mangus]

Noisy power? Bad USB cable? Does having the key on or off change the behavior?

I don't know. Doesn't sound like a software issue, though.

[toliphint]

Noisy power? Bad USB cable? Does having the key on or off change the behavior?

I don't know. Doesn't sound like a software issue, though.

Solved -- Plugged in AutoProm and installed FTDI driver 2.08.14 as referenced in this post ( http://www.gearhead-efi.com/Fuel-Inject ... rkie/page2). Problem solved and everything stable as it should be. Previous version of driver was 2.8.2.0.